Payment Gateway Saudi Arabia: Mada, STC Bank and Apple Pay

This guide is for international ecommerce, digital-content and software merchants collecting relatively small, frequent Saudi payments. It covers international cards, Mada, STC Bank (formerly stc pay) and Apple Pay. It separates market facts, public documentation and account approval.

Commercial disclosure: HaiPay publishes this evidence-led product guide. It is not an independent ranking, binding offer, merchant approval or legal opinion.

What a Saudi payment gateway needs to support

A useful shortlist covers the payment lifecycle. Start with six questions:

1. Shopper fit: Which card or wallet journey will the customer recognise and complete?
2. Merchant fit: Which legal entity, website, app, business model and transaction profile can apply?
3. Route fit: Which payment route is documented publicly, and which route is enabled for the merchant account?
4. Currency fit: What currency does the shopper see, what account balance records the funds, and what reaches the merchant bank?
5. Operational fit: How are payment status, failed payments, refunds, disputes and finance-record matching handled?
6. Commercial fit: Which fees, tax, foreign exchange (FX), payout and risk conditions appear in the signed terms?

Plain-language terms used below:

• Platform balance: the balance recorded inside the provider account after an eligible successful collection.
• Presentment: the currency and amount shown to the shopper at checkout.
• Settlement: the provider’s payout instruction to the merchant, not the receiving bank’s posting time.
• Reconciliation: matching orders, payments, fees and payout records.
• Issuer authentication: the card-issuing bank’s identity or payment check.
• Underwriting: the provider’s eligibility and risk review before merchant approval.
• Acquiring: a provider’s acceptance and routing of card payments.

The international payment gateway guide covers wider selection. Local acquiring and cross-border acquiring frames entity, routing and settlement questions.

Saudi Arabia’s card and wallet landscape

These routes solve different checkout problems.

Market existence does not prove that a gateway, merchant entity or production account can use the route.

Source: “Use MADA Bank Cards for Buying Products through Internet”, “Notice of Transformation to STC Bank”, and “Apple Pay”, verified 2026-09-03.

International card acceptance is an account-level question

International cards are separate from Mada. A public card page still leaves the scheme, entity, currency and operating scope to written terms.

Confirm these account-level fields:

• enabled schemes, issuer authentication, transaction types, merchant-category restrictions and live limits;
• refunds, disputes, chargebacks (card-payment reversals) and reserve requirements (funds held against risk); and
• payout timing and currency by route.

Do not transfer a global card statement to every Saudi merchant or transaction. A shopper’s card, issuing bank, authentication result and the merchant’s approved configuration can all affect the outcome.

The credit card product page can start the product discussion. The signed quote and merchant configuration must finish it.

Mada is a national card network, not a bank transfer

Saudi Central Bank material describes Mada as the national payments system and discusses online Mada bank cards. This supports a card-network classification, not a bank-transfer classification.

Confirm how the Mada journey is presented, authenticated and reported. Also confirm whether the provider’s card route covers Mada for the entity and account.

Current HaiPay surfaces are inconsistent. The Middle East and North Africa (MENA) page and Saudi table place Mada with cards, while the pricing matrix places it under bank transfers. Mada remains a payment and card network. Resolve the commercial mapping in writing.

Source: “Use MADA Bank Cards for Buying Products through Internet”, “SAMA Announces the Launch of the New E-commerce Payments Interface”, “MENA Local Payment Coverage”, and “Payment Gateway Pricing & Fees”, verified 2026-09-03.

STC Bank and the legacy STC Pay route label

STC Bank’s notice explains its transformation from the stc pay wallet business into a digital bank. Reader-facing references should then use STC Bank.

HaiPay’s current public product and technical materials still use the label “STC Pay.” That label should be preserved when identifying the documented route. It should not be silently rewritten, because the technical label and consumer brand serve different purposes.

Confirm that the STC Pay-labelled route maps to the intended STC Bank journey. Device flow, activation, limits, refunds, disputes, settlement and reconciliation remain account questions.

Source: “Notice of Transformation to STC Bank”, “MENA Local Payment Coverage”, and “Saudi Arabia”, verified 2026-09-03.

Apple Pay for a Saudi-facing checkout

Apple’s Saudi page establishes a market payment experience. Customers need a compatible device and an eligible card from a participating issuer.

It does not prove provider activation or define underlying cards, entities, currencies, refunds, disputes, recurring use, token handling or settlement.

The public MENA page and Saudi table show an Apple Pay surface. Confirm production configuration and test required devices before showing it.

Source: “Apple Pay”, “MENA Local Payment Coverage”, and “Saudi Arabia”, verified 2026-09-03.

Market availability, public route and merchant activation are three gates

A production method should pass three gates:

1. Market existence: An official market or operator source confirms the payment network, brand or customer experience.
2. Provider public surface: Current provider material documents the method, currency path or route status.
3. Merchant activation: The provider approves the contracting entity and enables the method for the merchant’s production account.

No gate substitutes for another. Only account configuration, acceptance testing and signed terms establish activation.

Use this sequence for every method. A market logo is not an eligibility, price or settlement promise.

