#esset-webhook-account

1 messages · Page 1 of 1 (latest)

amber atlasBOT
weary girder
#

I think only a created event is sent out there but can't test right now. If you do this in test mode, the events will be generated properly so you can see what gets generated by trying there

lone arch
#

ok, directly after creating the account using the API, an "account.created" will be sent.. and IF anything changes (e.g. verification requirements change), there'll be an additional "account.updated" event sent?

#

what happens if Stripe completes verification (and sets capabilities) directly upon account creation? would that not render an additional account.updated event?

weary girder
#

Yes that is how those events work as far as I know.

I am actually not sure how that second scenario would work or if it is possible. Are you using Custom Connect? I think that would be the only flow that allows you to provide enough info upfront to satisfy the capability requirements. Even so I think verification would still take some time, though I'd need to look further in to that

scenic tartan
#

esset-webhook-account

#

Hey @weary girder and @lone arch, taking over. There is no account.created Event. That doesn't exist and never has. When you create an Account, you know about it since you just made the API request so you should store the information about it synchronously. In the future, you might get an account.updated as identity verification happens over time. It could even be immediate if you provided PII we can verify in the creation, but it's not guaranteed to be immediate.

lone arch
#

OK, thanks; so capabilities could either be updated in the response to creating account... OR they are updated some time (milliseconds to eons) afterwards + notified with an account.updated event?

#

Meaning, we must check both the response + account.updated events

scenic tartan
#

correct. Definitely a bit confusing if you ask me, but historically Accounts couldn't be created via the API, you signed up in a browser during OAuth and then got connected to a platform after, so the "account.created" Event didn't really make sense at the time and we never added it 😦