Evaluation Payload

An evaluation request is composed of four required parts:

Field	Description
category	The type of dispute being evaluated
dispute	The disputed amount and currency
transaction	Details of the original transaction
evidences	Supporting evidence (varies by category)

Category

The category field identifies the type of dispute. Each category has its own evidence requirements.

Category	Description
fraud_online	Unauthorized online/e-commerce transactions
service_not_received	Goods or services paid for but not delivered
processing_duplicate	Transaction charged multiple times

info

The categories listed above are currently supported. Additional dispute categories will be available soon.

Dispute

The dispute object specifies the amount and currency being disputed. This may match the full transaction amount or be a partial amount when only some items or services are being disputed.

Loading dispute fields...

Transaction

The transaction object contains details of the original charge being disputed.

Loading transaction fields...

Evidences

The evidences object contains supporting information for the dispute. The required and optional fields depend on the selected category.

Evidence by Category

Select a category below to view its evidence requirements and example request:

Loading evidence data...

Required vs Optional Evidence

• Required evidence must be provided for the evaluation to proceed. Missing required evidence will result in a validation error.
• Optional evidence enhances the evaluation. Providing more evidence generally leads to higher confidence levels.

tip

Even if evidence is optional, providing it can significantly improve your confidence level. The more context you provide, the better the evaluation.

Cardholder Statement

The cardholder_statement is required for all categories. This is the cardholder's description of why they are disputing the transaction.

Requirements:

• Minimum 35 characters
• Should clearly describe the dispute from the cardholder's perspective
• Should include relevant details about why the transaction is being disputed

Example:

Loading example...

File Evidence

Some evidence fields accept file attachments (e.g., police_report, merchant_contact, purchase_order). To use file evidence, upload the file first and then reference it by UUID in your evaluation request.

Upload Endpoint

curl -X POST https://api.disputes.play.tripledev.app/api/files/evidence_files/ \
-H "Authorization: Bearer $API_KEY" \
-F "file=@police_report.pdf"

The response contains the file metadata:

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "url": "https://files.example.com/evidence/550e8400-e29b-41d4-a716-446655440000",
  "original_name": "police_report.pdf",
  "mime_type": "application/pdf",
  "size": 245678
}

Then use the returned id in your evidences object:

{
  "evidences": {
    "police_report": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Supported File Types

Type	Extensions	Max Size
PDF	.pdf	10 MB
Images	.jpg, .jpeg, .png	10 MB

The API returns a 422 status code when file validation fails (unsupported MIME type, empty file, or file too large).