Skip to main content
Skip to navigation

Stripe Billing

Sell Stripe Billing products in RevenueCat Web

Ask RicoChatGPTClaude

RevenueCat integrates with Stripe Billing, allowing you to sell Stripe products and subscriptions through RevenueCat's Web purchase flows.

With this integration, you can:

  • Sell Stripe Billing products and subscriptions via RevenueCat's hosted Web Purchase Links
  • Build flexible web to app funnels with Web Funnels, and use them with a Stripe checkout
  • Integrate RevenueCat's Web SDK to handle Stripe Billing purchases in your web app, and unlock entitlements on mobile
  • Build and A/B test RevenueCat's web paywalls connected to a mobile-optimized Stripe Checkout
  • Import Stripe Billing purchases that happen outside of RevenueCat, and unlock feature access with the RevenueCat SDK in your mobile app. (see Importing external purchases).

Web Paywall with Stripe Checkout

Before configuring Stripe Billing, be sure to review the compatibility notes below.

This page is the canonical setup reference for Stripe Billing provider configuration, product import, external purchase tracking, and sandbox setup. Use Connect to your Stripe account for shared Stripe connection details that also apply to RevenueCat Billing.

RevenueCat feature compatibility​

RevenueCat FeatureCompatibility
Importing external purchases✅ Supported
Web SDK✅ Supported
Web Purchase Links✅ Supported
Web Paywalls✅ Supported
Web Funnels✅ Supported
Redemption Links✅ Supported
Web SDK product changes✅ Supported (beta)

Stripe feature compatibility​

AreaNotes
Pricing modelsOnly per-unit and recurring quantity plans are supported. Tiered, usage-based, and customer-chooses pricing are not. Price type changes are also not supported after import: once a Stripe price is imported into RevenueCat, its price type cannot be changed.
Repeat consumablesWith Stripe Billing, a customer can purchase the same consumable one-time product more than once. Each purchase creates a new transaction and fires a fresh webhook. RevenueCat does not block repeat purchases of Stripe consumables. To limit a consumable to a single purchase per customer, enforce that restriction in Stripe. Subscriptions and non-consumable products still can't be purchased again by the same customer.
Payment methodsAsynchronous payment methods that settle off-session — bank debits (us_bank_account, sepa_debit, acss_debit, au_becs_debit, bacs_debit, nz_bank_account, pay_by_bank), bank transfers (customer_balance, multibanco), and cash vouchers (boleto, konbini, oxxo) — are not supported in RevenueCat purchase flows. PayPal and UPI are also not currently supported. Redirect-based payment methods, which open another page or app to approve the payment, are not currently supported either. These include Cash App Pay, iDEAL, Bancontact, Revolut Pay, and buy now, pay later methods such as Klarna. To enable other payment methods, edit the Stripe Billing (RevenueCat) payment method configuration in your Stripe dashboard. With Managed Payments, Stripe controls which payment methods are available.
Revenue calculationsProrated amounts from upgrades and downgrades are not factored into MRR or Revenue. Disable proration in Stripe or pass prorate=false for accurate figures.
CancellationsBoth immediate and end-of-period cancellations are supported. MRR/Revenue is only accurate for immediate cancellations when proration is disabled. Cancellations may take up to two hours to reflect in RevenueCat.
PausingTo pause a Stripe subscription, use Stripe's Pause subscription API. This requires flexible billing mode. Use Pause subscription, not Pause payment collection. Pause payment collection keeps the subscription active, so the customer keeps access. RevenueCat revokes access immediately when the subscription is paused, but does not currently send a SUBSCRIPTION_PAUSED event for Stripe. For more details, see Pausing Stripe subscriptions.
Billing issuesRevenueCat generates a billing issue event once when payment fails. No new events are created for subsequent retry failures. Configure retry behavior and failure handling under Settings > Billing > Subscriptions and email > Manage failed payments in Stripe.
Subscription managementCustomer self-service subscription management (cancellations, plan changes, receipts) is handled via the Stripe Customer Portal. The RevenueCat Billing Customer Portal does not apply. To let existing subscribers upgrade or downgrade from your own web app instead, use Web SDK product changes. Stripe manages the proration for those changes.
EmailsAll transactional emails are sent by Stripe, with the exception of the redemption email (see Redemption Links), which is always sent by RevenueCat.
Free trialsFree trials are supported in RevenueCat purchase flows. Add a trial to a price when you import it into RevenueCat. Free trials from external Stripe purchases are also reflected accurately in RevenueCat Charts and customer events.
CouponsStripe coupons are supported in RevenueCat purchase flows. Use the Checkout settings on your Stripe configuration to control whether the coupon field is shown at checkout. Coupons from external Stripe purchases are also correctly reflected in RevenueCat Charts and customer events.
Test ClocksStripe Test Clocks are not fully supported. Time divergences between Stripe and RevenueCat may cause data to be inaccurate.

