# Payment Integration for Saudi Applications: mada, STC Pay, Apple Pay and BNPL
Short answer: A Saudi product that accepts only international card rails will lose
sales. mada is the domestic debit scheme and the default way Saudis pay, Apple Pay leads
consumer preference, and BNPL through Tamara and Tabby is mainstream rather than niche. Your
payment service provider must be SAMA-licensed, and every invoice you issue has to satisfy
ZATCA Phase 2.
---
Why the international-cards-only default fails here
Teams building for Saudi Arabia frequently ship the stack they already know — Stripe-style
card acceptance, Visa and Mastercard, perhaps Apple Pay — and then cannot explain a
conversion rate well below their other markets.
The reason is that mada is the domestic debit network, operated as Saudi Arabia's
national payment scheme. It carries in the order of 8 billion transactions a year across
roughly 1.4 million point-of-sale terminals. For a large share of Saudi consumers it is the
card in their wallet. A checkout that cannot accept it is asking a meaningful portion of the
market to find another card, and many of them will simply leave.
Reported consumer preference puts Apple Pay first at around 36%, mada at about 22%, and STC
Pay near 12%. The shape of that distribution matters more than the precise figures: there
is no single method you can support and call it done.
---
The methods that belong in a Saudi checkout
mada — the domestic debit scheme, and non-negotiable for consumer-facing commerce.
Note that mada cards often carry co-badging with an international scheme, and routing
matters commercially: domestic routing generally carries different economics from routing
the same card internationally. This is worth understanding with your provider rather than
accepting the default.
Apple Pay — leads consumer preference and materially improves mobile conversion. On a
market where the purchase is overwhelmingly happening on a phone, treating it as optional is
a conversion decision disguised as a scoping decision.
STC Pay — a widely used digital wallet, particularly for peer-to-peer and mobile-first
commerce.
Tamara and Tabby — buy-now-pay-later, and mainstream in the Gulf rather than a fringe
option. For higher basket values they frequently change whether the purchase happens at all.
International cards — still required for expatriate and visitor traffic, which in Saudi
Arabia is a substantial segment, not an edge case.
---
SAMA licensing: verify the contracting entity
Payment services in the Kingdom are regulated by the Saudi Central Bank
(SAMA). Your provider must be appropriately licensed.
The practical due diligence step that teams skip: check the SAMA licensed-entities list,
then confirm the exact legal entity named in your contract matches it. A globally
recognised payments brand may contract with you through a regional entity whose licensing
status is a separate question. Verify the entity, not the logo, and do it before signing
rather than during an audit.
---
Every payment produces an invoice, and every invoice meets ZATCA
This is the integration that catches teams who scoped payments and compliance as separate
workstreams.
A consumer transaction generates a Simplified tax invoice, which must be reported to ZATCA
within 24 hours. A B2B transaction generates a Standard tax invoice, which must be cleared
by ZATCA before it reaches the buyer — a synchronous call in your transaction path.
So the sequence is not "take payment, then generate a receipt". For B2B it is "take payment,
clear the invoice with ZATCA, then deliver it", and your error handling has to cover the
case where payment succeeds and clearance does not. Design that path deliberately; it is
the one that produces angry reconciliation work if left to chance.
---
Aggregator or direct: the decision that is hard to reverse
Two broad routes, and the cost of switching later is high enough to be worth thinking about
properly up front.
A single aggregating gateway gives you one integration, one settlement relationship and
one support contact covering mada, cards, wallets and often BNPL. You reach market faster
and carry far less integration surface. You accept their pricing, their uptime, their
routing decisions, and the risk that a method you depend on is one they choose to deprecate.
Direct integrations per method give you control over routing — which matters
commercially, because domestic mada routing and international routing carry different
economics — plus the ability to negotiate each relationship and to fail over between
providers. You pay for that in integration surface, reconciliation complexity, and a
meaningfully larger ongoing maintenance burden.
The honest guidance: start with an aggregator unless payments are core to your product's
economics. For a typical e-commerce or SaaS business, the engineering time saved is worth
more than the basis points. For a high-volume marketplace or a fintech where payment margin
is the margin, direct relationships repay the effort quickly, and the decision deserves a
proper financial model rather than an engineering preference.
What makes this hard to reverse is not the integration — it is the stored payment
credentials, the settlement history and the reconciliation tooling built around one
provider's file formats. Ask early how a provider supports migration away from them; the
quality of that answer is informative.
---
Engineering considerations that are specific to this market
Arabic-first receipts and checkout. The checkout is where an awkward translation costs
the most, because it is where trust is thinnest. RTL layout, Arabic numerals where
appropriate, and correct currency formatting for the riyal are not polish.
Refunds across methods. BNPL refunds, wallet refunds and card refunds behave differently
and settle on different timelines. Model the refund flow per method rather than assuming one
path.
Tokenisation and saved cards. SAMA has pushed the baseline on tokenisation and wallet
readiness. Build for stored credentials properly rather than retrofitting.
Settlement and reconciliation. Multiple methods means multiple settlement files on
different cadences. Reconciliation is a real piece of engineering here, not an afterthought
for finance to handle in a spreadsheet.
---
Frequently asked questions
What payment methods should a Saudi e-commerce app support?
At minimum mada, Apple Pay, and international cards, with STC Pay and BNPL through Tamara
and Tabby for consumer commerce. mada is the domestic debit scheme and omitting it excludes
a large share of Saudi shoppers.
Is mada mandatory for Saudi e-commerce?
Not a legal requirement, but commercially close to one. mada carries around 8 billion
transactions a year across roughly 1.4 million terminals, and a checkout that cannot accept
it is turning away a substantial part of the market.
Does my payment provider need a SAMA licence?
Yes — payment services in Saudi Arabia are regulated by the Saudi Central Bank. Check the
SAMA licensed-entities list and confirm the exact legal entity in your contract is the
licensed one, rather than relying on the provider's brand.
How do Saudi payments interact with ZATCA e-invoicing?
Every transaction produces a tax invoice. Consumer (Simplified) invoices must be reported to
ZATCA within 24 hours; business (Standard) invoices must be cleared by ZATCA before being
given to the buyer, which puts a synchronous call in your B2B transaction path.
---
*Market figures cited are from public reporting as of September 2026 and move quickly.
Verify current SAMA licensing status and provider capability directly before selecting a
payment partner.*