The Chargeback Notification informs merchants when a chargeback is created or when its status changes during the dispute process.

Chargeback Statuses

Status	Description
`PENDING`	The chargeback was created in the system and the balance reservation was made.
`APPROVED`	The chargeback was approved by the acquirer or issuer. The dispute was lost and the funds remain debited from the merchant’s account.
`REJECTED`	The chargeback was rejected or reversed. The dispute was won, and the reserved amount is returned to the merchant’s account as a credit.

Notification Parameters

Parameter	Type	Description
`chargebackId`	`string`	Unique identifier of the chargeback.
`transactionId`	`string`	UUnique identifier of the related purchase.
`amount`	`integer`	Amount of the chargeback
`currency`	`string`	Currency of the chargeback amount, according to ISO-4217
`status`	`string`	Current status code of the chargeback
`created`	`datetime`	Date and time when the chargeback transaction was created or change its status. Date format ISO-8601
`order`	`string`	Purchase order number generated by the merchant.
`reasonCode`	`string`	Chargeback reason code
`description`	`string`	Chargeback reason description

Example Notification

{
  "chargebackId": "123456",
  "transactionId": "6594100",
  "amount": 62615,
  "currency": "UYU",
  "status": "PENDING",
  "created": "2024-02-17T18:10:45.667",
  "order": "merchant-1236540",
  "reasonCode": "13.3",
  "description": "Multiple processing of a transaction"
}

Response Expected

The merchant’s webhook endpoint must return HTTP 200 (OK) to confirm that the notification was successfully received and processed. If Bamboo receives any other status code or no response, the notification will be retried according to the Retry Policy

Response Code	Meaning
`200`	Notification successfully received and processed.
`4xx`	Client-side error (invalid endpoint, payload rejection, or failed signature validation).
`5xx`	Temporary server error. Bamboo will retry the notification automatically.

Next Steps

Webhook Overview

Learn about authentication, retry policy, and webhook configuration for Payins.

Transaction Webhook

Receive asynchronous notifications for purchases and refunds.

Error Codes

Understand possible error responses and how to handle them.