How to Avoid High App Store Commission Fees While Onboarding
The most common way to avoid high app store commission fees while onboarding is to move the onboarding and the first payment out of the app and onto the web. A user clicks an ad, goes through a quiz or onboarding flow in the browser, pays on a web paywall, then installs the app and logs in. The store is not involved in that first payment, so its commission does not apply to it. Apple charges up to 30% on in-app purchases, or 15% under its Small Business Program.
This is not a loophole, and it is not free. You take on payment processing, taxes, refunds and support, and you have to stay inside store rules that vary by region and change over time. Below: what actually changes in onboarding, how the main options compare, and what to check before you commit.
Why store fees hit hardest at onboarding
Onboarding is where most subscription revenue starts. If every new subscriber pays through in-app purchase, the store takes its cut on the first payment and on renewals. For a young app with thin margins on paid acquisition, that cut can decide whether a channel is profitable.
To see how much it matters for you, calculate it from your own data:
- Take your gross subscription revenue for the last full month.
- Multiply it by the commission rate that applies to you (15% or 30% for Apple, and check Google Play's current rate separately).
- Compare that number with your monthly paid acquisition spend and your payment processing costs on the web.
If the store cut is larger than the cost of running a web checkout, the move is worth a serious look. If it is smaller, you may be better off optimizing your existing in-app paywall.
How to move from in-app purchases to a web subscription
Moving from in-app purchases to a web subscription is mostly a funnel and billing change, not a rewrite of your app. The usual steps:
- Pick the entry points. Start with traffic you control: paid social, search, creators, email. Do not touch your organic App Store installs at first.
- Build the web onboarding. Recreate the first-run questions as a quiz or onboarding flow in the browser, ending in a personalized result.
- Add a web paywall and a payment provider. Stripe is the common starting point. More on this below.
- Connect entitlements. After payment, the user's account must be marked as subscribed in the backend or in your subscription tool, so the app unlocks on login.
- Handle the install handoff. The user downloads the app and logs in with the same email or account they used on the web.
- Keep in-app purchase as a fallback. Users who install organically or who do not come through the funnel still need a way to pay in the app.
The typical flow looks like this: ad, landing page or quiz, personalized plan, paywall, payment, app download and login. Each step can be measured, which is one of the side benefits.
What changes in onboarding when the first payment is on the web
Several things behave differently from an in-app flow.
Account creation moves earlier. In-app, you can let users explore before asking for an email. On the web, you need an email or login before or at payment, because that is how the app will recognize them later. Ask for it right before the paywall, after the user has invested time in the quiz.
The quiz does more work. A browser has no product to show yet, so the quiz has to build the case: goals, current habits, a result the user cares about. A quiz builder helps here, but the real work is the question design.
The paywall is a page, not a system dialog. You control copy, price display, trial terms and layout, and you can test them. You also carry the responsibility for clear terms, cancellation instructions and local consumer rules.
Attribution gets better. A web funnel carries UTM parameters and can send server-side events to ad platforms. In-app flows lose much of that signal. If you run paid social, this can improve how your campaigns optimize, though you should measure it instead of assuming it.
There is a handoff step that can leak users. Some people pay and never install. Plan for a confirmation email, a clear download button, and a way to log in without friction. Track the share of payers who reach their first app session; that is your leak rate.
Web paywall with Stripe: what you need
A web paywall with Stripe is the simplest way to start. At minimum you need:
- A Stripe account with subscription products and prices that mirror your app plans.
- A hosted or embedded checkout on your paywall page.
- Webhooks from Stripe to your backend or subscription tool, so a successful payment becomes an active entitlement.
- Email receipts and a cancellation path, such as a customer portal link.
- A way to match the web customer to the app user, usually by email or an account ID.
You can build this yourself with engineering time, or use a funnel builder that already ships the paywall, Stripe connection and event tracking. A paywall builder such as web2wave's covers that part without code. Stripe is available on all web2wave plans, and some teams later add other processors for specific markets.
Whichever route you take, test refunds, failed renewals and plan changes before you send paid traffic. Those edge cases are where support tickets come from.
App store commission alternatives compared
There is no single way to bypass app store fees, and the word "bypass" oversells it. These are really different setups with different trade-offs. Here they are compared factor by factor.
Who handles the first payment
- In-app purchase only: The store.
- Web checkout built in-house: You, through your own payment provider integration.
- Web2app funnel built with a funnel builder: You, through a payment provider connected to the builder.
Commission on the first payment
- In-app purchase only: The store's rate, up to 30% on Apple, 15% under the Small Business Program.
- Web checkout built in-house: No store commission, but you pay payment processing fees.
- Web2app funnel built with a funnel builder: No store commission, plus processing fees and the builder's own cost.
Engineering effort
- In-app purchase only: Lowest, the store handles billing UI.
- Web checkout built in-house: Highest: checkout, webhooks, entitlements, analytics, testing tools.
- Web2app funnel built with a funnel builder: Low to moderate: you connect your subscription tool and login.
Onboarding control
- In-app purchase only: Limited to what you can ship in an app release.
- Web checkout built in-house: Full, but every change needs a developer.
- Web2app funnel built with a funnel builder: Full, and non-developers can edit flows and run experiments.
Refunds, taxes and support
- In-app purchase only: Largely handled by the store.
- Web checkout built in-house: Yours. Depending on the provider, tax handling may be yours or the provider's.
- Web2app funnel built with a funnel builder: Yours, with the setup depending on the payment provider you choose.
If you want a broader look at tools in this category, the guide to web2app funnel builders goes through the options.
Risks and compliance: check before you move traffic
Store policy on external payment links and web purchases differs by country and has changed more than once. Before you send any user from an app to an external checkout, read the current App Store Review Guidelines and Google Play policy for the regions you sell in. Do not rely on a blog post, including this one, for a legal answer. Our web2app funnel compliance guide lists the points to review.
Beyond store rules, check these:
- Linking from the app. Whether and how your app may point users to a web purchase depends on region and current policy. A funnel that starts from an ad and ends with an app install is a different case from an in-app button that opens a checkout.
- Pricing consistency. If web and in-app prices differ, users notice. Decide your policy before launch.
- Consumer law. Trial terms, auto-renewal disclosure and cancellation rules apply in the US, UK and EU, and the details differ.
- Refunds and chargebacks. The store used to absorb this friction. Now you do. Track refund rate and dispute rate from day one.
- Taxes. VAT and sales tax on digital subscriptions are your concern or your payment provider's. Confirm which with your provider and accountant.
None of this means you should not move. It means the saving is real only after you subtract processing, tooling, support and compliance work. Compute net savings from your own numbers, not from a headline percentage.
Where a funnel builder like web2wave fits
web2wave is a no-code builder for web2app funnels: quiz and onboarding flows, web paywalls, A/B experiments, UTM and attribution tracking, a user CRM and email sequences, with AI localization into 40+ languages. It connects to subscription tools such as RevenueCat, Adapty, Qonversion, Superwall and Apphud, and sends server events to Meta, TikTok and Snapchat pixels. You can see the full list of integrations before deciding whether it fits your stack. More than 3,000 web funnels are active on the platform.
Two public examples show what teams do with this kind of setup. MyMental AI GURU generated over $100K in revenue with web2wave, with about 55% of subscribers still active, refunds under 5% of revenue and paying users from 40+ countries. Leya AI scaled its funnel roughly tenfold with localization. These are single-company results and not a forecast for your app.
It is one option among several. If you have a strong engineering team and a very specific checkout need, building in-house may be the better fit.
How to test the move without risking your revenue
Run the web funnel as a controlled experiment, not a migration.
- Send a defined slice of paid traffic to the web funnel and keep the rest on the current in-app path.
- Compare the two groups on the same period: cost per paying subscriber, refund rate, first-month retention and revenue per install, all after fees.
- Change one thing at a time in the funnel, such as quiz length, paywall copy or trial structure. A/B testing is how you separate funnel changes from traffic noise.
- Only then increase the share of traffic going to the web path.
Keep an eye on the whole path, not just checkout conversion. A funnel that converts well on the web but loses half the payers before their first app session will not deliver the saving you expect.
FAQ
Can I bypass app store fees completely?
Not completely. You can avoid the store's commission on payments that happen on the web, such as the first payment in a web2app funnel. Purchases made inside the app are still subject to store rules and fees, and policies vary by region and change. Check the current App Store Review Guidelines and Google Play policy.
How do I avoid app store fees on a subscription app?
Move the onboarding and first payment to a web funnel, connect a payment provider such as Stripe, and unlock the app when the user logs in. Keep in-app purchase available for users who come in another way. Then compare net savings after processing, tooling and support costs.
Is a web paywall with Stripe enough?
It is enough to take payments. You also need webhooks to grant access in the app, a cancellation path, receipts, tax handling and tracking. You can build these yourself or use a funnel builder that includes them.
Will users drop off if they have to leave the app to pay?
Some may, which is why the web funnel is usually used for traffic that has not installed yet, such as ads. The risk sits in the handoff from payment to install and login. Measure the share of payers who reach their first app session and fix the leaks there.
Do I need developers to move to web subscriptions?
Building everything in-house needs developers. A no-code funnel builder reduces that work, but you still need someone to connect your subscription tool, set up app login and test the full flow before sending paid traffic.
To see how a web2app funnel would work for your app, book a demo or start free.
.webp)
