Receive the chargeback from your acquirer including the dispute reason code (e.g., 10.4 for card-absent fraud, 13.1 for merchandise not received); identify the specific evidence requirements for the reason code under Visa's dispute rules.
Gather compelling evidence: for fraud disputes this may include prior undisputed transaction history from the same card, device fingerprint matches, IP address history, or signed delivery confirmation; for services disputes it may include correspondence, terms of service acceptance, and usage logs.
Prepare the representment package with a rebuttal letter that explicitly addresses each element of the cardholder's claim and maps each piece of evidence to a specific counter-argument.
Submit the representment through your acquirer's dispute portal or API within the representment deadline (typically 30 calendar days from the dispute processing date); include all evidence files in the accepted format (PDF preferred).
Monitor for the second presentment: if the issuer re-presents after your representment, you have the option to accept the liability or escalate to pre-arbitration within the next deadline window.
Track representment win rates by reason code to identify patterns and improve prevention strategies (e.g., adding delivery confirmation for shipment-related disputes).
Known gotchas
Compelling evidence under Visa's CE3.0 framework requires two or more prior undisputed transactions from the same card and device or shipping address for fraud reason codes; incomplete evidence sets are rejected.
Submitting a representment does not pause the financial debit — the disputed amount remains debited from your account until the dispute resolves in your favor.
Visa arbitration fees (charged to the losing party) can exceed the dispute amount for small transactions; evaluate cost-benefit before escalating low-value disputes to arbitration.
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