PayTabs Gateway for Magento 2

Key Features

Real Magento payment gateway implementation using service contracts and command pools (authorize, capture, sale, refund, void) wired via di.xml

Cards plus mada local debit support for Saudi shoppers, with Apple Pay enabled through the PayTabs hosted page

PayTabs hosted/iframe payment page so card PAN never touches your server, keeping checkout in PCI-DSS SAQ-A scope

Server-to-server callback (IPN) and customer return URL both signature/token verified before any order state change

Multi-currency MENA settlement (e.g. SAR, AED) configurable per website / store-view scope

Admin configuration under Stores -> Configuration -> Payment Methods, protected by Magento admin ACL with encrypted credential storage

Refunds issued directly from the Magento credit memo screen, posted to PayTabs as online refunds

Order-status mapping (pending, processing, payment review) plus transaction records visible in Sales -> Transactions

Fraud-prevention controls passed through to PayTabs (3-D Secure / OTP flows, AVS where supported)

Configurable specific-country, min/max order total, and sort-order rules like any native Magento payment method

Optional REST/GraphQL checkout compatibility so headless / PWA Studio storefronts can use the method

Structured logging of gateway requests, callbacks and errors to var/log for auditing and dispute resolution

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

PayTabs Gateway for Magento 2 is a build-to-order payment integration for Saudi and UAE merchants who want a trusted regional acquirer wired correctly into their checkout. This is not an instant Adobe Commerce Marketplace download — ECOSIRE builds the module against your PayTabs merchant profile, installs it on your Magento install, and supports it after go-live.

The extension ships as a proper Magento module under app/code/Ecosire/PayTabs, registered with the payment gateway service contracts (Magento\Payment\Gateway). We implement command pools (authorize, capture, sale, refund, void), request/response builders, and a response validator wired through di.xml, so PayTabs behaves like a first-class native method — not a bolted-on redirect hack. The storefront uses PayTabs' hosted/iframe payment page so card PAN data never touches your server, keeping you in PCI-DSS SAQ-A scope.

Customers can pay with international cards, mada local debit, Apple Pay, and alternative MENA methods enabled on your PayTabs account. Server-to-server callbacks and the customer return URL are both verified (signature/payment_token check) before an order transitions, so a closed browser tab never loses a paid order. Multi-currency MENA settlement, configurable per store view / website scope, lets you run SAR and AED storefronts from one Magento instance.

Admin configuration lives under Stores → Configuration → Sales → Payment Methods, gated by admin ACL, with credentials stored in Magento's config (encrypted profile key). Transactions, refunds initiated from the credit memo screen, and webhook events are logged for audit. Built for Magento Open Source and Adobe Commerce 2.4.x (PHP 8.1–8.3), and delivered with install docs, a smoke-test checklist, and a defined support window.

What you get

Custom Magento 2 module (Ecosire/PayTabs) delivered as installable source under app/code or as a Composer package

Remote installation and configuration on your Magento Open Source or Adobe Commerce 2.4.x environment

Connection to your live PayTabs merchant profile (profile ID + server key) with sandbox validation first

Checkout smoke-test pass: card, mada and Apple Pay paths plus a verified refund from a credit memo

Admin and operator documentation covering configuration, refunds and callback troubleshooting

Source code with composer.json, di.xml, ACL and config so your team retains full ownership

Defined post-delivery support window for bug fixes and compatibility questions

Compatibility note covering your PHP, Magento and theme/checkout (Luma or custom/PWA) versions

Who this is for

Saudi e-commerce merchant

Runs a SAR storefront on Magento and needs mada plus Apple Pay at checkout to convert local shoppers who do not use international cards. Wants PayTabs wired in correctly rather than a fragile redirect.

UAE / GCC multi-store operator

Sells across UAE and KSA from one Magento instance and needs PayTabs configured per store-view for SAR and AED settlement, with one team managing refunds from the Magento admin.

Agency or in-house Magento developer

Wants a clean, service-contract-based gateway module they can read, extend and maintain — not an obfuscated marketplace black box — with ECOSIRE handling the PayTabs-specific wiring and edge cases.

How PayTabs Gateway for Magento 2 Compares

Criterion	ECOSIRE	Custom Build	Competitor
Built specifically for your Magento version, theme and currencies	Included	Included	Partial support
mada local debit support out of the box	Included	Partial support	Included
Apple Pay via PayTabs hosted page	Included	Partial support	Included
Installed and configured for you on your store	Included	Not included	Not included
Full readable module source delivered (no black box)	Included	Included	Partial support
Instant self-service download from a marketplace	Not included	Not included	Included
Verified server-to-server callback handling against lost orders	Included	Partial support	Partial support
Direct support from the team that wrote the code	Included	Partial support	Partial support

Frequently Asked Questions about PayTabs Gateway for Magento 2

How long does delivery take, since this is build-to-order?

Typical delivery is around 5 to 10 business days from the point we have your PayTabs sandbox/profile credentials and access details. Standard card, mada and Apple Pay scope lands at the shorter end; custom currency, multi-store or headless/GraphQL checkout requirements extend it. We confirm a firm timeline in writing before starting and validate everything in sandbox before touching your live store.

Do I get ongoing support and updates after install?

Yes. Every build includes a defined post-delivery support window for bug fixes and configuration issues. Because you receive the full module source, your own team can also maintain it. For longer-term coverage — Magento 2.4.x point-release compatibility, PayTabs API changes, or PHP upgrades — we offer an optional ongoing support arrangement. This is not an auto-updating Marketplace listing; updates are delivered by ECOSIRE.

Is this the official PayTabs extension from the Adobe Commerce Marketplace?

No. This is a custom ECOSIRE build that integrates the PayTabs API into your Magento store using Magento's payment gateway service contracts. We are not reselling a Marketplace download. The advantage is that it is fit to your exact Magento version, theme, currencies and checkout (Luma, custom, or headless) and supported by us directly.

Does card data touch my server — what about PCI compliance?

No raw card data passes through your server. We use PayTabs' hosted/iframe payment page, so the PAN is entered on PayTabs-controlled fields. This keeps your store in the lighter PCI-DSS SAQ-A scope. Your final compliance obligations still depend on your overall setup, which we are happy to advise on.

Will it work with Adobe Commerce and a headless / PWA Studio storefront?

Yes for Adobe Commerce — the module targets both Magento Open Source and Adobe Commerce 2.4.x. For headless or PWA Studio, we expose the method over Magento's REST/GraphQL checkout so your frontend can initiate PayTabs payments. Tell us your storefront stack and we scope the GraphQL work into the build.

What do you need from me to start, and what is the price?

The build is a one-time 249 USD for the standard scope. To start we need a PayTabs sandbox profile (and live credentials before go-live), admin/SSH or deployment access to your Magento environment or a staging copy, and your Magento version, PHP version and active currencies. Anything beyond the standard scope is quoted up front before work begins.