EU Digital Markets Act and iOS payments in 2026: what subscription developers need to know

Apple's DMA compliance framework has created a genuinely different commercial environment for EU subscription apps — alternative payment processors, a new commission structure, and web linkout rights. This guide breaks down the new mechanics and offers a decision framework for whether switching away from Apple IAP is worth it for your app.

The EU Digital Markets Act (DMA) took effect for Apple in March 2024, and by 2026 the consequences for subscription iOS developers have become concrete and complex. If you distribute apps in the European Economic Area (EEA), you now face a genuinely different commercial environment — alternative payment processors, a new commission structure, and linkout-to-web rights that didn't exist two years ago.

This post walks through the DMA's practical impact on iOS subscription pricing and payment mechanics. It won't advocate for any particular path — the right choice depends heavily on your app's revenue, user base, and risk tolerance — but it will lay out the facts so you can make an informed call.

What the DMA actually changed for iOS subscription developers

The DMA designates Apple as a "gatekeeper" for the App Store. As a gatekeeper, Apple must allow:

1. Alternative app marketplaces on iOS devices in the EU
2. Alternative payment processors for in-app purchases in EU apps
3. Linkout rights — the ability to link users to an external website to complete payment

Apple implemented these under protest, designing its compliance framework around the Core Technology Fee (CTF) and a revised commission structure that critics argue preserves most of its economic advantage. Regardless of your view on Apple's intent, the practical mechanics are what you need to understand as a subscription developer.

The Core Technology Fee

Apple charges a CTF of €0.50 per first annual install after the first 1 million installs per year, across all apps distributed on any iOS marketplace — including Apple's own. For most indie developers, 1 million installs is a ceiling they'll never hit, making the CTF irrelevant in practice. For large-scale subscription apps — utilities, language learning, fitness — it becomes a real line item to model into your unit economics before choosing any distribution path.

Commission rates: the new math

Under Apple's DMA compliance framework, EU-distributed apps can choose from several commission tracks. The table below summarises the key paths and their approximate total costs:

SBP = Apple's Small Business Program, available to developers earning under $1M/year from Apple platforms.

The 13-percentage-point gap between the 30% default and the alternative-processor path sounds appealing. But it comes with upfront engineering cost, ongoing payment liability, and the loss of features like Billing Grace Period and Billing Retry that Apple IAP handles automatically. Analysis from app analytics firms consistently points to payment failure as one of the largest drivers of involuntary churn — losing Apple's retry logic is a concrete revenue cost, not a theoretical one.

StoreKit and alternative payments: the technical reality

Apple's alternative payment entitlement for the EEA requires a special entitlement applied for in App Store Connect, plus EU-specific code paths in your app. In practice, that means:

• Detecting the user's storefront using StoreKit's Storefront API to identify EEA purchases
• Routing EEA users to your alternative payment flow or to a web checkout linkout
• Building or integrating your own subscription lifecycle management — renewals, upgrade and downgrade flows, cancellation handling
• Handling EU VAT yourself, since Apple acts as Merchant of Record for standard IAP but not for alternative payment flows

Web linkout: the lower-cost middle path

The linkout right — placing a button in your EEA app that opens your website's checkout page — is the lower-engineering-cost option for developers already selling subscriptions on the web. Users tap the link, complete purchase on your site, and return to the app with an active entitlement.

Apple charges 17% (or 10% under SBP) on purchases attributable to in-app links. If you're already managing web subscriptions through Paddle, RevenueCat's web billing, or Stripe, the incremental engineering work centres on three things:

1. Detecting EEA storefronts and conditionally surfacing the linkout button in your paywall
2. Entitling the user inside the app after a completed web purchase — typically via an entitlement backend or a cross-platform SDK such as RevenueCat
3. Ensuring App Review can verify the linkout is clearly and honestly labelled

One constraint applies regardless of payment path: App Store Review Guideline 3.1.3 still prohibits pricing your in-app offering higher than your external offering when you use a linkout. If you run EEA-specific web promotions, you'll need to match or beat that price inside the app, or use a promotional offer to bridge the gap. The post on App Store pricing parity: should your iOS price match your web price? covers the global mechanics of this rule in more detail.

Decision framework: should you actually switch?

For most indie developers in 2026, the honest answer is: not yet. Here is a decision matrix based on developer profile and EEA revenue share that applies directional guidance — your specific numbers will determine the break-even point.

The most common mistake is over-indexing on the commission percentage while ignoring hidden costs. Analysis from app growth consultants suggests involuntary churn — payment failures, card expiry, billing errors — can account for a substantial share of total subscription churn, particularly in markets with lower card reliability. Apple's grace period and billing retry infrastructure suppresses much of this automatically. Before switching, instrument your current EEA involuntary churn rate as a baseline so you can model what you're giving up.

For a detailed look at how Apple's grace period and retry mechanics work, see the post on iOS subscription grace periods and billing retry: how Apple handles failed renewals.

What to watch in the second half of 2026

The DMA enforcement picture is still developing. Three things worth monitoring closely:

• European Commission investigations. The Commission opened proceedings against Apple's DMA compliance in early 2024, citing concerns about the CTF and the alternative marketplace design. Findings could force further changes to Apple's fee structure — potentially reducing the commission charged on the alternative-processor path.
• Payment provider tooling. Stripe and Paddle are both actively improving their EU-specific iOS payment tooling. A six-month wait may mean significantly simpler integration paths than exist today, reducing the engineering cost argument against switching.
• National court rulings. Parallel proceedings in Germany, France, and the Netherlands may produce requirements that diverge from the EC's position, creating a patchwork compliance challenge for apps with large EU footprints across multiple member states.

The prudent near-term move for most subscription developers is to instrument your EEA revenue share now — App Store Connect's territory breakdowns in Sales and Trends reports can give you the baseline — and revisit the build decision every quarter as the regulatory and tooling picture evolves. The commission maths can shift quickly if the EC findings go against Apple, and you want your data ready before that decision is forced on you.

Sources and further reading

• Apple Developer — DMA and apps in the EU
• Apple App Store Review Guidelines (section 3.1.3 covers linkout and alternative payment rules)
• Apple Developer Documentation — StoreKit Storefront API
• European Commission — Digital Markets Act: ensuring fair and open digital markets
• RevenueCat Blog — subscription lifecycle management and cross-platform billing guidance
• Paddle Blog — Merchant of Record, EU VAT compliance, and app developer payments