Skip to main content

Available events

Webhook payload

Every event uses the same envelope, and data is projected through a fixed allowlist — only the fields below are ever sent, regardless of the event. wallet carries type and deposit_address. virtual_account carries account_holder_name, account_number, iban, bank_name and bank_codes, plus bank_branch and bank_address on the three succeeded events.

Sample Events

collection_account.creation_succeeded

collection_account.disablement_succeeded

Check the collection account object parameter details here - Global Collection Account

Upcoming Webhook Events

The following webhook events will be available soon when Tazapay enables self-serve Collection Account creation via APIs.
These events describe the request driving the change, not the account. In the data block, id is the request id (cvar_/cwar_) and status is the request status. payment_method_type and metadata are not sent on these events. Use collection_account.creation_succeeded, disablement_succeeded or reenable_succeeded for the account itself.

collection_account.creation_under_approval_hold

collection_account.creation_requires_action

collection_account.creation_failed

collection_account.creation_cancelled

collection_account.disablement_under_processing

collection_account.disablement_requires_action

collection_account.disablement_failed

collection_account.disablement_cancelled

collection_account.reenable_under_processing

collection_account.reenable_failed

collection_account.reenable_cancelled

collection_account.reenable_succeeded