So my main app subscribes users to a plan, and that’s simple enough:
Stripe.js - Price - Create
Subscribe the user to a plan
This collects their cc info and lets me do dynamic pricing.
I’m working on embedding my product with a 3rd party. The second site will collect the user’s info and send it over, that’s simple enough with an API, where I’m struggling it with the subscription - what’s the best way to go about it?
Stripe Connect? Can they collect the user’s CC info and send that also over with the API? Should I send them my stripe keys and just have their app toggle my checkout page and then they send over the subscription ID in the API?
Hey @gilad, Good question and yeah, you’re right to pause before sending Stripe keys around definitely don’t do that.
The clean way to handle this is: let the 3rd-party site collect the user info and send it to your Bubble app through a secure API endpoint. Then, on your end, use a backend workflow to create the Stripe customer, attach their payment method, and start the subscription. That keeps everything safe and under your Stripe account.
If they need to handle payments directly, Stripe Connect is the way to go, it’s made exactly for that setup and keeps things compliant.
I’ve helped set up this kind of flow before (Bubble + external app + Stripe subscriptions), so if you’d like, I can help you map it out properly.
you will have to create sub-accounts on stripe, then set up for the logged-in user to generate these invoices that will be paid by their customers. The customer data of the third parties will not go to your account.
If you want to implement a commission (example: cade 5 dollars the user of the third spends I want to come to me 50 cents) look about slipt payment and implement.
