Chargeback Notification
Overview
In the event of a chargeback, PayBy sends the relevant chargeback information to the merchant via a data stream. The merchant must process the notification and respond according to the specifications outlined in this document.
Note:
- The same notification may be sent multiple times. Merchant systems must be able to handle duplicate notifications correctly.
- If PayBy does not receive a valid response from the merchant or if the response times out, the notification is considered failed and will be retried. The default retry schedule is as follows (in minutes): 2, 10, 10, 60, 120, 360, 900. However, PayBy does not guarantee final delivery.
- If the order status is unclear or the merchant has not received a payment result notification from PayBy, it is recommended to actively query the order status using the appropriate API.
Notification Parameters
acquireChargeback AcquireChargeback Required
Contains details of the chargeback order.
chargebackTime Timestamp(3) Required
- Timestamp indicating when the chargeback was initiated.
- Example value:
1581493898000
merchantOrderNo String(64) Required
- Unique identifier for the merchant's original order.
- Example value:
S10000
orderNo String(32) Required
- Unique identifier for the PayBy transaction order.
- Example value:
O1000
payAmount Money Required
- Total amount originally paid in the transaction.
chargebackAmount Money Required
- Amount being reversed or refunded due to the chargeback.
caseType String(200) Required
- Classification of the chargeback case, such as fraud, dispute, or duplicate transaction.
partnerId String(200) Required
- Identifier for the partner or merchant associated with the transaction.
- Example value:
200000003232
Response Parameters
Upon receiving the notification, the merchant should return the following JSON response to indicate successful receipt:
{"response":"SUCCESS"}
Any other response indicates an error or failure to process the notification.