External Payment Links in iPhone Apps: What US Small Businesses Need to Know in 2026

For more than a decade, if your iPhone app sold anything digital, the rules were simple: you used Apple's in-app purchase system, Apple took its cut, and you weren't allowed to tell customers they could pay less on your website. That has changed for apps on the US App Store.

Following the Epic v. Apple court rulings, apps on the US storefront can now include buttons and links that send customers to an external web checkout, and they can tell users when buying on the web is cheaper. For small and mid-sized businesses that sell subscriptions, memberships, courses, or other digital content through an app, this is one of the most meaningful shifts in mobile monetization in years.

It's also not fully settled. The question of whether Apple can eventually charge a commission on those link-out purchases is still working its way through the courts, and the Supreme Court has agreed to hear Apple's appeal. So the opportunity is real, but you should build for flexibility rather than assume today's rules are permanent.

Here's what the change actually means, who benefits, and how to set up web checkout in your app the right way.

First: Does This Even Apply to Your App?

A lot of business owners hear "Apple's payment rules changed" and assume it affects them. Many times it doesn't, because Apple's in-app purchase requirement only ever applied to digital goods and services consumed inside the app.

Apps that were never required to use Apple's in-app purchase

• Restaurants and coffee shops taking food orders
• Retail and ecommerce apps selling physical products
• Service businesses booking real-world appointments (salons, home services, clinics, auto repair)
• Event ticketing for in-person events
• Apps that let customers pay an invoice for real-world work

If your app falls in this group, you've likely always used Stripe, Square, Apple Pay, or a similar processor, and nothing about this ruling changes your setup.

Apps where this change matters

• Fitness studios selling on-demand or livestream class subscriptions
• Coaches, educators, and training businesses selling courses or premium lessons
• Membership communities and paid content apps
• Software tools with paid tiers or feature unlocks
• Media, newsletters, and publishers with digital subscriptions
• Apps that sell credits, tokens, or digital add-ons

If you're in the second group, keep reading. This is where external payment links can change your margins, your customer relationships, and your pricing options.

What Is Actually Allowed on the US App Store Now

For apps distributed on the US storefront, developers can generally:

• Place a button or link inside the app that opens an external web page to complete a purchase
• Use calls to action that tell users they can buy on your website
• Show pricing for the web option, including when it's lower than the in-app price
• Offer both Apple's in-app purchase and a web checkout option side by side

Two important caveats:

• This is US-only. The same link-out experience can still violate App Store rules in most other countries. If your app is available internationally, your app needs to show the external link only to users on the US storefront.
• The fee question is open. Right now, Apple isn't permitted to charge a commission on US link-out purchases, but appeals are ongoing. A future ruling could allow some form of fee. Plan your pricing so you can adjust if that happens.

Apple's App Store Review Guidelines are the source of truth here, and they're updated periodically. Before you ship, have your developer review the current guideline language, and for revenue-sensitive decisions, it's reasonable to loop in your attorney or accountant.

Why Small Businesses Should Care

The obvious benefit is cost. Every dollar that previously went to platform commission on digital sales can now potentially stay with you, or be passed back to the customer as a lower price. But the less obvious benefits are often just as valuable.

You own the customer relationship

When someone subscribes through Apple's in-app purchase, Apple handles the billing relationship. You get limited customer data and have less control over refunds, upgrades, and win-back offers. When they subscribe on your website, you get the email address, the billing history, and the ability to manage the account directly. That ties neatly into first-party data strategies and email marketing you may already be running.

One price, one account, every platform

Many businesses already sell the same membership on their website, in the iOS app, and in the Android app. Juggling three billing systems with different prices and different refund rules creates support headaches. Routing iOS buyers to your web checkout lets you unify more of that into one system.

More flexible offers

Web checkout gives you full control over promotions: bundles, annual plans with custom discounts, family or team plans, gift memberships, coupon codes from a partner, or a free trial tied to a specific campaign. You're not limited to the offer types an app store billing system supports.

The Trade-Offs Nobody Should Skip Over

Web checkout isn't automatically better. Apple's in-app purchase has real strengths, and you give some of them up when you send people to a browser.

• Friction. In-app purchase is often a single tap with Face ID. A web checkout means leaving the app, loading a page, and entering payment details. Every extra step can cost you conversions.
• Trust. Some users feel more comfortable buying through Apple. An unfamiliar checkout page can make people hesitate.
• Subscription management. Apple handles cancellations, receipts, and refunds through the user's Apple account. With web billing, that becomes your job, and you'll need a clear, easy way for customers to manage or cancel their plan.
• Payment processing isn't free. You'll still pay card processing fees and possibly subscription billing platform fees. The savings are real, but smaller than "zero commission" sounds.
• Sales tax and compliance. When Apple sells on your behalf, it handles a lot of the tax collection. When you sell directly, sales tax on digital goods becomes your responsibility, and rules vary by state. Talk to your accountant before you flip the switch.
• Regulatory uncertainty. If a future ruling allows Apple to charge a fee on link-outs, your math changes.

The smartest approach for most small businesses isn't "web only" or "Apple only." It's offering both, measuring what happens, and letting your own data decide.

