Visa Reason Codes Cheat Sheet With Evidence By Code (2026)

Feb 28, 2026

A chargeback can feel like getting a parking ticket with no photo attached. You know it happened, but you still have to prove what you did right. That’s why Visa dispute reason codes matter. The code tells you what the cardholder claimed, and it also hints at the kind of evidence Visa expects to see.

This cheat sheet maps common Visa reason codes to the evidence that usually wins or loses cases. It’s written for merchants who accept card payments and want fewer disputes, lower fees, and less ops chaos.

How Visa dispute reason codes work, and why evidence gets rejected

Visa groups disputes into four buckets, each with its own “story” and evidence style: 10.xx Fraud, 11.xx Authorization, 12.xx Processing Errors, and 13.xx Consumer Disputes. That structure is the backbone of Visa Claims Resolution, and it’s also why you should avoid one-size-fits-all rebuttals. A great delivery proof won’t fix a duplicate processing error, and an AVS match won’t solve “credit not processed.”

If you need a quick refresher on the categories and how Visa labels them, Sift maintains a clean breakdown of Visa chargeback reason codes.

Most lost representments fail for boring reasons:

• The evidence doesn’t match the exact transaction (amount, date, last 4, descriptor).
• Screenshots show a policy, but not that the buyer accepted it.
• Shipping proof exists, but it doesn’t prove delivered to the right place.
• Subscription logs show activity, but not that the customer understood the billing.

Also, don’t be surprised if you still see older labels in processor portals. Some legacy codes (for example, older “72” style references) can map into the newer 11.xx structure, depending on reporting and region.

When you build your response, think in “evidence layers”:

• Payment layer: auth code, AVS/CVV, 3DS results, EMV data.
• Customer layer: account ownership, login records, IP and device signals.
• Fulfillment layer: carrier scans, proof of delivery, service access logs.
• Policy layer: refunds, returns, cancellation terms, and proof of acceptance.

That framework keeps your packet tight, and it reduces irrelevant attachments that slow reviewers down.

Visa reason codes cheat sheet with evidence by code

Use the table below as a fast match between the dispute code and what you should pull first. For deeper lists and definitions, Kount keeps a reference page of Visa chargeback reason codes, and Chargebacks911 also publishes a Visa reason code list.

Here’s a merchant-friendly cheat sheet for common codes and “best first evidence”:

Takeaway: match the code to the claim, then submit evidence that answers that claim directly. Anything else is noise.

If you can’t tie each document to the exact disputed charge, the rest won’t matter. Match on date, amount, and identifiers before you upload anything.

One simple way to improve win rates is to package evidence like a story with receipts. Keep it short:

1. One-paragraph summary of what happened and why the dispute is wrong.
2. Three to five exhibits that prove the key facts (auth, delivery, usage, policy acceptance).
3. A timeline with timestamps (order, ship, deliver, cancel attempt, refund).

That structure helps reviewers, and it keeps your team consistent across hundreds of cases.

Reduce disputes before the code hits your queue

Representment is damage control. The cheaper win is stopping disputes before they become chargebacks that count against your ratio. Visa programs and alerts help because they create a short window to resolve the issue early, often with a refund when fighting isn’t worth it.

Chargebase is built for that workflow. It’s a chargeback prevention and recovery platform that connects to your payment provider in about two minutes, no code required. After that, it can send real-time alerts only when they’re likely to prevent a chargeback, and it supports configurable automation rules so teams don’t have to babysit every case.

Chargebase works with major networks used for pre-dispute prevention and resolution:

• Verifi CDRN (Cardholder Dispute Resolution Network): often used to stop disputes before they formalize, priced in a pay-per-alert model (the provided pricing example is $15 per alert), with enrollment that can complete within about 12 hours, and typically a manual refund step.
• Visa RDR (Rapid Dispute Resolution): rules-based resolution that can auto-refund eligible disputes (example pricing is $15 per alert), with enrollment that can take up to about 5 days, and generally auto-refund only.
• Ethoca Alerts: issuer-driven dispute alerts (example pricing is $25 per alert), with enrollment that can complete within about 12 hours, and manual or automated refund options depending on setup.

If you want the nuts and bolts of issuer alerts, this internal guide explains Ethoca alerts for preventing chargebacks. For day-to-day ratio control, the docs on how to keep chargeback rates low effectively lay out what to measure (alert acceptance rate, speed to action, and how many alerts still turn into chargebacks).

Speed beats perfection in pre-dispute alerts. A timely refund often costs less than a “won” dispute after hours of labor.

Conclusion

Visa dispute reason codes don’t just label a case, they tell you what proof to pull first. Once your team maps each code to the right evidence, responses get faster and cleaner. Even better, when you pair that playbook with alerts and rules-based resolution, fewer disputes reach the chargeback stage at all. Keep your evidence tight, fix the upstream causes, and protect your chargeback ratio before it becomes a bigger problem.