#leah_connect-onboarding
distant sableBOT
👋 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/1296516960372392007
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
left umbra
leah_connect-onboarding
bright sleet
When using hosted onboarding for custom connect for accounts who do not have access to the Stripe Dashboard. This shows up.
Just wondering what the purpose of this step is.
left umbra
@bright sleet we use this to confirm they own the account in the future when they aim to edit it. I think it's important in cases where for example they want to change their bank account on file
bright sleet
Thanks for sharing! If the email is associated with an existing Stripe account because my merchant is already using Stripe for other reasons, what happens?
left umbra
I don't think it's an issue and we'd know what account(s) to show based on what they picked. Otherwise they might get an error and be asked for another email. The best approach would be to just test this in production to confirm I think
bright sleet
will give this a shot!
As a platform do I have any visibility on the email or phone number left at this stage?
left umbra
no
bright sleet
Thanks for confirming! I just tried and there is an error message if I use an email associated with an existing merchant when entering the wrong phone number.
If I use an email associated with another merchant with the right phone number I can use my existing info
Thanks for helping me out on this one!
left umbra
sure thing!