Accepting online payments in Saudi Arabia looks simple from the outside. Add a checkout button, connect a provider, take mada and Visa. In practice, authorization rates, settlement times, 3D Secure rules, Apple Pay tokenization, installments, and reconciliation with ZATCA e-invoicing decide whether your store makes money or bleeds support tickets.
This guide is the full playbook for Saudi e-commerce and SaaS payments: what methods you must support, how the main providers compare technically, how to integrate without losing conversions, and how to operate in production.
1. What Saudi buyers actually use
Mada is the national scheme and dominates debit cards issued by Al Rajhi, SNB, Alinma, and others. Most Saudi shoppers pay with a mada card stored in Apple Pay. If your checkout shows only Visa and Mastercard, a large share will abandon. Apple Pay with mada tokenization is now the default expectation on iPhone, which holds majority share in the Kingdom.
Beyond cards, you need to understand three more rails. SADAD invoices are still used for B2B and government-adjacent payments, where the buyer pays via bank app against an invoice number that expires. Buy-now-pay-later with Tabby and Tamara drives fashion, beauty, and electronics baskets over 500 SAR. Wallets like STC Pay, Urpay, and Barq matter as cash-on-delivery alternatives, especially outside Riyadh and Jeddah where card trust is lower.
For B2B SaaS, expect bank transfers plus SADAD plus cards. Procurement teams will ask for a VAT invoice with your CR and VAT number before paying. Your payment flow must produce data that matches your Fatoora invoice exactly, otherwise finance reconciliation breaks.
2. Provider landscape in detail
Moyasar is the most developer-friendly Saudi PSP. REST API is clean, docs have Arabic examples, hosted checkout plus custom Apple Pay sheets work well, and mada plus Apple Pay support is solid. Webhooks are reliable with signing. Best fit is custom Next.js stores and SaaS that want control without enterprise sales cycles. Pricing is typically around 1.75 percent plus VAT for local cards, negotiable with volume.
Tap Payments offers a strong dashboard, multi-currency settlement, and broad MENA coverage including Kuwait and UAE. Integration is slightly heavier but supports saved cards, subscriptions, and strong 3DS handling. Fees trend a bit higher, often 2 to 2.5 percent. Good when you operate in multiple Gulf countries from one integration.
HyperPay suits enterprise and higher-risk verticals. It supports installments via Tabby and Tamara addons, SADAD, and dedicated onboarding with compliance help. API is older and docs require more back-and-forth, but local support in Riyadh helps with mada certification issues. Expect custom pricing and longer contracting.
Checkout.com and Stripe via Middle East entities work for international cards but verify mada coverage and settlement to Saudi banks before committing. Some global PSPs route mada as Visa, which raises decline rates and fees. Always run a pilot with real mada test cards from different issuers.
Questions to ask every sales rep are authorization rate by scheme for Saudi issuers, 3DS frictionless rate, settlement lag to your specific bank, chargeback process in Arabic, support for refunds and partial captures, webhook retry policy, and sandbox fidelity for mada and Apple Pay.
3. Fees, settlement, and total cost
Headline rate is not total cost. Local mada transactions often settle at 1.5 to 2 percent plus VAT. Visa and Mastercard Saudi-issued are similar. International cards add cross-border fees. Amex is highest. Tabby and Tamara charge merchant fees of 3 to 6 percent but lift conversion 20 to 30 percent on eligible baskets, so net is often positive.
Settlement takes 2 to 7 days to Saudi banks depending on provider and risk checks. First payouts after onboarding can take longer due to KYB. Reconcile daily against bank statements and your order database. Hold a rolling reserve mentally for refunds and chargebacks, typically 5 to 10 percent of weekly volume for new stores.
For SaaS subscriptions, factor failed payment recovery. Mada debit cards expire and get replaced often. Dunning with SMS in Arabic plus Apple Pay re-auth recovers far more than email alone.
4. Integration pattern that converts
Start with hosted checkout to launch in days. Then move to embedded Apple Pay sheet on product and cart pages for one-tap conversion. Keep card form as fallback with inline validation in Arabic, error messages that name the bank action, and automatic detection of mada BIN ranges.
Backend rules are store payment IDs from the provider alongside your order ID, handle webhooks with idempotency keys, and never trust frontend success callbacks alone. Implement states of pending, authorized, captured, failed, refunded, and disputed. Capture after inventory confirmation for physical goods to avoid refund fees.
Test matrix must include successful mada, successful Visa, failed 3DS challenge, insufficient funds, expired SADAD invoice, partial refund, full refund, duplicate webhook delivery, and timeout during clearance. Log raw provider codes plus normalized codes for support.
Frontend details matter. Show SAR prices with VAT inclusive note, show mada and Apple Pay logos above the fold, and do not surprise with shipping fees at the last step. Address form should support national address fields and Arabic names in UTF-8, which also keeps Fatoora buyer data clean.
5. Apple Pay and mada specifics
Apple Pay in Saudi usually means a mada card tokenized in Wallet. Your PSP must support mada token decryption and processing, not just Visa tokens. Test on real iPhones with STC Pay-backed and bank-issued mada cards. Verify the payment sheet shows correct Arabic merchant name, SAR total, and shipping.
For 3D Secure, Saudi issuers enforce step-up for many transactions. Your hosted or embedded flow must handle redirect and iframe challenges gracefully on mobile Safari and Chrome, preserving cart state. Log 3DS version, ECI, and CAVV for disputes.
6. Operations and reconciliation
Daily job should pull settlements, match to orders by provider reference, flag mismatches, and alert on authorization drops below baseline. Weekly review should track authorization rate by scheme, Apple Pay share, Tabby share, refund rate, and chargeback rate.
Common incidents are webhook secret rotation breaking signatures, provider downtime during White Friday, and SADAD expiry confusion. Runbooks need manual capture, manual refund via dashboard, and customer message templates in Arabic.
Align payments with Fatoora. Paid B2C order must produce a simplified e-invoice and be reported within 24 hours. Paid B2B order must go through clearance before sharing the stamped invoice. Mismatched totals between payment capture and invoice XML are a top audit flag.
7. Recommendation by stage
New store under 100 orders per month should use Moyasar or Tap hosted checkout with mada plus Apple Pay plus Tabby. Launch fast and measure.
Growing store to 1M SAR yearly should add embedded Apple Pay, saved cards, SADAD for B2B, and automated dunning. Negotiate rates with two months of volume data.
Enterprise should use HyperPay or dual PSP with routing by BIN to maximize auth rates, plus dedicated fraud rules and Arabic support SLAs.
Measure authorization rate by scheme weekly and fix drop-offs before adding new methods. Payments are compounding. One percent higher auth on mada often beats any new feature.
