1. Integration Guide
Dispute Service API
  • Dispute API
    • Integration Guide
      • Dispute Service Usage Guide
      • Security Requirements and Message Format
      • Special Rules
    • API Reference
      • Dispute
        • Dispute
        • Dispute
      • Notification
        • Dispute Notification
        • Alert Notification
  1. Integration Guide

Special Rules

Special Rules

Special Rules#

This section describes the special rules in the dispute defend flow.

disputeEndtime#

When Dispute service sends a new Chargeback notification to the merchant, it will calculate disputeEndtime based on the sending time and the latest defend submission time required by the Card Scheme. This means that the merchant needs to send the accept/defend API before this date.

Forced Completion#

When any of the following situations occurs, this dispute transaction will be marked as completed by Dispute service. After it is marked as completed, this dispute transaction will not respond to any POST-type API, that is, it will not respond to the accept/defend Dispute API.
1)Within the time range from the notification API sending time to disputeEndtime, the merchant does not send any POST-type API (accept/defend Dispute API).
Example: On 2025.4.19, a new Chargeback from Visa is notified to the merchant. At this time, disputeEndtime=2025.5.7.00:00
Before 2025.5.7.00:00, if Dispute service does not receive any POST-type API, this dispute transaction will be marked as completed by Dispute service.
2)The merchant does not integrate with the API.
If the merchant does not integrate with the API for a Chargeback, when the merchant chooses to manually upload defend documents / not to defend, Dispute service will also calculate a disputeEndtime and mark this dispute as case completed after that time.
Note: Since the merchant does not choose to defend through API, this [case completed] does not indicate that the defend process has been completed. It is only the result of automatic unified processing by the system. For the actual defend process, the merchant should communicate with EVO Payment operations personnel for processing.

Defend Recommendation Mechanism#

When Dispute Service sends an automatic notification for a Chargeback, it will recommend whether the merchant needs to defend based on the reason code of this Chargeback.
The recommendation information will be reflected in action.type and action.suggestion in the notification API. action.type contains the recommendation keyword. For example, “accept” means it is recommended to accept this Chargeback, “defend” means it is recommended to defend, and “evaluate” means it needs to be evaluated based on the specific situation. action.suggestion contains the specific reason for the recommendation.
Previous
Security Requirements and Message Format
Next
Dispute
Built with