#aby_docs
tulip crestBOT
đ 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/1426257522100146341
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
deft pebble
Connect integration doesn't support OAuth. Your platform will always create a new connected account
If your merchant / seller / partner has an existing Stripe account, they will be able to sign in and those information will be pre-filled to complete their onboarding to the new connected account with your platform (if you opt for hosted onboarding)
sand hamlet
Thank you for your quick answer!
Oh I see, so then there's nothing to do with OAuth, it's just like the regular onboarding from the existing accounts, as if they were brand new accounts, correct?
deft pebble
There won't be any OAuth to an existing Stripe accounts from your merchant / seller / partner. Instead, they can use the exiting data from their existing Stripe accounts to complete the onboarding of their new connected account on your platform
sand hamlet
Wonderful, thanks. Just another quick question. Since the Connected accounts will be onboarded again to the new platform, I assume they will need to pass the KYC process again? Or since their account has been already verified there's no need to provide all the documentation again for the verification?
deft pebble
They will need to complete the KYC process again