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’re challenging a dispute and need to attach supporting documentation.
  • You have receipts, delivery confirmations, or correspondence that show a transaction was valid.
ScenarioWhen a customer disputes a purchase at Maple Street Coffee, Clearpath Payments challenges the dispute by attaching evidence, such as 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

Check the dispute’s payment brand before uploading evidence. File type and size requirements vary by brand.

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
Include the file in the multipart form data under 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).