1. Connect your Stripe account​

⚠️Project owner requirement

Only the owner of the RevenueCat project can connect a Stripe account. Collaborator roles aren't able to add or remove a Stripe connection.

Log in to the correct Stripe account​

If you don't have a Stripe account yet, create one now.

If you're connecting a Stripe Sandbox for testing, make sure you're logged into that. If you're connecting a live Stripe account, make sure this is currently selected in your Stripe account switcher.

Install the RevenueCat Stripe App from the Stripe App Marketplace​

Log into the RevenueCat dashboard, go to your account settings and click the Connect Stripe button.

Again, make sure that the correct account is selected at the top right corner of the screen first.

Install the RevenueCat App and accept the required app permissions:

📘Stripe app permissions

RevenueCat only requests the permissions from Stripe found here. These permissions are necessary for RevenueCat to interact with your Stripe account, track your purchases and initiate Stripe Billing purchases within our platform. If the RevenueCat Stripe App is uninstalled, all permissions are revoked and RevenueCat will no longer be able to interact with your Stripe account in any way.

Connect your RevenueCat account to the RevenueCat Stripe app​

Click on View Stripe app settings and sign in with RevenueCat, from within the Stripe App:

After this, the connected Stripe account should be listed in your RevenueCat account settings page (you may need to refresh the page):

📘Connect to more than one Stripe account

You can connect to multiple Stripe accounts by repeating the steps above. Make sure you are signed into the correct account in the Stripe dashboard each time. You can then assign different accounts to each of your Stripe configs in RevenueCat.

Working with Stripe Test Mode and Sandboxes​

