Visa Chargeback Reason Codes: The Four Categories, Explained

Visa chargeback reason codes are the labels a customer's bank attaches to a reversed charge to tell you why it happened. That code sorts into one of four categories, and the category is what tells you which evidence will win the dispute back.

I've disputed chargebacks and built representment evidence on my own stores. The reason code was the first thing I checked every time, because it decides what evidence actually wins.

Read the category right and you know in a few minutes which family your dispute belongs to and what to gather.

Key takeaways

• Every Visa reason code sorts into one of four category families.
• The category number, 10 through 13, tells you the root cause.
• Fraud codes and consumer-dispute codes need completely different evidence.
• Cardholders get up to 120 days to file a Visa dispute.
• Visa consolidated 20-plus legacy codes into four categories in 2018.

What are Visa chargeback reason codes?

A Visa chargeback reason code is a two-digit-plus-decimal label, like 10.4 or 13.2, that identifies why a bank reversed a charge. Every code sorts into one of four categories. You may also see these called Visa dispute reason codes or dispute categories.

The category number does the real work. It names the root cause, and each number maps to one:

• 10: fraud, the cardholder didn't authorize it.
• 11: an authorization failure.
• 12: a processing error.
• 13: a complaint about the goods or service.

That root cause sets which documents you gather, so reading the category is your first move on any dispute.

Here's the caveat. The issuing bank picks which category a dispute lands in. So two disputes that feel identical to you can carry different codes and need completely different evidence. The code is the bank's read on what happened, and you respond to the code you got.

The four reason code categories

Visa splits every reason code into four families, and the split is by root cause, what actually went wrong with the transaction. The four are covered one at a time below, in Visa's own numbering order.

Fraud (10.x)

Fraud codes (10.1 through 10.5) mean the cardholder or their bank says the cardholder didn't authorize the transaction. This is the "I never made this purchase" family.

The most common code here is 10.4, card-absent fraud. It covers online and other card-not-present sales. It's also the code Visa's Compelling Evidence 3.0 program is built to fight. That program lets you show a pattern of legitimate prior use by the same cardholder.

Here's the trap.

Sometimes a 10.4 comes from a customer who genuinely bought the item and forgot, which is friendly fraud. On paper it looks identical to a real stolen-card case. The reason code alone won't tell the two apart, so read the full transaction history before you decide how to respond.

Authorization (11.x)

Authorization codes (11.1 through 11.3) mean something went wrong in how the transaction was approved. The purchase itself may be perfectly legitimate. The question here is about the approval step, while the cardholder's intent stays out of it.

Code 11.2 is the one to watch. It covers a merchant who processed a sale after getting a decline or a pickup response. That's a processing-discipline problem you control. Don't override a decline and re-run the charge, and you won't see this code.

Processing errors (12.x)

Processing error codes (12.1 through 12.7) cover transactions that were technically mishandled, like duplicate charges, the wrong currency, or the wrong amount. These are the most mechanical disputes in the set.

Two of them usually resolve fast. Codes 12.5 (incorrect amount) and 12.6 (duplicate processing) come down to your own transaction records. Either they match the disputed charge or they don't, and the answer is already in your system.

Code 12.1 is the exception.

It turns on timing rather than the amount, so it needs a different kind of proof, evidence that you submitted the transaction inside Visa's processing window.

Consumer disputes (13.x)

Consumer dispute codes (13.1 through 13.9) mean the cardholder has a complaint about the goods or service itself. Here the product is the issue, once authorization and processing both check out. This is the largest and most varied family.

The two you'll see most are 13.2 (cancelled recurring transaction) and 13.7 (cancelled merchandise or services). Both usually trace back to one root cause. The customer didn't recognize the charge on their statement.

A clear billing descriptor stops more of these than any evidence you can file after the dispute is already open.

Watch the split inside this family, because it decides your evidence. A 13.1 (merchandise or service not received) needs proof of delivery or fulfillment. A 13.3 (not as described) needs proof the item matched its listing. The two look alike on a notification but call for different documents.

Once you know which family a dispute belongs to, you'll want the exact code. Look up your specific reason code and its evidence requirements in our reason-codes tool.

How much time you have to respond

Visa gives cardholders up to 120 days to file a dispute, and merchants a set response window at each stage after that. The 120 days run from the transaction or the expected delivery date.

Miss your merchant window and you can lose a case you had the evidence to win.

The clock runs per phase. Under Visa Claims Resolution, a dispute moves through Allocation first, then Collaboration if it escalates. Each phase starts a fresh response window. ChargebackGurus reports Visa's published window at 30 days from day one of each phase.

Knowing your window is only half of it. You still need documents matched to your code, so pull the evidence for your specific code before you build the response.

Your acquirer can override Visa's number, though. Some processors and acquirers set an internal deadline shorter than Visa's window. When they do, their deadline is the one that binds you.

A missed window costs you more than the one case. A lost dispute still counts against your ratio, so it also adds to your chargeback monitoring program risk.

Why Visa's reason codes changed

Visa replaced more than 20 legacy numeric reason codes with the current four-category system under Visa Claims Resolution (VCR) in April 2018.

The old codes overlapped, and that ambiguity made disputes take weeks longer to route and decide. Folding them into four clear categories was Visa's fix for slow resolution.

You may still run into an old code, though. Some processor dashboards and older documentation still show legacy numbers, like code 30 or code 41. That's why you might see a code that doesn't match anything in this article.

FAQ

What is the reason code 30 on a Visa chargeback?

Code 30 is a legacy Visa reason code from before the 2018 remap, with no one-to-one equivalent in the current format. A dispute that once carried code 30 now files under one of the 13.x consumer-dispute codes.

Can one transaction get more than one reason code over time?

A single dispute keeps the code the issuer assigned it. But a transaction disputed, resolved, and disputed again can return under a different code, and each filing is judged on its own code.

Does the reason code change the chargeback fee amount?

No. Your processor's pricing sets the chargeback fee, so the reason code changes what evidence you need but leaves the cost the same.

What happens if Visa can't find a reason code for a dispute?

Every dispute that reaches the network is filed under a specific code, because the code is what routes it. If a code looks wrong or ambiguous, that's a question for your acquirer, who filed it on your behalf.