Dispute Notification Integration Guide
About 491 wordsAbout 2 min
2025-03-07
Asynchronous Notification Overview
- To enable dispute notifications, you can contact technical support staff for configuration.
- Whenever a dispute-related event occurs (such as when a retrieval request happens), the PingPongCheckOut notification service will create a JSON object containing event-related data and information.
- Then, the PingPongCheckOut notification service sends the JSON object to the configured notification address via HTTP POST request. After receiving the callback notification, merchants can perform subsequent business processing based on the asynchronous notification message.
Receiving Asynchronous Notifications
Prepare a Web Service Supporting HTTP POST
The PingPongCheckOut notification service will push JSON formatted data in HTTP POST manner, so the Web service provided by developers needs to be able to receive and parse JSON data from HTTP POST requests and return corresponding HTTP status codes.
Technical Support Configures Callback Notification Address
- The notification address needs to provide the merchant's own system real address, cannot fill in example addresses from interface documentation or demo.
- Must be a complete full path address starting with https:// or http://, and ensure that the domain name and IP in the URL are accessible from the public network, cannot fill in localhost, 127.0.0.1, 192.168.x.x and other local or internal network IPs.
- The address cannot carry parameters.
Correct Examples
- Complete public URL:
https://example.pay.cn:8080/notify/receive - Public IP with a concrete service path:
https://122.X.X.5:8080/notify/receive
Incorrect Examples
- Relative path only:
./PayNotify.aspx - Domain only without a concrete service path:
https://example.demo.cn:80 - Local or intranet address that is not publicly reachable:
https://localhost:8080/notify/
Processing Dispute Notifications
Use eventCode to determine which stage the dispute is in. After the merchant successfully receives the asynchronous processing result, respond with HttpCode 200, indicating that the merchant has successfully received the asynchronous result notification, otherwise, it will be treated as notification failure, triggering the retry mechanism with 3 retries, and if still failed after 3 retries, no further notifications will be sent, merchants can query dispute status through query interfaces.
| eventCode | Description |
|---|---|
| REQUEST_FOR_INFORMATION | Retrieval Request Notification |
| NOTIFICATION_OF_FRAUD | Fraud Alert Notification |
| NOTIFICATION_OF_CHARGEBACK | Dispute Notification |
| CHARGEBACK_RETURN | Dispute Rejection Notification |
| PREARBITRATION | Pre-arbitration Notification |
| CHARGEBACK_REVERSED | Dispute Cancellation Notification |
| PREARBITRATION_WON | Arbitration Success Result Notification |
| PREARBITRATION_LOST | Arbitration Failure Result Notification |
| DISPUTE_DEFENSE_PERIOD_ENDED | Dispute Defense Period Ended Notification |
| ARBITRATION | Arbitration Stage Entry Notification |