Content
Try for free

IAP vs Web Checkout: Fees, Trade-offs and When to Use

In-app purchase (IAP) sells your subscription through Apple or Google billing inside the app. Web checkout sells it on your own website or funnel, and the user then installs the app and logs in. The main difference is who processes the payment, and that decides who takes the commission, who owns the customer relationship and who handles refunds.

For most subscription apps the choice is not either/or. Apple charges up to 30% commission on in-app purchases (15% under the Small Business Program). Web checkout avoids that commission where store rules allow it, but you take on payment setup, tax handling, support and compliance. Many teams run web checkout for paid traffic and keep IAP as a fallback inside the app.

What is the difference between IAP and web checkout?

With IAP, the user taps a paywall in the app, confirms with Face ID or a Google account, and the store charges them. The store is the merchant. It manages the subscription, renewals, receipts and most refund requests. You get a purchase event through the store's server notifications or a tool such as RevenueCat, Adapty or Qonversion.

With web checkout, the payment happens before the user opens the app. A typical web2app funnel looks like this: ad, landing page or quiz, personalized plan, paywall, payment, then app download and login. You choose the payment provider (Stripe, Paddle, PayPal and others), and you hold the customer's email, payment history and attribution data from the first click.

The user experience differs too. IAP is one tap inside an app the user has already installed. Web checkout asks the user to enter payment details in a browser, and it works best when the user has already invested time in a quiz or onboarding flow before reaching the paywall.

How do the fees compare?

IAP costs a percentage of every transaction. Apple's rate is up to 30%, or 15% for developers in the Small Business Program. That share comes out of revenue before you see it, so it also reduces how much you can spend on ads and still break even.

Web checkout replaces the store commission with payment processor fees, which depend on your provider and contract, plus the cost of the tool you use to build the funnel. Check your provider's current rates rather than relying on a general number. Processor fees are usually lower than the store commission, but they are not zero, and you also pay for tax handling, chargebacks and support time.

Funnel builder pricing varies by model. On web2wave, Basic is $199/mo (up to 1,000 quiz starts), Starter is $590/mo (up to $10k revenue per month) and Pro is $990/mo (up to $40k revenue per month). These plans are flat monthly fees. Only the Advanced plan is a revenue share, at 2% of revenue with a $1,390/mo minimum. Whichever tool you pick, compare its fee with the commission you would otherwise pay on the same revenue.

IAP vs web checkout compared

Here is how the two options compare on the factors that matter most for subscription apps.

Commission

  • IAP: Up to 30% to Apple (15% under the Small Business Program).
  • Web checkout: Payment processor fees instead, which depend on your provider.

Customer data

  • IAP: The store holds the billing relationship. You see purchase events and whatever identifiers you set up.
  • Web checkout: You hold the email, payment history and funnel answers from the first visit.

Attribution

  • IAP: Depends on mobile attribution after install. Signal from ad click to purchase is harder to connect.
  • Web checkout: UTM parameters and ad pixels with server events track the whole path from click to payment.

Conversion path

  • IAP: One tap for the user, but the paywall appears only after install.
  • Web checkout: The user pays before install, so you can personalize the offer from quiz answers. Entering card details adds friction, which wallets such as PayPal can reduce.

Refunds and support

  • IAP: The store handles most refund requests. You have limited control over them.
  • Web checkout: You or your payment provider handle refunds and disputes, and you set the policy.

Tax and compliance

  • IAP: The store acts as the merchant and handles billing compliance.
  • Web checkout: Depends on your provider. A merchant-of-record provider such as Paddle takes on more of the tax work than a direct processor does.

Store rules

  • IAP: Fully within store policy.
  • Web checkout: Allowed where store rules and local regulation permit. Rules differ by region and change over time.

What do you gain and lose with web checkout?

The gains are mostly about margin and information. You keep a larger share of each payment, and you know who the customer is before they install. That lets you send email sequences, run win-back campaigns, and connect ad spend to subscription revenue with server-side events to Meta, TikTok or Snapchat. It also lets you test pricing and paywall variants without an app release.

