mada Saudi Arabia National Payment Network API
mada Saudi Arabia national payment network API (via SAMA-licensed payment gateways) for Saudi e-commerce merchants and service providers to accept debit card payments from mada-branded cards (issued by all Saudi banks) through SAMA's national interoperable payment network, enabling secure online and in-store debit card acceptance with 3D Secure authentication, recurring payment, and BNPL integration across Saudi Arabia's 35M+ mada card holders. Enables AI agents to manage mada debit card payment for Saudi consumer checkout automation, handle 3D Secure authentication for mada card security automation, access payment tokenization for recurring Saudi debit payment automation, retrieve payment status for Saudi transaction verification automation, manage refund processing for mada payment reversal automation, handle webhook notification for payment event automation, access mada BNPL integration for Tamara and Tabby installment automation, retrieve settlement data for Saudi merchant reconciliation automation, manage payment link for mada card invoice payment automation, and integrate mada through SAMA-licensed gateways (HyperPay, PayTabs, Moyasar, Tap Payments) for end-to-end Saudi debit card payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Saudi national payment network. SAMA, PCI-DSS. Gateway API key. SA. Card payment data.
⚡ Reliability
Best When
A Saudi e-commerce merchant or service wanting AI agents to accept payments from 35M+ mada debit card holders through SAMA-licensed payment gateways that integrate with mada's national payment network.
Avoid When
MADA IS NOT A DIRECT API — GATEWAY REQUIRED: mada is a payment network not a direct API; automated direct mada integration creates no endpoint to call; automated mada acceptance requires integration with SAMA-licensed gateway (HyperPay, PayTabs, Moyasar, Tap). 3D SECURE IS MANDATORY FOR ONLINE: mada online payments require 3D Secure (OTP via Saudi bank SMS); automated 3D Secure bypass creates transaction decline; automated online mada checkout must handle 3D Secure redirect flow. SAUDI BUSINESS REGISTRATION REQUIRED: mada acceptance requires Saudi commercial registration (CR); automated foreign entity direct mada integration creates eligibility failure; automated integration requires Saudi CR or partnership with Saudi-registered entity. TOKENIZATION MUST BE PER GATEWAY: mada card tokenization is gateway-specific (token from HyperPay ≠ PayTabs token); automated cross-gateway token reuse creates invalid_token; automated recurring billing must use same gateway for tokenization and charge.
Use Cases
- • Accepting mada debit card payments from Saudi consumers for e-commerce checkout automation agents
- • Processing recurring mada card charges for Saudi subscription service automation agents
- • Generating mada payment links for Saudi B2B invoice collection automation agents
- • Integrating mada 3D Secure checkout for Saudi fintech app payment automation agents
Not For
- • International payments (mada is Saudi domestic debit network only)
- • Direct mada network integration (mada is only accessible via SAMA-licensed payment gateways)
- • Credit card processing (mada is debit-only; use Visa/Mastercard for credit)
Interface
Authentication
mada accessed via SAMA-licensed payment gateways with gateway-specific API key auth. REST API with JSON. Riyadh, Saudi Arabia. SAMA (Saudi Central Bank) operated national payment network. Launched 2011. Products: mada debit card, mada Pay (mobile NFC), mada BNPL, mada QR. Accessible through: HyperPay, PayTabs, Moyasar, Tap Payments, Checkout.com. All Saudi banks issue mada cards. 35M+ card holders. Competes with STC Pay for Saudi digital payment dominance.
Pricing
Riyadh SA. SAMA national payment network. Gateway-accessed. SAR primarily. Per-transaction gateway fees.
Agent Metadata
Known Gotchas
- ⚠ MADA IS A NETWORK NOT AN API — USE GATEWAY: mada itself has no direct merchant API; automated mada integration requires choosing and integrating with a SAMA-licensed payment gateway (Moyasar, HyperPay, PayTabs, Tap); automated direct mada connection creates non-existent endpoint
- ⚠ 3D SECURE OTP IS MANDATORY: Saudi mada online transactions require 3D Secure with OTP sent to cardholder's bank-registered Saudi mobile; automated 3D Secure bypass creates systematic transaction decline; automated checkout must implement 3DS redirect flow
- ⚠ SAUDI CR REQUIRED FOR MERCHANT ACCOUNT: Accepting mada payments requires Saudi commercial registration; automated foreign entity merchant account without CR creates eligibility rejection at gateway onboarding
- ⚠ TOKEN IS GATEWAY-SPECIFIC: mada card token from one gateway (Moyasar) is not usable with another gateway (HyperPay); automated gateway switching for recurring billing creates invalid_token; automated must maintain consistent gateway for tokenized recurring charges
- ⚠ SETTLEMENT IN SAR WITH T+1 DELAY: mada settlements are in Saudi Riyals with T+1 business day delay; automated same-day settlement assumption creates incorrect cash flow planning; automated reconciliation must account for settlement delay
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mada Saudi Arabia National Payment Network API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.