Skip to main content
Customer events track the KYC/KYB onboarding lifecycle of a customer. Subscribe to them to keep your onboarding UI and compliance workflows in sync.

Populated fields

Every customer event carries the ids it concerns in the envelope’s related block. accountId is always set, together with userId for an individual customer or entityId for an entity. beneficiaryId is set when the event concerns one specific associated person of an entity. Keys that do not apply are null rather than absent.

Event types

For the full meaning of each state, see Verification statuses.

The data object

Every customer.* event carries the same three keys under data. All three are always present - they are set to null when they do not apply, so a strict schema validator never sees keys appear and disappear between event types.
name is "FirstName LastName" for an individual and the company name for an entity. email is the user’s email for an individual, or the company email declared at KYB for an entity - null when the entity declared none.

Example payload by event type

customer.created

customer.under_review

customer.awaiting_associated_person_information

An entity event scoped to one associated person: related.beneficiaryId is set, and data.beneficiary carries that person’s own verification status.

customer.resubmission_requested

customer.active

customer.rejected

customer.deactivated