- 01
Market
Saudi Arabia
- 02
Written for
CTO, Head of Digital, Commercial Director
- 03
Decision
Select and integrate a payment gateway for Saudi e-commerce properly
- 04
Languages
EN · AR
The flow
One payment, followed from the checkout to the bank statement
The card form is the visible sliver. Following one payment end to end shows where the engineering actually lives — and why the last node, which no demo ever shows, is where finance decides whether the integration works.
A payment flow in four stages — tokenised hand-off, 3-D Secure authentication, authorisation and capture, settlement and reconciliation — with a branch for refunds and disputes.
- 01
Hand-off and tokenisation
Card details go to the gateway’s hosted fields or page and come back as a token, so your servers never hold what an attacker most wants.
- 02
Authentication where required
3-D Secure challenges the buyer when the rules demand it — an OTP moment your checkout has to survive with its state intact.
- 03
Authorise, then capture
Funds are held, then captured in full or in part as the order actually ships — the split every partial shipment and every refund will lean on later.
- 04
Settlement and reconciliation
Days later the gateway pays out — net of fees, in batches on its own calendar — and a pipeline matches every payout line back to its orders.
Refunds and disputes
Every payment keeps a path backwards: full and partial refunds computed against what was actually captured, and disputes answered with the evidence trail the integration recorded on the way through.
Choosing the gateway
The categories that separate payment gateways once the brochures agree
Every gateway brochure promises the same features, so we assess by category against your operation — and publish no ranking of named vendors, because the right answer depends on your volumes, your bank and your back office, not on a league table.
Scheme coverage where you sell
mada support is the threshold question for a Saudi store, ahead of the international schemes and the wallets your buyers actually carry. The scheme-level engineering has its own page on this site; here it is a selection criterion with no acceptable compromise.
Settlement practices your finance team can live with
How often payouts arrive, in what currency, how fees are netted and how usable the settlement reporting is — differences invisible at signing and felt every closing day thereafter.
Dispute and refund tooling
Where disputes surface, what evidence can be submitted and how, whether partial refunds are first-class operations — the difference between a chargeback being an email thread or a workflow.
The developer surface
A sandbox that behaves like production, webhooks that arrive reliably and can be verified, idempotent operations, and documentation that answers questions rather than raising them — the category that decides how long the integration takes and how often it breaks.
Scope and friction
Keeping card data off your servers and the OTP out of the buyer’s way
Tokenisation is the single highest-return decision in the integration. When card details go straight from the buyer’s browser to the gateway’s hosted fields and your systems only ever see a token, the most sensitive data never touches your infrastructure — which shrinks your PCI assessment surface from an audit of your whole platform to a review of a much smaller integration. Shrinks, not erases: the reduced scope still carries obligations, and any architecture that routes card numbers through your own servers first should be treated as a design error to justify, not a default.
Authentication is where security and conversion meet, and the meeting can be managed. 3-D Secure exists to challenge the buyer when the issuing bank requires it, and a Saudi checkout should expect the challenge often — which makes its handling a design problem, not a compliance checkbox. The state of the cart must survive the redirect or the challenge window; a timeout or a mistyped OTP must return the buyer to a checkout that remembers them, with a way to retry that does not double-charge; and nothing else in the flow should add friction the rules did not ask for. Buyers do not abandon because a challenge exists — they pay through OTP prompts every day. They abandon when the store handles it worse than their banking app does.
The unglamorous half
Reconciliation is where the integration is finally graded
Weeks after launch, finance opens the bank statement and asks the only question that matters operationally: does the money match the orders? A payout is a batch — many orders, minus fees, minus refunds, minus disputes, on the gateway’s calendar rather than yours — and without a reconciliation pipeline, matching it to the order ledger becomes a monthly spreadsheet ritual that quietly absorbs days and still misses things. Partial captures and partial refunds make the arithmetic worse: an order captured twice and refunded once is three money movements against one order line, and a system that recorded only "paid" cannot explain any of them.
So we build reconciliation as part of the integration, not as finance’s problem afterwards. Every money movement — authorisation, capture, refund, fee, dispute, payout line — is recorded against the order it belongs to, settlement files are ingested and matched automatically, and only the exceptions reach a human, with the context to resolve them. The measure of success is quiet: a closing day where the numbers simply agree, and an audit question that is answered by a query rather than an archaeology dig.
Our role
What we integrate at the gateway layer and what stays with your bank
- 01
Selection without a sales agenda
We assess gateways against the categories above for your operation, and we resell none of them — so the recommendation has no commission behind it and no vendor to protect.
- 02
The integration, built for its worst day
Tokenised hand-off, authentication handling, capture and refund semantics, verified webhooks and idempotency — engineered and tested against the failure cases, because a payment system is defined by how it behaves when a step does not succeed.
- 03
Reconciliation your finance team inherits
The order-to-payout pipeline is delivered with the integration and handed to finance with the training to run it — because the integration is not finished when the first payment succeeds; it is finished when the first month closes cleanly.
Merchant accounts, acquiring relationships and commercial terms sit between you, your bank and the gateway; we engineer the layer that connects your store to them so payments, refunds and the closing day all behave.
Common questions
What buyers ask
Which payment gateway is best for a Saudi online store?+
There is no ranking that survives contact with a real operation, which is why this page names categories rather than vendors. The gateway that is right for you is decided by threshold questions first — mada support is non-negotiable for a Saudi store — and then by fit: settlement practices your finance team can work with, dispute and refund tooling that matches your volumes, and a developer surface your integration can rely on. Two merchants with identical storefronts can be right to choose differently because their banks, volumes and back offices differ. Our assessment scores the candidates against your operation, not against each other in the abstract.
Does tokenisation take our store out of PCI DSS scope completely?+
No — it shrinks the scope dramatically, and the difference matters. With hosted fields and tokenisation, card data never touches your servers, so the bulk of the standard’s heaviest requirements stop applying to your infrastructure, and validation typically drops to a much simpler self-assessment. What remains is real: the integrity of the page that loads the hosted fields is still your responsibility — a compromised storefront script can steal card data before it ever reaches the gateway — along with the security of your integration credentials and webhooks. Anyone who tells you tokenisation makes PCI someone else’s problem entirely is selling the setup, not describing it.
Why do our bank payouts never match our order totals, and whose job is fixing that?+
Because a payout is not an order — it is a batch of many orders, netted of fees, refunds and disputes, paid on the gateway’s settlement calendar rather than your sales calendar. The mismatch is structural, and closing it is an engineering job disguised as an accounting chore: every money movement recorded against its order, settlement files ingested and matched automatically, and the genuine exceptions routed to a person with the context to resolve them. If your team is doing this in a spreadsheet each month, the integration was delivered without its second half — the half that decides whether finance trusts the store.
In this cluster
Review your checkout with us
A payments architecture review covering gateway selection criteria, tokenisation scope, the 3-D Secure experience and the reconciliation design — before the contract is signed, when all of it is still cheap to change.
Start the conversation