Evidence Slot 1 — Saudi market infrastructure

This slot covers market, brand and regulatory questions.

Market evidence establishes vocabulary and customer context, not a provider entity, route or contract.

Source: “Use MADA Bank Cards for Buying Products through Internet”, “Notice of Transformation to STC Bank”, and “Apple Pay”, verified 2026-09-03.

Evidence Slot 2 — HaiPay product and commercial surfaces

This slot records current public product evidence and its boundary.

No account-level Saudi quote is used here. Route activation, final pricing, tax treatment, bank-settlement currency and fixed exchange rates are not presented.

Source: “MENA Local Payment Coverage”, “Saudi Arabia”, “Collection Application”, “Payment Gateway Pricing & Fees”, and “Payment Settlement Time: How Long It Really Takes”, verified 2026-09-03.

Evidence Slot 3 — Merchant operations

This slot converts public evidence into launch questions.

Only merchant-specific records can close these questions.

Source: “Saudi Arabia”, “Payment Gateway Pricing & Fees”, and “Payment Settlement Time: How Long It Really Takes”, verified 2026-09-03.

Saudi Payment-Route Evidence Matrix

The matrix is a selection tool, not an activation promise. “Available” below means only that the current public route table uses that catalog status.

The documented currency labels below are Saudi riyal (SAR) and US dollar (USD).

The ranges are documentation values, not universal merchant limits. The Mada classification conflict and a conflicting test-amount instruction prevent this table from serving as an implementation specification. Use the live account configuration and written acceptance criteria.

Source: “Saudi Arabia”, “Collection Application”, “MENA Local Payment Coverage”, “Payment Gateway Pricing & Fees”, “Use MADA Bank Cards for Buying Products through Internet”, “Notice of Transformation to STC Bank”, and “Apple Pay”, verified 2026-09-03.

SAR and USD presentment, balance and settlement are different facts

The public Saudi collection material says a successful SAR path adds funds to a SAR platform balance. It describes the corresponding result for a USD path and USD platform balance.

That evidence supports collection and balance currency only. It does not prove that SAR reaches a Saudi bank account, that USD is converted automatically, or that every merchant can choose either path.

Keep these stages separate in technical design, finance reporting and customer support.

Source: “Saudi Arabia” and “Collection Application”, verified 2026-09-03.

Public settlement scopes do not assign a Saudi route

The public settlement guide presents two relevant scopes. It does not resolve which one governs Mada, the STC Pay-labelled route or Apple Pay for a Saudi merchant.

In the published notation, T means the successful capture date.

For any quote, require the agreement to state the route, entity, cut-off, reserve conditions and the number of calendar days counted.

The public guide says settlement executes on working days. A weekend or holiday can defer execution to a working day, and bank transit follows that execution. The published timing therefore should not be restated as a guaranteed bank-arrival date.

Source: “Payment Settlement Time: How Long It Really Takes”, verified 2026-09-03.

Fees, VAT and contractual foreign exchange

Eligible card transactions start at 2.5% + US$0.30. That starting point depends on eligibility, contracting entity, market, method, volume, transaction quality, risk and the final quote.

No route-specific public price is assigned here to Mada, the STC Pay-labelled route or Apple Pay. A category-level starting price should never be copied into a Saudi business case without a method-level quote.

Confirm three commercial fields in writing:

• Value-added tax: Do not apply a general Saudi VAT percentage directly to a provider fee. Ask which entity invoices the service, whether tax is included in the quoted rate, and how the invoice presents it. Only the controlled quote and invoice terms can answer those questions.
• Foreign exchange: The applicable exchange-rate arrangement is locked under the merchant contract and confirmed in the quote.
• Outbound charges: Ask whether any outbound charge applies. The answer needs the route, entity, payout currency and signed commercial terms. This guide does not publish a Saudi outbound-fee rate.

Source: “Payment Gateway Pricing & Fees”, verified 2026-09-03.

Merchant entity and underwriting requirements

A route can appear in public documentation while an application remains ineligible. Confirm the contracting structure before allocating engineering time.

The preflight request should include:

• legal entity name, registration country and operating locations;
• website or app, product description and customer-support details;
• expected Saudi transaction count, average amount and maximum amount;
• refund profile, fulfilment timing and dispute exposure;
• required routes and presentment currencies;
• intended settlement currency and bank-account country;
• ownership, identity and business-verification documents; and
• requested sandbox, production and support contacts.

Ask for a written response that identifies eligible routes and remaining conditions. Do not treat a sales conversation, public table or successful sandbox payment as final production approval.

Integration, status, refunds, disputes and reconciliation

A checkout integration is not complete when the payment page returns the shopper. The merchant needs an authoritative payment state and a controlled fulfilment rule.

Before launch, document three operating controls:

• Payment status: Test successful, failed, pending, duplicate and late-confirmation cases. Define which server-side signal authorises fulfilment. Confirm retry behaviour, duplicate-safe request handling, order identifiers and support escalation without assuming a generic platform feature covers every route.
• Refunds and disputes: Obtain method-level confirmation for full and partial refunds, time windows, fees, funding, status tracking, customer disputes, evidence deadlines and final outcomes.
• Finance records: Confirm gross amount, fee, net amount, currency, payment time, route, merchant order, provider reference, payout batch and exception fields. Do not infer method-level report support from a collection page.

