Chargeback Notification

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


Chargeback Statuses

StatusDescription
PENDINGThe chargeback was created in the system and the balance reservation was made.
APPROVEDThe chargeback was approved by the acquirer or issuer. The dispute was lost and the funds remain debited from the merchant’s account.
REJECTEDThe 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

ParameterTypeDescription
chargebackIdstringUnique identifier of the chargeback.
transactionIdstringUUnique identifier of the related purchase.
amountintegerAmount of the chargeback
currencystringCurrency of the chargeback amount, according to
ISO-4217
statusstringCurrent status code of the chargeback
createddatetimeDate and time when the chargeback
transaction was created or change its status.
Date format ISO-8601
orderstringPurchase order number generated by the
merchant.
reasonCodestringChargeback reason code
descriptionstringChargeback 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 CodeMeaning
200Notification successfully received and processed.
4xxClient-side error (invalid endpoint, payload rejection, or failed signature validation).
5xxTemporary server error. Bamboo will retry the notification automatically.

Next Steps