Antom, leading provider of tailored payment solutions

supplyEvidence

This API is used to supplement and submit defense evidence for a specified chargeback dispute case.

Note: The request message for this API is large and must be initiated through the large-message gateway. Please select the corresponding large-message gateway address from the table below based on your country/region.

Country/Region

Method

URL

US

POST

https://open-big-na.alipay.com/v1/payments/supplyEvidence

SG

POST

https://open-big-sea.alipay.com/v1/payments/supplyEvidence

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.

Note: If the dispute does not exist or belongs to another merchant, DISPUTE_NOT_FOUND_OR_NO_ACCESS will be returned.

More information:

  • Maximum length: 64 characters

evidenceContent Map<String, Object>  REQUIRED

The evidence content collection. It uses a key-value structure:

  • The key is evidenceTag. The collection must contain at least 1 key and can contain up to 32 keys.
  • The value is the parameter object corresponding to the evidenceTag. The length of a single value must not exceed 4,000,000 characters.

Note: If the key is not included in the values of evidenceTag, EVIDENCE_TAG_NOT_SUPPORTED will be returned.

More information:

  • Maximum length: 10000000 characters

Response parameters

result Result  REQUIRED

The result of the API call.

disputeId String  

Antom dispute ID.

Note: This parameter is returned when the value of result.resultStatus is S.

More information:

  • Maximum length: 64 characters

evidenceResults Array<EvidenceResult>  

The list of processing results for each evidence tag.

Note: This parameter is returned when the value of result.resultStatus is F and the failure reason can be attributed to a specific evidence tag.

API Explorer

Request

Case
json
{
  "disputeId": "20260831190000000001",
  "evidenceContent": {
    "LOGISTIC_INFORMATION": {
      "trackingNumber": "SF1234567890",
      "postCode": "5***00",
      "shippingAddress": "***",
      "trackingUrl": "https://www.sf-express.com/track?no=SF1234567890",
      "proofOfShipment": "Signed for by the recipient on 2026-08-20 10:32 (SF Express)",
      "logisticScreenshotFile": {
        "fileName": "delivery_proof.jpg",
        "fileFormat": "JPG",
        "fileContent": "/9j/4AAQSkZJRgABAQAAAQ..."
      }
    },
    "CUSTOMER_COMMUNICATIONS": {
      "customerCommunications": "2026-08-20 buyer confirmed receipt in chat: \"Package received, thanks.\""
    },
    "RETURN_AND_REFUND_POLICY": {
      "returnAndRefundPolicy": "https://merchant.example.com/refund-policy"
    },
    "UNCATEGORIZED": {
      "supplementProof": "The buyer placed 14 undisputed orders with the same shipping address in the past 12 months.",
      "supplementProofFileList": [
        {
          "fileName": "order_history.pdf",
          "fileFormat": "PDF",
          "fileContent": "JVBERi0xLjQK..."
        },
        {
          "fileName": "crm_note.png",
          "fileFormat": "PNG",
          "fileContent": "iVBORw0KGgoAAAANS..."
        }
      ]
    }
  }
}

Response

json
{
  "result": {
    "resultCode": "PARTIAL_SUCCESS",
    "resultStatus": "F",
    "resultMessage": "part of the evidence tags failed"
  },
  "disputeId": "20260831190000000001",
  "evidenceResults": [
    {
      "evidenceTag": "LOGISTIC_INFORMATION",
      "success": "true"
    },
    {
      "evidenceTag": "CUSTOMER_COMMUNICATIONS",
      "success": "false",
      "resultCode": "EVIDENCE_TAG_NOT_SUPPORTED"
    },
    {
      "evidenceTag": "PROOF_OF_SERVICE_COMPLETION",
      "success": "false",
      "resultCode": "EVIDENCE_FIELD_MISSING",
      "failedFieldPath": "PROOF_OF_SERVICE_COMPLETION.merchantOrderNo"
    }
  ]
}

Result codes

resultCode

Status

Message

Recommended action

SUCCESS

S

All tags were saved successfully.

Wait for the notification from the notifyDefenseDocument API.

PARTIAL_SUCCESS

F

Some tags succeeded and some tags failed.

Read evidenceResults to locate the failed tags, and retransmit only the failed tags.

DISPUTE_NOT_FOUND_OR_NO_ACCESS

F

disputeId does not exist, or it does not belong to the merchant corresponding to the current merchant ID.

Do not retry. Verify whether the disputeId comes from a case pushed to this merchant through the notifyDispute or notifyDefenseStrategySuggestion API.

MERCHANT_NOT_ENABLED

F

The merchant has not enabled the intelligent defense API.

This cannot be resolved by modifying parameters. Contact your Antom account manager to apply for activation. Do not retry before it is enabled.

EVIDENCE_TAG_NOT_SUPPORTED

F

The key in evidenceContent is not within the 24 enumerated evidence tag values, or it is not applicable to this merchant’s MCC classification.

Retry after correction. Use evidenceResults.evidenceTag to locate the specific unsupported tag.

EVIDENCE_CONTENT_INVALID

F

The value corresponding to the tag is not a JSON object, the structure cannot be parsed, or the JSON object content is empty.

Retry after correction. Reconstruct the tag object according to the field requirements of the corresponding tag.

EVIDENCE_FIELD_MISSING

F

A required parameter is missing within the tag

Retry after correction. Use evidenceResults.failedFieldPath to locate and complete the missing parameter, for example, LOGISTIC_INFORMATION.trackingNumber, and retransmit only that tag.

FILE_FORMAT_NOT_SUPPORTED

F

The file format is not supported. fileFormat is not within PDF, JPG, JPEG, PNG, or WORD.

Convert the file to a supported format and retry. Note that the format value must be in uppercase.

CAPACITY_EXCEEDED

F

Capacity limit exceeded, for example, the number of keys in evidenceContent exceeds 32, or the number of elements in UNCATEGORIZED.supplementProofFileList exceeds 5.

If the number of evidenceContent keys exceeds 32, split them into multiple submissions, with different keys in each batch. If UNCATEGORIZED.supplementProofFileList exceeds 5, do not split it into batches because retransmitting the same tag overwrites the previous submission. Instead, merge the files before submission or use another applicable tag. The server does not silently truncate data; the entire request is rejected when the capacity limit is exceeded.

FIXED_EVIDENCE_SIZE_EXCEED

F

The merchant-level fixed evidence exceeds the 32 KB UTF-8 byte limit after merging.

Simplify the fixed evidence content and retry. The entire request fails, and the retained content remains unchanged.

TIME_EXCEEDS_LIMIT

F

The defense deadline has passed.

Do not retry. The case has reached a final status. Stop submitting.

PROCESS_FAIL

F

General business failure that does not belong to the explicit error types above.

Do not retry. Contact Antom Technical Support for troubleshooting.

UNKNOWN_EXCEPTION

U

System exception, including exhaustion of concurrent write retries.

Retry is allowed. Retransmitting the same tag overwrites the previous submission and does not create duplicate risks.

PARAM_ILLEGAL

F

The parameter format is invalid, for example, disputeId is missing or too long, evidenceContent is empty or not an object, or a parameter value contains illegal control characters.

Correct the input parameters and retry.