Solved

How to handle web subscriptions sync?

  • 23 August 2021
  • 3 replies
  • 48 views

Badge

We are using Paddle for web subscriptions and aren’t sure how to link userIDs and sync status with RevenueCat. Is there a way we can post userIDs and subscription status to RevenueCat so that when the user logs in on iOS we know if they are subscribed or not. The reason I want to do it this way is because otherwise we’ll have to create a new layer on our backend that tracks subscription status for all users and we will need to check that instead of the RevenueCat SDK which kind of defeats the purpose. 

 

Otherwise, we could first check if they are RevenueCat subscribed then check our backend too - which would work I think. But isn’t there some web sdk for subscriptions?

icon

Best answer by cody 23 August 2021, 18:10

View original

3 replies

Badge

More info: I see the REST API here https://docs.revenuecat.com/reference#receipts that we could use to create subscribers, but what should we put for the productID fields - can we just put a random stripe product (even if we aren’t using stripe) so that MRR / rest of the analytics/purchases appear?

 

I see you need some sort fetch token as well - is there a way around this? 

Userlevel 3
Badge +7

Hey @Zachary Shakked! 👋

We don’t support subscriptions from Paddle at the moment. For web payments, Stripe is the only supported platform and will require a Stripe account to be connected to your RevenueCat account so we can fetch updates from Stripe directly.

I’d be happy to add Paddle to our backlog as a platform/feature request, but for now we aren’t able to consume these purchases. You may be able to leverage our promotional entitlements system to replicate a transaction, but you’ll need to manage this manually from your end. This won’t be able to track purchase price / MRR / any analytics though, just entitlement access for your user. Does that make sense?

Badge

@cody I think a better roadmap piece than adding paddle would just allow arbitrary purchase sync and don’t require the fetch token parameter - wouldn’t that be easier? 

Reply