#igmltd_connect-oauth-standard
dawn hatchBOT
👋 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/1432393529186979951
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
brisk folio
Hello, it is possible to connect existing accounts with this process:
https://docs.stripe.com/connect/oauth-standard-accounts
After that you can make calls with them the same way you do for the accounts that you create directly.
dawn hatchBOT
icy kite
hi @brisk folio, thank you for you prompt response.
I think the thing that threw us off was "OAuth is not recommended for new Connect platforms. We recommend using Connect Onboarding for Standard accounts instead"
Further questions just for clarity, does that mean we will manage 2 onboarding processes, one for existing (oauth) and one for new accounts? Or will the the Connect OAuth onboarding automatically direct them to create an account if there is not one?
If an account was created by an onboarding, can the client later move and keep that account to use as normal?
meager summit
Hi 👋
I'm stepping in as my colleague had to go.
Currently OAuth is the only way you can connect with existing Stripe Accounts. Onboarding for Standard accounts requries you to create a new Standard Connect account as part of the process.
icy kite
just for clarity, does that mean we will manage 2 onboarding processes, one for existing (oauth) and one for new accounts? Or will the the Connect OAuth onboarding automatically direct them to create an account if there is not one?
meager summit
If there is no account, then you should create the account and use the hosted onboarding flow. If the user already has an account, that is where OAuth is appropriate.
icy kite
got it thanks, so we would would just need 2 options on our end, "connect existing" and "Create new"
and finally:
If an account was created by an onboarding, can the client later move and keep that account to use as normal?
meager summit
What do you mean by "can the client later move"? What is moving?
icy kite
What do you mean by "can the client later move"? What is moving?
If they choose to stop using our service, can they retain their stripe account we created through onboarding?
meager summit
Yes. You would disconnect the account from your platform in the Dashboard like we describe here: https://docs.stripe.com/connect/dashboard/managing-individual-accounts#remove-accounts
We call out that this still allows your customer to use their Stripe account:
Removing an account only disconnects it from your platform. It still functions as a normal Stripe account.
For accounts you connect to through OAuth, you can use the deauthorize API request we document here: https://docs.stripe.com/connect/oauth-standard-accounts#revoked-access
icy kite
thank you for the info - just what we needed for now.
meager summit
Great 🎉 Happy to help 🙂