Skip to main content

Available events

Webhook payload

Every collection account event has the same body. data is the collection account, in the same shape as the Get Collection Account response. The request that triggered the event appears in data.requests.
The account and the request have separate statuses. data.status is always the account status (enabled or disabled). To see what happened to a request, read status on the matching entry in data.requests.

requests

Each entry in data.requests describes one request on the account. data.requests reflects the account when Tazapay sends the webhook, not when the event occurred. If a webhook is delayed or retried, a request’s status can be later than the event type suggests. To get the latest state, call Get Collection Account.
Webhook timestamps use RFC 3339, for example 2026-09-16T10:45:28.936281Z. The top-level created_at and updated_at on the Get Collection Account response use a different format. Parse each source with its own format.

Sample Events

collection_account.creation_succeeded

collection_account.disablement_succeeded

The account is disabled, so currencies is empty and every currency in currency_status is disabled. The disablement request is the first entry in requests.
Check the collection account object parameter details here - Global Collection Account

Status values by event

These events use the same body as described in Webhook payload. data is the collection account, data.status is the account status, and the request that triggered the event is in data.requests. The table lists the values you can expect on each event. “Request status” is the status of the triggering entry in data.requests.
On the disablement_* events other than disablement_succeeded, the account is still enabled and still accepts funds. Do not treat collection_account.disablement_failed as a change in account status.

collection_account.disablement_failed

This sample shows a failed request. The account stays enabled. The failure appears in the top-level data.failure_reason and on the disablement entry in data.requests.