#jordan-r_connect-for-marketplace
cunning sirenBOT
👋 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/1433567247254949969
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
worn granite
Example:
Jordan's Gym is the Gym Organization
Jordan's Gym - Houston, Jordan's Gym - West Hollywood, etc - Are gym locations where users can purchase memberships from in our app.
Jordan's Gym - Houston - does not collect sales tax on gym memberships
Jordan's Gym - West Hollywood - does collect sales tax
Payouts would go to Jordan's Gym
worn granite
Thank you 🙏
sterile lotus
I think probably you want 'standard' accounts with direct charges. The platform provides the technical underpinnings of the payments, but your connected accounts are the locations/businesses with which your customers do business, correct?
worn granite
Yes, that’s correct.
We’re a marketplace and in our app users are able to purchase through us, and we split the profits between the gyms and ourselves.
sterile lotus
I know the breadth of our docs can be overwhelming, but we have a lot of useful material around this topic
worn granite
But if we have our gym partners create standard stripe accounts, how would we be able to offer setup inside of our app if not for stripe connect?
sterile lotus
For example, I think https://docs.stripe.com/connect/integration-recommendations is agood starting point
You can still use hosted onboarding with Account Links. You could also do Embedded Components, which is more of a technical lift than Account Links
https://docs.stripe.com/connect/standard-accounts#how-to-use-connect-onboarding-for-standard-accounts
https://docs.stripe.com/connect/embedded-onboarding
worn granite
Ah, ok. That may have solved the question then.
Because that would also allow gyms to set tax rules on a per-location basis by using multiple locations under one org
sterile lotus
Yeah, you would just register each Stripe Account in their own jurisdiction and then Stripe tax would calculate based on that
And then for payments on accounts you don't want to use Stripe Tax on - you just don't turn it on
worn granite
Got it. Ok, we'll give that a try, thank you for your help!
Sorry, one more question
sterile lotus
sure!
worn granite
In this example, if we were to use embedded components, would this enable us to create an experience where a gym organization is created in stripe connect and then subsequent locations are tied to that primary organization accounts as well?
In the documentation I'm able to see how how marketplaces are set up for 1 on 1 when dealing with a single vendor https://docs.stripe.com/connect/end-to-end-marketplace
But I haven't found any docs that help us with setting up multiple stripe accounts for the same vendor.
sterile lotus
So in Stripe parlance, the primary account that is creating the direct charges on its standard accounts is the "Platform", and the - 'locations' in your situation - are the "connected accounts."
It is the normal/usual thing for a platform account (which creates its connected accounts in most cases) to have multiple connected accounts
I think that speaks to what you were asking
worn granite
Yes, I think that explains it. Thank you so much. I think we've got enough to get us pointed in the right direction now.
sterile lotus
Awesome! Good luck!
cunning sirenBOT