Web vs. App Store Subscriptions: Cutting Platform Fees Legally

On this page 8 sections

1. What Apple and Google Take on Subscriptions Today
2. Linking Out to Web Checkout on iOS and Alternative Billing on Android
3. Fee Math: Web vs. App Store Subscriptions at Scale
4. Conversion Drop-Off and How to Minimize It
5. Who Handles Refunds and Chargebacks in Each Model
6. Migrating Existing In-App Subscribers to Web Billing
7. Setting up App Subscription Payment Processing
8. Next Steps

Key takeaways

• Web billing can cost less than app store commissions, but only if conversion loss, overhead and any platform fees on linked purchases don't erase the gap.
• Apple and Google rules for linking to outside checkout in the U.S. have changed and may still be changing, so confirm current terms before you build.
• On web checkout you become the merchant of record, which makes refunds, chargebacks, sales tax and auto-renewal compliance your responsibility.
• Existing in-app subscribers can't be moved automatically. Plan a timed, opt-in migration that avoids double billing.

If you sell a subscription inside a mobile app, the platform's commission is probably one of your largest costs. This guide on web vs. app store subscriptions compares what Apple and Google keep with what it costs to run billing on your own payment processor. It explains where U.S. link-out rules are heading and gives you a break-even formula. It also walks through the conversion, refund and chargeback tradeoffs that decide whether moving subscribers to web checkout actually pays off.

This is general information, not legal advice. Platform policies and court-ordered changes have moved quickly. Confirm current terms in your developer accounts and with counsel before you change your billing flow.

What Apple and Google Take on Subscriptions Today

When a customer subscribes through in-app purchase, the platform acts as the merchant of record. It charges the payment method stored in the user's Apple or Google account, handles the receipt, and sends you proceeds after deducting its commission.

Both platforms use tiered commission structures. Smaller developers enrolled in the platforms' programs can typically get reduced rates. Subscriptions can also qualify for lower rates, but the conditions vary by platform, including whether subscriber tenure matters. Your actual rate depends on your program enrollment, your revenue and the specific terms in your agreements. Pull the exact figures from your Apple and Google developer account agreements rather than relying on headline numbers.

The commission isn't pure cost. In exchange for it, the platform covers:

• Card processing and payment acceptance
• Stored payment credentials and one-tap purchasing
• Collection and remittance of sales tax and VAT in many jurisdictions
• Refund handling and customer billing support
• Chargeback exposure, because disputes land on the platform's merchant account rather than yours

When you compare web and app store costs, measure web billing against everything you'd have to replace, not just the processing rate.

Linking Out to Web Checkout on iOS and Alternative Billing on Android

For years, both stores restricted apps from steering users to cheaper outside payment options. Recent U.S. litigation and regulatory pressure have loosened those anti-steering rules for apps distributed in the U.S. storefronts. The details have shifted more than once, and some remain subject to appeals and policy updates.

Check these points before you design a flow to link out to web checkout on iOS:

1. Whether external links and buttons are permitted in your app category, and in what form (button styling, placement, wording).
2. Whether the platform shows its own disclosure or interstitial before users leave the app.
3. Whether any commission applies to purchases made through the link. This has the largest effect on your math. If a fee applies to linked purchases, your savings shrink by that amount.
4. Whether you must also offer in-app purchase alongside the web option.

On Android, Google has offered alternative billing options in some markets and has faced its own U.S. court-ordered changes. Eligibility, service fees on alternative billing and user-choice requirements can differ from Apple's approach. Check the current terms in your Google developer account, and treat the two platforms as separate projects.

Rules outside the U.S. storefront differ. A link-out permitted for U.S. users may not be permitted elsewhere, so check your build flags by region.

Fee Math: Web vs. App Store Subscriptions at Scale

Card processing almost always costs less than the store commission. The real question is how much net revenue you keep per subscriber once you account for lost conversions. Wanting to avoid the Apple App Store subscription fee entirely only makes sense if the web flow keeps enough buyers.

The Break-Even Formula

• In-app net per subscriber = price × (1 − store commission)
• Web net per subscriber = price − card processing − per-subscriber overhead − any platform fee on linked purchases
• Break-even conversion = in-app net ÷ web net

Web billing wins if your web flow converts at least the break-even share of the users who would have bought in-app.

An Illustrative Example

All numbers below are illustrative only. They are not current Apple, Google or processor rates. Replace them with your own contract terms.

At the lower commission tier, the web flow has to keep about 92% of would-be buyers just to break even. At the higher tier, it can lose about a quarter of them and still come out ahead.

Three factors move this math more than most teams expect:

