Gulf Payment Gateways: Mada, Apple Pay, STC Pay, Tabby & Tamara (2026 Guide)
Running an ecommerce store in Saudi Arabia or the wider Gulf without Mada and Apple Pay is like opening a store in Riyadh that only accepts US dollars. The card is in the customer's wallet — but your checkout refuses it. Cart abandonment is immediate and silent.
This guide covers the five payment rails that actually matter in Saudi Arabia and the GCC in 2026, what each one costs, how long integration realistically takes, and what happens to your conversion rate if you skip any of them.
Why Gulf payments aren't like US/EU payments
In the US, "accept Stripe and move on" is a reasonable default. In the Gulf, it isn't. Three things are structurally different:
- Mada is the domestic debit scheme. Almost every Saudi debit card is Mada-first. International Visa/Mastercard rails work, but they carry higher fees, more declines, and Saudi shoppers often see a "contact your bank" error that never occurs with Mada.
- Apple Pay adoption is extreme. iOS has 75%+ share of mobile in KSA and UAE. A huge share of checkouts happen with a thumb on Face ID. No Apple Pay button = 30–40% friction on mobile.
- BNPL is mainstream, not fringe. Tabby and Tamara aren't "alternative" — they routinely drive 20–35% of GMV on fashion, beauty, and electronics stores.
Build a checkout that ignores these three realities and you will quietly lose more money than any ads budget could ever earn back.
The five rails you need to know
| Gateway | Coverage | Fee range | Integration effort | Why you need it |
|---|---|---|---|---|
Our pick for most Saudi stores We integrate Mada + Apple Pay + STC Pay + Tabby/Tamara in one clean checkout, with ZATCA-compliant invoicing baked in. One contract with us, unified reporting, no checkout juggling. | All 5 rails + more | Bundled | 2–4 weeks | Everything below, done right |
Mada (via HyperPay, Moyasar, PayTabs, Checkout.com) Mandatory for any Saudi store. Debit-first, low decline rate, cheapest per-transaction. Not optional. | KSA (near-universal) | 1.0–2.0% | 1–2 weeks | Captures 60%+ of KSA checkouts |
Apple Pay Effectively mandatory on mobile. Face ID one-tap checkout. Works with Mada and international cards. Requires HTTPS + domain verification. | iOS users across GCC | Same as underlying card | 2–5 days | 30–40% mobile conversion lift |
STC Pay Wallet with huge KSA footprint. Strong with younger shoppers. Integrates via major PSPs or direct. | KSA + regional | 1.5–2.5% | 1 week | 10–20% incremental conversion |
Tabby / Tamara (BNPL) Split-in-4 or pay-later. Pushes AOV up. Merchant pays a higher fee but typically earns it back via bigger baskets. | KSA, UAE, Kuwait, Bahrain | 3–7% | 3–7 days | 20–35% GMV on eligible orders |
What each one actually does
Mada — the backbone of Saudi ecommerce
Mada is the Saudi Payments Network domestic card scheme. Virtually every debit card issued by a Saudi bank is a Mada card (usually co-branded with Visa or Mastercard for international use). Domestically, the Mada rail is used.
Why it matters: Mada fees are lower, authorization rates are higher, and Saudi shoppers recognize the logo and trust it. If your checkout shows "Visa / Mastercard only", you are actively filtering out the majority of Saudi domestic traffic.
How to add it: through a local PSP (HyperPay, Moyasar, PayTabs, Checkout.com's Saudi entity, or Telr). Expect a KYC pack: CR (commercial registration), VAT certificate, bank account, website with T&Cs and refund policy, and a demo of the checkout.
Apple Pay — the mobile conversion multiplier
Apple Pay isn't really a separate gateway — it's a tokenized way to present an existing card (Mada, Visa, Mastercard) to your PSP. The user taps the button, authenticates with Face ID, and the payment goes through.
Why it matters: no card entry form, no OTP juggling, no "my card was declined but I don't know why". On mobile, which is 70%+ of Gulf traffic, the Apple Pay button often doubles mobile conversion versus a manual card form.
Integration is small but strict: domain association file (apple-developer-merchantid-domain-association), merchant ID, and the PSP's JS widget. Budget 2–5 days including Apple's domain verification.
STC Pay — Saudi Arabia's home-grown wallet
STC Pay is a licensed digital wallet from STC (Saudi Telecom). Users fund it from their bank, send money peer-to-peer, and pay merchants online and in-store. It has a very strong brand among younger Saudi shoppers.
Why it matters: for a subset of your customers, STC Pay is the default payment method. They don't even enter a card. Offering it directly (not via card token) captures 10–20% incremental conversion at low incremental cost.
Tabby & Tamara — BNPL without the drama
Both are regulated Saudi fintechs offering "split in 4" (four equal payments, no interest) and "pay later" (30-day) options. They assume the credit risk — you get paid in full upfront, minus the merchant fee.
Why it matters: higher average order value. A SAR 700 abaya becomes "SAR 175 now, then 3 more payments", and conversion lifts significantly on higher-ticket items. For stores selling fashion, beauty, electronics, and home goods, Tabby/Tamara typically drive 20–35% of GMV.
What it costs: 3–7% merchant fee depending on category and volume. Sounds high versus Mada's 1–2%, but the bigger baskets and lower cart abandonment usually net out positive.
The integration timeline, honestly
Most agencies will tell you "we'll integrate payments" and leave it at that. Here's how it actually breaks down on a real project:
| Phase | Work | Duration | |---|---|---| | KYC & contracts | CR, VAT cert, bank docs, PSP applications (Mada via HyperPay/Moyasar, then Tabby, Tamara, STC Pay separately) | 2–4 weeks in parallel with dev | | Checkout dev | Cart, shipping, address, tax, Mada+Apple Pay flow, STC Pay flow, BNPL flow | 2–3 weeks | | ZATCA invoicing | Phase 2 compliant e-invoice generation + signing per order | 1–2 weeks | | Testing | Sandbox transactions per gateway, refund flows, partial captures, 3DS challenges | 1 week | | Go-live | Switch to production credentials, first real transaction monitoring | 1–2 days |
Total: 5–8 weeks for a properly integrated multi-gateway Saudi checkout. Anyone quoting you "2 days for Mada + Apple Pay" is using a pre-built connector — which can be fine for a starter store, but you'll hit limitations fast (subscriptions, marketplaces, B2B workflows).
Common pitfalls that cost real money
We audit Saudi stores regularly and these five issues show up again and again:
- Cards-only checkout. Visa/Mastercard input form, no Mada button, no Apple Pay button. Mobile conversion stuck at 1.2% when it should be 3.5%+.
- Apple Pay only on the cart page, not on product detail pages. The express checkout Apple Pay button on PDP can lift conversion 15–25% on its own.
- BNPL installment amounts not shown until checkout. Display "or 4 payments of SAR X with Tabby" on the product page. The shopper decides to buy there, not at checkout.
- No ZATCA-compliant invoice emitted after purchase. Saudi B2B customers won't buy from a store that can't give them a proper tax invoice. See our ZATCA Phase 2 checklist for the compliant setup.
- One PSP for everything, priced badly. The "all-in-one" PSP quote often has hidden cross-border fees. Splitting Mada via a local PSP and international cards via a separate route usually saves 0.3–0.8% on blended fees.
What we do on CloudTopia projects
For Gulf ecommerce clients we default to the following stack, because it's the combination that has the fewest failure modes:
- Mada + Visa/Mastercard + Apple Pay via a single local PSP (HyperPay or Moyasar typically)
- STC Pay as a named button next to Apple Pay on mobile
- Tabby and Tamara side by side on product pages and cart, with installment pricing shown
- ZATCA Phase 2 e-invoice generated per order, emailed and stored
- Unified reporting in the admin dashboard — no logging into 4 separate portals
This is included in our ecommerce builds starting at SAR 15,000. We also retrofit this stack onto existing Salla, Zid, Shopify, and WooCommerce stores when the out-of-the-box integration doesn't go far enough.
How to choose between PSPs
The big local players — HyperPay, Moyasar, PayTabs, Checkout.com, Telr — all support Mada + Apple Pay + international cards. The differences are in the details:
- Moyasar — developer-friendly API, fast onboarding, strong for small and mid stores.
- HyperPay — enterprise-grade, deep integrations, strong for marketplaces and subscriptions.
- PayTabs — regional (works across GCC), good for stores selling in multiple Gulf countries.
- Checkout.com — global infrastructure, best if you also sell to EU/UK; requires more onboarding effort.
- Telr — strong UAE presence, decent KSA coverage, often a pragmatic regional choice.
We've worked with all five. For most Saudi SMBs we recommend Moyasar for the cleanest developer experience, then HyperPay when volume justifies the onboarding overhead.
Common questions about Gulf payment gateways
Legally, no — you can run a Saudi store without Mada and sell via Visa/Mastercard only. Practically, yes — you'll lose the majority of Saudi domestic traffic. Every serious Saudi merchant integrates Mada.
The honest summary
For a Saudi store in 2026, a payment stack without Mada + Apple Pay is not a payment stack — it's a leak. STC Pay and a BNPL provider (Tabby or Tamara) close the remaining gaps. Each one is a separate merchant agreement with its own KYC timeline; bundle them into a single integration sprint rather than bolting them on one at a time after launch.
The good news: once the stack is in place, it's stable. These gateways don't change every quarter. You build it once, keep the ZATCA invoicing side up to date, and focus on what actually moves the needle — product, traffic, and fulfillment.
