Webhook notification sent to your configured webhook URL when a refund succeeds or fails.
Use data.refund_id and data.reference_id to match the notification to your refund.
Verify the x-callback-token header and respond with HTTP 200 to acknowledge receipt.
Your Xendit unique webhook token to verify the origin of the webhook. It is highly recommended for your integration to verify this value.
Refund status webhook notification
{
"event": "refund.succeeded",
"business_id": "62440e322008e87fb29c1fd0",
"created": "2024-10-28T05:29:08.000Z",
"api_version": "v3",
"data": {
"refund_id": "rfd-1402feb0-8b79-85ae-9d1e-e69394d3949c",
"reference_id": "refund-order-123",
"business_id": "62440e322008e87fb29c1fd0",
"payment_id": "py-1402feb0-8b79-85ae-9d1e-e69394d3949c",
"status": "SUCCEEDED",
"amount": 10000,
"currency": "IDR",
"channel_code": "CARDS",
"reason": "REQUESTED_BY_CUSTOMER",
"created": "2024-10-28T05:29:07.000Z",
"updated": "2024-10-28T05:29:07.000Z"
}
}refund.succeeded indicates that the refund completed successfully.
refund.failed indicates that the refund could not be completed.
Xendit-generated identifier for the business that owns the transaction
Timestamp when the webhook notification was created, in ISO 8601 date-time format.
Version of the refund webhook payload.
Details and current status of a V3 refund.
Xendit-generated identifier for a refund.
A Reference ID from merchants to identify their request.
Xendit-generated identifier for the business that owns the transaction
Xendit unique Payment ID generated as reference for a payment.
PENDING: the refund is still processing.
SUCCEEDED: the refund completed successfully.
FAILED: the refund could not be completed; check failure_code for details.
The intended payment amount to be refunded to the end user.
ISO 4217 three-letter currency code for the payment.
Channel code used to select the payment method provider.
Reason for requesting the refund.
ISO 8601 date-time format.
ISO 8601 date-time format.
Channel-specific failure code if the refund fails; otherwise null or omitted.
Additional refund information, when available from the channel.
Reference provided by the acquirer to help trace the refund.
Custom data attached to the refund. Supports up to 50 entries. Keys must be no longer than 40 characters. Values may be strings (up to 500 characters), finite numbers, booleans, or null. Nested objects and arrays are not supported.
Webhook notification acknowledged.