Sell app subscriptions on the web. Manage them in one place
Selling outside the app stores does not have to split your subscriber data.
This page explains how a web checkout can feed the same entitlement system your mobile apps already use, which billing engine you can bring, and how to choose between a hosted checkout link and a paywall embedded on your own site.
What you can do with a web subscription flow
A web purchase path gives you four practical levers. First, you can point paid traffic at a web paywall instead of the App Store, so campaign reporting reflects which ads produce paying subscribers, not only installs. Second, you can place a button inside your app that opens a web checkout, a route the product overview frames as a way to bypass the 15–30% App Store fees on new purchases, upgrades, and reactivations. Third, you can test offers that store rules or review delays would otherwise block, including lifetime deals, guarantees, discounts, and bundles. Fourth, you can run email win-back campaigns that offer a discount to churned subscribers, a route the overview frames as keeping more of the revenue than a store sale would leave you. Before relying on any of these levers, model the economics for your own catalog: compare the store commission you would otherwise pay against your processor fees, refund exposure, and the cost of the traffic or messaging that drives the web purchase, then treat the result as a planning estimate rather than a guaranteed margin.
Pick the billing engine that fits your business
You are not locked into a single payment processor. Three options are described: the built-in billing engine, positioned as the fastest route from zero to a working web checkout; Stripe Billing, where you connect an existing Stripe account; and Paddle Billing, where you connect a Paddle account if you prefer its merchant-of-record model. In each case the web subscription is kept alongside your mobile subscribers in one unified record. Which engine suits you depends on factors worth checking directly with each provider: the currencies and payment methods you need, who is the merchant of record, how tax and invoicing are handled, and what settlement timing your finance team requires. Treat the positioning above as a starting hypothesis and confirm current capabilities and commercial terms before you commit.
Two ways to sell on the web
The first surface is a hosted checkout link. You generate a link and place it in an email, an ad, or an in-app button; the checkout flow runs across three screens and can be live in minutes without engineering work. The second surface is an embedded paywall built with the Web SDK. It uses the same visual editor, A/B tests, and targeting rules as your mobile paywalls, with full control over design through Experiments. Many teams use both surfaces.
Checkout components worth planning for
Two components shape the purchase experience. Native-feeling checkout means adding Apple Pay and Google Pay buttons so a single tap can start the purchase, which reduces friction. Easy app-to-web setup means dropping a single button into your app that sends users to the web checkout. Both are implementation choices you can adopt independently of which billing engine you connect.
How access reaches the app after a web purchase
After a web purchase, the system generates a redemption link: a one-tap deep link that opens your app and grants the correct entitlements automatically. No custom syncing logic is required. Whether the purchase happened on the web, on iOS, or on Android, the subscriber has a single unified record covering entitlements, purchase history, and analytics. That record is the authoritative reference your app checks when it decides what to unlock.
Track campaigns to revenue, not just installs
You can pass UTM parameters through to your web paywall so campaign reporting reflects paying customers rather than installs alone. Web and mobile subscription data then flows into the platform's charts and into your MMP through pre-built integrations. The practical input is the UTM string on the traffic you send; the practical output is revenue attribution by campaign.
Compliance and fees: what to check before you build
Compliance depends on your specific implementation. For app-to-web purchases you must be enrolled in an approved program such as Apple External Purchase Links, while web-to-app funnels have more flexibility. On cost, standard platform pricing applies based on the monthly tracked revenue that flows through your account, with no extra fee for the web capability itself, and payment processor fees are paid separately to Stripe, Paddle, or the built-in billing engine. Because program eligibility, store rules, and fee schedules change, verify the current requirements for your region and app category, and confirm the applicable pricing and processor terms, before committing to a flow.
A short decision checklist
Use these questions to choose a starting configuration. (1) Do you already have a website? If not, a hosted checkout link is the lower-effort path. (2) Do you need the same paywall design and experiments on web and mobile? If so, plan for the embedded Web SDK surface. (3) Do you already run Stripe or Paddle? Connecting an existing account keeps your processor relationship. (4) Do you want the shortest setup? The built-in billing engine is positioned for that. (5) Will you drive traffic from inside the app? Confirm you qualify for an approved external-purchase program first. (6) Do you need campaign-level revenue reporting? Plan to pass UTM parameters to the paywall.
Web platform vs. billing engine: a one-line mental model
The web platform is the whole capability set: the Web SDK, web paywalls, and integrations. The built-in billing engine is one engine you can run inside that platform, powered by Stripe. If you connect Stripe or Paddle instead, you are still using the web platform; you have simply chosen a different engine underneath.
| Engine | What you bring | Positioning |
|---|---|---|
| Built-in billing engine | Nothing external; built-in engine | Fastest path from zero to web checkout |
| Stripe Billing | An existing Stripe account | Keep your current processor relationship |
| Paddle Billing | A Paddle account | Merchant-of-record model |
Engine descriptions reflect the supplied product overview; confirm current capabilities and pricing with the provider.
| Surface | Where it lives | Setup effort | Design control |
|---|---|---|---|
| Hosted checkout link | Email, ad, or in-app button | Generate a link; live in minutes, no engineering | Three-screen checkout flow |
| Embedded Web SDK paywall | Your own website | Embed via Web SDK | Same visual editor, A/B tests, and targeting as mobile |
Many teams use both surfaces; effort descriptions are qualitative, not measured.
Frequently asked questions
Do I need a website to sell subscriptions on the web?
No. A hosted checkout page can be linked from your app, an email, a social post, or an ad. If you do have a website, the Web SDK lets you embed a full paywall experience directly into your page.
How do entitlements sync between web and mobile?
Automatically. When a user purchases on the web, the entitlement system makes the subscription active as soon as they open your iOS or Android app. No custom syncing logic is needed.
Can I use my existing Stripe or Paddle account?
Yes. You can connect an existing Stripe or Paddle account, and web subscriptions stay in sync with mobile subscribers in a single unified record.
Is this compliant with Apple and Google rules?
It can be, when used correctly. The platform provides infrastructure for complying with platform rules for both web-to-app and app-to-web purchases. For app-to-web, you must be enrolled in an approved program such as Apple External Purchase Links. Web-to-app funnels have more flexibility. Compliance always depends on your specific implementation, so review current documentation for details.
What are the fees?
Standard platform pricing applies, based on the monthly tracked revenue that flows through your account. There is no extra fee for the web capability. Payment processor fees are paid separately to Stripe, Paddle, or the built-in billing engine.
How is the web platform different from the built-in billing engine?
The web platform is the complete set of capabilities for selling on the web, including the Web SDK, web paywalls, and integrations. The built-in billing engine, powered by Stripe, is one engine you can use as part of that platform. In short: the platform is the whole; the billing engine is one component.