Retrieve the dispute object and note the evidence_due_by timestamp; you have roughly 7–10 days from issuance depending on the card network
Collect evidence artifacts: customer communication logs, shipping/delivery confirmation, service-usage logs, signed receipts, and customer IP/device fingerprint from your own records
Map each artifact to the correct Dispute Evidence field (e.g., customer_communication, shipping_documentation, uncategorized_file) and upload binary files via the Files API to obtain file token IDs
Call the Update Dispute endpoint with the populated evidence object and set submit=true to send to the card network before the deadline
Monitor the dispute status field via webhook (charge.dispute.updated) for transitions to won or lost; a lost dispute does not allow resubmission on the same chargeback
Known gotchas
Setting submit=false saves a draft but does NOT submit; evidence is not sent to the network until submit=true is explicitly passed
File uploads must be complete before the deadline; uploading evidence after evidence_due_by silently fails without error on the submission call
Evidence fields have character limits; exceeding them truncates content server-side, so keep textual evidence concise and prefer file attachments for long documents
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp