#david-thorand_best-practices

1 messages ยท Page 1 of 1 (latest)

compact loomBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1328364749909655552

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

undone flint
#

Hmm, depends what you mean by 'multiple tenants'? Is this some kind of marketplace/platform?

wise basin
#

Right. Our users/customers will be able to sign up to our platform and sell tickets to their customers.

undone flint
wise basin
#

Will our customers need to sign up for a Stripe account or can we handle everything for them?

undone flint
wise basin
#

Any way to prevent that step? So our customers only create an account with us and we'll handle the rest?

undone flint
#

Nope

#

The closest you can get is the API onboarding where you essentially whitelabel the flow

#

But under the hood there is still a Stripe account

wise basin
#

I think that should be fine. They wouldn't get in "contact" with the underlying Stripe account with the API integration, would they?

undone flint
#

Not sure what you mean by 'contact'?

#

You can whitelabel the entire experience so to your users Stripe doesn't even exist

wise basin
#

That's what I mean, perfect ๐Ÿ™‚

undone flint
#

If we inform/contact you about one of your users (i.e. we require ID/verification) then the onus is on you to get that info and provide it to us via our API

wise basin
#

Got it. That's it for now then. Thanks for the quick insights!