.png)
.png)
When Fortnite returned to the U.S. App Store on May 20, 2025, it wasn't a reconciliation. Judge Yvonne Gonzalez Rogers had ruled three weeks earlier that Apple willfully violated a court injunction, and Apple had run out of ways to stall.
That ruling changed the economics of every subscription app on iOS. U.S. developers can now include buttons and links inside their apps that send users to a web checkout, complete a purchase through Stripe, and skip Apple's 15%–30% commission entirely. That's not a loophole. It's the law.
This is the biggest monetization shift in mobile since the App Store launched. Here's exactly what changed, how to set it up, and the failed payment recovery risk that almost nobody's covering.
In April 2025, U.S. District Judge Yvonne Gonzalez Rogers found Apple had deliberately undermined her 2021 injunction. Apple's response had been to allow a single external link while still charging a 27% commission on linked-out purchases and showing pop-up "scare screens" to discourage users from leaving the App Store. The court called this a "cover-up."
The ruling stripped all of it. Apple was barred from charging commission on external purchases, barred from UX friction designed to deter web payments, and required to allow in-app buttons directing users to off-app checkout. The December 2025 Ninth Circuit ruling partially modified this, saying Apple may eventually collect some commission, but the amount must be set by the district court. As of May 2026, the case is heading to the Supreme Court, and external link rules remain in effect.
Before the ruling, developers couldn't include any link, button, or promotional copy directing users to a cheaper option outside the app. Now they can:
Most apps still need to offer IAP alongside external options. Only reader apps like Spotify and Kindle can go web-only.
Apple now requires a single neutral disclosure when users tap an external payment link: "You're about to go to an external website. Apple isn't responsible for the privacy or security of purchases made on the web." Users click through to your Stripe checkout. No scare screens.
The core economics are straightforward. Apple's IAP takes 30% per transaction (15% if you're under $1M ARR). Stripe charges approximately 2.9% plus 30 cents. On a $9.99/month subscription, that gap is $2.70 per payment. At 100,000 subscribers, that's $270,000 a month that could be going to your business instead.
IAP isn't just a payment processor. It's a managed billing stack. Moving to Stripe means you're now responsible for tax compliance across every jurisdiction, fraud prevention and chargebacks, failed payment recovery, and subscription management. Stripe handles most of this natively, but you need to build the infrastructure before you migrate subscribers.
Before writing any code, confirm you have:
Critical: Apple won't let you export existing IAP subscriber payment data, so you can't silently migrate active subscribers. Prompt them to resubscribe through web checkout when their in-app term ends.
Pass a unique app account token as a URL parameter when the user taps the external link. Store that token as Stripe customer metadata when the checkout session is created, listen for the checkout.session.completed webhook, match the token to the user in your database, and grant the entitlement. The user returns to the app via deep link with access already unlocked.
Most web billing guides skip this. When a subscriber's Apple ID payment fails, Apple manages the retry and often the recovery. You don't own that process, but it runs.
When you move to Stripe, you own it completely.
Industry data puts the monthly failed payment rate for B2C subscriptions at 7%–10%. On web billing, it can run higher for two reasons:
Moving to web billing without a recovery strategy in place can erode some of the margin you're gaining from lower Stripe fees.
Stripe's Smart Retries will attempt the charge again at machine-learning-determined intervals. If those fail, dunning emails go out asking the subscriber to update their card.
Here's the problem. Your iOS app subscriber doesn't think of themselves as a "web billing subscriber." When they get a payment failure email from Stripe, many ignore it and quietly lose access. That's involuntary churn: the customer never intended to cancel, but they're gone. Stripe's own data shows recovered subscribers continue paying for an average of seven more months after recovery.
Redux Payments sits on top of your Stripe account and monitors bank health signals to identify the exact window when a retry is most likely to succeed, timed to issuing bank availability. The subscriber never sees a failure notification.
This matters more on web billing than IAP because you're now carrying the full recovery burden yourself. Redux is built specifically for B2C subscription businesses on Stripe, where each lost subscriber represents months of LTV. Learn more about the Redux AI Recovery Engine and how it layers on your existing Stripe setup without replacing it.
Web billing means collecting subscription payments through Stripe on your own website instead of through Apple's In-App Purchase system, trading a 15%–30% commission for ~2.9% + 30 cents while taking on responsibility for taxes, fraud, and payment recovery yourself.
Yes, for U.S. users following the April 2025 Epic vs. Apple ruling, though most apps must still offer IAP alongside the web option.
Stripe is the standard choice, with native subscription billing, webhook-based entitlement syncing, Smart Retries, and Stripe Tax built in.
With IAP, Apple manages retries and Account Updater card refreshes automatically. With Stripe web billing, you own the entire recovery process, and failure rates tend to run higher because credit card data ages faster and manual entry errors don't exist in a one-tap Apple Pay flow.
Stripe offers Smart Retries, which provides a baseline level of recovery. But Smart Retries is broad by nature, since it has to work across Stripe's large B2B customer base. Redux is specialized for B2C, retrying on paydays to catch insufficient-funds declines and offering frictionless card update flows.
No, as long as external payment links follow Apple's placement rules, include the neutral disclosure message, and your app still offers IAP unless it qualifies as a reader app.
Possibly: the December 2025 Ninth Circuit ruling said Apple may collect some commission, but the amount must be set by the district court, and current no-commission rules remain active while the Supreme Court reviews the case.
The margin math on web billing is compelling. But the failed payment risk on Stripe compounds quietly, especially when you're migrating a subscriber base that previously relied on Apple's recovery infrastructure.
Run your free churn audit with Redux Payments before you migrate. You'll see your current failed payment rate, your recovery gap against Stripe's baseline, and estimated revenue at risk. That number tells you exactly what recovery infrastructure you need on day one.
.png)
.svg)
.svg)
