#esset
hazy ingot
vast yarrow
Can you share the evt_xxx IDs?
vast yarrow
Yep, the way to figure out which is the most recent event is by looking at the previous_attributes hash
When you test data to onboard accounts, statuses/requirements like this will change ~instantly and each change is reflected in an account.updated event
In live mode it's likely to take longer to verify accounts, so less likely that those changes will be as quick. But previous_attributes is how you'd know which is the most recent, because we cant guarantee webhook event ordering
smoky shoal
Hm.. Can they ever go from active -> pending?
vast yarrow
They can lose active status sure if we determine that there's additional verification required later: https://stripe.com/docs/connect/testing-verification#testing-thresholds
smoky shoal
OK... so, that in combination with equal timestamp would make it impossible to know for sure which the correct state is?
In theory, it could be events triggered when someone loses active status...?
vast yarrow
OK... so, that in combination with equal timestamp would make it impossible to k...
Not understanding the scenario in which that would happen
smoky shoal
They can lose active status sure if we determine that there's additional verification required later: https://stripe.com/docs/connect/testing-verification#testing-thresholds
Was thinking if that was a theoretical possibility because of the above?
First an update where they have "active", at the same time as it goes to "pending"
vast yarrow
Not immediately, no. At least not in a real world scenario. Generally you'd track future_requirements to be notified of any upcoming requirements that may impact capability/account status: https://stripe.com/docs/connect/custom-accounts/future-requirements
smoky shoal
OK, thanks.
vast yarrow
np