Stripe poised to capture $8-10B iOS GMV

This is less a new product launch than a sudden route change in who gets paid on iOS. If Apple can no longer force digital purchases through its own billing, a slice of app revenue that used to disappear into App Store commissions can move onto standard card rails, where Stripe already has the checkout, iOS SDK, and merchant relationships to capture it. At Stripe’s roughly 3 percent gross payments pricing, even $8B to $10B of migrated GMV would be strategically meaningful volume, even if the net revenue retained is far smaller after interchange and network costs.1 2 3 4

• The key mechanic is simple. An app can send a user out to a web checkout, let them pay in the browser, often with Apple Pay still available, then return them to the app. That swaps Apple’s old in app billing toll for a normal processor fee, which makes Stripe the most obvious default for developers already using it on the web.2 4
• Not every developer will switch. External checkout adds friction, so the first movers are likely to be larger apps with enough revenue to justify the work, or apps that already sell across web and mobile and want one payment stack. Research on the ecosystem points to a rough pain line beginning around $5M to $10M in annual revenue.3 5
• The broader spend opportunity is bigger than payments alone. Once billing leaves Apple, developers also need someone to handle subscriptions, fraud, chargebacks, tax, and global payment method coverage. That makes Stripe the center of gravity for the new stack, but also opens room for partners and specialists like Adyen, Airwallex, Primer, Anrok, and Taxwire around it.3 5 6

The next step is an unbundling of the App Store into a full commerce stack chosen by the developer. Stripe is positioned to win the first leg because payments is the wedge, but the bigger long term prize is owning the surrounding software layers that turn migrated iOS GMV into higher margin revenue beyond simple processing.1 3 6