Skip to main content
Webhooks are event-based notifications that are received when a specific event related to the Card occurs.
In rare cases, such as network retries, read timeouts, processing delays, or delivery failures, the same webhook might be sent more than once for the same event. To prevent unintended side effects, implement idempotency in your webhook handler to handle duplicate deliveries.

Webhook signature

You will receive the webhook signature in the webhook header. Here is a sample header from a webhook request.
Always capture the webhook payload in its raw text format before parsing into JSON. Parsing and reserialising the payload can change the structure (for example, array ordering, spacing, or null handling) and cause a signature mismatch during verification. Use the exact raw body string from the request when computing the signature.

Card transaction webhooks

Webhook payload fields

The webhook payload contains important metadata in its top-level fields. The following events are triggered at different stages of a card transaction:

Card transaction data fields

Status and statusCode mapping

The following table shows the possible statusCode values for each transaction status:

Card refund webhooks

Webhook payload fields

The webhook payload contains important metadata in its top-level fields. The following events are triggered at different stages of a card refund:

Card refund data fields

Card status update webhooks

Webhook payload fields

The webhook payload contains important metadata in its top-level fields. The following events are triggered when a card’s status changes:

Card status update data fields

Verifying the signature is mandatory before processing any response. Refer to Signature Verification for more details.