The losses are real, so plan for them. Card entry in a browser converts differently from a one-tap store purchase, and the gap depends on your traffic and offer. You own refunds, chargebacks and customer support. You need subscription management that links the web payment to an in-app entitlement, so the user is unlocked when they log in. And you must follow store guidelines and regional rules about steering users to external payments.

One public example shows what the model can produce. MyMental AI GURU (Latiwara OÜ) generated over $100K revenue with web2wave. About 55% of its subscribers remain active, refunds are under 5% of revenue, and paying users come from 40+ countries. Results like this depend on the app, offer and traffic, so treat the case as an illustration, not a forecast.

When should you keep IAP, and when should you move to web checkout?

Keep IAP as the main path when most of your installs are organic or come from store search, when your users are already inside the app and ready to buy, or when your market's rules make external payments hard to use. IAP is also the simplest option for a small team that does not yet have the capacity to run support and payments.

Move paid traffic to web checkout when you buy installs from Meta, TikTok or similar channels and your margin is under pressure from the store commission. A funnel that collects quiz answers first can show a personalized plan, which gives the paywall more context than a generic in-app screen. If you advertise in several countries, localizing the funnel matters as well.

The hybrid setup is the most common one. Paid traffic goes through a web funnel, and everyone else sees the in-app paywall. A subscription tool such as RevenueCat, Adapty, Qonversion, Superwall or Apphud can unify entitlements from both sources, so a user who paid on the web has the same access as one who paid in the app. Read the web2app funnel compliance guide before you launch, because the rules depend on your platform and region.

How do you set up a web checkout funnel?

Start with the path a user takes from ad to app. Build the landing page or quiz, then the personalized plan, then the paywall and payment, and finally the install and login step. Each step needs tracking, so you can see where users drop off.

web2wave is a no-code builder for these web2app funnels. It covers quiz and onboarding flows, web paywalls, A/B experiments, UTM attribution, a user CRM and email sequences. Stripe is available on all plans. PayPal, Paddle and Unlimit start on Pro, and Primer.io, Solidgate, Braintree and Adyen are on Advanced. You can design the payment step with the paywall builder. Pro also adds A/B testing and a custom domain, and Advanced adds AI localization into 40+ languages. If you want a hand with the build, web2wave also offers a Growth Service with done-for-you funnels.

Whatever tool you use, follow this order:

  1. Pick the payment provider and decide who handles tax.
  2. Connect your subscription tool so web purchases unlock the app on login.
  3. Add ad pixels and server events so conversions reach your ad platforms.
  4. Test the paywall with two or three variants before you scale spend.
  5. Keep an IAP paywall in the app for users who did not come through the funnel.

FAQ

Is web checkout cheaper than IAP?

Usually, because processor fees are typically lower than the store commission of up to 30%. You also pay for the funnel tool, tax handling and support, so compare the total cost on your own revenue.

Can I use web checkout and IAP together?

Yes. Many apps send paid traffic to a web funnel and keep IAP inside the app. A subscription management tool can merge both purchase types into one entitlement, so users get the same access either way.

Does web checkout convert worse than IAP?

It depends. Card entry adds friction, but a quiz and personalized plan before the paywall can raise purchase intent. Test it against your own baseline with an A/B experiment rather than trusting a general figure.

Who handles refunds with web checkout?

You or your payment provider do, instead of the store. That gives you control over the refund policy, but you need a support process. MyMental AI GURU reports refunds under 5% of revenue, though results vary by app.

Is web checkout allowed on iOS?

It is allowed where store rules and local regulation permit, and those rules differ by region and change over time. Check current guidelines for each market and read a compliance guide before you launch.

Want to see how a web2app funnel could work for your app? Book a demo or start free.

Share this Article

Build your web funnel with web2wave

Start using web funnels: Launch faster, convert better, and keep more revenue with no app store limitations