Stripe has two options for testing in a sandbox environment:

  • Test Mode (Might not be available if your Stripe account hasn't completed onboarding for live transactions. Does not support Managed Payments.)
  • Sandboxes (newer, function as isolated test accounts. Support Managed Payments.)

We recommend using Sandboxes for testing Stripe Billing purchases in RevenueCat. See Stripe's comparison for more details.

Stripe Sandboxes in RevenueCat​

Since sandboxes function as standalone accounts, you'll need to install the RevenueCat Stripe app in each sandbox you wish to use, and create a dedicated config in RevenueCat.

To use a Stripe sandbox for testing:

  1. Switch to the sandbox you wish to connect to RevenueCat.
  2. Install the RevenueCat app from the Stripe Marketplace.
  3. Follow the remaining steps on this page to add a config and configure RevenueCat purchases.
  4. Connect your live account and create an additional Stripe config for it in the RevenueCat dashboard when transitioning to live purchases.

2. Create a Stripe config​

After connecting your Stripe sandbox or live account, create a Stripe web config inside the RevenueCat project where you want to use Stripe.

  1. In your project, go to Web in the lower section of the project dashboard.
  2. Create a web config for Stripe.
  3. Enter a configuration name and select the Stripe account (either a sandbox or live account) you connected in the previous step.

Once created, the config has several tabs for further configuration:

Purchase tracking​

The Use Managed Payments when Available toggle controls whether Stripe Checkout is initiated in Managed Payments mode across all purchase flows using this config — Funnels, Web Purchase Links, and the Web SDK. This can be enabled at creation or changed here later. If a product is not eligible for Managed Payments or the feature is not enabled on your Stripe account, the checkout will fall back to standard Stripe Billing mode. See Stripe Managed Payments.

This tab also contains External Purchase Tracking settings for importing purchases that happen outside of RevenueCat purchase flows. You can choose whether RevenueCat registers an active subscription when Stripe creates its invoice or after the invoice is paid. This choice applies to automatic tracking and manual receipt submissions. See Track External Purchases for details.

Enable Redemption Links to allow anonymous purchases — users don't need a registered account to complete a purchase. You can configure a custom URL scheme in the mobile SDK to handle redeeming the purchase in your app after checkout. See Redemption Links for full details.

Appearance​

Customize the look of purchase flows using this Stripe config, including app icon, logo, and brand colors. These settings also apply to the Stripe Checkout that is embedded in your purchase flows.

Subscription management​

Configure the Stripe Customer Portal URL (or a custom URL) to direct customers to manage or cancel their subscriptions. This URL is returned in the managementUrl property of the SDK's CustomerInfo object and anywhere else customers should be directed to manage their purchases.

You can configure the Stripe Customer Portal in your Stripe dashboard settings.

Tax behavior​

When RevenueCat reports revenue and tax figures for Stripe Billing transactions — in webhooks, scheduled exports, integrations, and the Revenue chart — it needs to know whether the listed product price is treated as already including tax or not. This is controlled by the configuration's tax behavior setting. It only affects how taxes are calculated and reported for revenue figures; it does not change the price your customer is charged at checkout.

Configuration createdDefault tax behavior
On or after May 1, 2026Tax-excluded — the listed price is treated as containing no tax. Revenue is reported at the full listed amount; tax_percentage is 0 unless Stripe provides a precise value via Stripe Tax.
Before May 1, 2026 (legacy)Legacy behavior — RevenueCat estimates a tax portion within the listed price, and revenue figures are reduced accordingly. See How we estimate taxes for the underlying calculation.

The customer-facing transaction price is the same under both behaviors. Only the breakdown between revenue and tax in RevenueCat's reporting changes.

📘Switching an existing configuration to the new default

Stripe Billing configurations created before May 1, 2026 keep the legacy behavior by default. To switch an existing configuration to tax-excluded, contact RevenueCat support. Switching changes the revenue and tax figures that RevenueCat reports for transactions on this configuration going forward, so review the impact on your dashboards, exports, and downstream integrations before opting in.

3. Create products and prices in Stripe​

Create and manage your products directly in the Stripe dashboard.

Considerations:

  • The product description field in Stripe will be displayed in the purchase flow, if you add it.
  • We recommend adding a product image (e.g. your app icon), which is presented in Stripe's mobile-optimized checkout
⚠️One price per product recommended

In Stripe, a product can have multiple prices. Because a product in RevenueCat maps directly to a single Stripe product, only one price can be selected per product when importing. We recommend creating a single price per Stripe product to avoid ambiguity in your purchase flows.

To sell every price on a Stripe product instead, see Multiple prices per Stripe product.

Pricing model compatibility​

These Stripe pricing models can be sold within RevenueCat Web purchase flows:

  • Recurring - flat rate (e.g. $1.99 per month)
  • One-off - flat rate (e.g. $23.99 paid once)

These pricing models are only supported when synced as external purchases:

  • Recurring - package pricing (e.g. $5.99 per 10 units / month)
  • One-off - package pricing (e.g. $30.00 per 12 units)

These pricing models are currently not supported in either mode:

  • Recurring - tiered pricing (e.g. starts at $1.99 per unit + $5.00 / month)
  • Recurring - usage based (e.g. $13.99 per unit / month - based on metered usage)
  • One-off - customer chooses price
📘Repeat purchases of consumable products

With Stripe Billing, a customer can buy the same consumable one-time product multiple times through RevenueCat purchase flows. Each purchase creates a new transaction and triggers a fresh webhook. RevenueCat does not prevent repeat purchases of Stripe consumables. To limit a consumable to a single purchase per customer, configure that restriction in Stripe.

Subscriptions and non-consumable products can't be purchased twice by the same customer.

📘Stripe Managed Payments compatibility

If you intend to use Stripe Managed Payments, ensure the product tax code selected in Stripe is compatible with Stripe Managed Payments. Products that don't meet this requirement will fall back to standard Stripe Billing checkout.

4. Import Stripe products into RevenueCat​

Once your Stripe products and prices are set up, import them into your RevenueCat project via the Product Catalog.

  1. In the Product Catalog, navigate to Products and select the Stripe config you created.
  2. Click Import. RevenueCat will display all products available in your connected Stripe account.
  3. Check the products you want to import. If a product has more than one price, select which price to use in RevenueCat purchase flows.
  4. Click Import to confirm. Successfully imported products will appear with a Published status.

If your Stripe products carry more than one price each, see Multiple prices per Stripe product for importing each price as its own RevenueCat Product.

5. Create an Offering​

With your Stripe products imported, create an Offering to group them for use in purchase flows.

  1. In the Product Catalog, go to Offerings and create a new Offering.
  2. Enter an identifier and display name.
  3. Create a Package for each product you want to present, and select the corresponding Stripe product from your Stripe config for each package.

Once your Offering has at least one package, it can be used in Web Purchase Links, Web Paywalls, Web Funnels, and the Web SDK.

6. Add payment domains to enable Apple Pay & Google Pay​

RevenueCat automatically registers its hosted checkout domains (pay.rev.cat for Web Purchase Links and signup.cat for Funnels) with your Stripe account, so Apple Pay and Google Pay work out of the box on those domains. If you've configured a custom domain for Funnels, it is also auto-registered with Stripe once the domain is verified.

If you're initiating purchases with the Web SDK on your own domain, you'll need to register that domain yourself. Follow the steps here to add it in your Stripe account.

If Apple Pay or Google Pay don't appear in your checkout despite auto-registration, the RevenueCat app in your Stripe account may have pending permission updates that need to be approved. See Troubleshooting for details.

7. Use Stripe in RevenueCat purchase flows​

  1. Go to Funnels in the project dashboard, then use the Purchase Links section to create a web purchase link.
  2. Select the Offering and the Stripe config you created.
  3. Complete the remaining settings and publish the link.

Use the Sandbox or Production link depending on the type of Stripe account you've connected. Stripe Checkout is embedded directly inside the web purchase link.

Web Funnels​

See detailed instructions on how to create Web Funnels.

  1. Go to Funnels in the project dashboard and create a funnel from scratch or from a template.
  2. Under Checkout Settings, select your Stripe config.
  3. For the Paywall step, select the Offering that contains your Stripe products.

After publishing the funnel, use the Sandbox or Production URL to test or deploy. Stripe Checkout is embedded in the Checkout step of the funnel.

Web SDK​

When initializing a purchase via the Web SDK, use the Stripe config you created. Refer to the Web SDK documentation for implementation details. To let existing subscribers upgrade or downgrade from your web app, see Web SDK product changes.

Stripe promotion codes​

Customers can redeem Stripe promotion codes in Stripe Checkout or open a Web Purchase Link or Web Funnel with a code supplied in the URL. Create the coupon and its customer-facing promotion code in Stripe, in the same account and environment used by your Stripe config. Pass the promotion code text, such as SAVE20, rather than a coupon ID or a promo_ ID.

Enable promotion codes​

  1. Open your Stripe config under Web in the RevenueCat dashboard
  2. In the Checkout settings, enable Allow promotion codes and save the config
  3. To accept codes from a URL, also enable Allow discount codes on the Web Purchase Link or the funnel's checkout step
  4. Save the Web Purchase Link, or publish the funnel to apply the change

Both settings are opt-in. Existing links and funnels require you to enable the setting and save or publish them.

The Stripe config's Allow promotion codes setting also enables manual code entry in Stripe Checkout. The link or funnel's Allow discount codes setting controls forwarding codes supplied in the URL.

Pass a code in the URL​

Append ?discount_code=SAVE20 to the shared Web Purchase Link or funnel URL. If the URL already contains query parameters, append &discount_code=SAVE20 instead. URL-encode the code when constructing the link.

For example, an anonymous Web Purchase Link with Redemption Links enabled can use:

https://pay.rev.cat/<your-link-token>?discount_code=SAVE20

For a Web Funnel, add the parameter to the funnel's entry URL. The funnel carries the code to checkout.

Checkout behavior​

Offering and paywall prices remain undiscounted. Stripe validates and applies the promotion code when creating Checkout, where the customer sees the final payable total.

If the code can't be resolved or Stripe rejects the discount, Checkout can continue without a pre-applied discount. Test your code in sandbox and check the final total before sharing the URL with customers.

Stripe Billing uses Stripe promotion codes. The Automatically apply code selector and Show code input field setting for RevenueCat Billing discounts don't apply to Stripe Billing. Use the URL parameter to supply a code and the Stripe config's Allow promotion codes setting to enable manual entry.

This flow applies to Stripe Checkout. Promotion codes aren't supported by the Web SDK's separate express Apple Pay button.

8. Test your Stripe configuration​

We recommend using Stripe Sandboxes for testing. Each sandbox connection requires a dedicated Stripe config in RevenueCat, with products imported and offerings configured.

Stripe Billing sandbox subscriptions use full subscription periods. Stripe's Test Clocks can advance billing time in Stripe, but RevenueCat continues to use real time, so customer status and events in RevenueCat may not match what you see in Stripe. See Stripe feature compatibility.

Implementation considerations​

Renewal webhooks and access on your backend​

When a Stripe subscription renews, Stripe moves it into the next billing period as soon as the previous period ends. Collecting the renewal payment can finish later. RevenueCat extends the Entitlement when the new period starts, but the RENEWAL webhook is sent only after Stripe confirms the invoice has been paid.

Because of this, purchased_at_ms represents the start of the new period, not when the webhook was sent. Payment can complete later, so there can be a gap between the renewal period starting and the webhook being sent. You can use event_timestamp_ms to see when RevenueCat created the event.

We recommend against removing access as soon as the previous expiration_at_ms passes. During this gap, the cached expiration can be in the past even though the subscriber is still entitled in RevenueCat while payment is pending. Instead:

  • Keep access active until you receive an EXPIRATION webhook, and update the cached expiration when the RENEWAL webhook arrives. A missing RENEWAL webhook does not mean the subscription has expired.
  • Or, if the cached expiration has passed, call GET /subscribers before removing access. RevenueCat will already return the new expiration during this gap.

For more information on syncing access from webhooks, see Syncing Subscription Status.

Pausing Stripe subscriptions​

Pausing a Stripe subscription revokes the customer's entitlement in RevenueCat immediately. RevenueCat mirrors Stripe's subscription status. Stripe requires the subscription to use flexible billing mode.

Pause it with Stripe's Pause subscription API, or the Pause subscription action in the Stripe Dashboard. Don't use Pause payment collection. RevenueCat picks the status change up from the Stripe integration automatically.

When Stripe sets the subscription status to paused, RevenueCat revokes the entitlement immediately. The customer profile shows the subscription as paused and the entitlement as inactive.

For a pause that starts and ends on set dates, use a pause schedule on a Stripe subscription schedule. RevenueCat updates access when the subscription actually becomes paused, and again when it resumes.

Webhook events​

RevenueCat does not send SUBSCRIPTION_PAUSED for Stripe.

A Stripe pause currently produces:

  • BILLING_ISSUE
  • CANCELLATION with cancel_reason BILLING_ERROR
  • EXPIRATION with expiration_reason BILLING_ERROR

Stripe payment failures also use BILLING_ERROR. See Cancellation and Expiration Reasons.

⚠️Paused subscriptions look like billing failures

A Stripe pause sends the same events as a payment failure. You cannot tell them apart from the webhook events alone.

To distinguish a pause from a real billing failure, check the subscription status in RevenueCat (paused vs in_grace_period, in_billing_retry, or expired), the customer profile, or the subscription status in Stripe (paused vs past_due or unpaid).

Resuming the subscription restores the entitlement. If Stripe creates a new invoice and that invoice is paid, RevenueCat sends a RENEWAL. A resume that does not create a new invoice does not send a RENEWAL.

Was this page helpful?