Mada Classification Conflict Map

The classification evidence can be read as a simple chain:

Evidence chain: Saudi Central Bank: national payment and card network → provider MENA page: card grouping → versioned Saudi table: card-labelled path → pricing matrix: bank-transfer grouping.

The first three points support treating Mada as a card-network requirement. The pricing placement conflicts with that classification. It should not be used to rename Mada or assign a bank-transfer price.

The safe commercial action is to ask for a written method mapping. It should state the route, pricing category, shopper flow, settlement scope and responsible product owner.

Source: “Use MADA Bank Cards for Buying Products through Internet”, “MENA Local Payment Coverage”, “Payment Gateway Pricing & Fees”, and “Saudi Arabia”, verified 2026-09-03.

STC Bank Naming and Route Map

The naming chain is different:

Naming chain: Current consumer brand: STC Bank → legacy provider commercial label: STC Pay → public technical route label: STC Pay → merchant decision: confirm current journey and activation.

Use STC Bank when discussing the current customer brand. Use the exact STC Pay label when quoting the provider’s route documentation. Do not describe the current bank brand unconditionally as a wallet.

The final merchant record should preserve both meanings. It should map the consumer-facing name to the documented route label, tested shopper journey, account configuration and signed commercial terms.

Source: “Notice of Transformation to STC Bank”, “MENA Local Payment Coverage”, and “Saudi Arabia”, verified 2026-09-03.

Saudi checkout-to-balance-to-settlement evidence flow

The flow prevents a balance claim from becoming a bank-settlement claim.

Shopper order in an approved currency → successful collection → corresponding platform balance → contract-defined conversion or no conversion → route-specific settlement instruction → bank transit → merchant bank receipt.

This model is also useful for reconciliation. Every transition should have a currency, timestamp, identifier and accountable evidence source.

Source: “Saudi Arabia”, “Collection Application”, and “Payment Settlement Time: How Long It Really Takes”, verified 2026-09-03.

Saudi Quote Verification Checklist

Ask the provider to complete every applicable row in writing.

Where HaiPay may fit

HaiPay may be worth evaluating when international cards, Mada, the STC Pay-labelled route and Apple Pay match the Saudi checkout scope under review. Its public Saudi materials provide a starting point for a route and currency discussion.

The public evidence is not enough for launch. Ask for a written preflight response covering the entity, route, merchant activation, live limits, shopper flow, SAR or USD presentment, balance, bank settlement, VAT, FX, refunds, disputes and reconciliation.

Review the local payment product, the MENA payment-method page and public pricing. Then use the contact page with the completed checklist.

When this route set may not fit

This route set may not fit a merchant needing a guaranteed Saudi entity, local acquiring or SAR bank settlement before review. It also needs method-level operating terms.

Methods outside this guide need a separate review. Large-ticket business-to-business (B2B) collection and bank-transfer workflows need a different assessment.

A provider fits only when account approval, customer journey, controls and signed economics match the requirement.

Disclosure and limitations

HaiPay publishes this commercial guide about its service. It is not a universal provider ranking.

Sources were checked on 3 September 2026. Obtain current written terms before relying on a route, price or timeline.

This is not legal, tax, accounting, investment or financial advice. Obtain suitable professional advice.

Sources

1. Saudi Central Bank, “Use MADA Bank Cards for Buying Products through Internet”, accessed 2026-09-03. Supports Mada’s national payment and card-network context and online bank-card use.
2. Saudi Central Bank, “SAMA Announces the Launch of the New E-commerce Payments Interface”, published 2025-07-07; accessed 2026-09-03. Supports Mada’s role in Saudi national payment infrastructure and ecommerce.
3. STC Bank, “Notice of Transformation to STC Bank”, accessed 2026-09-03. Supports the transformation from stc pay and the current STC Bank consumer brand.
4. Apple, “Apple Pay”, accessed 2026-09-03. Supports Saudi market availability and the eligible-device, card and issuer conditions.
5. HaiPay, “MENA Local Payment Coverage”, accessed 2026-09-03. Supports the public Mada, STC Pay and Apple Pay product surfaces and its card grouping.
6. HaiPay Docs, “Saudi Arabia,” version 20260701, accessed 2026-09-03. Supports public route rows, catalog status, SAR and USD table ranges, and corresponding balance descriptions.
7. HaiPay Docs, “Collection Application”, accessed 2026-09-03. Supports the collection-to-balance descriptions and documents the classification and test-instruction conflicts noted in this guide.
8. HaiPay, “Payment Gateway Pricing & Fees”, accessed 2026-09-03. Supports the conditional eligible-card starting price and the conflicting Mada placement in the pricing matrix.
9. HaiPay, “Payment Settlement Time: How Long It Really Takes”, accessed 2026-09-03. Supports the T+5 (calendar days) international-card scope, T+7 (calendar days) GCC scope and working-day execution context.