In-app vs out-of-app billing in 2026: store billing or Stripe

TL;DR
In-app vs out-of-app billing in 2026 is a choice per platform and country. A $9.99 monthly US subscription nets very different amounts by route, read on November 12, 2026:
- Apple In-App Purchase nets $6.99 in a subscriber's first year and $8.49 after, or $8.49 from day one in the Small Business Program.
- Google Play billing nets $8.49 in the US, UK and EEA: a 10% service fee plus a 5% billing fee.
- Stripe on Android through Google's alternative billing or external links nets about $8.33, because Google's 10% still applies and card fees come on top.
- A Stripe web checkout linked from a US iOS app nets about $9.33 today. Apple charges no commission on those sales while a court sets the rate, and Apple has proposed 10% for subscription renewals.
- Music and publishing apps can use Apple's reader app route instead: one link to your own site.
The fee is only half the decision
Every billing comparison starts with the commission. Stripe's own guide puts in-app billing at 15% to 30% per transaction. But the route also decides who owns the subscriber: who sees the email address, who handles refunds, who runs win-back offers and who can move the subscriber to the web.
In-app purchase keeps all of that inside Apple and Google, and it is the smoothest checkout a phone has. Out-of-app billing gives you the customer record and lower fees, at the cost of a browser step. For health apps, where HIPAA and PCI add their own rules, see our healthcare app payments guide. This guide covers music and subscription publishing.
Google charges 10% on every subscription route since June 30, 2026
Google's June 24, 2026 announcement set a 10% service fee on auto-renewing subscriptions regardless of whether you use Google Play billing, alternative billing or external web links. Google Play billing adds a 5% billing fee in the US, UK and EEA. The rollout began June 30, 2026 in those regions.
Leaving Google's checkout no longer removes Google's cut. Its US alternative billing page says enrolled developers must report transactions and pay the service fee from October 1, 2026, reporting each US transaction within 24 hours.
Apple moved the other way in the US. Guideline 3.1.1(a) lets US storefront apps include buttons and external links to other purchase methods without an entitlement. Apple currently charges no commission on those US sales while the court sets a rate, per AppCoding. On August 13, 2026 Apple proposed 15% for standard apps and 10% for subscription renewals. No rate is set as of November 12, 2026.
How we built this guide
- Fees come from Apple, Google and Stripe pages, read on November 12, 2026. Net amounts are our arithmetic in US dollars, before taxes.
- Court status comes from two trade reports, dated August 14 and October 10, 2026. Recheck before you launch.
- The buyer patterns come from Mercury's presales records for music and subscription publishing accounts, aggregated and unnamed.
This is a reading of published rules, not legal advice.
The billing routes at a glance
| Route | Where it applies | Platform fee on subscriptions | Payment processing |
|---|---|---|---|
| Apple In-App Purchase | Worldwide | 30% in year one, 15% after; 15% in the Small Business Program | Included |
| Apple US link-out to web checkout | US storefront | 0% today; rate pending in court | Your processor, e.g. Stripe |
| Apple reader app link | Worldwide, reader apps only | No in-app purchase allowed | Your processor on your site |
| Google Play billing | US, UK, EEA rates since June 30, 2026 | 10% service fee plus 5% billing fee | Included |
| Google alternative billing or external link | US program | 10% service fee | Your processor |
| Web checkout only | Your site | None | Your processor |
What a $9.99 subscription nets on each route
Stripe's pricing is 2.9% plus 30 cents per US card charge, and Stripe Billing adds 0.7% of billing volume. Apple's subscription page pays 70% in a subscriber's first year and 85% after, and the Small Business Program pays 85% from day one under $1 million a year.
| Route | Deductions on $9.99 | Net |
|---|---|---|
| Apple IAP, year one | 30% | $6.99 |
| Apple IAP, after year one or Small Business Program | 15% | $8.49 |
| Google Play billing | 10% + 5% | $8.49 |
| Google external or alternative billing with Stripe | 10% + 2.9% + $0.30 + 0.7% | about $8.33 |
| Apple US link-out with Stripe, today | 2.9% + $0.30 + 0.7% | about $9.33 |
| Apple US link-out at Apple's proposed 10% | 10% + Stripe fees | about $8.33 |
Two things stand out. On Android, leaving Google Play billing saves nothing at $9.99: Google's 10% stays, and Stripe's fixed 30 cents costs more than Google's 5% billing fee. And price level changes the answer. On a $99.99 annual plan, Stripe's fees come to about $3.90, and the web nets about $96.09 against $69.99 through Apple IAP in year one.
Reader apps: the route built for music and publishing
Apple's reader app rules cover apps whose primary function is magazines, newspapers, books, audio, music or video. A reader app can let people use content they bought elsewhere and, with the External Link Account Entitlement, link once to your own site to create or manage an account.
The conditions are strict. The app must not offer in-app purchases on iOS, iPadOS or tvOS while it uses the entitlement. The link opens the default browser, not a web view, goes straight to your site without redirects, and carries no extra URL parameters. Each tap shows Apple's interstitial sheet first. Apple's page adds that from October 1, 2026, reader apps distributed in the EU may promote out-of-app offers without an actionable link.
For a music service or a publication with an established web audience, this is the route with no Apple fee. You trade away the one-tap purchase inside the app.
Publishers comparing ready-made paywalls can start with our guide to paywall services.
One subscriber, three billing systems
Most music and publishing services end up with more than one route: Apple IAP for impulse sign-ups, Google Play billing on Android, Stripe for the web. The billing systems do not talk to each other, so your backend must.
- One account ID. Map each Stripe customer, Apple transaction and Google purchase to the same user.
- One entitlement record. Store what the user can access, updated from all three sources. Apple's In-App Purchase page points to App Store Server Notifications for near-real-time refund and subscription status.
- One place to manage. A subscriber who bought on iPhone cancels in Apple's settings, not on your site. Show each user where their subscription lives.
- No double billing. Before showing a paywall, check every source. A web subscriber who opens the app should see the content, not an offer.
Stripe's mobile digital goods guide covers the Stripe side: Checkout in the browser for US iOS apps, in-app card payments for US Android apps, and a hosted customer portal for subscription management.
What the rest of a subscriber stack costs as the audience grows is covered in our guide to the subscription app tech stack.
When Stripe is the only option
Apple and Google collect money from buyers. They do not pay your artists, writers or creators. If your model is two-sided, where fans pay and artists also pay or get paid, the payout side needs your own processor and a payout system, whatever route collects the subscription.
Physical goods follow different rules: Stripe's mobile guide notes you can accept payments for them in the app with Stripe, on both platforms.
Which creator payment flows Apple still rejects is covered in our guide to the guideline 3.1.1 rejection.
What music and publishing buyers bring us
Mercury's presales records hold a group of music, audio and subscription publishing accounts: streaming platforms, a music discovery network, an AI voice app and a paid publication.
- Every account planned to take money from the first release.
- Around 50% already had or were adding web billing on Stripe next to the store apps.
That is where the friction sat. One buyer had a Stripe subscription on its website and needed in-app subscriptions on iOS and Android to coexist with it, and that conflict became an objection in the deal. Another wanted fans to pay for discovery and artists to pay for visibility, with the platform moving money in and out. Neither question was about fees. Both were about one account across several billing systems.
Keep the account, rent the checkout
Our view: decide where the subscriber account lives before you pick a checkout. Put it on your backend, tied to your own user ID, and treat Apple, Google and Stripe as checkouts that feed it. Then choose routes per platform with the math above, and revisit each time a fee or a court ruling moves.
Mercury Development has built apps since 1999 with 500+ engineers. For Grant's, the financial journal, Mercury redesigned the phone and tablet apps, including payment gateway integration for client-side PCI compliance. For Muzic Swipe, Mercury built a music discovery platform from concept to launch across mobile and web.
Written by Rob Devereaux, Chief Operating Officer at Mercury Development. Rob has run the firm's operations from Hudson, Ohio since 2019 and has over 20 years of operational and financial experience. The presales records behind this article's music and publishing buyer section sit in the operations he oversees.
Send us your pricing and we will map the billing routes
Tell us your plans, prices and where subscribers sign up today. We will map the net revenue per route and per platform, and the account design that keeps every subscriber in one place.