Apple External Payment Links: What the Epic Ruling Changes for App Teams
A U.S. court decision in Epic v. Apple bars Apple from blocking iOS apps in the United States from linking users to an external checkout, and from charging a commission on purchases completed outside the app. That opens a practical second path alongside in-app purchases — but it does not remove in-app purchases for most apps, and enforcement is still settling.
What changed
The injunction has three core parts. First, no commission on outside purchases: developers keep the revenue minus their own payment-processor costs, instead of paying the usual 15–30% range. Second, unrestricted linking: placement, formatting, and content of in-app links or buttons to an external purchase page cannot be restricted by Apple. Third, no gating or scare tactics: beyond a neutral redirect notice, Apple cannot add full-page warnings or extra hurdles designed to dissuade users from leaving the app to buy elsewhere. The earlier workaround fee of 27% on external purchases was rejected by the court.
In-app purchase vs. external checkout: the key distinction
In-app purchases remain the route for purchases initiated inside the iOS app, and most apps are still required to offer them alongside any external link. Reader apps are the main exception. Treat any approval of an external-only non-reader app as uncertain: it may reflect how quickly guidance was implemented rather than a durable exemption. Plan for a future review to require in-app purchases unless your app clearly qualifies as a reader app.
What each team can do differently
Developers gain freedom to integrate their own payment flow — for example through a web checkout provider — and to launch it from an in-app button or web view, then return the user to the app. Because web changes can be deployed server-side, price, copy, and flow fixes do not need to wait for app review. Product teams can design a branded funnel with richer product detail, bundles, and upsells, and test flexible pricing such as time-limited offers, coupon codes, referral discounts, or localized pricing. Marketing teams can reinvest the recovered margin in acquisition or trials, collect first-party contact details at checkout, and instrument web analytics so ad-to-purchase journeys are attributable end to end.
A practical test checklist
Use this checklist before enabling an external option: Confirm the user is in the U.S. storefront and on an eligible iOS version. Keep the existing in-app purchase paywall as Variant A. Add Variant B with both in-app purchase and a clearly labeled external-purchase button. Label choices plainly, for example a fast in-app option and a web option with its price or benefit. Instrument prompt, checkout start, completion, and return-to-app events. Compare conversion, revenue per user, and churn between variants. Iterate copy, price, and placement quickly, and re-check review guidance before any wider rollout.
Web paywall buttons in context
A web paywall button is a component that moves a user from an in-app paywall to a hosted web checkout and then unlocks entitlements automatically on return. It is useful when you want to test external checkout without rebuilding the whole purchase flow, but it does not replace the eligibility checks above. Keep in-app purchase available for most apps, limit the test to eligible U.S. traffic, and let measured results — not the margin difference alone — decide whether to expand.
Frequently asked questions
Can Apple still charge a fee on web purchases?
No. Purchases completed outside the app cannot be charged an Apple commission under the ruling described here, and Apple cannot restrict the placement, formatting, or content of links or buttons that send users to an external purchase page. A neutral notice that the user is being redirected is still allowed.
Do I still need to offer in-app purchases?
Most apps must still also offer in-app purchases. Reader apps, such as Spotify, are described as the main exception and have begun shipping versions using external payments only. Some non-reader apps were observed passing review without in-app purchases, but that may reflect inconsistent enforcement during the transition and could lead to rejection on a later update.
How should I test an external checkout safely?
Target U.S. iOS traffic only, using geolocation and SDK version filters so ineligible users stay on in-app purchases. Keep the existing in-app purchase paywall as one variant and add an external-purchase option as the other, then compare conversion, revenue, and churn before rolling out more widely.
What can product and marketing teams change in the funnel?
Yes. You can explain other purchasing options in the app, design a checkout that matches your branding, add product detail or bundles, and test pricing, promotions, and messaging that in-app purchase rules previously limited. Instrument the full path from in-app prompt to web checkout and back to the app so drop-off points are visible.