Alternative Payments on iOS: Two Years In, the Economics Are Clear

Apple's DMA mandate and US court-ordered payment links gave iOS developers real alternatives in 2024. Two years on, the picture is clear: big platforms win, indie developers should focus elsewhere.

Since early 2024, the App Store’s fee structure has been under sustained legal and regulatory pressure. The EU’s Digital Markets Act forced Apple to offer alternative distribution and payment options in Europe. A US federal court order gave American developers the right to link users to external payment pages. Two years on, the developer community has real-world experience with both frameworks. The headline finding: alternative payments on iOS are a genuine win for large-scale consumer apps with existing payment infrastructure  — but offer little practical benefit, and some real risk, for the typical indie subscription developer.

What alternative payments actually cost in 2026

Apple’s DMA compliance framework for the EU is often summarized as “lower fees,” but the details matter. Developers who remain on the App Store with an alternative payment processor in the EU still pay a reduced 17% commission (versus the standard 30%). Those who choose to distribute outside the App Store through third-party marketplaces can drop that to 0% commission — but the Core Technology Fee (CTF) kicks in: €0.50 per install per year once an app exceeds one million installs annually. For most indie developers that threshold is never reached. For apps with genuine scale it becomes a meaningful variable cost that needs careful modelling before committing to an external distribution strategy.

In the United States, the situation is arguably less favorable. The 2024 federal court injunction requires Apple to allow external purchase links, but Apple’s rules specify that purchases completed through those links still incur a 27% Apple commission, reported and paid by the developer. The math works out poorly: you’re running your own payment processor (Stripe adds roughly 2.9% + $0.30 per transaction), managing renewals, refunds, and subscription state yourself — and saving just three percentage points versus the standard 30%. For most subscription apps charging under $20/month, that saving is trivially small against the engineering and support cost.

The real fee picture at a glance

The Small Business Program — 15% commission for developers earning under $1M/year from Apple — remains the single biggest fee reduction available to indie developers. It requires zero engineering work.

Who is actually winning with alternative payments

The developers publicly leveraging alternative payments share a clear profile: large consumer platforms with millions of users, brand recognition that overcomes trust friction outside the native payment sheet, and dedicated payment infrastructure teams. According to public announcements, major streaming and creator-platform companies moved quickly to add external purchase links in the US after the injunction, redirecting subscription sign-ups to their own web flows. This works for them because a significant share of their users begin on desktop or web — the App Store is a distribution channel, not their primary acquisition funnel.

For an indie app, the dynamics are meaningfully different. Your user discovered you on the App Store. They trust the familiar Apple payment sheet. Routing them out to Safari to complete a purchase introduces measurable friction that typically hurts conversion rates — and conversion rate is the dominant variable in subscription economics, upstream of everything else.

Reports from developers who have experimented with external links describe the same pattern: power users who already know the product complete the off-App-Store purchase; new users and casual browsers drop off at the redirect. The segment most likely to convert via the cheaper payment path is also the segment least sensitive to price in the first place.

The higher-ROI levers for indie developers

The alternative-payments story attracts attention because it involves large companies in court and regulatory bodies issuing mandates. But for most app builders, the higher-return moves lie elsewhere.

Purchasing Power Parity pricing remains dramatically underused. Apple’s regional price tiers let developers set prices specific to 175+ territories. In markets like Brazil, India, Mexico, Turkey, and Southeast Asia, pricing at local PPP equivalence can lift conversion rates substantially compared to charging full US prices in every market. A developer shipping at $9.99/month globally, without localized pricing, is leaving revenue on the table in every emerging market simultaneously — no legal filing required to fix it.

Subscription recovery flows — grace periods, billing retry logic, and App Store in-app messaging for lapsed payments — are a proven tool for reducing involuntary churn. StoreKit handles all of this natively; no external payment infrastructure needed.

Localized App Store metadata and screenshots affect conversion before the subscription decision is even reached. Markets with localized screenshots and keyword metadata consistently outperform English-only listings in browse and search. If you’re shipping to ten or more territories without localized assets, the gap compounds with scale. See how localization cost breaks down for App Store metadata.

The bottom line: understanding alternative payments is worthwhile — especially if you already operate web subscriptions or are targeting EU users at meaningful scale. But for the typical indie iOS developer, Apple’s fee structure is not the binding constraint on subscription economics. Conversion, retention, and market reach are  — and all three are addressable without rebuilding your payment stack.

Sources and further reading

• Apple Developer — App Store policies and Core Technology Fee documentation
• Apple Small Business Program
• RevenueCat Blog — subscription economics and SDK updates
• CourtListener — Epic v. Apple case docket and court orders