Retrieve the Dispute object via API to identify the chargeback reason code (e.g., 'fraudulent', 'product_not_received', 'credit_not_processed') — the reason code dictates which evidence types are compelling.
Assemble evidence tailored to the reason code: for 'fraudulent' on a card-present or 3DS-authenticated transaction, pull the ECI value, authentication reference, and AVS/CVV match results; for 'product_not_received', compile delivery confirmation, tracking numbers, and proof of digital delivery.
Upload evidence files using the Stripe Files API (PDF or image), then attach each file ID to the appropriate field in the dispute evidence object.
Set a clear rebuttal letter in 'uncategorized_text' that narrates the transaction timeline and explicitly addresses the cardholder's claim.
Submit the evidence before the Stripe-displayed deadline (which is earlier than the raw network deadline to allow processing); late submissions are not forwarded to the network.
After submission, monitor the dispute status webhook for 'charge.dispute.closed' with outcome 'won' or 'lost'; log the outcome for win-rate tracking per reason code.
Known gotchas
Submitting excessive or irrelevant evidence does not help — card network arbitrators review a constrained set of document types per reason code; padding the bundle with unrelated files can obscure the key proof.
For 'fraudulent' disputes on non-3DS transactions, liability typically rests with the merchant; the practical threshold for winning is high — quantify expected win rates before investing in representment for low-value disputes.
Stripe's evidence field names map to specific network evidence categories; using the wrong field (e.g., placing a refund policy in 'shipping_documentation') means the evidence may not be transmitted correctly to the issuer.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?