Should a SaaS with a mobile app use RevenueCat or Stripe for subscriptions?
It depends on where the purchase happens. Stripe, or another web payment provider, handles checkout in the browser. Inside an iOS or Android app, Apple and Google require their own billing for digital features, and RevenueCat is the layer that makes those store purchases manageable: one SDK, receipt tracking, and restores. A SaaS with web and mobile clients usually runs both and maps them to a single entitlement on its own server, so a customer who pays on either side gets access everywhere.
The store rules decide before you do
RevenueCat and Stripe are not competing answers to one question. Which one you use is set by where the customer pays, and inside a mobile app the stores make that choice for you.
Apple's App Review Guideline 3.1.1 says that if you want to unlock features or functionality within your app, including subscriptions, you must use in-app purchase. Google Play's Payments policy says Play-distributed apps that require or accept payment for access to in-app features or services must use Google Play's billing system, and its examples include subscription services and cloud software.
So a Stripe Checkout page inside your iOS or Android app is not an option for selling a consumer subscription. On the web, nothing changes: checkout runs through Stripe or another payment provider. Sources: App Review Guidelines and Google Play Payments policy.
The exceptions that matter to SaaS
Apple's guidelines list cases where other purchase methods are allowed. Four of them come up for SaaS products. These are summaries read on November 15, 2026, not legal advice. The guidelines change and App Review applies them case by case, so read the current text before you design a paywall.
- Multiplatform services (3.1.3(b)): an app may let users access subscriptions they bought on your website, provided those items are also available as in-app purchases within the app.
- Enterprise services (3.1.3(c)): an app sold only directly to organizations for their employees may let those users access previously purchased subscriptions. Consumer, single user, and family sales must use in-app purchase.
- Free stand-alone apps (3.1.3(f)): a free companion to a paid web-based tool does not need in-app purchase, but only for VoIP, cloud storage, email services, or web hosting, and only with no purchasing or calls to action in the app.
- United States storefront: the guidelines state that entitlements are not required for developers to include buttons, external links, or other calls to action in their United States storefront apps.
What each tool actually does
Stripe charges the customer on your behalf in the browser. RevenueCat does not charge anyone: Apple or Google does, and RevenueCat tracks the result so you do not integrate two store APIs yourself.
RevenueCat's price is on top of the store's commission, not instead of it. Its pricing page lists the service as free up to $2,500 in monthly tracked revenue, then 1% of tracked revenue. Source: RevenueCat pricing. For the web side, the Stripe fee calculator estimates processing fees.
| Stripe | RevenueCat | |
|---|---|---|
| Where the purchase happens | Browser checkout | App Store and Google Play in-app purchase |
| Who charges the customer | You, through Stripe | Apple or Google |
| What it adds | Checkout, invoices, subscription billing | One SDK for both stores, receipt tracking, restores, entitlements |
| Listed price | Per-transaction processing fees | Free up to $2,500 in monthly tracked revenue, then 1% |
| Server signal | Signed webhooks | Webhooks and a subscriber API |
One entitlement, two payment rails
The design that keeps this manageable: your server owns one record of what a customer may use, and both payment rails write to it. Feature checks read that record and never ask Stripe or RevenueCat directly.
supastack ships this boundary. The details below are what the kit does, and they are the parts that are easy to get wrong:
The RevenueCat setup guide covers the store and dashboard steps. For the web side of the same ledger, see idempotent billing webhooks and the payment provider comparison.
- Purchases belong to the workspace, not to a device or a single login, and only owners and admins can buy.
- A RevenueCat webhook never grants access by itself. It triggers a fresh server-side read of the subscriber's current state, so a forged or replayed event cannot unlock a plan.
- The webhook is authenticated with a shared secret before anything else runs.
- Refunded purchases do not count, grace periods are honored, and sandbox purchases are rejected in production.
- Mobile access is recorded under the same plan key the web plans grant, so a feature gate checks one thing.
Avoid charging the same customer twice
Two rails create one new failure: a customer who subscribes on the web and then again in the app. The fix is ordering. Ask your server for the entitlement before you render a paywall, and show the current plan instead of a purchase button when access is already active.
Tell customers where a subscription is managed. A store subscription is cancelled in the App Store or Google Play settings, and a web subscription is cancelled in your billing page. Sending someone to the wrong place is a support ticket and sometimes a refund.
Keep a visible restore action in the app. Apple's guideline 3.1.1 says you should make sure you have a restore mechanism for any restorable in-app purchases.
When you can skip RevenueCat
Not every product needs it. Skipping is reasonable in these cases:
You can also integrate StoreKit and Google Play Billing directly. That removes the RevenueCat fee and adds two APIs, receipt validation, and renewal handling to the code you maintain.
- The product is web only, or the desktop app loads the web app and uses web checkout.
- The mobile app is sold only to organizations and fits Apple's enterprise services exception.
- The mobile app has no purchasing at all and fits one of the narrow free companion categories.
Common questions about RevenueCat and Stripe
- Can I use Stripe inside my iOS app?, Not to unlock digital features for consumers in most storefronts. Apple requires in-app purchase for that, with the exceptions listed above. Stripe remains the right tool for your web checkout.
- Is RevenueCat free?, It is free up to $2,500 in monthly tracked revenue according to its pricing page, then 1% of tracked revenue. The store's own commission is separate.
- Does RevenueCat replace Stripe?, No. RevenueCat manages purchases made through the app stores. Web checkout still needs a payment provider, and your server ties both to one entitlement.
- Can I test purchases in Expo Go?, No. The native purchase module is not part of Expo Go, so you need a development build and a store sandbox account.
- What happens when a store purchase is refunded?, The next server-side read of the subscriber's state shows the refund, and access ends. That is why the server reads current state instead of trusting the event that announced a purchase.