How to Add Web Checkout to Your iOS App: A Practical Plan

If you've decided it's worth exploring, here's the sequence we recommend.

1. Audit what you sell and where

List every paid product in your app, how it's billed today, and what it costs you after platform fees. Identify which products are digital (and therefore were tied to in-app purchase) and which aren't. This tells you how much is actually on the table.

2. Get your web checkout right first

Your web checkout is now part of your app experience, so it needs to feel like it. That means:

• A mobile-first page that loads fast on a phone
• Apple Pay and Google Pay support, so buyers aren't typing card numbers on a small screen
• Branding that matches the app, so the handoff doesn't feel like a different company
• A short form: ask only for what you truly need
• Clear pricing, renewal terms, and a visible way to cancel

Subscription billing tools like Stripe Billing, and app-focused subscription platforms that support web purchases, can handle recurring payments, failed card retries, and customer portals so you don't build that from scratch.

3. Make sure the purchase unlocks the app instantly

This is where many implementations fall apart. After a customer pays on the web, they come back to the app and expect their content to be unlocked right away. To make that work:

• Use a shared account system. The user should be logged in with the same account in the app and on the web.
• Pass identity securely. When the app opens your checkout link, include a secure, short-lived token so the web purchase is tied to the right account without forcing a second login.
• Handle entitlements on your server. Your backend should be the single source of truth for who has access to what, whether they paid via Apple, Google, or the web.
• Return users to the app. Use universal links or deep links to send customers straight back into the app after checkout, with their purchase active.

4. Show the link only where it's allowed

Because external purchase links are permitted on the US storefront but not most others, your app needs logic that checks the user's App Store storefront and only displays the web purchase option to US users. International users should continue to see your standard in-app purchase flow.

5. Keep in-app purchase as an option

For most businesses, removing in-app purchase entirely is premature. Offer both. A common pattern is a paywall screen with the in-app purchase option and a clearly labeled "Save on our website" option beneath it. Some customers will choose convenience, others will choose the lower price, and you'll learn which group is bigger for your audience.

6. Measure everything

Track the full funnel for both paths:

• Paywall views
• Taps on each purchase option
• Completed purchases on each path
• Net revenue per purchase after all fees
• Refund rates, cancellation rates, and retention over time

The number that matters isn't which path gets more purchases; it's which path produces more net revenue and longer-lasting customers.

Pricing Strategy: Should Web Be Cheaper?

You're now allowed to tell users that buying on your site costs less. Whether you should is a business decision, and there's no single right answer.

• Pass savings to customers. A lower web price is a strong incentive and can drive adoption of web checkout. It's the clearest way to overcome the extra friction.
• Keep prices the same and keep the margin. Simpler messaging, fewer complaints from existing in-app subscribers, and more revenue per sale.
• Add value instead of cutting price. Offer a bonus on web purchases, like an extra month on annual plans or an exclusive resource, without changing your base price.

Whatever you choose, keep prices easy to change. Given that the commission question is still in front of the courts, avoid locking yourself into public pricing promises that only make sense under today's rules.

Don't Forget Android

Google Play has its own set of billing rules, alternative billing programs, and ongoing legal developments, and they don't mirror Apple's. If your app is on both platforms, design your backend so entitlements work the same regardless of where a customer paid, but treat each store's billing rules as a separate checklist. What's allowed on the US App Store isn't automatically allowed on Google Play, and vice versa.

Common Mistakes to Avoid

• Showing external links globally. This is the fastest route to an App Store rejection outside the US.
• Making users log in twice. A clunky handoff between app and browser kills conversions.
• Delayed unlocks. If content doesn't unlock immediately after a web purchase, expect support tickets and refund requests.
• Hiding the cancel option. Web subscriptions need an obvious, simple way to cancel. Beyond being good practice, the FTC and many states have rules around subscription cancellations, so build cancellation flows carefully.
• Ignoring sales tax. Selling digital goods directly can create tax obligations Apple used to handle for you.
• Betting everything on today's ruling. Build so you can switch the web option on or off, or adjust pricing, without shipping a new app version. Remote configuration makes this easy.

Is It Worth It for Your Business?

Here's a quick gut check:

• Probably worth exploring if digital sales through your iOS app are a meaningful part of revenue, you already sell the same product on your website, or you want more direct control of your subscriber relationships.
• Probably not urgent if your app only sells physical goods or real-world services, your digital in-app revenue is small, or you don't have the backend to manage accounts and entitlements across platforms yet.

For many businesses, the right first step is a modest one: add a web checkout option for one product, keep in-app purchase in place, and spend a couple of months watching the numbers.

Need Help Setting Up Web Checkout in Your App?

Adding external purchase links touches your iOS app, your website, your backend, and your payment setup, so it's worth getting the architecture right the first time. At Kodbee, we build mobile apps and the web checkout experiences that sit behind them, from secure account handoffs to storefront-aware paywalls and unified entitlements across iOS, Android, and the web.

If you're wondering whether link-out payments make sense for your app, or you want a second set of eyes on your current setup, get in touch with our team. We'll help you figure out what's worth doing now and what's worth waiting on.