MODEL.ACTION.
This structure helps you understand which part of the system triggered the event and what action occurred.
Available events
| Model type | Event types |
|---|---|
ACCOUNT_VERIFICATION | ACCOUNT_VERIFICATION_SUBMITTED, ACCOUNT_VERIFICATION_COMPLETED, ACCOUNT_VERIFICATION_FAILED |
RECIPIENT | RECIPIENT_CREATED, RECIPIENT_UPDATED, RECIPIENT_DELETED |
Event types by model
The following sections document each event type. Each event object is nested within the standard webhook payload structure, with unique data in theobject field containing event-specific information.
ACCOUNT_VERIFICATION
Events related to bank account verification processes and status updates.ACCOUNT_VERIFICATION_SUBMITTED
ACCOUNT_VERIFICATION_SUBMITTED
Triggered when a bank account verification request has been successfully submitted to the verification service.For detailed field definitions, see API Reference.
Example
ACCOUNT_VERIFICATION_COMPLETED
ACCOUNT_VERIFICATION_COMPLETED
Triggered when account verification finishes successfully and the verification result is available.For detailed field definitions, see API Reference.
Example
ACCOUNT_VERIFICATION_FAILED
ACCOUNT_VERIFICATION_FAILED
Triggered when account verification fails due to some issue.For detailed field definitions, see API Reference.
Example
RECIPIENT
Events related to Beneficiary Hub recipient management and lifecycle operations.RECIPIENT_CREATED
RECIPIENT_CREATED
Triggered when an end-user successfully adds a new recipient.For detailed field definitions, see API Reference.
Example
RECIPIENT_UPDATED
RECIPIENT_UPDATED
Triggered when an end-user modifies any recipient information, including setting a new default recipient.For detailed field definitions, see API Reference.
Example
RECIPIENT_DELETED
RECIPIENT_DELETED
Triggered when an end-user removes a recipient.For detailed field definitions, see API Reference.
Example