Identify the dispute reason code from the incoming chargeback to determine the workflow: allocation disputes (e.g., fraud, authorization-related) assign liability to the merchant automatically without requiring issuer collaboration, while collaboration disputes (e.g., processing errors, consumer disputes) require back-and-forth between issuer and acquirer.
For allocation disputes, assess whether compelling evidence can overcome the pre-assigned liability; if so, submit a representment with evidence through your acquirer within the VCR deadline (typically 30 calendar days from the dispute processing date).
For collaboration disputes, respond to the initial inquiry from the issuer within the specified timeframe by providing supporting documentation through your acquirer's dispute portal or API.
Track dispute status and deadlines using the Visa Dispute Management System (VDMS) or your acquirer's dispute API; VCR condensed the multiple legacy chargeback cycles into a two-cycle maximum.
If the first representment is denied, evaluate whether pre-arbitration or arbitration escalation is warranted based on dispute amount and evidence strength.
Document all dispute actions with timestamps and response codes for compliance and chargeback ratio monitoring.
Known gotchas
In allocation workflow, liability is pre-assigned based on rules — submitting a representment without compelling evidence wastes the one allowed response cycle.
VCR timelines are calendar days, not business days; weekends and holidays count toward the deadline, making prompt action critical.
Confusing the workflow type (allocation vs. collaboration) leads to using the wrong response strategy and missing the correct evidence requirements.
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