Onboarding webhooks deliver real-time notifications of state changes in a business sub-account throughout the onboarding lifecycle — including compliance approval, rejection, and Requests for Information (RFI). Use these events to drive integration logic without polling. See the Business Onboarding Overview for how webhooks fit into the end-to-end onboarding flow.

Events

Event	Description
`account.approved`	The business sub-account has passed compliance review and is approved for use.
`account.rejected`	The business sub-account has been rejected during compliance review and cannot be activated.
`account.rfi`	Compliance review has identified issues that require partner action before the account can proceed.

`account.approved`

Fired when a business sub-account passes compliance review and becomes active.

Payload

Field	Type	Description
`event_name`	string	Always `account.approved`.
`data.status`	string	Account status. Always `APPROVED` for this event.
`data.customer_id`	string (UUID)	Identifier of the customer associated with the sub-account.
`data.company_name`	string	Legal name of the business as captured during onboarding.
`resource.id`	string (UUID)	Identifier of the business sub-account.
`resource.type`	string	Resource type. Always `account` for this event.

`account.rejected`

Fired when a business sub-account is rejected during compliance review.

Payload

Field	Type	Description
`event_name`	string	Always `account.rejected`.
`data.status`	string	Account status. Always `REJECTED` for this event.
`data.customer_id`	string (UUID)	Identifier of the customer associated with the sub-account.
`data.company_name`	string	Legal name of the business as captured during onboarding.
`resource.id`	string (UUID)	Identifier of the business sub-account.
`resource.type`	string	Resource type. Always `account` for this event.

`account.rfi`

Fired when compliance review identifies one or more issues that require partner action before the sub-account can proceed. See RFI Handling for the response flow.

Payload

Field	Type	Description
`event_name`	string	Always `account.rfi`.
`data.account_id`	string (UUID)	Identifier of the business sub-account.
`data.status`	string	Account status. Always `RFI_PENDING` for this event.
`data.issues`	array of `Issue`	List of issues identified during review. Each issue describes a problem, the required corrective action, and the target entity.
`resource.id`	string (UUID)	Identifier of the business sub-account.
`resource.type`	string	Resource type. Always `ACCOUNT` for this event.

Issue object

Field	Type	Description
`code`	string	Machine-readable code identifying the issue (e.g., `ID_EXPIRED`, `INVALID_PROOF_OF_ADDRESS`, `UNSATISFACTORY_PHOTOS`).
`description`	string	Human-readable description of the issue.
`action`	string	Corrective action required (e.g., `REUPLOAD_DOCUMENT`).
`target`	`Target`	The entity the action applies to (business or controller).

Target object

Field	Type	Description
`type` / `entity`	string	Entity type the issue applies to: `CONTROLLER` or `BUSINESS`.
`controller_id`	string (UUID)	Identifier of the controller. Present when the issue targets a controller.
`account_id`	string (UUID)	Identifier of the business sub-account. Present when the issue targets the business.
`document_id`	string (UUID)	Identifier of the document the action applies to.