Kinno

[regal orchid]

What specifically is the issue? How are is it not updated on your end?

Because of our setup, we should also look at capability.updated events to be able to tell if an account is verified
Be curious to know why you think this is required. AFAIK, it's not.

We handle the person.updated and account.updated events as 1 type and simply fetch the account entity at the start of the events handler, this would be an obvious issue if we only receive a person.updated event without a corresponding account.updated event, or if only the person verification details were changed.
The general recommendation is to listen for account.updated events, which have all the fields that denote whether an account is active: https://stripe.com/docs/connect/identity-verification-api#determining-if-identity-or-business-verification-is-needed

[hard ember]

Well, we don't really receive an account.updated event for some of our customers, haven't been able to get a list of reproducible steps to see which setups end like this, we do however receive a person.updated event, if capability really shouldn't fall under this workflow then I'm guessing we're handling the person event incorrectly

[regal orchid]

we don't really receive an account.updated event for some of our customers,
That sounds suspect. Do you have an example?

[hard ember]

Sorry for the late responses, just to clarify, we do receive account.updated events for all of our customers, it just seems that sometimes we don't receive one that would lead to an account being marked as verified on our side

Is it reasonable to assume that for some customers we will receive a standalone person.updated event confirming their verification without an account.updated event?

If that sounds suspect as well I can go quickly fetch an id for you to check, but from what you've hinted at so far with your questions and clarifications it seems it's our early assumptions about how to handle the events are at fault 😅

[minor kraken]

Hello 👋
Taking over as ynnoj needs to step away soon

If you have concrete examples, that'd help clarify a few things!

Is it reasonable to assume that for some customers we will receive a standalone person.updated event confirming their verification without an account.updated event?
as far as I know, if an account gets verified then an account.updated event should be generated.

[hard ember]

interesting, I also have to go for now, I think I'll have to debug stuff on our side a bit more but I'll be back if anything confusing comes up

Thanks for the help so far!

[minor kraken]

NP! 🙂 Good luck