Skip to main content
Answer

Creating Stripe customers based on RevenueCat subscriptions

  • September 19, 2025
  • 1 reply
  • 61 views
R
Forum|alt.badge.img+2

I’m evaluating RevenueCat for our in-app subscription integration.
We have the following requirements:

  • We currently handle web based subscriptions using Stripe.
  • We want to add the option to purchase subscriptions via in-app purchases.
  • We want to see customers subscribed via the app stores in our Stripe dashboard and their subscription status
  • We already integrate our user account system with Stripe and want to do minimal changes, ideally when an app store customer would be created the existing should be able to connect it with the user account without modifications

My questions:

  • How can we sync app store subscribers to Stripe?
  • I’ve looked at the RevenueCat Stripe app in the Stripe marketplace, but couldn’t figure out how to use it properly, it talks about sending Stripe tokens to RevenueCat. Not sure I understand it correctly, but this sounds like RevenueCat tries to be the single source of truth for Stripe based web subscriptions. As I understand it this is the opposite to what we want.

Any help or guidance would be greatly appreciated.

Best answer by jeffrey_bunn

Hi ​@rmridev! You’re correct that the integration tends to go the other way. When Stripe purchases happen, you can either POST the purchase tokens to RevenueCat (so we can track your subscribers/metrics and unlock entitlements for your customers) or allow RevenueCat to automatically track Stripe purchases via server notifications. 

Customers who purchase on mobile platforms are not automatically created in Stripe, as RevenueCat is the source of truth for subscriptions/entitlements, and Stripe can’t handle subscription management for non-web purchases.

If you want RevenueCat to handle in-app purchases and entitlement management for your subscribers, I’d suggest:

  1. POSTing Stripe purchases to RevenueCat, via either of the methods above
  2. Integrating in-app purchases for mobile customers
  3. Setting up webhooks. You can catch purchase events and, if desired, sync various attributes to Stripe.

That said, our customers tend to use RevenueCat for metrics and subscription/entitlement management, with the Stripe dashboard being a secondary resource, rather than the primary one.

This post has been closed for comments

1 reply

jeffrey_bunn
RevenueCat Staff
Forum|alt.badge.img+6
  • jeffrey_bunn
  • RevenueCat Staff
  • Answer
  • September 23, 2025

Hi ​@rmridev! You’re correct that the integration tends to go the other way. When Stripe purchases happen, you can either POST the purchase tokens to RevenueCat (so we can track your subscribers/metrics and unlock entitlements for your customers) or allow RevenueCat to automatically track Stripe purchases via server notifications. 

Customers who purchase on mobile platforms are not automatically created in Stripe, as RevenueCat is the source of truth for subscriptions/entitlements, and Stripe can’t handle subscription management for non-web purchases.

If you want RevenueCat to handle in-app purchases and entitlement management for your subscribers, I’d suggest:

  1. POSTing Stripe purchases to RevenueCat, via either of the methods above
  2. Integrating in-app purchases for mobile customers
  3. Setting up webhooks. You can catch purchase events and, if desired, sync various attributes to Stripe.

That said, our customers tend to use RevenueCat for metrics and subscription/entitlement management, with the Stripe dashboard being a secondary resource, rather than the primary one.

R
Terms & ConditionsCookie settingsAccessibility statement