astro785

[crystal valve]

Hi 👋 moving your additional message into the thread to keep the main channel cleaner:

I thought of using connect for several reasons:

The simplicity of having only one API key to manage (the one of the master account)
The simplicity of onboarding for each store: when they first connect to the platform, I can generate a link to do the KYC on the Stripe side, with information prefilled.

But maybe that's not what Connect is for?

Another way of doing it would be to let each store create their own Stripe account, and make them enter their public/private API keys directly in the dashboard settings.

I’m not sure which path to follow here, can anybody enlighten me ? Thanks a lot ! 😁

That's a bit of a business decision question, but my thinking is the owner/operator of the service you're building would be the best owner of the Platform Stripe account.

I do think Connect will technically work the way you're describing, but would recommend double checking with our Support team if you're worried your use-case would clash with our terms or policies:
https://support.stripe.com/?contact=true

The other approach that comes to mind, is to build a Stripe App. They're similar to the Connect flows you were looking at, and have several different structures depending on your exact needs:
https://stripe.com/docs/stripe-apps/how-stripe-apps-work