Linking iOS Users to Web Checkout: Cut App Store Fees on Digital Sales

On this page 7 sections

1. What Changed: Apple's Anti-Steering Rules and the iOS External Payment Link
2. In-App Purchase vs. Web Payment: Fee Math on a $9.99 Subscription
3. What You Take on When You Process Payments Yourself: Refunds, Disputes, Tax
4. Designing the Link-Out Flow so Users Actually Complete Payment
5. Syncing Web Purchases Back to In-App Entitlements
6. When Staying on App Store Billing Still Makes Sense
7. Next Steps

Key takeaways

• A web checkout can keep more of each sale, but only if enough users finish paying after they leave the app.
• Your current app store commission tier decides whether linking out pays off. At lower tiers the margin gap can be thin.
• On the web, you own refunds, chargebacks, fraud, sales tax and auto-renewal compliance that the app store used to handle.
• Build a server-side entitlement system before launch so web buyers get access in the app right away.

For years, apps selling subscriptions and digital content had one way to charge iPhone users: Apple's in-app purchase system, which takes a commission from every sale. Court rulings and policy changes have opened the door to an iOS external payment link, which is a button or link that sends users to your own web checkout. This guide shows how to compare the real per-sale margin of in-app billing against a linked web checkout. It also covers the conversion drop-off and chargeback exposure you take on and how to build a link-out flow that users actually complete.

What Changed: Apple's Anti-Steering Rules and the iOS External Payment Link

Apple's App Store rules have long included anti-steering provisions. These limited how apps could tell users about cheaper prices or payment options outside the app. For digital goods and subscriptions, in-app purchase was effectively the only path on iOS.

The Epic v. Apple Anti-Steering Ruling

The long-running Epic Games v. Apple litigation produced court orders that limited Apple's ability to stop U.S. apps from pointing users to outside purchase options. Apple has responded with guideline changes and appeals. The rules have shifted more than once on three questions: what a link may look like, where it can appear and whether Apple can collect a fee on linked purchases.

Before you build anything, read Apple's current App Review Guidelines and any developer notices that apply to your storefront. Have counsel review your plan. This article is general information, not legal advice.

The rules differ by country. A link-out flow that is permitted for U.S. users may not be allowed in other storefronts. If your audience is international, turn the feature on only in regions where it is allowed.

Google Play Alternative Billing

Google Play has offered alternative billing options in some markets, separate from its standard billing system. Its U.S. terms have also been shaped by litigation, in this case Epic v. Google. Alternative billing on Google Play has often come with a reduced service fee rather than no fee. Confirm Google's current program terms, eligibility and fee structure before you model your Android economics.

The practical takeaway: the platform fee on a linked or alternative purchase may not be zero. Treat it as a variable in your model, not an assumption.

In-App Purchase vs. Web Payment: Fee Math on a $9.99 Subscription

App store commission and web checkout costs are different kinds of expense. The app store bundles payment processing, fraud handling, refunds and often tax collection into one percentage. On the web, you pay for each of those separately. Some of those costs show up as risk rather than as a line item.

The table below is illustrative only. The commission percentages are sample inputs, not a statement of Apple's or Google's current terms. The web processing rate is also a sample. Replace every number with your actual rates.

Sales tax is excluded for simplicity.

Factor in Conversion Drop-Off

A higher margin per sale only helps if people finish paying. Each extra step loses some buyers, whether it's leaving the app, waiting for a browser to load or typing card details. Compare each path by net revenue per user who taps "Subscribe," not by margin alone.

Here is an illustrative example. Say 100 users tap the subscribe button, and 70 of them complete an in-app purchase.

• At the illustrative 30% commission: 70 × $6.99 = $489.30. To match that, your web checkout needs just over 54 completions ($489.30 ÷ $8.99). Web conversion can fall to roughly 78% of in-app conversion before you lose money.
• At the illustrative 15% commission: 70 × $8.49 = $594.30. Your web checkout needs just over 66 completions to match. Web conversion can only fall to roughly 94% of in-app conversion before you lose money.

The second case matters most. If you already pay a reduced commission, the margin gap may be too small to absorb normal checkout friction. Run this math with your own numbers before you invest in the build.

Price Points and Billing Frequency Matter

Card processing usually includes a fixed per-transaction fee, which weighs heavily on small tickets. In the illustrative numbers above:

• A $9.99 monthly charge costs $0.60 to process, or about 6% of the price.
• A $79.99 annual plan costs about $2.70 to process, or roughly 3.4% of the price.

This is why many developers send users to the web for annual plans first. Fewer, larger charges keep processing costs low as a share of revenue. They also mean fewer renewals that can fail or be disputed. Our subscription payment processing guide covers how to reduce failed renewals once you control billing.

What You Take on When You Process Payments Yourself: Refunds, Disputes, Tax

When a user pays through the app store, Apple or Google is the seller. When the user pays on your website, you are the merchant, and the platform's back-office work becomes yours.

Refunds and Customer Support

App store users are used to requesting refunds from Apple or Google. Web buyers will come to you. You need:

