In-app purchases vs web payments: what the stores allow in 2026
Digital goods sold in an app must use in-app purchase in most countries; physical goods and services use your own gateway. Rules and fees, October 2026.
By Sohail Hussain21 November 20267 min read
If your app sells digital content, features or subscriptions, Apple and Google require their own in-app purchase systems in most countries, and take a commission of 15 to 30 percent, as of October 2026. If it sells physical goods or services used outside the app, such as products, deliveries, rides or appointments, you must use your own payment gateway, and the stores take nothing. Between those two lines sit exceptions (reader apps, one-to-one live services, apps sold to businesses) and a growing list of countries where you may link users to pay on your website, each with its own fees. The rules have changed several times since 2024 and differ by country, so treat this post as a map and check the official pages before you design a payment flow.
This is not legal or tax advice; for a large revenue decision, have a lawyer read the current terms for your countries.
Which purchases must use in-app purchase?
The core rules are in section 3.1 of Apple's App Store Review Guidelines and in Google Play's Payments policy. They line up closely:
| What you sell | Examples | Apple | Google Play |
|---|---|---|---|
| Physical goods | Clothing, groceries, spare parts | Your own payment method; in-app purchase not allowed | Your own payment method; Play Billing not allowed |
| Services used outside the app | Taxi rides, food delivery, salon bookings, gym membership, event tickets | Your own payment method | Your own payment method |
| Digital features and content | Premium tier, extra storage, courses, in-game currency, ad removal | In-app purchase, with regional exceptions | Play Billing, with regional programs |
| Real-time one-to-one services | Tutoring, medical consultation, personal training by video | Your own method allowed; one-to-many classes must use in-app purchase | No matching exception listed; check the policy for your case |
| Reader apps | Magazines, books, music, video bought elsewhere | May let users sign in to content bought elsewhere | Generally possible if the app does not sell or point to the purchase; check the policy |
| Software sold to organisations | Staff tools, B2B SaaS paid by the company | May let enterprise users sign in; consumer sales must use in-app purchase | Generally possible if the app does not sell or point to the purchase; check the policy |
Most business apps we build are in the first two rows: ordering, booking and field service apps, where the store rules are simple and the payment runs through Razorpay, Stripe or a regional gateway. The difficult cases are subscriptions and digital content, which is where the rest of this post focuses.
Our mobile app development work covers both routes: the store subscription systems on both platforms, and gateway payments with receipts and webhooks.
What do the stores charge, as of October 2026?
Apple. The standard commission on paid apps and in-app purchases is 30 percent. Developers with under US$1 million in proceeds the previous year can join the App Store Small Business Program and pay 15 percent. Auto-renewing subscriptions drop to 15 percent after a subscriber's first year. Different terms apply in the European Union under the Digital Markets Act, where Apple offers an alternative fee structure that it has revised more than once.
Google. In most countries, Google's service fee is 15 percent on the first US$1 million of earnings a year and 30 percent above that, with subscriptions at 15 percent. From June 30, 2026 in the US, the UK and the European Economic Area, and from September 30, 2026 in Australia and Japan, Google introduced a new structure that separates a service fee from a billing fee for using Google Play Billing, with rates that depend on the purchase type, when the user installed the app, and which programs you join. In India and South Korea, developers can offer an alternative billing system next to Play Billing for a fee 4 percentage points lower. Read the current table on Google's service fees page for each country you sell in.
Your own gateway. For web or physical-goods payments, card processing costs a few percent per transaction plus, in some countries, a small fixed fee. Our Stripe fee calculator and Razorpay fee calculator show the exact cut for your price.
Can you send users to your website to pay?
It depends on the country, and this is the part that changes most often.
- United States. Following the Epic v. Apple case, Apple's guidelines allow apps on the US storefront to include buttons and links to purchase on the web, without a special entitlement. Whether, and how much, Apple may charge on purchases made through those links is still being argued in the courts as of October 2026. Google, after its own case with Epic, now allows external links and alternative billing in the US through its programs, with a service fee still due.
- European Union. Both stores allow alternative payment processing and links to outside offers under the Digital Markets Act, each with its own fees and enrolment.
- India. Google allows alternative billing alongside Play Billing, with the lower fee above. For Apple, the worldwide rules below apply unless it announces India-specific terms, so check its guidelines before you rely on either.
- Elsewhere. A few countries, such as South Korea and Japan, have local laws that led Apple and Google to allow alternatives, usually with a reduced commission still payable. In the rest of the world, Apple's guidelines still forbid buttons or links that steer users to other ways of paying for digital goods.
Everywhere, you can email your own customers about your website's prices; the restrictions are about what appears inside the app.
What does each option do to your margin?
On a US$10 a month subscription, before taxes, as of October 2026:
| Route | Fee | You keep, roughly |
|---|---|---|
| Apple in-app purchase, standard rate, first year | 30% | US$7.00 |
| Apple in-app purchase, Small Business Program or after year one | 15% | US$8.50 |
| Web checkout through a card gateway | About 3% plus a fixed fee | US$9.40 to 9.70 |
On paper, the web always wins. In practice, three things narrow the gap:
- Conversion. An in-app purchase is two taps and Face ID. Leaving the app for a web checkout loses buyers at every step. Fewer sales at a better margin can earn less.
- Work you do not have to do. The stores handle the checkout, receipts, refunds, failed card retries and, in most countries, collecting and paying the sales tax, VAT or GST on the sale. With web payments, all of that is yours.
- Building both. If you sell on the web where allowed and through in-app purchase elsewhere, your backend has to track one subscription across three systems. Services such as RevenueCat exist to do this, at a cost.
Which should you choose?
Selling physical goods or services: your own gateway, always. This is the simplest case and the most common for business apps; how much a mobile app costs lists gateway payments at 40 to 80 hours of work.
Selling digital content or subscriptions, under about US$1 million a year: start with in-app purchase on both stores at the reduced 15 percent rate. Building and maintaining a web checkout, regional link-out rules and entitlement syncing costs more in development than it saves at that revenue, and the 60 to 120 hours for in-app purchases and subscriptions in a cross-platform build is already significant.
Larger digital revenue, mostly in the US or EU: add web payments where the rules allow, keep in-app purchase as the default elsewhere, and budget for the legal review and the extra engineering. Revisit the decision every few months, because the rules are still moving.
B2B software: if companies pay you on invoice for staff accounts, the app can simply let those users sign in, under Apple's enterprise exception. Do not offer consumer sign-up and payment in the app unless you also offer in-app purchase.
Whichever route you take, decide it before design starts, because it shapes the sign-up flow, the backend and the review notes; App Store rejection reasons shows what happens when a payment flow is decided late. Our app cost calculator includes payments and subscriptions as a line item, and the mobile app development guide covers the other decisions that belong in the brief.
Was this guide useful?