#lucaswork_best-practices
1 messages ยท Page 1 of 1 (latest)
๐ 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/1329541519471808705
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- lucaswork_docs, 6 days ago, 6 messages
Hello, I will see what public docs we have on this but to answer your questions: you can connect that account to yours with our OAuth process. Their account would connect to yours like a normal standard account, their connected accounts will remain connected to their account and they will keep their normal relationship to them.
https://docs.stripe.com/connect/oauth-reference
"their connected accounts will remain connected to their account and they will keep their normal relationship to them"
how would this affect rev share? basically our connected accounts are used on a per checkout page basis and as the platform account, we capture some fee from the revenue of our connected account
Two things to keep in mind here:
- Standard accounts can only connect to one platform at a time. If the account that wants to connect to you is already connected to another platform, instead of connecting we will clone their account and that new account (with no connected accounts) would get connected to your account.
- We don't support "grandfather connect" as in, your platform A can make calls for as connected account B, but you can't make calls as them that in turn make calls for one of their connected account C. A can make calls for B, B can make calls for C, but A can't make calls for C.
If by that you mean that you set an application fee or application fee percent on the Checkout Sessions that you create, then no, their existing connect setup shouldn't be effected by that. As with your other Checkout Sessions for other connected accounts, we automatically take the application fee that you specify out of the payments that you directly specify it on, but that doesn't affect any of their other payments.
can you clarify that last one? Lets say we are account A and normally charge 3% application fee on our connected accounts (ie account B). What happens if they connect to us and their connected accounts (account C) have a checkout session. Does the application fee set by account A trickle down and still get revshare from account C?
does that make sense? account C is the grandchild from your scenario above in #2
๐ stepping in here
There is no grandchild relationship here.
You only collect application fees from charges on your Connected Accounts and similarly they would do the same for their Connected Accounts.
You would have no interaction with their Connected Accounts
ah okay! that clears it up, thank you
if they allowed it, would there be any way via api to take our potential client's connected accounts and instead connect them to us?
No, you can't interact with their Connected Accounts at all.
They would have to connect to you separately but you can't access their information via the API.
okay great, I appreciate all the help! you guys are very helpful here. have a nice day