Dispute notifications via webhooks

PrimeiroPay sends dispute information via webhooks to inform the merchant about the current status of the dispute.

The merchant shall inform a listener HTTPS URL to its account manager in order to set up this feature.

When your service receives a webhook notification, it must return a 200 HTTP status code. Otherwise, the webhook service considers the notification delivery as failed. PrimeiroPay currently does not retry failed webhooks.

Example:

{
  "uniqueId":"777777777777777",
  "merchantId":"8acda4cb6193d56a0161949d31de0dda",
  "merchantTransactionId":"1331837",
  "amount":1762.0,
  "caseNumber":"26379847",
  "chargebackCountRequest":1,
  "disputeEndDateTime":"2019-10-09 21:00:00.000",
  "notificationDateTime":"2019-10-02 11:00:00.000",
  "status":"WIN",
  "acquirerReasonCodeId":77,
  "adyenMerchantRefId":"4147",
  "reasonCode":"000.100.222",
  "disputeReason":"Transaction Not Recognized By Cardholder",
  "brand":"MASTERCARD",
  "brandReasonCode":"4837"
}

Frequency

Whenever the “status” changes a webhook is being sent to the listener URL. A dispute notification can have the following status: OPEN WIN LOSE The merchant receives therefor maximum three notifications for a single transaction. PrimeiroPay currently does not retry failed webhooks.

Last updated