• Low price points. A fixed per-transaction fee hurts a $2.99 plan far more than a $29.99 plan.
• Annual plans. Billing once a year means one fixed fee instead of twelve, and fewer failed renewals.
• Fees on linked purchases. If the platform takes a commission on link-outs, rerun the formula. The case for leaving may get much weaker.

For a closer look at the software layer, see our comparison of subscription billing costs for Stripe Billing, Recurly and Chargebee.

Conversion Drop-Off and How to Minimize It

In-app purchase is hard to beat on friction. The user's payment method is already stored, and they confirm with a fingerprint or face scan. Every extra step on the web costs you buyers. These tactics help close the gap:

• Offer wallet payments. Apple Pay and Google Pay on your web checkout restore something close to one-tap purchasing.
• Prefill identity. Pass a signed token in the link so the user arrives logged in, with their email already filled in.
• Keep it to one page. Put the plan, price, renewal terms and payment fields on a single mobile-optimized page.
• Return users to the app instantly. Use a deep link or universal link so access unlocks without a manual re-login.
• Show the value plainly. If current platform rules allow you to show a lower web price, say so clearly. If they don't, lead with other benefits, such as easier plan management.
• Test before you switch fully. Send a share of new users through the link-out and measure completed subscriptions, not clicks.

Don't trade conversion for fraud exposure. Tools like 3D Secure authentication can shift liability on fraud disputes. Our guide to 3D Secure without lost sales explains how to apply it selectively.

Who Handles Refunds and Chargebacks in Each Model

This tradeoff is the one merchants most often underestimate. Moving to web billing moves risk onto your merchant account.

Pay attention to the statement descriptor. Subscribers used to seeing the app store on their statement may not recognize a new charge and may dispute it. Use a clear, recognizable descriptor and send a receipt for every renewal.

You'll also need a written refund policy. Our guide on whether your subscription refund policy should be prorated, partial or none covers the options. Expect "I cancelled" disputes, and have the playbook in how subscription sellers win cancelled recurring chargebacks ready before launch. Watch your chargeback ratio thresholds closely for the first few months after migration.

Migrating Existing In-App Subscribers to Web Billing

You generally can't transfer an existing Apple or Google subscription to your own processor. The billing relationship belongs to the platform, so migration is opt-in and the subscriber has to take action.

A clean migration usually follows these steps:

1. Segment first. Start with monthly subscribers near renewal. Approach annual subscribers only when their term is ending.
2. Read expiration dates server-side. Use platform receipt and notification data so you know exactly when each in-app period ends.
3. Prevent double billing. Have the user cancel auto-renew in their Apple or Google account, then start the web subscription when the paid in-app period ends. Don't charge for days they've already paid for.
4. Collect consent properly. Show the price, billing frequency, renewal terms and cancellation steps before the first charge. Store the card as a credential-on-file with the customer's agreement.
5. Communicate through your own channels. Use email and account pages you control, and follow current platform rules on in-app messaging.
6. Keep entitlements in one place. Your backend should grant access from either source so no one gets locked out mid-switch.

State automatic renewal laws apply once you're the merchant of record. They can include rules on consent, reminders and online cancellation. See our state-by-state automatic renewal law compliance map and confirm the details with counsel.

Setting up App Subscription Payment Processing

Have the payment infrastructure in place before your first link-out goes live:

• A merchant account approved for recurring billing. Subscription businesses often land in a medium-risk tier. Expect underwriting to review your cancellation flow, refund policy, terms and projected volume. Our guide to getting a merchant account approved for a subscription business explains what reviewers look for. Tell your processor about the expected jump in volume up front, because a sudden spike can trigger holds.
• A gateway that tokenizes cards and supports recurring billing. MannyPay supports online payment gateways like Authorize.net and NMI and integrates with major e-commerce platforms.
• Card account updater and smart retries. These keep renewals from failing when cards expire. See how to reduce failed subscription payments and churn.
• A sales tax plan. Taxability of digital subscriptions varies by state. Confirm your obligations with a tax professional.

MannyPay provides e-commerce and online payment processing for low- and high-risk merchants, and a specialist can review your recurring billing needs. Approval and pricing depend on underwriting.

Next Steps

1. Pull your actual commission rates from both developer accounts.
2. Confirm current U.S. link-out rules and any fees on linked purchases.
3. Run the break-even formula with your real price, processing quote and overhead.
4. Test the web flow with a share of new users before migrating existing subscribers.

If the numbers work, request a free processing quote from MannyPay. A specialist will respond within one business day to review your volume, billing model and setup options.

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.