Skip to main content
What is it? The dispute evidence upload endpoint accepts supporting documentation when challenging a dispute. Each upload returns an attachment ID you reference in your dispute response.
When to Use
  • You need to provide documentation to support your dispute challenge.
  • You have receipts, delivery confirmations, or correspondence to prove a transaction was valid.
  • You want to increase your chances of winning a dispute case.
ScenarioWhen a customer disputes a purchase at Maple Street Coffee, Clearpath Payments challenges the dispute by attaching evidence — receipts, proof of delivery, or correspondence with the customer.

​
Implementation rules

  1. Files must be uploaded before responding to a dispute with a challenge
  2. File format and size requirements vary by payment brand (see table below)
  3. The returned attachmentId must be included in the respondToDispute mutation when challenging a dispute
  4. At least one attachment is required when challenging a dispute
  5. Multiple files can be uploaded separately, and will be referenced together in a single dispute challenge

​
File requirements by payment brand

Make sure to check the dispute’s payment brand before uploading evidence, as each brand has different file type and size requirements.

​
Upload process

The upload process uses a standard multipart form data request to a REST endpoint:
Where:
  • {baseUrl} is your Tesouro API base URL
  • {disputeId} is the ID of the dispute you’re uploading evidence for
The request should include the file in the multipart form data with the field name file.

​
Error handling

The endpoint responds with a 400 status code if the file size exceeds the limit or if the file type isn’t supported for the dispute’s payment brand. Check the payment brand requirements before uploading.

​
Using attachment IDs

After successfully uploading evidence, use the returned attachmentId when challenging a dispute with the respondToDispute mutation (see Respond to a dispute).