How to choose a payment gateway in the UAE
If you run a restaurant in the UAE, "which gateway should I use?" is one of the highest-leverage decisions you'll make this year. The wrong one costs you 0.6–1.5% in fees you didn't have to pay, plus 2–4 days of cash flow per month. Here's how to think about it.
What a gateway actually does
A payment gateway sits between your POS and the customer's card or wallet. It tokenises the card, sends the transaction to the acquirer, and tells your POS whether to print a receipt. Three fees apply:
- Gateway fee — usually 0.5–1.5% + a small fixed amount per transaction.
- Acquirer / processor fee — depends on the card brand and the type (domestic vs international, debit vs credit).
- Mobile-wallet fee — Apple Pay, Google Pay, Samsung Pay go through a card network so they're the same as a card, but with different decline rules.
The four questions to ask any gateway
- What's the per-transaction rate for a domestic, consumer, debit card? This is the base case. Everything else is up from here.
- What's the settlement time? T+1 (next day) is normal. T+2 to T+4 is common for newer gateways. T+7 means a week of cash-flow gap you didn't plan for.
- What does the dashboard actually show? Can you reconcile a chargeback against a transaction? Can the cashier void a transaction without calling support?
- Is the integration well-supported in your POS? A "supported" gateway is one where the POS vendor treats it as a first-class citizen — webhook events, idempotent retries, refund flow, partial captures.
The trap: gateways quote headline rates that look low ("0.8%!"), but the real cost is the cross-border markup, the per-transaction fixed fee, the chargeback fees, the monthly minimum, and the settlement delay. Compare the all-in cost on a sample day, not the marketing rate.
The UAE-specific landscape
Three clusters of gateways work well in the UAE:
- International: Stripe, Adyen, Mollie — strong developer experience, good settlement, but a bit pricier on cross-border.
- Regional / MENA: MyFatoorah, Tap, PayTabs — local acquirers, strong Arabic UX, better rates on domestic cards.
- Cash-on-delivery & mobile banking: not gateways per se, but worth integrating alongside — CashU, Payit (FAB), Samsung Wallet.
For a single-venue restaurant, one of each cluster is overkill. For a group operating across the GCC, the regional gateway usually wins on cost, the international wins on developer ergonomics, and a multi-gateway POS lets you pick per transaction.
What "good" looks like at the POS layer
Whatever gateway you pick, your POS should be gateway-agnostic. You should be able to:
- Switch the active gateway per branch without re-training the team.
- Show the customer the same QR-pay flow regardless of the gateway under the hood.
- Reconcile tips, voids and refunds against the gateway's dashboard without exporting a CSV.
- Have a webhook-backed "payment received" event, not a polling loop.
The one thing most people forget
Chargebacks. Every gateway handles them differently, and the difference shows up in your monthly statement. A chargeback fee of AED 50 vs AED 250 is, on a restaurant doing 2 chargebacks a month, AED 400/month. Over a year, that's AED 4,800. Ask about the fee, the dispute flow, and whether the gateway pre-warns you before a chargeback is filed (some do, by email, with a 24-hour response window — that alone is worth switching).