#devik

1 messages · Page 1 of 1 (latest)

lone fernBOT
#

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.

  • devik, 45 minutes ago, 11 messages
  • devik, 11 hours ago, 7 messages
void fossil
#

account.updated event is send only once for each action, e.g. when I fill out the hosted onboarding page, I will receive the event only once when the verification is fully completed
Not necessary. If Stripe performs other async actions, it will also send account.updated for the outcome

If the account object has non-empty requirements or any "disabled" value in capabilities, it means the user needs to provide some missing information and I should generate a new account link.
Yes, that's right! Here's the information to handle such a case (Step 4 and 5): https://stripe.com/docs/connect/custom/hosted-onboarding#new-reqs-due

Stripe hosted onboarding for Custom accounts

Let Stripe collect identity verification information for your Custom connected accounts.

idle monolith
#

Not necessary. If Stripe performs other async actions, it will also send account.updated for the outcome

#

What kind of async actions are possible?

#

I guess my question is really - how can I determine the account has a status of "Pending" similar to that in the Dashboard and no action from the user is required until Stripe finishes some operations.

#

Or perhaps - if I receive account.updated and account object has non-empty requirements or any "disabled" value in capabilities, can I always safely assume that I can generate account link and send the user for onboarding again?

void fossil
#

What kind of async actions are possible?
For example, document can take some time to verified.

I guess my question is really - how can I determine the account has a status of "Pending" similar to that in the Dashboard and no action from the user is required until Stripe finishes some operations.

Or perhaps - if I receive account.updated and account object has non-empty requirements or any "disabled" value in capabilities, can I always safely assume that I can generate account link and send the user for onboarding again?
The process will be listening to account.updated event and look for requirements for the incomplete requirements. In the case that requirements isn't empty, a new account link should be created and send to the user to complete the remaining onboarding process.

idle monolith
#

Do I need to check capabilities or just requirements are sufficient to decide if any action is required without delving into details?

void fossil