esköre™

InsightsMobile App Development13 min readNovember 18, 2026

Stripe or In-App Purchase for Subscriptions? Apple Fees by Storefront in 2026

Stripe can't take payment for digital features sold inside an iPhone app, so most subscriptions go through Apple. This guide sets out the 2026 fees, the open US link-out question and what a web path adds to your build.

Mobile App Development at Eskore
Photo by Unsplash on Unsplash

This guide covers Stripe vs in-app purchase subscriptions and Apple fees by storefront in 2026, so you can pick a payment path before you build. The short version: if a subscription unlocks digital features inside an iPhone app, Apple's rules expect in-app purchase, and Stripe can't take that payment inside the app. The one place this is moving is the United States, where a court case has opened a route to web checkout that is still unresolved. This article sets out the rule, the current fees, the maths on a $10 monthly plan and the build work a web path adds. Rates are as at 17 November 2026.

This is not legal or tax advice. Read Apple's terms yourself, and speak to an accountant or lawyer about your situation before you choose a payment path.

Stripe vs in-app purchase subscriptions: the short answer

Can you use Stripe for subscriptions in an iPhone app? Not for digital features unlocked inside the app. Apple's guidelines require in-app purchase for those. Stripe is for payments taken on the web, and for physical goods and real-world services consumed outside the app.

The US is where the answer has a date on it. The Epic Games v. Apple litigation has produced a proposal that would let US developers send users to a web checkout for a commission of up to 15%. As at 17 November 2026, that proposal is not settled, and the reporting we reviewed says Apple cannot collect the commission until the court approves a fee.

For a US subscription app selling digital features today, the default is in-app purchase on iOS. A web checkout is a separate decision with its own build cost, covered below. For Canadian apps, the US route doesn't apply on our reading of the current rules, and that needs confirming before you commit.

Digital features vs physical goods: where the rule applies

The rule sits in section 3.1.1 of Apple's App Review Guidelines. The wording at the time of writing is:

If you want to unlock features or functionality within your app (by way of example: subscriptions, game currencies, game levels, access to premium content, or unlocking a full version), you must use in-app purchase.

Check the wording on the day you publish, because Apple revises the guidelines. The test is whether the payment gives the user something inside the app. If it does, you are in in-app purchase territory.

Take a $10 monthly subscription to premium training videos played inside the app. The videos are digital and consumed in the app, so the subscription goes through in-app purchase. Now take a Denver HVAC company, a hypothetical example, whose app books and takes payment for a service call at the customer's home next week. That service is delivered in the physical world, so the payment doesn't have to go through Apple. Physical goods work the same way. A box of coffee shipped to the customer sits outside Apple's system.

Mixed apps are where teams get into trouble. A fitness app that sells a membership and also sells a physical programme kit needs those two flows separated in the product, the pricing and the review notes.

Apple's subscription fees in 2026: 30%, 15% and the first-year rule

Apple's standard commission on in-app purchase is 30%. Two things bring it down to 15%:

  • The Small Business Program. Check the programme terms for eligibility.
  • Subscriptions after the first year. The 15% rate applies once a subscriber has a year of paid service. The year is counted per subscriber, not per app or per calendar year. A subscriber who started in March pays 30% for their first year of paid service and 15% after that, whenever your app launched.
Situation Apple commission
Standard rate 30%
Small Business Program 15%
Subscription, first year of paid service (per subscriber) 30%
Subscription, after first year (per subscriber) 15%

Last checked: 17 November 2026, against third-party summaries of Apple's terms. Confirm these figures on Apple's developer pages before you rely on them or model anything. Check how Apple treats lapsed and returning subscribers before you model churn, because the summaries we reviewed don't settle that.

Google Play subscription fees

Our sources disagree. One lists 15% on auto-renewing subscriptions. Another lists 10% plus a 5% billing fee. We have not confirmed either figure against the Play Console fee page, so we are not quoting one here. Check the Play Console directly, note the date, and only then put a number in a model.

Android has its own fee structure, so one price produces different margins on each store. A $10 plan that keeps $8.50 on iOS after year one may keep something quite different on Google Play. Model both stores separately.

Epic Games sued Apple over how the App Store limits developers from telling users about other ways to pay. The Ninth Circuit largely upheld the earlier ruling. It also held that Apple may charge a commission on link-out purchases if the commission is based on costs genuinely and reasonably necessary for coordinating external links, and it sent that question back to the district court. Ashurst's summary of the Ninth Circuit ruling sets out the reasoning.

