External iOS Payments: Pros, Cons and Gotchas for App Teams
The US ruling that lets iOS apps link to external payment options is often framed as a simple fee win. The reality is more nuanced. Moving checkout outside the App Store changes who handles payment operations, how users experience the purchase flow, and how you measure acquisition. This guide walks through the assumptions behind the fee-savings argument, the operational costs that can erode it, and the advantages that are easy to miss.
What the ruling actually changes
The ruling requires Apple to permit US iOS apps to link to external payment options. It also bars Apple from taking commission on those external payments and from showing biased warning screens designed to discourage users from leaving the app. Apple may still display a neutral notice that the user is leaving the app and being redirected.
That combination removes two major barriers: the commission itself and the most aggressive anti-steering friction. It does not remove every friction point, and it does not transfer Apple's back-office payment work to anyone else. Those responsibilities move to the app team unless a third party takes them on.
A premortem for the fee-savings hypothesis
The common hypothesis is that switching to external payments will produce a 27% gain in the US from reduced fees. Before committing, stress-test that hypothesis against three assumptions.
Assumption 1: No additional costs erode the gain
This is the most dangerous assumption. Selling through the App Store means Apple handles much of the payment relationship behind the scenes. External payments shift chargebacks, refunds, payment fraud, delinquent payments and sales tax compliance onto the app team. Sales tax rules vary by state, and building the infrastructure to manage them can consume a meaningful share of the fee difference. For smaller apps already paying a 15% fee, the starting gain is lower and the operational drag proportionally larger.
A Merchant of Record such as Paddle, or a subscription-sync billing platform that keeps subscriptions and entitlements aligned across web and mobile, can absorb some of that burden. Teams that already scaled with web-to-app have likely solved this; everyone else faces a new hurdle.
Assumption 2: Funnel conversion stays constant
Biased interstitials are gone, but a neutral exit notice remains. Over time users may become accustomed to it, but in the near term it adds friction and increases drop-off before checkout. Web checkout also tends not to match the speed of paying in-app with Apple Pay, so a smaller share of users may reach the payment page. This mirrors what web-to-app funnels often show versus in-app purchases. The gap may narrow as checkout experiences improve, but it should be modeled rather than assumed away.
Assumption 3: The only comparison is in-app purchases
In-app monetisation was never the only option. Web-to-app has been used for years by apps seeking lower fees and other advantages. The new ruling makes app-to-web a formal strategy, but it does not give app-to-web everything web-to-app has. In particular, UTM tracking that maps users and cohorts back to specific campaigns and creatives is not available in an app-to-web flow. Attribution is never perfect in either direction, so this is a tradeoff to weigh rather than a reason to stop.
Advantages beyond the fee line
Even if the realized gain is 20% or 15% rather than 27%, several other effects can make app-to-web attractive.
1. Faster cash flow for paid acquisition
Apple's payout cycle plus bank processing can mean 60-65 days between a user's payment and the money reaching the developer's account. That delay is painful when scaling paid acquisition, and some companies offer advances against pending Apple payments to bridge it. Merchants of Record such as Paddle and payment service providers such as Stripe typically pay out much faster, in some cases the same week or same day. For bootstrapped teams without outside funding, that working-capital difference can matter as much as the fee percentage.
2. Trial conversion
Across many apps, web trial conversion has often run higher than in-app conversion. Part of that gap has come from reminder emails and a more cumbersome web cancellation journey. The Click-to-Cancel Rule is intended to curb dark patterns, so the size of this advantage may shrink. In the short term, cancellation on the web still tends to involve more friction than cancelling through the App Store, which can lift trial conversion at least temporarily.
3. Revenue retention
Higher renewal rates on web revenue versus in-app revenue have been observed repeatedly. Perceptycs, a growth agency, reported that one of its clients saw a 3x increase in year-one renewals for web purchasers versus App Store purchasers, while cautioning that 3x is likely an outlier rather than a typical result. Click-to-Cancel should narrow the gap, but enforcement on the web, especially for international developers selling to US users, is not trivial.
4. Checkout UX can be tailored
Not every user prefers Apple Pay. Some older users reportedly prefer paying by card on the web because it feels safer and more familiar than double-clicking and scanning a face in an app they just downloaded. External checkout lets developers customise payment methods and offer different checkout options to different user groups, which was not possible with in-app purchases alone. That opens room to test checkout variants based on first-party data collected in the app.
5. A middle path for freemium apps
For utility apps with a freemium model, web-to-app has often made little sense because the value that convinces users to convert appears only after they sign up and try the product. Forcing an onboarding quiz or an immediate purchase from a landing page usually underperforms. App-to-web changes that: traffic can still go straight to the app, users can experience the freemium product, and then they can be guided to a web payment. A web purchase button is one way to implement that handoff.
Netting it out
The metric impact is still uncertain and will only become clear through implementation and testing. One likely outcome is that some developers pass part of the savings to users as discounts or offers, especially in crowded categories such as health and fitness. A developer might extend an additional 20% discount and still net more per user than charging a 20% higher price in-app. External payments are unlikely to deliver a simple 27% uplift on day one, but stacked together the benefits could make app-to-web a standard growth strategy.
| Area | Question to answer before switching | Why it matters |
|---|---|---|
| Fees | What is the realistic net fee difference after payment processing and platform costs? | The headline 27% is a gross figure, not a guaranteed net gain. |
| Operations | Who will handle chargebacks, refunds, fraud, delinquent payments and sales tax? | These tasks move from Apple to the app team unless a Merchant of Record or billing platform takes them on. |
| Funnel | How much drop-off will the neutral exit notice and web checkout introduce? | Conversion may fall before checkout even if the fee per transaction improves. |
| Attribution | Can you still map users and cohorts back to campaigns without UTM tracking? | App-to-web flows lose the UTM visibility that web-to-app provides. |
| Cash flow | How much faster will payouts arrive, and does that fund acquisition? | Faster settlement can support paid growth, especially for bootstrapped teams. |
| Retention | Will web cancellation friction help or hurt long-term renewals? | Short-term retention gains may shrink as Click-to-Cancel enforcement matures. |
| UX | Which user segments prefer card checkout over Apple Pay? | External checkout allows payment-method customisation that in-app purchases do not. |
| Freemium | Can users reach the aha moment before being asked to pay? | App-to-web preserves the in-app freemium experience before the payment step. |
Checklist items reflect the considerations discussed in the source article; they are not a guarantee of outcomes.
Frequently asked questions
Does the ruling mean iOS developers pay no fees on external payments?
Apple is barred from taking commission on external payments under the ruling. However, payment processors, Merchants of Record and the cost of managing chargebacks, refunds, fraud and sales tax still apply. The net gain is therefore lower than the gross fee difference.
Can Apple still show a warning when users leave the app to pay?
Yes. Biased interstitials designed to discourage external purchases are prohibited, but a neutral notice informing users that they are leaving the app and being redirected is still allowed.
Why is attribution harder with app-to-web?
Web-to-app flows can use UTM tracking to connect users and cohorts to specific campaigns and creatives. App-to-web flows that rely on external payments cannot replicate that tracking, so campaign-level attribution is less precise.
How does the Click-to-Cancel Rule affect external payment advantages?
The rule targets dark patterns in cancellation. If it is enforced effectively, some of the retention and trial-conversion advantage that web checkout has enjoyed through cancellation friction may shrink. Enforcement on the web, particularly across borders, is not straightforward, so the timing and size of that effect are uncertain.