Apple’s old model may have had strict rules, but at least it had clarity. In 2026, the days of predictable 15% or 30% are over: after EU regulators enforced the Digital Markets Act (DMA), Apple replaced its flat commission with a system where the final cost is shaped by the payment path you choose and how your app is distributed.
Apple also now formally allows external payments, but only under defined frameworks. Depending on whether you link out, sell in-app, or distribute outside the store entirely, you’ll face different combinations of costs, rules, and reporting burdens.
So in the EU, there’s no single Apple fee anymore. And the structure has already been rebuilt twice this year: a layered model of stacking fees took effect in January, and on August 18 Apple replaced it with a single set of business terms for every EU developer — eliminating the Core Technology Fee, the Initial Acquisition Fee and the Store Services Fee, and setting one rate per payment path. Developers can sign the new terms now; they take effect October 1.
In this article, we break down how the new fee structure works, why alternative payment methods are not always cheaper in practice, and what materially changed for developers as the new system took effect in 2026.
How Apple App Store fees work in 2026: The old model vs the new reality
With the new fee system, what a developer pays depends on two things:
- where the payment happens — Apple In-App Purchase, alternative processing inside the app, or your own checkout on the web
- how the app is distributed — the App Store, an alternative marketplace, or your own website
On paper, there’s more flexibility than ever — in-app purchases, external payments, outbound links, alternative distribution. In practice, each option carries its own rate, its own rules, and its own operational weight.
| Before (pre-DMA) | After (post-DMA, EU) |
|---|---|
| Single commission (15–30%) | One commission per payment path (5–26%) |
| Same rules globally | Region-specific logic (EU ≠ US ≠ Japan ≠ Brazil ≠ ROW) |
| Simple developer obligations | Complex reporting and compliance requirements |
| Switch your setup whenever you want | Payment options locked in for 12 months |
| % fee easy to model and forecast | Rate is knowable, but real cost depends on your own stack |
How App Store fees changed in 2026
What triggered all this? In short: regulation.
The shift began in Europe, where the Digital Markets Act forced Apple to open up its ecosystem, allowing alternative payments, external links, and alternative distribution. The first version of Apple’s response was a menu of tightly scoped options, each with its own pricing and constraints. The second version, announced in August, collapsed that menu into one set of terms — simpler to read, but with a commitment attached.
As a result, developers no longer choose whether to pay Apple — they choose what to pay for, and for how long.
How that plays out in practice depends heavily on where your users are. The EU, US, Japan and Brazil now each operate under a different regulatory framework with different rules, fee structures, and trade-offs.
External payments don’t mean that App Store fees are gone
The introduction of external payments is often seen as a major win for EU developers. But can they flip the switch and return to clean, predictable economics? Not quite.
External payments aren’t an exit from Apple’s system, but an entry into a more complex configuration of it. What you gain in flexibility, you pay for in complexity:
- engineering overhead — separate payment flows, maintenance, fraud prevention, ongoing updates
- legal and compliance burden — local regulations, reporting, and liability for payments
- UX friction — leaving the native App Store flow, lower conversion rates, and trust concerns
So while the structure may look more open, the reality is that most choices come with hidden downsides that cancel out the savings.
Let’s look at how Apple EU App Store fees are structured from October 1:
| Payment path | Standard rate | Reduced rate |
|---|---|---|
| App Store with Apple In-App Purchase | 26% | 15% |
| App Store with alternative payment processing in the app | 20% | 10% |
| App Store with a link out to your own checkout | 15% | 10% |
| Distribution via alternative marketplace or the web | 5% Core Technology Commission | — |
The reduced rate applies to the App Store Small Business Program, the Mini Apps Partner Program and the Video Partner Program — and, on In-App Purchase, to auto-renewing subscriptions after their first year.
Two distinctions worth making explicit, because they get conflated constantly:
The 5% Core Technology Commission is about distribution, not payment. It applies to apps distributed outside the App Store. It is not the rate for selling on the web from an App Store app — that’s 15%.
Traffic that never touches the app isn’t Apple’s business at all. A user who arrives from an ad, pays on your web checkout, then downloads your app and signs in carries no store commission, no CTC and no reporting obligation. Every rate in the table above describes a purchase that starts inside the app.
To put the rest in context: per Apple’s own data, 88% of EU developers pay no commission at all, and 75% are on the Small Business Program with reduced rates. The standard-rate debate only matters for the minority operating outside those programs.
And even for that minority, the added engineering, compliance, and UX costs often erase the difference. Apple’s November 2025 analysis found that more than 90% of developers who switched to alternative terms did not pass commission savings to consumers: prices stayed the same or increased.
What the August terms changed beyond the rates
In-App Purchase can now sit alongside alternative payment options. In the EU this wasn’t previously permitted — it was one or the other. Now both can appear on the same paywall, subject to Apple’s presentation requirements. For teams that have spent two years arguing about which converts better, this is the first chance to actually measure it.
But your setup is locked for 12 months. Developers select their payment options — In-App Purchase, alternative processing in the app, linking out, or a combination — and must maintain that selection for a year. This is the one decision in the release with a hard deadline and a real cost to getting wrong.
Link-outs are restricted for young audiences. Apps in the Kids category can’t link out to a website to complete a transaction. For users under 18, alternative payment processing and link-outs require a parental gate. For users under 13, linking out for transactions isn’t allowed at all. In EU member states that require parental consent above 13, the protections scale accordingly.
If your audience skews young, this isn’t a fee question — it’s a question of whether the web path is available to you at all.
More companies qualify to distribute outside the App Store. Eligibility to operate an alternative marketplace or distribute via the web now includes a moderate financial-stability score from Dun & Bradstreet, being publicly traded or owned by a public company, venture funding from an established firm, a completed audit by a licensed accountant, or being a government entity, educational institution or nonprofit. Notarization is still required for every alternatively distributed app.
What this means for subscription apps specifically
Here’s the arithmetic worth doing before you pick a setup:
| Scenario | Apple In-App Purchase | Link out to your checkout | Gap |
|---|---|---|---|
| Standard developer, year 1 | 26% | 15% | 11 points |
| Standard developer, year 2+ | 15% | 15% | none |
| Small Business Program, any year | 15% | 15% | none |
For a subscription business, the fee advantage of linking out lives almost entirely in the first year of each subscriber’s life. After that Apple charges the same either way, and for Small Business Program members it’s the same from day one. Add your own processing, tax, fraud and support costs on top, plus the conversion lost sending someone out of a native flow, and a 15% link-out can land close to what In-App Purchase costs.
Which is why the percentage was never the real argument.
The systemic consequence: Monetization is now fragmented by region
Even if you stick to in-app purchases, the landscape has changed: monetization rules now vary by region, and the same app no longer runs on a single economic model.
In the EU, developers now sit under a single set of business terms — but with rates that differ by payment path, a 12-month commitment, and restrictions tied to audience age. The European Commission said on August 18 that it welcomes the changes and is monitoring them, and indicated periodic fines aren’t currently on the table, which effectively closes a dispute that produced a €500 million fine in April 2025. Epic called the new rates junk fees and argued that accepting them hollows out the DMA.
In the US, the situation is still in legal flux — and still the cheapest link-out anywhere. Since April 2025, developers can include external payment links without Apple charging any commission, a result of the Epic v. Apple ruling. The Ninth Circuit upheld the contempt finding but declined to bar commissions permanently, saying any rate should reflect Apple’s actual costs. The Supreme Court took up a narrow question on the civil contempt standard on June 30, with Apple’s merits briefing due September 14. And on August 14, Apple told the district court what it wants: 15% standard, 10% for partner programs, 5% for Small Business Program members. Those rates can’t be charged until the court approves them. The commission-free window is still open — but you can now see the number on the other side of it.
Japan is a third regulated market: the Mobile Software Competition Act took effect on December 18, 2025, opening alternative marketplaces, third-party payments, and external link-outs. The rates differ from the EU — standard In-App Purchase came down to 26% (21% commission plus 5% payment processing), 21% for alternative payments inside the app, 15% Store Services on transactions completed on an external site within seven days of the tap, and 5% Core Technology Commission for alternative marketplaces. Alternative marketplaces are already live: Epic Games Store and AltStore launched in Japan in January 2026.
Brazil is the newest addition, and the easiest to miss. Under an agreement with the competition regulator CADE announced in June, developers can distribute apps through alternative marketplaces, operate marketplaces themselves, offer out-of-app promotions, and process payments outside In-App Purchase, beginning with iOS 26.5.
China isn’t a DMA story, but it moved in the same direction: from March 15, 2026, the standard rate on the China mainland storefront dropped from 30% to 25%, and the reduced rate — Small Business Program, Mini Apps Partner Program, and auto-renewals after the first year — went from 15% to 12%.
The UK is moving the same way but hasn’t arrived yet. Apple was designated with Strategic Market Status in October 2025, and the first CMA commitments — fairer app review, ranking transparency — took effect April 1, 2026. Commission fees weren’t addressed: UK developers still pay 15–30%. The CMA consulted on steering requirements through July 28 and says it will decide later this year, with the stated expectation that any steering fee should be lower than the store’s own commission.
As a result, a single product is forced to maintain multiple parallel monetization stacks. Payment flows, fees, legal terms, and even UX decisions are now made region by region, rather than globally, and this changes how the business operates:
- Analytics — metrics aren’t directly comparable
- Processes — more exceptions, manual decisions, and coordination overhead
- Decision speed — every experiment requires regional context
How the new App Store fees and rules impact subscription apps
LTV becomes harder to predict
For subscription businesses, predictability has always been a strength, but in 2026, two users of the same product can bring in different revenue depending on region or payment flow.
Commissions, App Store fees, and operating costs now differ across regions and setups. As a result:
- subscription LTV is no longer stable or comparable across regions
- financial models need regional context
- forecasting errors grow with scale
Put simply, new Apple EU App Store fees and payment rules add more variables to how revenue plays out over time, making financial planning less certain and forcing more scenario-based thinking, even when the product remains the same.
Margin pressure on paid acquisition
Paid acquisition already ran on thin margins, and in 2026, they’re even thinner. CAC keeps rising, while Apple’s new fee structure adds complexity and delays clarity.
This creates a risky combination: higher user acquisition costs, delayed visibility into real net revenue, and monetization choices that reveal their real effect too late.
For subscription apps, these dynamics can gradually squeeze profitability and weaken the economics of key acquisition channels.
Slower experimentation inside in-app
As payment and compliance setups become more complex, the room to experiment shrinks. In practice, this leads to tighter constraints on pricing tests, less flexibility in combining offers, and longer cycles from idea to production. From October 1, there’s a 12-month commitment on your payment configuration on top of that.
Experimentation is still possible, but slower, harder to execute, and more expensive.
Operational overhead becomes permanent
What used to be a one-time setup has turned into an ongoing cost of doing business: legal reviews, compliance and local requirements, monthly payment reporting, and region-specific monetization configurations.
This change creates a lasting drag on speed and execution, which is especially painful for subscription teams that depend on fast iteration and operational efficiency.
Exposure to sudden rule changes
What’s allowed today might be blocked tomorrow or priced differently. The EU fee structure was rebuilt twice in eight months. For apps operating across multiple regions, this volatility creates risks that can’t be mitigated by product work alone. It forces structural decisions about where monetization happens, how revenue flows are built, and how quickly the team can adapt when the rules shift.
How leading teams handle Apple’s new monetization rules: 3 strategies
Once the emotional response to Apple’s new fees fades, teams face a single question: how to adapt without hurting the business. The market is settling on a few strategic paths — none perfect, but each solving a different part of the equation.
1. Absorb fees
One way to handle Apple’s new fee structure is to accept it and rebalance your margins elsewhere. This usually means one of two things: raising prices to protect profitability which can hurt conversion rates, or absorbing the costs. To make up for it, teams have to improve retention, increase prices, add upsells, or cut acquisition costs just to keep the same level of revenue.
With 15% on auto-renewals, this is more defensible than it was in the spring. It’s still a strategy for survival, not for growth.
2. Localize monetization
You can go further and localize monetization by region: different paywalls, different payment paths, and different pricing and product decisions.
From an economic perspective, this can be effective. Operationally, it adds weight:
- more complexity in code and UX
- internal processes require special rules for different markets
- higher costs of support and mistakes
The approach is viable, but only for teams ready to handle the added complexity at scale. With six regulatory regimes in play, it’s also less optional than it was.
3. Add web-based monetization
Teams are increasingly turning to the web monetization to take control of how offers are structured, how users pay, and how revenue is captured. This approach provides:
- direct payment methods outside the App Store,
- full control over pricing and paywall logic,
- faster testing and iteration,
- and long-term independence from platform constraints.
Note what’s no longer top of that list: a large fee saving. In the EU, that argument now only holds for first-year subscribers on standard terms. The reasons to do it are the other three.
| Strategy | Description | Pros | Tradeoffs / Risks |
|---|---|---|---|
| Absorb fees | Keep in-app monetization, accept new Apple fees | Simple setup, stable UX | Lower margins, less flexibility, scaling limits |
| Localize monetization | Adapt pricing and flows by region | Higher relevance, can improve margins | High operational cost, harder to maintain |
| Add web layer | Shift pricing, billing, and experiments to the web | Faster iteration, more control, higher LTV | Requires infrastructure and clear data model |
Monetization strategies in 2026 side by side
What web2app brings to your monetization stack in 2026
1. Additional monetization layer to reduce dependency on a single channel
Instead of relying on in-app flows, you can shift acquisition, onboarding, billing, retention mechanics to the web, where you have more control and fewer constraints. And worth repeating: traffic that goes from an ad straight to your web checkout carries no store commission at all. That isn’t a link-out — it’s your own funnel.
Case: Glam AI — more control + fewer store fees
A good example is Glam AI, a subscription-based AI app with relatively low ARPU. For products like this, a 30% store fee is a direct margin pressure. The team moved part of their monetization and experimentation to the web with FunnelFox.
The result: higher margins through reduced fees, faster onboarding tests, and more control without engineering work.
2. Faster pricing, offer, and billing experiments
One of the key advantages of web2app is speed. Web funnels make it possible to test pricing, onboarding, and offers without app review constraints, in-app mechanics, or long release cycles.
In the Glam AI example:
- the first web2app flow was launched in a single day
- new creative and onboarding hypotheses were tested in parallel
- new team members reached productivity within 1–2 weeks
In 2026, where rules vary by region and your in-app payment setup is committed for a year at a time, this kind of operational agility becomes a core growth lever.
3. More control over offers and lifecycle moments
Web2app doesn’t stop at payments. It also lets you design key lifecycle moments as product decisions rather than accept them as system constraints.
For example, you can:
- build personalized paywalls with custom logic for regions, cohorts, or entry points
- set up automated payment retries and manage chargebacks with full control
- design custom cancellation flows to reduce churn
4. A hedge against platform and policy risk
Finally, web2app acts as a strategic hedge. When your entire monetization strategy depends on one store, one platform, and one set of shifting rules, you’re building on unstable ground. Two rebuilds of the EU fee structure in eight months is the argument.
Web2app gives you:
- an independent payment and pricing infrastructure you fully control
- a way to adapt faster to regional rule changes without rewriting your app
- long-term resilience by decoupling business logic from platform constraints
Here’s how web2app compares to other monetization setups in 2026:
| Capability / constraint | In-app | Link out from the app | Web2app |
|---|---|---|---|
| Store fee (EU, from Oct 1) | 26%, or 15% on auto-renewals and reduced programs | 15%, or 10% on reduced programs | none — the purchase never touches the app |
| Speed of experimentation | Low — tied to app review, and a 12-month payment commitment | Medium — needs legal/ops alignment | High — launch in hours, quick iterations |
| Setup complexity | Low | High — requires infra, legal, monthly reporting | Low — pre-built blocks, no code needed |
| Offer & billing flexibility | Limited by SDK & native flow | Depends on custom build | Full — pricing, paywalls, checkout, retries, cancellation logic |
| Control over user journey | Minimal — store-owned UX | Fragmented | Full control — acquisition to churn |
| Young-audience restrictions | None | Kids category blocked, under-13 blocked, under-18 parental gate | None |
| Risk exposure (policy, fees) | High — fully coupled with App Store | High — subject to audits & rule shifts | Low — independent stack with fallback options |
Where FunnelFox fits in
FunnelFox helps mobile teams take control of their acquisition and monetization and brings together two key components: a web2app funnel builder for fast launches and experimentation, and a modern billing infrastructure for full control over subscriptions, payments, and revenue recovery.
With FunnelFox, you can reduce reliance on App Store flows and get more revenue without adding engineering overhead. Whether it’s launching region-specific offers, adapting pricing without release cycles, or managing churn with alternatives to cancellation, FunnelFox gives you the tools to act quickly and build a more profitable, controllable monetization stack.
In 2026, the winners are not those chasing the lowest percentage, but those who diversify payment flows instead of defaulting to in-app and preserve control points for pricing, billing, and experiments. And FunnelFox is how you get it.
Looking to diversify beyond in-app and protect your revenue? Book a demo.
Final takeaway: Structure beats percentage
The real question in 2026 isn’t how much Apple takes — it’s how your monetization is structured, and what that structure enables. Costs now show up not just in percentages, but also in slower launches, tighter margins, and fewer options to adapt.
Apple just cut its EU link-out rate to 15% — and set In-App Purchase on auto-renewals to the same 15%. For a subscription business, the fee gap between selling in the app and selling on your own site has largely closed. If the only reason you were building a web layer was Apple’s cut, the case got thinner. If the reason was control, it got stronger.
That’s why strong teams don’t optimize for the lowest cut. They design for control, flexibility, and speed, and increasingly the web is where they build it.
You have until October 1 to pick your in-app payment setup. You’ll live with it for twelve months.
