braydensterrett

[lapis trout]

Hello 👋
We don't recommend relying on the chronological order exactly. The events are generated and delivered asynchronously.

It essentially comes down to the information you need on your end. Like even though we deliver N number of events for certain actions, you don't really need to listen to all of them in case the information you need is reflected by one out of those N events

[desert bough]

Okay, let me pose an example to you then and see what you think. We are using the Stripe hosted Connect onboarding flow to KYC folks. Running through this form causes several account.updated events to get sent. If the user is payouts_enabled that would trigger some things to happen on our end. Only one of these events will have this value as true if the user has been successfully verified and adds an external account.

I'm basically reading the payouts_enabled value each time a webhook is sent and validating that the user doesn't have any currently_due requirements anymore. Is there any concern that we would receive the event showing full eligibility and then receive another event (past event) showing that there are more requirements?