The rulings and guidelines described below apply to the United States App Store only. Other regions operate under separate frameworks - for example, the EU Digital Markets Act (DMA) has its own set of rules governing alternative payment methods. Contact support@zerosettle.io if you have questions about a specific region.
Apple v. Epic: Background
The key court rulings and guideline changes relevant to alternative payment links in iOS apps come from the Epic Games v. Apple case and its aftermath.The Original Injunction (September 2021)
Judge Yvonne Gonzalez Rogers issued a permanent injunction prohibiting Apple from preventing developers from including buttons, external links, or other calls to action that direct users to purchasing mechanisms outside of Apple’s in-app purchase system.The Contempt Ruling (April 30, 2025)
After Apple imposed what the court considered obstructive compliance measures (including a 27% commission on external purchases and interstitial warnings designed to discourage users), Judge Gonzalez Rogers found Apple in contempt of court. The ruling stated that Apple had willfully violated the injunction and ordered Apple to stop impeding developers from linking to external payment methods.Updated App Review Guidelines
Following the contempt ruling, Apple revised its App Review Guidelines to reflect the court’s order:Guideline 3.1.1(a): “On the United States storefront, there is no prohibition on an app including buttons, external links, or other calls to action, and no entitlement is required to do so.”
Guideline 3.1.3: “The prohibition on encouraging users to use a purchasing method other than in-app purchase does not apply on the United States storefront.”Based on these published guidelines, US developers can include external payment links in their iOS apps without applying for a special entitlement.
Checkout Presentation Methods
There are three ways to present a web checkout from an iOS app. Each has different trade-offs for user experience and App Review:| Method | User Experience | App Review | Notes |
|---|---|---|---|
| External Safari | User leaves app to complete purchase | Explicitly allowed by Apple | Zero review friction; sanctioned method |
| In-App Browser (SFSafariViewController) | User stays in app; Safari engine | May face slower review | Better UX but not explicitly sanctioned |
| Inline WebView (WKWebView) | Embedded directly in app UI | May face slower review | Best UX but not explicitly sanctioned |
External Safari Browser
The user taps a button in your app and is taken to Safari (or their default browser) to complete the purchase. After payment, a universal link brings them back to your app. Based on Apple’s updated guidelines, this is the explicitly sanctioned method and typically carries zero App Review friction.In-App Browser (SFSafariViewController)
Opens the checkout page inside your app using Safari’s rendering engine. The user stays within your app throughout the purchase flow. This provides a better user experience than external Safari but is not the explicitly sanctioned method - App Review may be slower or raise objections.Inline WebView (WKWebView)
The checkout is embedded directly into your app’s UI as a native-feeling bottom sheet or full-screen view. This provides the best conversion rates and user experience. Like SFSafariViewController, this approach may encounter more App Review scrutiny than external Safari.Google Play
Google has taken a parallel path toward allowing alternative payment methods on Android.User Choice Billing
Google’s User Choice Billing program allows developers to offer alternative payment methods alongside Google Play Billing. When a user makes a purchase, they can choose between Google Play’s payment system and the developer’s alternative.US Policy Changes (October 2025)
Following regulatory pressure and the Epic Games v. Google jury verdict, Google updated its US policies to allow developers to use alternative payment methods with a reduced service fee. Based on these changes, apps distributed on Google Play in the US can direct users to external payment flows.On Android, ZeroSettle opens a Custom Tab (Chrome) for the checkout flow. This is the standard approach for external payment on Android and does not face the same review scrutiny as iOS.
ZeroSettle’s Approach
ZeroSettle is designed to follow Apple’s and Google’s published guidelines so you can focus on your app:- All three iOS checkout methods (external Safari, SFSafariViewController, WKWebView) are supported and switchable via remote config - no code changes required
- US geofencing is handled automatically, ensuring external checkout is only offered where legally permitted
- Merchant of Record status means ZeroSettle handles tax compliance, receipts, disputes, and refunds
- Android Custom Tabs are used for checkout on Google Play, following standard platform conventions
Legal / Compliance Note - ZeroSettle is not a law firm and does not provide legal advice. Our products are designed to align with Apple’s published App Store guidelines and external purchase/link-out requirements, as well as relevant court rulings. We recommend that developers review their specific implementation with their own legal counsel.