Visa Chargeback Codes: Old Numeric Codes vs. the Current System

Visa chargeback codes come in two generations, and mixing them up is why so many merchants end up building the wrong response. If you are looking at a two-digit code like 30, 53, or 75, you are looking at Visa's old numbering system, retired since 2018. If you are looking at something like 10.4 or 13.1, you are looking at the current system. This guide covers what the old codes meant, how they map to today's categories, and where to go for a full breakdown of the current codes.

{{cta}}

Visa's Legacy Chargeback Codes (Pre-2018)

Before April 2018, Visa assigned each dispute a two-digit numeric code. Some processors and older documentation still reference these numbers, which is why they keep showing up in searches. Here is what the most common legacy codes meant and how they roughly line up with today's categories.

These are general equivalents, not exact one-to-one replacements. If a processor or acquirer still hands you a two-digit code today, confirm the current category directly with them, and use the condition and transaction date applicable to the case. Visa’s June 2024 guide limits old 12.1 late presentment to transactions through 12 April 2024; 11.3 applies to that issue for transactions completed on or after 13 April 2024.

What Replaced the Old Codes: Visa Claims Resolution

In April 2018, Visa rolled out Visa Claims Resolution (VCR), an overhaul that replaced the two-digit codes with four dispute categories and standardized the response process across all of them. VCR also folded in Visa Resolve Online (VROL), the platform that exchanges the dispute data behind the scenes; see our guide to Visa Resolve Online for how that piece works.

The Four Current Visa Dispute Categories

Visa organizes disputes into Fraud, Authorization, Processing Errors and Consumer Disputes. Check the actual condition in Visa’s 18 April 2026 rules and the processor notice. The table below describes current conditions; historical codes may still matter for older transactions.

For the full code-by-code breakdown, including evidence requirements and response windows for every code from 10.1 through 13.9, see our Visa chargeback reason codes guide. If the code you received is specifically 83 (fraud in a card-absent environment), our dedicated guide to that code covers it in more depth, and old code 30's modern equivalent gets the same treatment in our guide to reason code 13.1.

Other Card Networks Use Their Own Codes

Visa's code system only applies to Visa transactions. Mastercard, American Express, and Discover each run separate numbering, so a code that means one thing on a Visa statement can mean something unrelated on a Mastercard one. If you process multiple networks, our Mastercard chargeback reason codes guide covers that network's equivalent system. For examples across every network, see our overview of chargeback reason codes.

How to Respond to a Visa Chargeback Code

1. Identify the category, not just the number. A code tells you which of the four categories you are dealing with, and that determines what evidence Visa expects from you.
2. Check your response window. Use the merchant response deadline in your processor or acquirer notice; a network response window is not a universal 30-day merchant deadline. Our Visa dispute rules and time limits guide covers deadlines and fees in detail.
3. Gather category-specific evidence. Fraud disputes need proof of authorization, and for the common card-absent fraud code, our Compelling Evidence 3.0 guide explains how to use transaction history to shift liability back to the issuer. Authorization disputes need proof you obtained and processed the correct approval, which our guide to unauthorized transaction chargebacks covers directly.
4. Watch your dispute ratio. Visa’s current VAMP monitoring considers reported fraud and disputes, applicable monthly counts, regional rules, acquirer criteria and exclusions. A fraud ratio alone does not establish automatic enrollment or fines. Our Visa's Fraud Monitoring Program guide provides legacy background; for current VAMP thresholds, see Visa’s VAMP fact sheet and confirm the applicable criteria with your acquirer.

Cutting Out the Manual Lookup on Every Chargeback Code

Matching each incoming code to the right evidence and deadline is exactly the kind of repetitive work that eats up a chargeback team's time. Chargeflow reads the code automatically, builds the category-specific evidence package, and submits it within the response window, so no dispute slips past its deadline because someone was still looking up what a code meant.