• A written refund policy that is easy to find before purchase
• A way for users to cancel without contacting support, where the laws of the states your customers live in require it
• Support staff or tools that can look up a web purchase by email or account ID

Chargebacks and Friendly Fraud

On the web, a cardholder can dispute a charge with their bank. Each dispute can carry a fee, and a high dispute ratio can put your merchant account at risk with the card networks. Digital subscriptions tend to draw a few common dispute patterns:

• "I didn't recognize this charge." The billing descriptor doesn't match the app name users know.
• "I cancelled." The user cancelled in the app's settings and assumed that also covered a web subscription.
• "Someone else bought this." A family member made the purchase, or someone used a stolen card.

Read up on spotting and fighting friendly fraud and on winning "cancelled recurring" chargebacks. Adding 3-D Secure authentication at checkout can also help reduce fraud-related disputes on card-not-present payments.

Sales Tax and Auto-Renewal Laws

App stores generally handle sales tax and VAT on in-app purchases. On the web, that responsibility may shift to you. Several U.S. states tax digital goods or software subscriptions, and the rules vary. See our overview of sales tax on software subscriptions by state, then confirm your obligations with a tax professional.

Recurring billing is also regulated. Many states have automatic renewal laws covering disclosures, consent and cancellation. These laws generally depend on where your customers live, not where your business is based. Our state-by-state map of automatic renewal laws is a useful starting point. Confirm your obligations with a qualified attorney.

Getting Approved for a Merchant Account

Processors underwrite digital goods and subscription businesses carefully, especially those with free trials or high refund rates. Describe your business accurately on the application, including your products, billing model and trial terms. Use the correct merchant category code. If you have been declined before, our guide to why digital products merchant accounts get flagged explains what underwriters look for.

If you don't want to handle tax and compliance yourself, compare merchant of record vs. payment processor models. A merchant of record takes on more of that work, usually at a higher cost.

Designing the Link-Out Flow so Users Actually Complete Payment

Conversion drop-off is the biggest threat to your web margin. Every step you remove protects revenue.

1. Identify the user before they leave. Pass a secure, short-lived token in the link so the checkout page already knows who the user is. Don't make people log in again in a browser.
2. Show the price clearly at checkout. Display the plan, billing frequency, renewal terms and cancellation method above the pay button.
3. Offer wallets. App users are used to one-tap payment. If your gateway supports Apple Pay or Google Pay on your web checkout, offer them so mobile users don't have to type card details.
4. Keep the page mobile-first and fast. Use a single page with a short form and no navigation menus that lead users away.
5. Return users to the app automatically. Put a universal link or deep link on the confirmation page so the user lands back in the app with access already unlocked.
6. Follow the platform's presentation rules. Apple and Google may require specific wording, placement or disclosure screens for external links. Follow them exactly. Trying to work around them risks app rejection or removal.
7. Measure every step. Track how many users tap the link, load the page, start payment and complete it, so you can see where they drop off.

For gateway and checkout setup, see our ecommerce payment processing guide. MannyPay's online payment processing supports card-not-present acceptance through payment gateways such as Authorize.net and NMI.

Syncing Web Purchases Back to In-App Entitlements

A user who pays on the web and then hits a paywall in the app is likely to request a refund, file a dispute or leave a bad review. Entitlements must work reliably from day one.

Build a Server-Side Source of Truth

• Store each user's access level on your own server, tied to their account rather than their device.
• Update access from your gateway's webhooks (payment succeeded, renewal failed, refunded, disputed). Don't rely only on the confirmation page loading.
• Have the app check your server for access at launch and when the user returns from checkout.

Handle the Edge Cases

Tell users where to cancel. A web subscriber who checks iPhone settings won't find the subscription there. Put a "Manage Subscription" link in the app that opens your web account page.

When Staying on App Store Billing Still Makes Sense

Linking out isn't the right move for every app. In-app billing may still be the better choice when:

• You already pay a reduced commission. As the math above shows, the gap may not cover the cost of checkout friction.
• Your products are low-price, impulse purchases. Small consumables and in-game items depend on instant, one-tap buying.
• You sell in many countries. Handling international tax, currency and fraud yourself can cost more than you save.
• Your team is small. Running support, disputes and compliance in-house takes real time.
• Your users rely on app store features. Family sharing, familiar refund flows and centralized subscription management matter to some audiences.

Many developers run both. They keep in-app purchase as the default and offer a web option for annual plans or for users who already have an account.

Next Steps

1. Pull your actual commission tier and current platform terms for each storefront.
2. Plug your numbers into the per-user model above to find your break-even conversion rate.
3. Get quotes for card-not-present processing that include gateway, dispute and fraud-tool costs.
4. Build entitlements and cancellation flows before you launch the link.
5. Test with a small group of users and measure completion rates before a wide rollout.

If you're setting up web billing for an app, MannyPay's payment solutions cover online acceptance, payment gateways and 3-D Secure authentication, subject to underwriting. Request a free processing quote, and a MannyPay specialist will respond within one business day.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.