#mmwt_reconnecting-connected-accounts
lilac saddleBOT
👋 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/1442981355138060359
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
rich sparrow
👋 taking a look 🙂
rich sparrow
Since there is no way to enable platform controls on a pre-existing account. I think it makes the most sense to create an account on your end and then use it to generate an account-link and have the user onboard with that as it will restrict them to the account_id you passed in during account-link creation.
coarse mauve
hmm I was worried that would be the case. My question for this would be if a user already has a Stripe account and I go through this route and through API I create an Account for them using their email, if that email already has a Stripe account would it appear under thier Stripe account in their Dashboard as a new account? or what would happen in this case?
rich sparrow
When your user ID (email address) is associated with multiple accounts the Dashboard presents a list of accounts you can view when signed in.
coarse mauve
so if I create an account and place the email as part of the API and then launch the Account-Link to continue the onboarding, does this require them to still login to that account? or would it directly take them to onboarding (entering their business information, etc)
Also, if we do go this route, if the user after connecting, disconnects, and then wants to connect again, do we need to always keep track of their previous account ID and reuse that? or would we call the Account API again with the same email and account ID would be passed back the original one that was created the first time?
rich sparrow
They would need to log into their user account (not merchant account) to ensure they have access to sign in with that email.
I'm a little fuzzy on this question
"or would we call the Account API again with the same email and account ID would be passed back the original one that was created the first time?"
If you make the account creation call passing in the email it will result in a new account_id.
coarse mauve
okay so our platform would need to hold on to the account ID we created for them and if for some reason they decide to disconnect the Stripe account from our platform then if they try to re-connect we need to pass the original account ID back to Stripe for them to re-connect back to that same account and not create a new account
lilac saddleBOT
rich sparrow
I think the catch here is you can't pass a previously disconnected account id to the account link. so you would be back to using oauth, which has the same platform control limitations in the first place. I think in that case it makes more sense to start over with a new account.
Is this a scenario you've encountered before?