Skip to content
AppDues
Log in
Contact salesSign up

Keep more revenue with a single web purchase button

A web purchase button adds a hosted checkout option to an existing paywall.

People who choose it leave the app briefly, pay on the web, and return with access already unlocked. That gives you a way to offer web pricing where store rules allow it, while keeping the native purchase path available.

Decision checklist: should you enable it, and where?

Use this checklist before enabling the button for a segment:

  • Confirm the current app-to-web purchase rules for each country and platform you plan to target, including how the link must be presented.
  • Create the web product in the product catalog first, so the button has something to sell.
  • Build or edit the paywall, add the button component, and link it to that web checkout.
  • Set Targeting so the button appears only where it is allowed, by country, platform, and scenario.
  • Decide the fallback: if no web product is available for a person, show native in-app purchase instead of a dead end.
  • Publish and test the full loop — button tap, web checkout, return to app, unlocked access — with no app update required for paywall changes.

Compliance is a targeting decision, not a one-time switch

Store rules on linking from an app to web payment have been changing, including after the April 2025 Epic v Apple ruling, which opened more markets for Apple and Google. Requirements still vary by market and platform, so the practical control is Targeting: show the button only in places that meet policy, and expand instantly when new markets open. If a web product is unavailable, automatic fallback to native in-app purchase protects the sale.

Test web versus in-app, then iterate

Treat the button as an experiment, not just a new link. Split traffic between an in-app-only paywall and a web-eligible version, then compare the full funnel — not only immediate conversion, but longer-term impact as well. Because web and in-app transactions feed the same charts, webhooks, and integrations, you can read results in one place.

For iteration, you can change wording such as a web savings message, adjust discounts, or rearrange layout without waiting for another app store review. That makes the paywall a faster place to test price and copy hypotheses.

Example using the captured setup: create a web product, add the button to a paywall variant, target it to an eligible country and platform, and run it against the in-app-only variant. If the web variant wins on net revenue after processing fees, expand Targeting; if it does not, keep the fallback and revise copy or discount before retesting.

Frequently asked questions

Availability of the button is worldwide, but permission to use it depends on App Store and Google Play policy in each country. Apple still requires in-app purchase alongside external payments, so removing it entirely is not the intended setup. Web checkout uses Stripe Billing, with standard processing fees plus the normal plan fee. Analytics stay unified across web and in-app transactions.

ConfigureTargetTest

Frequently asked questions

Is the Web Purchase Button available worldwide?

The button itself can be shown worldwide. Whether it may be used in a given country depends on App Store and Google Play rules there. Targeting lets you limit visibility by country, platform, and scenario, and you can widen it later without an app update as rules change.

Can or should I remove IAP entirely?

No. Apple still requires in-app purchase to be offered alongside external payment options. You can present both and test the mix, rather than removing in-app purchase entirely.

What payment processor is used by the Web Purchase Button?

Web checkout is handled through Stripe Billing, with standard processing fees plus the normal platform plan fee. Other payment platforms were described as coming soon.

Will using the Web Purchase Button mess up my analytics?

Web and in-app purchases are combined in the same charts, webhooks, and integrations, so reporting does not need to be split manually.