#iconate_standard-connect-oath
stoic kernelBOT
👋 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/1503456564739047484
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
jagged oracle
Is OAuth with Standard Accounts still possible for Connect Platforms?
Yes, this is still the canonical way for Platforms to connect with existing Standard Accounts
For the deeper question, we document that here: https://docs.stripe.com/connect/oauth-changes-for-standard-platforms
ivory stump
Mmm not super clear here-
"When a user of a Standard account controlled by another platform connects to your platform, the Connect onboarding flow directs them to create a separate Standard account to use with your platform. The new account automatically connects to your platform."
So if they go through the oauth flow for our platform, does it create a new stripe account technically under our platform. As it says here
"create a separate Standard account to use with your platform"
jagged oracle
IF they are already controlled by another Platform
But it won't create a new account auto-magically. The user is directed to take this action by the flow.
ivory stump
Ok, so if they arent, they preserve the existing account, and we have read_write access to it?
arent already controlled by another platform that is
jagged oracle
Correct
ivory stump
ok great, thank you for clarifying
jagged oracle
Happy to shed what 💡 I can 🙂