#Wurkzen
1 messages · Page 1 of 1 (latest)
Hello
Bismarck we have an issue during the onboarding of a stripe connected account. For some reason when the onboarding finishes the account_onboarded is not set to true
The user has to return to the onboarding process, 2 to 3 times, each time providing different information
Why doesnt the onboarding process just collect everything before they send the user back to our platform? This is confusing to our users
Basically to onboarding an account today
- We redirect to stripe for connect account onboarding.
- The user provides all the information and then is redirected back to our platform.
- Our platform doesnt get the webhook stating that the account is onboarded so we then redirect them back to Stripe and stripe asks for more information and redirects the user back to our platform once its provided
- The webhook is not received yet, so we send the user BACK to stripe to provide MORE information, then stripe redirects back to us...
- FINALLY we receive the webhook for account onboarded
Hi, what does 'everything' mean here? Do you have an example? Deoending in the location, the service agreement, and capabilities the information required can very account by account: https://docs.stripe.com/connect/required-verification-information
Why not just collect everything at once? It's very confusing to our customers and we had to add a modal that says "You may have to repear this process 2-3 times"
thats fine i understand the information required
Are you saying that https://docs.stripe.com/api/events/types#event_types-account.updated is not sent after they complete onboarding?
but why do you redirect the users back to the platform when they confirm everything if you didnt truly collected all the required information?
Yes we get the account updated webhook but NOT the account_onboarded
Hm, I'm not sure that I understand what you're seeing. Can you share an example account where you see this behavior so I can further look?