notifyDefenseStrategySuggestion
This API is used to proactively push defense strategy recommendations to merchants after the AI analysis of a chargeback case is completed.
Structure
A message consists of a header and body. The following sections are focused on the body structure. For the header structure, see:
Note: Set the data type of each parameter (except array) as String. This means that you must use double quotation marks (" ") to enclose the parameter value. Examples:
- If the data type of a parameter is Integer and its value is
20, set it as "20". - If the data type of a parameter is Boolean and its value is
true, set it as "true".
Request parameters
disputeId String REQUIRED
Antom dispute ID, used to associate the notification with a local dispute case.
More information:
- Maximum length: 64 characters
notifyTime Datetime REQUIRED
Notification generation time. This parameter, together with disputeId, forms the logical event identifier of this notification: retry notifications reuse the same notifyTime, while a new logical event generates a new notifyTime.
More information:
- Maximum length: 32 characters
- The value follows the ISO 8601 standard format. For example, "2019-11-27T12:01:01+08:00".
winRateLevel String REQUIRED
Predicted win rate level. Valid values are:
-
HIGH: Indicates that the evidence is relatively strong and defense is recommended. -
MEDIUM: Indicates that the evidence strength is moderate, and supplementing missing evidence tags can improve the probability of winning. -
LOW: Indicates that the probability of winning is relatively low, and accepting the dispute may be recommended.
More information:
- Maximum length: 8 characters
evidenceList Array<EvidenceList> REQUIRED
More information:
- Maximum length: 32 characters
cardholderDisputeReason String
More information:
- Maximum length: 256 characters
defenseStrategyDescription String REQUIRED
More information:
- Maximum length: 2048 characters
Response parameters
result Result REQUIRED
A fixed value, which is sent to Antom to acknowledge that the notification is received.
Request
{
"disputeId": "20260831190000000001",
"notifyTime": "2026-08-31T19:00:00.000+08:00",
"winRateLevel": "HIGH",
"evidenceList": [
{
"evidenceTag": "LOGISTIC_INFORMATION",
"winRateContribution": "HIGH",
"obtained": "false"
},
{
"evidenceTag": "ORDER_INFORMATION",
"winRateContribution": "MEDIUM",
"obtained": "true"
},
{
"evidenceTag": "CUSTOMER_COMMUNICATIONS",
"winRateContribution": "LOW",
"obtained": "false"
}
],
"cardholderDisputeReason": "13.1 Merchandise/Services Not Received",
"defenseStrategyDescription": "The cardholder claims non-receipt. Tracking data shows delivery was signed for on 2026-08-20. Recommend defending this dispute and supplying the logistics proof of delivery together with the buyer-seller chat records."
}Response
{
"result": {
"resultCode": "SUCCESS",
"resultMessage": "success",
"resultStatus": "S"
}
}Result/Error codes
| Code | Value | Message | Further action |
|---|---|---|---|
| SUCCESS | S | Success. | No further action is needed. |