vlad_api

[modest tusk]

👋 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/1289317684583858206

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[snow oasis]

For additional clarity, the live account ID he connected via the onboarding link created in the dashboard is acct_1PbJyrRseTT2fJd3, while the account ID created via the API is acct_1Q3jn0R5kTC2qnqd.

He used the exact same login for both of these.

[novel patio]

Yes, this is expected, a new account is created for use with your platform and user will need to complete onboarding. Ideally, the existing identity info will be re-used from the existing account, but for a variety of reasons that may or may not happen.

For looking into specific cases/accounts, please contact our support team: https://support.stripe.com/contact

[snow oasis]

So, in some cases, will they need to create an entirely new Stripe account? Like, literally a new account? I just went through the process with two of my existing live Stripe accounts, and when I reached the onboarding step and logged in, it correctly prompted me to select an existing account. However, for some merchants, even if they log in with an existing Stripe account, it still creates a new one. Does that mean they end up with two separate accounts?

If that's the case, why does the exact same flow work when you generate an onboarding link via the Stripe Dashboard and send it to them? In that case, it picks up their existing account and connects it. Shouldn't the behavior be consistent, whether the link is generated through the Dashboard or the API?

[novel patio]

That sounds like you may have been using the legacy oauth flow that we dont recommend, and the behaviour depends on some account details.

Generally, we recommend you create the account explicitly via the API and send the user to an onboarding account link

Each paltform should have an isolated connected account

Yes, a given dashboard user will have multiple stripe accounts within that

they'll all be tied together within their dashboard, but isolated form one another in terms of payments and platform connections etc

[snow oasis]

I'm using https://api.stripe.com/v1/accounts and https://api.stripe.com/v1/account_links to generate the link. Are those outdated legacy oauth flows?

[novel patio]

Nope, thats the recommended path, that will always create a new account

(you create it when you call POST /accounts)

[snow oasis]

Yes, that's what I use, and I understand that it creates a new account. However, after creating the new account, it redirects them to log in. If they log in with an account that already has an existing live, verified account, it should show that account and allow the merchant to select it or create a new one. But for many of our merchants, even though they log in with a valid, existing account, there's no prompt to select their existing business. Instead, they are forced to re-create and re-verify everything from scratch. However, if I generate this onboarding link via the Stripe Dashboard and they click it, it takes them through the exact same flow but this time, after they login, it does prompt them to select their existing business. This is why I'm confused. It's the same flow. I'm using the latest API for onboarding merchants.

[novel patio]

I'm not sure why that difference would exist, I would suggest contact support with a specific account ID that experienced this so they can investigate why this happened and if it is expected.