TL;DR: Choosing app payment methods in Saudi Arabia comes down to one rule: digital goods consumed inside the app — courses, subscriptions, coins, premium features — must be sold through Apple's and Google's in-app purchase (IAP) systems, while physical goods and real-world services must use an external payment gateway. The gateway layer is where Mada, Apple Pay, STC Pay, and Tamara belong; you cannot swap IAP for a gateway just because gateway fees are lower. For many Saudi apps in 2026, the most practical setup is a hybrid: store IAP by default inside the app, plus a policy-compliant web checkout that accepts local payment methods. Get this wrong and Apple or Google can reject your app — or remove it after launch.
Why payments are the first decision, not the last
Most founders I talk to treat payments as a checkout detail to sort out "before launch." It isn't. Your payment model determines your margins (Apple and Google take up to 30%; gateways typically take low single digits), your backend architecture, and even whether your app passes review at all.
Saudi Arabia adds its own layer. Users here expect Mada — the national debit card network — at every checkout. Apple Pay adoption is high, digital wallets like STC Pay are everywhere, buy-now-pay-later through Tamara is a normal way to split larger purchases, and bank transfer is still a legitimate channel for high-ticket and B2B sales. None of that changes Apple's and Google's rules, though. The art of choosing app payment methods in Saudi Arabia is fitting local expectations inside global platform policy — not around it.
I've spent 10+ years building for this market — React Native apps on both stores, WooCommerce backends, and payment flows that had to survive App Review. This guide is the explanation I wish clients had before our first call.
The one question that decides everything: what are you selling?
Everything follows from a single classification:
- Digital goods consumed inside the app — online courses, subscriptions, premium features, ad removal, virtual currency. Apple and Google require their in-app purchase systems for these. No exceptions for local preference.
- Physical goods and real-world services — product delivery, restaurant orders, salon bookings, rides, in-person training. Apple and Google prohibit IAP for these. You must use an external gateway (or cash on delivery).
- Anything sold on your website — neither Apple nor Google has any say over your web checkout. The rules govern what happens inside the app, not your business.
That third point is the foundation of every compliant hybrid strategy, and we'll come back to it.
App payment methods in Saudi Arabia: the full comparison
| Method | What it is | Allowed inside the app? | Best fit |
|---|---|---|---|
| Apple / Google IAP | The stores' own billing systems | Required for digital goods | Subscriptions, courses, premium features |
| Mada | Saudi national debit network, via a licensed gateway | Only for physical goods / real-world services | E-commerce, delivery, bookings |
| Apple Pay / Google Pay (via gateway) | Wallet layer over cards, including Mada cards | Same rule as Mada | Fast checkout for real-world sales |
| STC Pay (now part of stc bank) | Digital wallet | Same rule as Mada | Wallet-first users, transfers |
| Tamara (BNPL) | Split payments under SAMA oversight | Gateway-side only — never as an IAP substitute | Higher-ticket carts, web checkout |
| Bank transfer | Manual payment against an order or invoice | Not as an in-app digital-goods checkout | B2B, corporate training, high-ticket |
One clarification that confuses almost everyone: Apple Pay appears in both worlds. When a user buys an in-app subscription, the confirmation sheet is Apple's billing system — that's IAP. When a user pays for groceries in an app with Apple Pay, that's a gateway transaction that happens to use the Apple Pay wallet. Same button feel, completely different rails and rules.
Apple and Google's IAP rules in plain language
Both platforms say essentially the same thing: if the thing being purchased is unlocked or consumed inside the app, the purchase must go through their billing. Apple spells this out in App Review Guideline 3.1.1; Google in its Play payments policy.
The commercial terms, briefly:
- The headline commission is 30%, but both stores offer 15% tiers — Apple's Small Business Program for developers earning under $1M/year, reduced rates on subscriptions, and Google's equivalent programs. Most Saudi startups qualify for 15% from day one.
- IAP handles currency, taxes, refunds, and receipts through the store. You never touch card data — but you also never see the customer's payment details, and refunds go through Apple/Google, not you.
When are external gateways allowed inside an app?
- Physical goods and real-world services — always the gateway (this is mandatory, not optional).
- "Reader"-style apps (content purchased elsewhere, consumed in-app) can exist without any in-app checkout — the Netflix model.
- Regional carve-outs: court rulings in the US and the Digital Markets Act in the EU have forced Apple and Google to allow external purchase links and alternative billing in those storefronts. As of early 2026, those carve-outs do not automatically extend to the Saudi storefront. Rules are moving fast — re-check the current guidelines before every submission, not just the first one.
The Tamara reality: BNPL for Saudi apps
Tamara is the most-requested payment feature in my client conversations, and for good reason — splitting a 1,500 SAR purchase into installments removes real friction. But three facts get missed:
- Tamara is a gateway-side product. It integrates through web checkouts, e-commerce plugins (WooCommerce, Salla, Shopify), or its merchant API — see Tamara's official site for current offerings. It is not, and cannot be, a replacement for Apple or Google IAP.
- It operates under SAMA oversight, which matters for your own compliance posture — pair it with a licensed payment provider for the card side.
- It earns its fees on higher baskets. In my experience, BNPL makes the most sense when your average order is in the hundreds of riyals or more; for a 30 SAR digital top-up it solves nothing.
So if installments matter to your model, the question isn't "how do I put Tamara in my app?" — it's "which of my sales can legitimately flow through a checkout where Tamara lives?"
The hybrid pattern: how I built Tafrud's cart mode
When I built Tafrud — an e-learning platform for the Saudi market, live on both the App Store and Google Play with a WordPress/LearnPress/WooCommerce backend — I hit this exact wall. Courses are digital goods, so in-app sales had to be IAP. But the business also needed Tamara and bank transfer for larger purchases. The answer was what I call cart mode:
- Store IAP is the default. Every course is purchasable through Apple or Google billing, identical on iOS and Android. This is the baseline that keeps both stores happy.
- A server-controlled flag can switch individual courses into cart mode, routing that purchase to a WooCommerce web cart — where Tamara and bank transfer are available.
- The app reads its configuration from the server at launch. Which courses use the cart, whether the cart tab appears at all, and how conservative the iOS build behaves are all controlled from the website — no app update, no re-review.
- Entitlements sync both ways. Buy on the web, and the course unlocks in the app. That's fully allowed on both platforms — it's the same model Netflix and Kindle use.
The critical detail is iOS posture. Apple is far stricter than Google about apps steering users toward external payment for digital goods, so the iOS build defaults to the most conservative behavior and every relaxation is a deliberate, server-side decision. Running lead generation for six automotive brands taught me to treat every conversion path as something you measure and control remotely — the same discipline applies here: never hard-code a payment decision you might need to reverse in review week.
What it costs to get it wrong
- Rejection at review — typically days to weeks of delay per cycle while you rebuild the flow.
- Removal after launch — apps that slip through and later get flagged go down with zero notice, taking your acquisition spend with them.
- Account termination — repeated circumvention of billing rules can end your developer account, not just the app.
- Retrofit cost — bolting IAP onto an app built around a gateway means new product catalogs in two consoles, receipt validation, restore-purchases flows, and server-side entitlement logic. It is typically a rebuild of the entire purchase layer, not a patch.
- Regulatory exposure — on the gateway side, work only with SAMA-licensed payment providers (PayTabs, Moyasar, Tap, and HyperPay are common choices in KSA).
A decision checklist before you build
- Classify every product you sell: digital-in-app or real-world.
- Digital goods → IAP on both stores; enroll in the reduced-commission programs.
- Real-world goods/services → a licensed gateway with Mada and Apple Pay as the baseline; add Tamara if your basket size justifies it.
- High-ticket or B2B → web checkout with bank transfer or invoicing.
- Want both worlds → build the hybrid: IAP default, server-controlled web cart, conservative iOS behavior, entitlement sync.
- Re-verify platform rules at every submission — app payment methods in Saudi Arabia sit at the intersection of global policies that are actively changing in 2026.
FAQ
Can I use Mada or STC Pay inside my mobile app?
Yes — for physical goods and real-world services, integrated through a licensed payment gateway. No — for digital content consumed inside the app; on both iOS and Android those purchases must go through the stores' in-app purchase systems.
Does Tamara work with Apple's in-app purchases?
No. Tamara is a gateway-side BNPL provider and cannot replace or sit inside Apple or Google billing. If installments matter for your digital products, sell them through a web checkout — which the platforms don't control — and unlock the content in the app.
How much do Apple and Google take compared to a payment gateway?
Apple and Google charge 15–30% depending on your revenue and product type; Saudi payment gateways typically charge a small percentage plus a fixed fee per transaction. The gap is real, but it never justifies routing digital in-app sales around IAP — the removal risk outweighs the savings.
Can customers buy on my website and use the purchase in my app?
Yes, and it's fully policy-compliant — this is how Netflix and Kindle operate. What's restricted, especially on iOS, is actively steering users from inside the app to that external checkout for digital goods. That steering behavior is exactly where a hybrid setup needs careful, server-controlled design.
If you're planning an app for the Saudi market and the payment model is the part keeping you up at night, that's the part I enjoy most. See how the full pattern works in the Tafrud case study, browse what I build, or get in touch — I'm happy to pressure-test your payment plan before you write a line of code.