#jemen_docs
1 messages ยท Page 1 of 1 (latest)
๐ 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/1308808994197868544
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐ I'm not sure what you mean when you're referring to "errors" occurring in the account.updated webhook, or how that relates to the use of the onboarding connect embedded component. Can you elaborate on that?
Yeah, hi, I'm sorry, I've mispoked. I'm referring to this:
The Account object has a requirements hash, representing the requirements needed to verify the account.
And requirements has errors inside, which are related to past_due.
Gotcha. Offhand I'm not thinking of any cases where you wouldn't be able to use the onboarding embedded component to allow your user to remediate the missing details, but it's hard to say for sure without knowing the specific errors.
Are you running into issues when testing this flow?
We did not tested that. We are just exploring if it is possible. So in that case we need to give user e.g link to dashboard and let him to fix it by his own, right?
We would like to help user as much as possible in this case.
The user needs to provide the information, whether you generate an Account Link or present them with the onboarding component.
Yeah, we know, but he can get errors, afterwards right? Let's say because he did not verify his identity.
He fill everything, but then... in sometime, he gets eventually_due and later past_due -> errors.
So we wanted to know, to make him "repair it" using our app.
As far as I'm aware that's supported by the onboarding component.
To be more precise, yours embedded onboarding.
It is?
Great!
Are those possible errors written somewhere?
And one more question... Cause this is quite annoing, we've been using embedded onboarding for some time and the thing we don't like the most is we need to fill almost every detail - adress, name, etc. Is there some way how to skip this process at least in testing mode?
I know there is ONLY skip for bank account details.
Are the errors listed in the sections here what you're asking about?
https://docs.stripe.com/connect/handling-api-verification#validation-and-verification-errors
Sorry, I'm blind...
Not that I'm aware of offhand. I know that exists for hosted onboarding, but I don't think it's made its way into the embedded component yet.
So, there's a plan for it?
That I'm not sure of, I'm just pretty sure it isn't there now. I'd suggest reaching out to our Support team for questions about future features or product improvement questions like this:
https://support.stripe.com/?contact=true
Great, thank you very much @scarlet lodge, pleasure to solving problems with you.