Visa Chargeback Reason Codes: The Full 2026 List for Merchants

Visa is the largest card network, which means most merchants see Visa disputes more than any other. The good news is that Visa’s reason-code system is the most logical of the four networks: the code itself tells you the category, so you can read a dispute at a glance.

This is the full 2026 reference for Visa chargeback reason codes. It covers the four categories, every code that matters to a card-not-present merchant, the evidence that wins each one, the time limits, and the Compelling Evidence 3.0 framework that has reshaped how fraud disputes are fought.

How Visa reason codes are structured

Visa uses a two-part decimal format. The digit before the dot is the dispute category; the digit after identifies the specific reason within it. This makes the system self-documenting once you know the four categories:

• Category 10 — Fraud: the cardholder says they did not make or authorize the transaction.
• Category 11 — Authorization: the transaction was approved when it should not have been.
• Category 12 — Processing Errors: the transaction was processed incorrectly.
• Category 13 — Consumer Disputes: the cardholder has a complaint about the goods or services.

So the moment you see 10.4, you know it is fraud. 13.1 is a consumer dispute. 12.5 is a processing error. This structure came out of Visa’s Dispute Resolution overhaul, which replaced the old numeric-only codes with the category-based system merchants use today. For how Visa’s scheme compares to the other networks, see the complete reason codes guide.

Category 10 — Fraud

Fraud is the category card-not-present merchants encounter most, and much of it is friendly fraud rather than true criminal fraud. These disputes hinge on proving the genuine cardholder made and benefited from the transaction.

10.4 is the one to know. It is the default code for disputed ecommerce transactions and the code you will most likely fight. Because it captures so much friendly fraud, it is also highly winnable with the right evidence. We cover it in depth in our dedicated Visa reason code 10.4 guide.

Category 11 — Authorization

Authorization disputes claim the transaction should never have been approved. They are less common for online merchants but do occur, particularly when authorizations expire or are processed after a decline.

The defense for category 11 is almost always documentary: your processor’s authorization records showing a valid approval code for the correct amount.

Category 12 — Processing Errors

Processing-error disputes claim the transaction was handled incorrectly — charged twice, for the wrong amount, in the wrong currency, or submitted too late. These are usually winnable with clean transaction records.

For 12.6 duplicate-processing disputes, the winning move is proof that two similar charges are genuinely two separate purchases — different order numbers, different items, or different timestamps — rather than one transaction billed twice.

Category 13 — Consumer Disputes

After fraud, this is the category ecommerce merchants see most. The cardholder acknowledges the purchase but claims a problem: the item never arrived, was not as described, was defective, or a promised refund never came.

13.1 (Merchandise/Services Not Received) is the workhorse of this category. It is won or lost on delivery evidence: tracking that shows the item reached the cardholder’s address, with signature confirmation where you have it. For digital products, download or access logs do the same job. Our reason code 13.1 guide walks through exactly what to submit.

Visa time limits

Two clocks apply to every Visa dispute:

• Cardholder filing window: generally 120 days from the transaction or expected delivery date, extended to as much as 540 days for goods or services with a future delivery or event date.
• Merchant response window: roughly 20 to 30 days at the network level, but your processor’s internal deadline is shorter and is the one that actually governs your case. Submit well before it.

Miss the merchant deadline and the dispute is forfeited automatically, no matter how strong your evidence was.

Compelling Evidence 3.0

The most important development in Visa disputes is Compelling Evidence 3.0 (CE 3.0), which specifically targets card-absent fraud disputes under code 10.4.

CE 3.0 lets you defeat a fraud claim by demonstrating a history of prior undisputed transactions from the same cardholder that share identifying data points with the disputed transaction. Qualifying data points include:

• IP address
• Device ID or fingerprint
• Account login / customer ID
• Shipping or delivery address

When you can show that the same customer previously made purchases sharing these markers — and did not dispute them — Visa treats that as compelling evidence that the disputed transaction is legitimate, shifting liability back to the issuer. In practice, CE 3.0 has turned many “unwinnable” friendly-fraud disputes into winnable ones, provided you actually capture and retain that transaction-linking data. The catch is exactly that: you need the historical data on hand, structured, at the moment a dispute lands.

The bottom line

Visa’s reason-code system rewards merchants who read the code first. The category (10, 11, 12, or 13) tells you the shape of the dispute; the specific code tells you the evidence bar. Fraud (category 10, especially 10.4) and consumer disputes (category 13, especially 13.1) are where card-not-present merchants spend most of their time, and both are highly winnable with the right, code-matched evidence.

Capturing that evidence — AVS/CVV results, IP and device data, prior-transaction history for CE 3.0, delivery tracking — at the moment of sale and having it ready the instant a dispute arrives is the hard part. DisputeDash does it automatically for every Visa code, so the right proof is already assembled before the clock starts.