Apple has since proposed charging US developers up to 15% when a user follows an in-app link and completes a digital purchase on the web. MacRumors reported the 15% proposal. According to TechTimes' reporting on the case, Apple cannot collect a link-out commission until Judge Yvonne Gonzalez Rogers approves a fee. The same reporting says Apple is currently barred from collecting a commission on approved US link-out purchases. The matter has also reached the US Supreme Court, where filings were made in 2026.

Older articles still quote a 27% link-out commission, and that figure is part of the current argument rather than a closed chapter. The same November 2026 reporting says Epic argues a 27% link fee defied the court order, and that the Solicitor General disagrees. The outcome is open. Don't model 27% as a settled rate, and don't treat it as off the table.

Where that leaves a US founder: the reporting says a commission is currently barred and the fee is unresolved. That does not tell you whether a link-out is allowed under the App Review Guidelines on the day you build. The Newly summary we looked at lists the EU, Japan and Brazil as allowing external purchase links and does not mention the US, so we don't rely on it for US status. Check the current conditions in Apple's guidelines and developer documentation, and take legal advice if you plan to depend on a link-out.

A link-out is a set of build steps, not a setting you switch on:

  1. An external link in the app. The link or button must follow Apple's presentation and disclosure rules. Confirm the current conditions in the guidelines before you design the screen.
  2. A web checkout. Your site takes the payment, handles the account, and returns the purchaser to the app.
  3. An entitlement. Your backend records that the user has paid, and the app reads that record to unlock features.
  4. Account and restore handling. The web purchase has to attach to the right app user, and it has to keep working after a reinstall or on a new device.

None of this is a dashboard toggle. It is a web funnel, an entitlement service and a review conversation with Apple, and it should be scoped before anyone writes code. Because the fee is unresolved, build the entitlement layer so it can support more than one path, and don't hard-code a commission into the product.

Canada and other storefronts: check the rules first

The US link-out proposal concerns US storefronts. Newly's guide to external purchase links says the external purchase link is allowed in the EU, Japan and Brazil, and that elsewhere guideline 3.1.1(a) still forbids it. On that reading, Canada is outside the permitted list. Newly is a third-party summary, so confirm this against Apple's current guidelines before you commit. For GTA founders, this is the most important check in this article.

On that reading, a Canadian founder selling digital features should plan on in-app purchase for the App Store. Treat any web checkout as a question to settle with Apple in writing, not as an assumption. Eskore has offices in Toronto and Thornhill, so we work with GTA founders on this question directly.

The UK, UAE, Australia and Singapore are not covered in this article. We have not verified Apple's current rules for those storefronts in this research, so we are not making claims about them yet. Treat them as a follow-up, and check the current guidelines for each one before you plan a launch there. Our London office can take that question on for UK founders as a separate piece of work.

Stripe vs in-app purchase on a $10 monthly plan: the maths

Take a founder in Austin with a $10 monthly plan, selling digital features in a Raleigh-built app. The arithmetic is the same in New York or Denver. The assumptions:

  • US standard rates. Apple's 30% in year one and 15% after year one, per subscriber.
  • Stripe's standard US card rate of 2.9% plus 30 cents per charge.
  • Stripe Billing at 0.7% on one row. Stripe Billing rates conflict across sources, so check Stripe's current US page.
  • The hypothetical link-out row assumes a 15% fee that is not in force.
  • Excludes tax, refunds, chargebacks, support and build costs.
Path Apple or link-out fee Stripe processing You keep
In-app purchase, year one (30%) $3.00 none $7.00
In-app purchase, after year one (15%) $1.50 none $8.50
Web checkout via Stripe none $0.59 $9.41
Web checkout via Stripe, with Billing at 0.7% none $0.66 $9.34
Hypothetical 15% link-out (not in force) $1.50 $0.59 $7.91

Last checked: 17 November 2026. US standard rates; Stripe Billing rate to be confirmed on Stripe's current US page.

On plain Stripe card processing, the saving against in-app purchase is about $2.41 a month in year one and about $0.91 a month after year one. Adding Stripe Billing at 0.7% trims that to about $2.34 and $0.84.

Under the hypothetical 15% link-out, the picture changes. You would keep about $0.91 more than in-app purchase in year one, but after year one you would keep $0.59 less, because the link-out path carries the same 15% fee plus Stripe's card charge.

These are small amounts per subscriber. If 1,000 subscribers were all in their first year, the plain Stripe saving would be about $2,410 a month, before costs. The saving has to cover the engineering, support, refund and chargeback handling, and tax work that a web path adds. Weigh it against those costs, not against the headline fee.

What a web checkout adds to your build

