What it is
mada is a card scheme, not a wallet and not a payment provider. It is the national payment network of Saudi Arabia, owned by the Saudi Central Bank, and it sits behind the debit cards issued by Saudi banks. When a customer pays with a mada card online or in store, the transaction is authorised and cleared over that network and settled to the merchant by an acquirer. You do not join mada directly. You reach it through a licensed acquirer or a PSP, and it appears in your checkout as one card option among several. mada also supports wallet provisioning, so a mada card can sit inside Apple Pay, Google Pay and mada Pay.
- mada is the national payment network of Saudi Arabia, owned by the Saudi Central Bank.
- It is a card scheme rather than a wallet or a payment provider.
- Merchants reach it through a licensed acquirer or PSP, not by joining directly.
- mada cards can also be provisioned into Apple Pay, Google Pay and mada Pay.
Where it is used
mada operates in Saudi Arabia and settles in Saudi riyals. It is a major domestic debit rail to evaluate for Saudi buyers, but merchants should verify availability through a Saudi-licensed acquirer or PSP rather than treating acceptance as automatic. Confirm entity requirements, local acquiring route, online versus in-store support, settlement currency, payout timing, refunds, disputes, authentication, reconciliation, and pricing before showing mada at checkout. There is no simple direct cross-border version for foreign merchants to join without an approved local route.
- mada is a Saudi domestic debit rail and should be evaluated for Saudi consumer checkout.
- Foreign merchants generally need an approved acquirer or PSP route rather than direct scheme access.
- Confirm online, in-store, authentication, refund, dispute, and reconciliation workflows.
- Ask about Saudi riyal settlement, payout timing, reserves, and entity requirements.
- Do not assume mada is available for your account until the provider approves it.
Which businesses it suits
mada suits essentially every business selling to Saudi consumers, because debit is how a large share of the population pays and acceptance is expected by the regulator. E-commerce, retail, restaurants, transport, utilities, education and government-related payments all fit. It suits you less as a standalone answer if your customers are international travellers using Visa or Mastercard, or expatriate buyers who hold foreign cards, since those need international scheme coverage too. In practice you do not choose between mada and international cards, you carry both. It is also the sensible base layer for any merchant planning to add instalments later on.
- mada suits almost every business selling to Saudi consumers, since debit is the default.
- Retail, e-commerce, restaurants, transport, utilities and education all depend on it.
- It is not a standalone answer for travellers and expatriates holding foreign cards.
- Most merchants carry mada alongside Visa and Mastercard rather than choosing between them.
How merchants usually connect
Merchants reach mada through a Saudi-licensed acquirer or through a PSP that holds that relationship. Onboarding requires a business licence, identification for the legal representative and bank account details, plus the usual review of your website, product and volumes. Because acceptance is expected by the Saudi Central Bank for merchants above certain thresholds, treat mada as part of your compliance checklist rather than a conversion experiment. Integration is normally through the acquirer's API or hosted page, and mada appears as a card option at checkout with 3-D Secure authentication for online transactions.
- Merchants connect through a Saudi-licensed acquirer or a PSP holding that relationship.
- Onboarding needs a business licence, identification, bank details and a business review.
- Treat mada as part of your compliance checklist, not as a conversion experiment.
- Online mada transactions authenticate through 3-D Secure at checkout.
Cross-border merchant notes
A foreign merchant does not apply for a Saudi licence to accept mada. Acceptance runs through a licensed acquirer, which is the route the Saudi Central Bank expects for merchants outside the Kingdom. Collection happens in Saudi riyals, and the money leaves the country through the acquirer or PSP under Saudi foreign exchange rules, so model conversion and timing. Local scheme rules matter here: mada debit interchange is regulated, merchants above defined thresholds are expected to accept it, and cash-only retail has been discouraged for years. Confirm the current thresholds with your acquirer.
- A foreign merchant accepts mada through a licensed acquirer rather than by getting a Saudi licence.
- Collection is in Saudi riyals, with repatriation under Saudi foreign exchange rules.
- mada interchange is regulated, and acceptance is expected above defined thresholds.
- Confirm the current acceptance thresholds with your acquirer before launch.
Fees, settlement and refunds
Treat any published rate as a starting point only. Real pricing shifts with country, industry, volume, settlement currency, integration method and contract terms. Verify against the operator's official pricing page or a written quote before you commit. The structure is helpful here because mada interchange is regulated, so the scheme cost is capped, and what varies is your acquirer or PSP margin on top, plus any cross-border conversion. Settlement runs in riyals on your acquirer's schedule, commonly one to two business days. Refunds are card reversals, and chargebacks follow card scheme rules.
- Treat published rates as a starting point and verify the real price on the official page or in a quote.
- mada interchange is regulated and capped, so the variable part is your acquirer margin.
- Settlement runs in riyals on your acquirer's schedule, commonly one to two business days.
- Refunds are card reversals, and disputes follow card scheme chargeback rules.
Alternatives and complements
Visa and Mastercard are complements rather than alternatives, since they cover international cards, travellers and premium segments that mada does not. STC Pay and other local wallets are worth adding for customers who prefer to pay from a balance. Buy now, pay later providers such as Tabby and Tamara are strong additions in Saudi Arabia, where instalment behaviour is mainstream, and they layer on top of a working card setup. Bank transfer suits large corporate invoices. The practical advice is to build the card layer first, then add wallets and instalments.
- Add Visa and Mastercard for international cards, travellers and premium segments.
- Add STC Pay and similar wallets for customers who prefer paying from a balance.
- Add Tabby or Tamara once the card layer works, since instalments are mainstream in Saudi Arabia.
- Use bank transfer for large corporate invoices above card comfort levels.
Questions to ask before you integrate
Ask your acquirer whether mada acceptance is included in your Saudi setup or needs separate activation. Ask for the settlement currency, the payout schedule and any minimum payout. Ask whether your entity needs a local presence to settle in riyals. Ask about the acceptance thresholds that apply to your business and whether you are in scope. Ask how 3-D Secure is handled and what your liability is on authenticated transactions. Ask how chargebacks and refunds are processed. Finally, ask whether Apple Pay and mada Pay provisioning are supported through the same integration.
- Is mada acceptance included in your Saudi setup, or does it need separate activation?
- What is the settlement currency, the payout schedule and any minimum payout?
- Does your entity need a local presence to settle in Saudi riyals?
- How is 3-D Secure handled, and what is your liability on authenticated transactions?
- Are Apple Pay and mada Pay provisioning supported through the same integration?
Merchant usage and connection route
mada in the payment stack
mada is central when a merchant needs domestic card-network acceptance for Saudi customers rather than relying only on international card schemes. Use it to compare Saudi ecommerce, in-app, POS, tokenization, refund, dispute, and reconciliation requirements, especially when local cardholder behavior and bank routing matter.
Connection route
Merchants typically reach mada through a Saudi acquirer, bank merchant-services relationship, PSP, gateway, payment facilitator, or platform. Confirm whether mada is enabled directly by the acquirer or through a gateway bundle, and who is responsible for authorization routing, settlement, refunds, disputes, and technical support.
Verification questions
- Is mada required for ecommerce, app, POS, tokenized card, recurring, or card-present flows?
- Which Saudi bank, acquirer, PSP, gateway, or platform provides the merchant route?
- Who handles authorization, settlement reporting, refunds, disputes, 3DS, tokenization, and risk review?
- What Saudi entity, bank account, documentation, product category, and integration requirements must be confirmed?
- Does the route support the merchant's currencies, channels, customer devices, and expected transaction values?
Merchant caveats
- mada acceptance should be verified for the exact channel and merchant category.
- Gateway availability does not define acquiring, settlement, or dispute responsibility.
- Tokenization, recurring, and refund behavior may require separate provider confirmation.
- Provider examples are discovery examples only, not recommendations or support evidence.
Provider examples to verify
Related markets
Keep researching
- mada
- PSP contacts in Saudi Arabia
- Payment Channel Directory
- Submit payment requirements
- Visa Payment Acceptance
- Mastercard Payment Acceptance
This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.
Sources
Capability verification checklist
Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.
- Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
- Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
- Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.
Official links to open
Commercial terms to confirm
| Pricing model | card acquiring or network priced |
|---|---|
| Pricing basis | official public pricing or terms |
Fields still to confirm
- Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
- FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.
Integration route to confirm
| PCI scope | confirm hosted checkout tokenization or direct card handling |
|---|
Fields still to confirm
- API / checkout route: confirm with the provider, acquirer, PSP, or official documentation before launch.
- SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Sandbox: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Webhooks: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
- 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.
Operational features to confirm
No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.
Fields still to confirm
- Recurring billing: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Marketplace split: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Partial refund: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Preauth / capture: confirm with the provider, acquirer, PSP, or official documentation before launch.
Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.
Questions merchants ask
Is mada a card, a wallet or a payment provider?
It is a card scheme. mada is Saudi Arabia's national payment network, owned by the Saudi Central Bank, and it sits behind the debit cards issued by Saudi banks. Merchants do not join it directly, they accept it through a licensed acquirer or PSP alongside Visa and Mastercard.
Do merchants have to accept mada in Saudi Arabia?
Acceptance is expected by the Saudi Central Bank for merchants above defined thresholds, and cash-only retail has been discouraged for years, so most merchants selling to Saudi consumers should treat mada as mandatory. Confirm the current thresholds with your acquirer, because they determine whether your business is in scope.
Can a foreign merchant accept mada payments?
Yes, through a licensed acquirer rather than by applying for a Saudi licence. A foreign business reaches mada via a Saudi-licensed acquirer or a PSP holding that relationship, collects in Saudi riyals, and repatriates under Saudi foreign exchange rules, so plan for conversion and timing.
How much does mada cost a merchant?
Any figure online is a first filter, not a quote. Final pricing depends on country, industry, volume, settlement currency, integration method and contract terms. The useful structural point is that mada interchange is regulated and capped, so the variable part is your acquirer margin.
How long does mada settlement take?
Settlement runs in Saudi riyals on the schedule your acquirer or PSP applies, commonly one to two business days after the transaction. Cross-border merchants should add the time their provider takes to convert and remit, so ask for the full timeline in writing before launch.
Does mada work with Apple Pay and Google Pay?
Yes. A mada card can be provisioned into Apple Pay, Google Pay and Samsung Wallet, and mada also offers its own mada Pay wallet for Android devices. Ask your acquirer whether wallet provisioning is supported through the same integration as card acceptance.