Launch powerful web-enabled paywalls in minutes
Drag, drop, and go live, all before your coffee gets cold. With built-in hosting, zero PCI concerns, and instant unlocks, you’ll ship faster than ever.
Explore the docs
Built on our native Paywall editor
Just drag-and-drop the button component, and direct to a web purchase; Available in all our SDKs 5.25.1 / 8.11.3+ and up
No hosting, no PCI scope
RevenueCat serves the checkout and handles payments via Stripe Web Billing, with other payment platforms coming soon
Automatically unlock access
Users land back in-app with access unlocked, while the SDK invalidates cache for you
Compliant 
by default, flexible 
by design
Platform rules around app-to-web purchases are evolving. Following the April 2025 Epic vs Apple ruling, Apple and Google now allow apps to link to web payments in more markets, with specific requirements on how those links are shown. RevenueCat gives you the tools to follow those rules, based on the latest app-to-web purchase guidelines.
You decide where the Web Purchase Button appears using Targeting, so it's only shown in countries, platforms, and scenarios that meet store policies. When new markets open up, you can expand instantly; no app update required. If a web product isn't available, we automatically fall back to native IAP, so you never lose a sale.
Smarter paywalls, more revenue
A/B testing tools and analytics make optimizing conversion easy.
![]()
Measure what matters
Split traffic and compare IAP-only versus web-eligible paywalls in real time. See full funnel analytics to understand immediate and long-term impact
![]()
Iterate your way to success
Swap copy (“Save 30 % on web”), discounts, or layouts without another App Store review
How to ship a paywall with the Web Purchase Button
- Create a web product in the product catalog
- Edit or build a paywall in the paywall builder
- Add a purchase button and link it to your web checkout
- Publish and test instantly, no app update required
Frequently asked questions
The Web Purchase Button can be shown worldwide. Whether you’re allowed to use it depends on App Store and Google Play policies in each country. As those rules continue to open up, you control where the button appears using Targeting; no app update required. For details on what’s allowed today, see the app-to-web purchase guidelines.
No. Apple still requires offering IAP alongside external payments. RevenueCat lets you show both or run tests to find the right mix.
RevenueCat Web Billing uses Stripe, with standard processing fees plus your normal RevenueCat plan fee. Other payment processors are coming soon.
All web and in-app transactions roll into the same charts, webhooks, and integrations automatically.
Ready to grow?
Our entire suite of features comes standard and it's free to get started.