E-commerce4 min read
UAE payment gateways compared
Network International, Telr, PayTabs, Checkout.com, Stripe and the BNPL providers, compared on integration model rather than headline rate - plus Jaywan, Aani, wallets, cash on delivery, and the terms worth negotiating before you sign.
Danial AhmedFounder & engineering manager
On this page
Choosing a UAE payment gateway looks like a fee comparison and is actually three separate decisions: who acquires your card transactions, how you integrate (which sets your PCI scope), and which local rails you add beyond cards. Merchants who compare only the headline rate usually discover the other two decisions after go-live, when they are expensive to reverse. Here is the comparison we run on an e-commerce build.
The shortlist
Every provider below is either licensed by the Central Bank of the UAE under the retail payment services regime or partnered with a licensed acquirer. Verify current licence status before contracting — it is a genuine differentiator and it changes.
| Provider | What it is | Integration | Best fit |
|---|---|---|---|
| Network International (N-Genius) | The largest regional acquirer; gateway plus acquiring in one contract | Hosted page, hosted fields, direct API | Established merchants wanting a single UAE contract |
| Telr | Dubai-based PSP, quick onboarding, multi-currency | Hosted page, API, plugins | SMEs and first storefronts |
| PayTabs | Regional PSP with strong GCC coverage | Hosted page, API, plugins | Merchants selling across the GCC |
| Amazon Payment Services | Regional gateway with broad card coverage | Hosted page, API | Mid-market retail |
| Checkout.com | Enterprise processor with granular control and reporting | API-first | High volume, in-house payments engineering |
| Stripe | Global platform, UAE entity, excellent developer tooling | API, hosted checkout | Product-led and subscription businesses |
| Tabby / Tamara / Postpay | Buy-now-pay-later, paid to you upfront | Widget plus checkout method | Larger baskets, where instalments change the decision |
Your integration model sets your PCI scope
This is the decision with the longest tail, and it is technical rather than commercial.
- Hosted payment page (redirect to the provider): PCI DSS SAQ A, the lightest compliance burden. Conversion cost is the redirect, which on mobile is smaller than most merchants assume.
- Hosted fields / iframe: still SAQ A in most configurations, with the card form rendered inside your own checkout. This is the right default for most UAE storefronts.
- Direct API with card data touching your server: SAQ D, annual assessment, network segmentation, quarterly scans. Choose this only with a payments engineer on staff and a reason.
The local rails most comparisons miss
Cards are not the whole picture in the UAE, and three additions materially change conversion or cost.
Jaywan, the domestic card scheme operated by Al Etihad Payments, is being issued by UAE banks at scale and carries domestic processing economics. Ask any acquirer explicitly whether they accept it; some answers are still "on the roadmap".
Aani, the national instant payment platform, supports request-to-pay and account-to-account transfers that settle immediately. For high-value baskets, the cost per transaction can be dramatically lower than card interchange, which makes it worth engineering for even at modest volume.
Apple Pay and Google Pay are not optional in this market. Wallet adoption on iOS in the UAE is high, tokenised payments skip manual card entry and the 3-D Secure one-time password, and the conversion difference on mobile is usually the largest single improvement available at checkout.
Cash on delivery remains a real requirement in several categories, and it is a payment method with an operating cost: courier COD handling fees, cash reconciliation, and a failed-delivery rate that goods-in-transit accounting has to absorb. Price it as a method, not as a convenience.
What to negotiate beyond the headline rate
The merchant discount rate is the number in the proposal; these are the numbers in the contract.
- Settlement period. T+2 to T+7 is the usual UAE range. The difference between them is working capital.
- Rolling reserve. New merchants are frequently held at a percentage of turnover for the first months. Negotiable with trading history.
- FX markup. If you price in AED and your customer's card is issued abroad, someone converts. Know who and at what spread.
- Chargeback and refund fees. Charged per event, sometimes on refunds too.
- Setup and monthly minimums. Often waivable; almost never volunteered.
- BNPL commission. Materially higher than card rates, because the provider carries the credit risk and pays you upfront. Model it as a marketing cost against basket-size uplift, not as a payment fee.
Make 3-D Secure work for you rather than against you
UAE issuers enforce 3-D Secure aggressively, and the one-time password step is where mobile baskets die. The version 2 protocol allows a frictionless flow when the merchant sends enough risk data — device, billing, transaction history — for the issuer to authenticate without challenging the customer.
Most gateways send the minimum by default. Sending the full data set is a configuration and integration task worth doing in week one; the reduction in challenged transactions is usually visible within a fortnight.
How to decide in an afternoon
Write down your monthly volume, average basket, currency mix and whether you need recurring billing. Ask two acquirers for a written rate sheet including settlement period and reserve. Confirm Apple Pay, Google Pay and Jaywan support in writing. Choose hosted fields unless you have a specific reason not to. Then add one BNPL provider and measure basket-size change for sixty days before adding a second — and make sure the widget does not cost you the performance you built, as covered in Core Web Vitals for UAE e-commerce.