Web Purchase FAQs
2025 Ruling on External Payment Options
In late April 2025, a U.S. District Court ruling found Apple in violation of a 2021 injunction meant to allow developers to direct users to external payment options, like Web Billing.
As a result, iOS developers are now permitted to guide users to web-based payment flows without additional Apple fees or restrictive design requirements.
Resources
FAQs
How do I add web payments to my iOS app?
Add a new app in your RevenueCat project and select Web Billing as the payment provider. RevenueCat also supports the web payment flow using Web Billing directly in RevenueCat Paywalls v2.
Read more in Configuring Web Billing.
What does the recent ruling mean for web payments outside of the United States?
This ruling only affects web payments in the United States. The App Store has existing restrictions on web payments outside of the United States.
Can I remove in-app purchases and exclusively use web payments in my app?
No. As of now, we understand the recent ruling to still require in-app purchases to be available alongside any web payment offers.
Can I use my existing web checkout with Paywalls v2?
Not yet, we are working on adding support for existing web checkouts with Paywalls v2.
Can I send a customer directly to the checkout flow for a given product?
Yes, but only if your offering has a single product. We are working on adding support for linking to a specific product in an offering.
If Stripe Chargeback Protection is enabled on my Stripe account, do RevenueCat Web Billing transactions remain protected?
Yes. Stripe Chargeback Protection covers transactions created through RevenueCat Web Billing when it’s enabled on your Stripe account.