Why Connect Platforms Track Both Account and Person Updates
· 2 min read
Track verification at the right level
A Connect account may have requirements about the business and separately about people associated with it. Stripe’s API verification documentation advises watching account updates and, when using the Persons API, person updates too. The distinction matters when a team reports progress to a merchant. An event about one associated person's data does not describe every requirement on the account.
Keep a support record for each kind of change
Map the account identifier to the merchant case. For each associated person, keep a pointer to that person's open item within the case. The event is a signal to read the current record. An account webhook can reflect a company requirement or an account-level change. A person event can point your team toward a document or information request for a specific individual.
| Event or state | Follow-up check |
|---|---|
| Account updated | Review current account-level requirements and affected capabilities |
| Person updated | Identify the person and review the related item |
| An error appears again | Read the newest reason before asking for evidence |
| A previously open item disappears | Check the rest of the account before closing the case |
Use the event record to answer a concrete question
A merchant asks why their company still sees an onboarding task after a director submitted identification. Support can use the person update to identify that document's status and then use the account record to see whether a company task remains. If the outstanding item is independent, explain who needs to act and what evidence is still needed. The separation makes an accurate reply possible even when people send their documents at different times. Preserve the identifiers and observed states in case a later update opens a different request.