Guide · 8 min read
App Store External Payment Links 2026: What Indie Devs Actually Get
Apple's App Store now permits US apps to include a button linking users to an external website to complete a purchase — a change forced by the Epic v. Apple litigation that took years to actually land. The implementation requirements are strict, the commission situation is legally unsettled after the Ninth Circuit's December 2025 ruling, and the revenue math is not as favorable as the headlines implied. Here is what the policy actually allows, what it costs, and how to decide whether building it makes sense for your app.
What the external purchase link entitlement actually allows
The entitlement grants your US App Store app permission to display one button linking to a single, static URL you own — for purchasing digital goods or subscriptions outside Apple's in-app purchase system. The entitlement is boolean: you either have it or you don't. You apply through App Store Connect, Apple reviews the request, and the entitlement is scoped to the US storefront only. Non-US users must not see the button at all, and apps that fail to enforce the geo-restriction have had their entitlement revoked.
The scope is intentionally narrow. You get one URL — not a parameterized link, not an A/B rotating destination, and not a direct link to a third-party payment platform. The link must go to a website you own or maintain. Apple defines digital goods broadly enough to cover app subscriptions, consumable credits, and access passes, but the entitlement explicitly excludes physical goods and reader apps. Reader apps have a separate, more permissive entitlement that was granted years earlier.
The most common misconception is that this works globally. It does not. The Epic injunction applies to the US district only — Apple operates under different frameworks in the EU (Digital Markets Act), Japan, South Korea, and other markets where regulators have mandated similar access. Each region has distinct rules, and the implementation requirements differ enough that a single code path won't cover them all. If your revenue skews outside the US, this entitlement affects a smaller share of your total business than you might assume.
The commission math: what Apple actually charges on external links in 2026
Apple's commission on external-purchase transactions is legally unsettled as of mid-2026. Apple's initial response to the Epic injunction was to charge a 27% fee on purchases completed after an external link click — preserving almost all of the 30% take rate. The US district judge rejected that fee structure, ruling that the 27% rate was engineered to make the option economically nonviable rather than comply in good faith with the injunction.
The Ninth Circuit Court of Appeals then partially reversed that sanction in December 2025: Apple is entitled to charge a reasonable fee, but the district court must determine what reasonable means. The case has been sent back for further proceedings. The current practical state is that Apple is not collecting a commission on external-link transactions while the fee is being litigated — but that status can change without notice. If you are modeling external-link revenue into any financial forecast, treat the eventual fee as an open variable, not zero.
The useful math for indie developers: if you currently pay 15% (Apple's Small Business Program rate for developers earning under $1M annually) and your web payment processor charges ~3%, the net saving per transaction is around 12 percentage points — assuming Apple charges nothing. For a subscription at $9.99/month that works out to roughly $1.20 extra per subscriber per month before accounting for web checkout conversion drop-off. That number needs to survive a realistic drop-off estimate before the implementation pays off.
How to apply for the entitlement and what Apple approves
Applying for the entitlement happens inside App Store Connect under your app's App Information section. You submit a request describing how you plan to use the link, Apple reviews it within a few business days, and either grants or denies the entitlement. Apps must already be live on the US App Store — new apps cannot apply pre-launch. Apple has approved requests across productivity, health, news, and utilities categories, but has declined apps with recent guideline violations or apps whose primary function appears to be a payment routing wrapper.
The entitlement is granted per-app, not per-developer account. Each app in your portfolio that wants external purchase links needs its own application and its own static destination URL. Apple reviews the destination page as part of the approval process — the page must sell only your app's own digital content, contain no referrals to competing apps, and include no copy that explicitly compares your pricing against Apple's in-app purchase prices. Post-approval changes to the destination page that violate those terms are grounds for entitlement removal without a prior warning.
Before you apply, also update your App Store listing metadata to reflect the new pricing option. If you plan to offer a discount on the web checkout versus your App Store price, that discrepancy is noticeable to users who read your subtitle and promotional text. The subtitle vs. promotional text breakdown covers how to surface the right message in each field. Apple does not require the listing and web page to match on price, but inconsistencies that look like bait-and-switch can generate user reports.
Implementation requirements: the button, the copy, and the mandatory disclosure
Apple mandates the button appearance in detail. The button must use a plain style with no fill color, no background, and no containing shape — it cannot resemble a primary CTA button. The button must include Apple's link-out SF Symbol to the right of the label text. Apple provides template copy phrases that you must use verbatim; you cannot write custom label text. The purpose of these constraints is to visually de-emphasize the external link relative to your in-app purchase buttons — this is an intended asymmetry, not an oversight.
Before the user is redirected, your app must present Apple's required disclosure sheet. The sheet explains that the user is leaving the App Store experience, that Apple is not responsible for the external website's privacy practices, and that purchases made there are not managed by Apple. You cannot dismiss this sheet programmatically — the user must tap to confirm they want to continue. Apps that suppress, skip, or restyle the disclosure sheet are rejected. This friction is the core reason web checkout conversion rates run below in-app purchase rates even when the product is identical.
The technical implementation uses the ExternalPurchaseLink StoreKit API, available on iOS 17.4 and later. Because the entitlement is only active on the US storefront, your code must check Storefront.current.countryCode and show the button only when it returns 'USA'. Skipping this region check is the leading cause of rejection for apps that implement everything else correctly. Budget two to four weeks for the build and at least one full rejection cycle — Apple's review of external-link apps is more thorough than a standard submission.
Is the revenue uplift real? The honest math for indie apps
The revenue uplift is real but smaller than coverage suggests, and it arrives with a conversion cost that most analyses omit. Redirecting a user from your app to Safari interrupts the purchase flow at its highest-intent moment. Subscription businesses that have implemented external-link flows report web checkout completion rates running 15–35% below in-app purchase completion rates, depending on audience sophistication and how the paywall is designed. That conversion gap must be subtracted from the margin saving before you know whether the net result is positive. The in-app purchase vs. subscription vs. one-time pricing guide has the baseline conversion and margin benchmarks you can use to run the numbers for your specific price point.
The math tips favorably for apps with high average transaction values — subscription prices above roughly $50/year, or lifetime purchase prices above $100. At those levels, the per-transaction savings are large enough to absorb a 20–30% drop in completion rate and still net ahead. For a $4.99/month subscription, the absolute dollar saving per subscriber is small enough that even a modest web conversion drop erases the gain. On Apple's Small Business Program (15% base rate), the absolute saving is already narrower, and the break-even threshold shifts higher. This is a tool for high-ARPU apps, not a universal upgrade.
A less obvious benefit sits outside the margin math: email addresses. Users who subscribe via in-app purchase are primarily Apple customers — you receive no email, no payment detail, and no direct billing relationship. Users who subscribe on your website give you a first-party relationship you can use for renewal communications, win-back campaigns, and cross-sell. For developers building out a direct user acquisition channel as a complement to App Store organic, the web checkout is strategically valuable even at subscription prices where the margin saving alone would not justify the build.
What your external page can do that in-app purchase cannot
Your external payment page can offer prices that don't exist in your App Store listing. You can run web-exclusive promotions, offer annual plans cheaper than your App Store annual price, and accept payment methods Apple doesn't support — including regional payment methods relevant to specific markets. You can also display comparison copy, cancel-any-time language, and pricing transparency that Apple's in-app guidelines restrict or make awkward to present inside the app itself.
The external page can implement contextual pricing — showing different offers based on how the user arrived. A user who clicked from inside your app's premium-feature gate is at peak motivation and may convert on a full-price annual plan. Designing that moment well is the same discipline covered in the contextual paywall design guide, but executed on the web rather than inside a native paywall sheet. The principles are the same; the implementation is different, and you have more layout flexibility.
One firm constraint: the external page cannot include content that directs users to competing apps or compares your pricing to Apple's in-app purchase in a way that frames Apple negatively. You can sell your own subscriptions, bundle your own apps, and offer your own terms — but you cannot use the entitlement as a gateway to an affiliate-style model routing purchases to other developers. Apple checks the destination page during entitlement review and has revoked entitlements from apps that added prohibited content after approval.
Before you build the external payment flow
The external purchase link is worth building if your average transaction value is high, your users are technically comfortable with web checkouts, and you want a direct billing relationship rather than App Store Connect as your sole data source. It is probably not worth the implementation overhead for apps with sub-$50 annual plans and casual consumer audiences where any payment friction is a conversion killer.
Run the margin math using your own conversion data, factor in a realistic 20–30% web checkout drop-off, and assume Apple will eventually charge a fee somewhere in the 5–15% range when the litigation settles. Build that conservative scenario first. If it still makes sense, start the entitlement application — it takes a few business days and costs nothing to find out whether Apple will approve your app.
Design your paywall in the screenshot editor →
Frequently asked questions
can i link to my own website for payment in my ios app?
Yes — US App Store apps can include an external purchase link to a website you own for digital goods, provided you apply for and receive Apple's StoreKit external purchase link entitlement. The link is US-only, must go to a single static URL on your domain, and requires Apple's mandated button styling plus a mandatory disclosure modal before the user leaves the app.
what commission does apple charge on external payment links in 2026?
The fee is legally unsettled as of mid-2026. Apple originally proposed 27%, a US district court rejected that structure as noncompetitive, and the Ninth Circuit ruled in December 2025 that Apple may charge a reasonable fee — sending the case back to the district court to determine what that means. Apple is currently not collecting a commission on external-link purchases during litigation, but that status can change. Do not build financial models that assume the rate stays at zero.
is the app store external payment link available outside the united states?
No — the StoreKit external purchase link entitlement is scoped to the US App Store storefront only. The EU, Japan, South Korea, and other markets have separate regulatory frameworks with distinct implementation requirements. Apps must implement a storefront check using <code>Storefront.current.countryCode</code> and hide the button for non-US users. Failing this check is the leading cause of entitlement revocation after initial approval.
what does the required apple warning message say when users click the external payment link?
Apple's mandatory disclosure sheet tells users they are leaving the App Store experience, that the external website is not operated by Apple, and that any purchases made there are governed by the third-party site's terms and privacy policy rather than Apple's. The sheet must appear before every redirect and cannot be bypassed, restyled, or skipped. The user must tap to confirm before the redirect proceeds.
is it worth adding an external payment link for a small indie app?
For most small indie apps — especially those with subscription prices under $50/year or casual audiences — the web checkout conversion drop will consume the margin saving and leave you no better off. The best candidates are apps with high-value annual or lifetime plans, technically engaged users comfortable with browser checkouts, and a strategic interest in building a first-party billing relationship. If you're on Apple's Small Business Program (15% rate), the absolute saving per transaction is also narrower, which raises the break-even threshold further.