A web checkout is more than a payment button. The work includes:

  • Webhooks from Stripe to your backend for subscription created, renewed, failed, cancelled and refunded events.
  • An entitlement service, so there is one record of who has access and the app reads from it.
  • Restore across devices and reinstalls. Apple's receipts handle this for in-app purchase. Your own system has to handle it for web purchases.
  • One account across iOS and Android. A subscriber who pays on the web needs access on their phone, and any Android purchase has to be honoured in the same record, subject to Google's rules.
  • Billing edge cases: failed-payment retries, plan changes with proration, cancellations, receipts and invoices.

Eskore's mobile app development services cover payments and subscriptions, and our custom software development work covers the backend and payment logic behind them. If the web checkout runs as a separate site, our web development team can build that part too.

Before any build starts, write the payment path down: which purchases use which route, how the entitlement is stored, and what the app shows at each step. If you don't have in-house engineers to own this decision, our guide to fractional CTO work in Toronto explains what that role costs and covers.

Refunds, tax and chargebacks on web billing

With in-app purchase, Apple handles much of the billing and refund process for the purchase. On a web path, that work comes to you:

  • Tax. You take on tax handling for web sales. In Canada that can mean GST or HST. In the US, sales tax rules vary by state and by product type.
  • Refunds and support. Billing questions, refund requests and cancellation queries land in your support queue.
  • Chargebacks. Chargebacks and bank disputes arrive through Stripe and the card networks. You respond with the evidence, and you bear the cost of any dispute you lose.

Ask your accountant about GST, HST and US sales tax before you choose a path. Tax outcomes depend on your structure and location. If you are weighing a US entity for the business, our LLC formation and filings service covers registering a US LLC or a Canadian corporation, and our guide to US LLCs for Canadians in Toronto sets out the tax check to run first. That check should come first either way.

App Review: get a clear answer before you build

Don't expect a clean yes or no from forums. In one Apple developer forum thread on integrating web-based Stripe payments with an iOS app, the reply recommended a session with App Review rather than answering the question directly. Foresight Mobile's article on Base44 and Stripe says apps that use Stripe for digital content get rejected.

Prepare for the review conversation in writing:

  1. Document the app's flow, screen by screen, showing where the user starts a purchase and where they end up.
  2. Record the exact wording of any link, button or message that points to a web purchase.
  3. State the reason for the web checkout: the physical good or real-world service it covers, or the link-out route if that applies to your storefront at the time.
  4. Explain how the entitlement works, so the reviewer can see how web and app access connect.

Send this before the build is locked, not after a rejection.

Moving existing subscribers to web billing

One approach is to let existing Apple subscriptions expire naturally, then offer web resubscription. The steps below are a plan to check against the current guidelines before you act on them:

  1. Decide which subscribers are eligible and when the change applies. Set the cut-off date in writing.
  2. Leave Apple subscriptions running. Don't cancel them on the user's behalf. Let them expire naturally.
  3. Tell users what is changing, in wording that follows the guidelines on how users may be directed to other purchase options.
  4. Offer web resubscription when the Apple subscription ends, and link the web account to the app user.
  5. Prevent duplicate charges. Before creating a web subscription, the entitlement service checks for an active Apple subscription and blocks overlap.
  6. Keep access continuous. A paying user should not lose features during the switch.
  7. Make pricing and cancellation clear on both routes, so users know what they pay and how to stop paying through either one.
  8. Track by cohort, so you can see whether the change works for the users it affects.

Decision checklist: which payment path fits your app

Work through these before you choose:

  • What do you sell? Digital features inside the app use in-app purchase by default. Physical goods and real-world services may sit outside it.
  • Which storefronts do you need? The US and Canada are not treated the same on our reading, and the other priority markets need separate checks.
  • Can you carry the fee in year one and after? Compare 30% and 15% against what the web path saves, after build costs.
  • Do you have build capacity for webhooks, an entitlement service, restore and account linking?
  • Who handles support, refunds, chargebacks and tax?
  • Is there an App Review plan, written down, with a request for a review conversation before the build?
  • Is there an Android plan, with a verified Google Play fee and the same entitlement model?
  • Is there a migration plan for existing subscribers?

If the checklist and the verified rules don't point clearly to a web path, keep in-app purchase as the default.

Settle your Stripe vs in-app purchase path and Apple fees before the build

If you are deciding how Stripe vs in-app purchase subscriptions and Apple fees should work in your app, the payment path is the first decision to make. It shapes the build, the review plan and the maths on every subscriber. If you want independent advice on that choice first, our consultancy and strategy team can talk it through with you.

Eskore sets out written scope, a fixed price and a launch date before work starts. One team covers software, design, cloud and marketing, so the app, the backend and the payments are planned together, and you own the code and the accounts. We won't promise savings. We will work through the maths on your own numbers, and you can browse our case studies for more context. Book a free 30-minute scoping call to settle your payment path before any code is written.

Questions

Need help with this?

Talk to our mobile app development team.