One React Native subscription stack for iOS, Android and web
React Native teams often end up with two subscription systems: the native stores for mobile and a separate web checkout with its own reconciliation logic. The react-native-purchases web path narrows that gap by letting the same SDK and the same entitlements system cover a web build alongside iOS and Android. This guide maps the moving parts, the configuration branch, and the calls that remain native-only.
What the web support actually changes
The package react-native-purchases now has a web path. A browser build can host plan selection and account management while the mobile apps read the same entitlement state, so the browser stops being a page that only advertises the product. The practical gain is architectural: one SDK, one entitlements source, and no bespoke bridge between a web billing provider and the native purchase records.
This is not a claim that web and native purchases are the same transaction. They are separate rails that converge on one backend. That distinction drives almost every configuration and limitation below.
Two purchase rails, one entitlements view
On iOS and Android, the SDK talks to the App Store and Google Play. On the web, purchases go through the Web Billing product, which uses Stripe or Paddle as the payment processor. Web Billing is deliberately separate from native in-app purchases, but it writes into the same entitlements system, so access can be granted across platforms when the same appUserID is used.
From the app's side, subscription state should look the same no matter where the customer originally paid. A web sign-up can unlock premium features in the mobile app without platform-specific branching in your entitlement logic.
Configuration map: one branch, three keys
The setup is a platform branch at initialization. The web build receives a Web Billing public API key; iOS and Android keep their native public keys. The supplied configuration module shows the exact shape of that branch and should be used as-is rather than paraphrased.
A quick control map for the branch:
- Platform.OS === 'web' → Web Billing public API key.
- Platform.OS === 'ios' → public Apple API key.
- Platform.OS === 'android' → public Google API key.
After configuration, entitlement checks are written once. The supplied entitlement and offering module demonstrates that the same calls — checking offerings, reading customer info, purchasing a package — are intended to work on all three platforms. The app logic does not need to ask where a subscription was bought.
Dashboard side: a Web Billing app and web products
Enabling web purchases is not only a client change. You also create a Web Billing app in the dashboard and configure products for web. Those products sit alongside the iOS and Android products but are billed through Web Billing rather than the native stores. Treat the dashboard product setup and the client key branch as one checklist item: a web key without web products will not produce a working purchase flow.
Expo: faster iteration, same native testing requirement
For Expo projects, the web path is useful during development. Subscription UI, entitlement logic and integration flows can be previewed in the browser without immediately building a custom development client. That shortens the loop between a change and a visible result.
It does not remove the native testing step. Real in-app purchases on iOS and Android still require an Expo development build. Web support lowers early setup cost; it does not substitute for store-environment testing.
What does not work on web
Web billing is a different rail, so some native-store operations have no web equivalent. Web purchases require Web Billing and cannot process native iOS or Android in-app purchases. Operations that depend on native store APIs are unsupported in web environments, including getProducts, purchaseProduct and restorePurchases. Expo Go and similar sandbox environments do not support purchasing either.
The supplied restore example illustrates the boundary: a restorePurchases call is valid on iOS and Android but not on web. If your shared code calls it unconditionally, guard it by platform rather than assuming a silent no-op.
For web subscriptions, customers manage their plans through the vendor-hosted customer portal, which provides a consistent way to update or cancel outside the native stores.
A pre-flight checklist
Before shipping a shared subscription build, confirm each item:
- The web build initializes with the Web Billing public API key, not a native key.
- A Web Billing app and web products exist in the dashboard alongside the native products.
- Entitlement checks use the same entitlement identifiers on every platform.
- The same appUserID links a web purchase to the mobile account.
- getProducts, purchaseProduct and restorePurchases are guarded so they are not called on web.
- Native purchase testing happens in an Expo development build, not Expo Go.
- Web customers are pointed to the vendor-hosted customer portal for plan changes and cancellation.
Where this fits
For a React Native app already selling on mobile, adding the web surface is now a configuration and product-setup task rather than a second billing integration. The SDK and entitlements layer stay shared; the differences are the key used at startup, the products configured for web, and the native-only calls that need a platform guard.
Frequently asked questions
Are web purchases the same as iOS or Android in-app purchases?
No. They are separate rails. Web purchases go through the Web Billing product with Stripe or Paddle as the processor, while iOS and Android purchases go through the App Store and Google Play. Both feed the same entitlements system.
Which API key does the web build use?
The web build initializes with a Web Billing public API key. iOS and Android continue to use their native public keys, selected by the platform branch at startup.
Which SDK calls are unsupported on web?
getProducts, purchaseProduct and restorePurchases depend on native store APIs and are not supported in web environments. Expo Go and similar sandbox environments also do not support purchasing.
Can I test real purchases in Expo Go?
No. Real in-app purchases on iOS and Android require an Expo development build. The web path helps you preview subscription UI and entitlement logic earlier, but it does not replace that build.
How do web subscribers change or cancel their plan?
They use the vendor-hosted customer portal, which provides a consistent way to update or cancel subscriptions outside the native app stores.