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?
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?
@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?
+1 for requesting Paddle integration with RevenueCat.
@cody any update on where this is on the roadmap?
+1 paddle integration would be amazing. Is this coming any time soon?
+1 paddle integration or a way to sync web purchases with RC for analytics… switching from stripe to paddle to simplify foreign sales tax filing. It would be great to get RC LTV per Paying Customer charts on web users too, and/or app store buyers who purchase add-ons through web checkout.
+1 For Paddle integration :)
This is a dealbreaker, and we’ll probably have to move away from RC because of this. Updating the API to allow non-Stripe billing events would be a good enough way to handle this.
@cody How is this with the new REST API you’re currently developing? Anything in there that would make synching purchases without Stripe (or the native SDK of course)?
+1 for Paddle.
Is this on the roadmap? Or any other Merchant on Record web payment platforms? Selling internationally on Stripe is brutally complicated with all the international tax compliance
+1 for Paddle integration or any way subscribers can be created from there.
@cody a Paddle or REST integration for other services than Stripe would be really helpful. The issue with Stripe is that when you‘re based in Europe, you have a shitload of accounting to do if you do not use a merchant of record like Paddle. Zapier integration might also be interesting for these purposes.
@cody hey, is there any progress since this issue was first discussed? We want to enable web purchases for our multiplatform app and Paddle is basically the only choice to avoid huge tax compliance overhead.
+1 for Paddle integration. It is now a major obstacle to migrating our app to RevenueCat :/
Since there is no movement for 2 years on this matter: Has anyone successfully done this?
I am only referring to syncing subscriptions from web and app with Paddle + RC based on Cody's recommendation.
@Zachary Shakked