Unbundling App Store Billing

This ruling turns Apple from an all in one toll collector into a distribution channel that can no longer force use of its payment rail. In practice, an iOS app can still reach iPhone users through the App Store, but send a user out to a web checkout run by Stripe or another processor, then bring them back into the app. That breaks the old bundle where discovery, install, billing, subscriptions, fraud handling, and tax collection were tied together.

• The immediate winner is not just Stripe, but a whole replacement stack. Once billing is separated from distribution, developers can pair a web checkout with Apple Pay, then add tax, billing, and multi processor orchestration tools as they scale. That makes App Store commerce look more like normal internet commerce.
  1 sacra 4 sacra 5 sacra
• The trade off is conversion versus margin. Apple still owns the fastest purchase flow because card details, subscription management, refunds, and trust are already built into iOS. External checkout adds taps and operational work, so the biggest gain goes to larger apps where saving roughly 20 to 27 points of take rate outweighs some conversion loss.
  3 apple 4 sacra 6 apnews
• This also shifts competition upmarket. Smaller developers may keep using Apple because the bundle is simple, but larger consumer apps can now rebuild the stack with Stripe, Adyen, Airwallex, Primer, Anrok, or Taxwire depending on geography and complexity. The more global the app, the less likely one vendor handles everything.
  4 sacra 5 sacra

From here, iOS payments should become a modular software market, not a platform tax. Stripe is well positioned because it already powers web checkout at scale, but the bigger long term change is that billing, tax, and payment routing can now be won by specialist vendors one workflow at a time.