pcpw

[silk nacelle]

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• pcpw, 3 days ago, 5 messages
• pcpw, 3 days ago, 86 messages
• pcpw, 3 days ago, 9 messages

[fading ermine]

And which webhook event should I listen for when this happens?
account.updated and you'd look at the requirements[disabled_reason] field: https://stripe.com/docs/connect/handling-api-verification#determine-if-verification-is-needed

As for why they're rejected, could be for any number of reasons really (we can't verify the user/account, they're breaking Stripe Tos, etc). Not really a question for this server

[ruby basin]

If an account is rejected, will the user be able to resubmit their details for re-verification?

[fading ermine]

No, you'd need to lodge an appeal I believe. Simply re-onboarding won't work

[ruby basin]

So in that case, should I create a new Standard Account from the API and let my user onboard again?

Or would this be a special case that I'd have to handle manually

[fading ermine]

Yes

[ruby basin]

https://stripe.com/docs/connect/standard-accounts#return_url

Thanks. Follow up question. Does the details_submitted parameter on a Stripe Account denote whether the user has fully completed the onboarding process?

[fading ermine]

Yes: https://stripe.com/docs/api/accounts/object#account_object-details_submitted

[ruby basin]

Just to confirm, if the user has only gone through half of the onboarding, the parameter will be false?