Chargeback Reason Codes Cheat Sheet: What Evidence Fits Each Code

Apr 05, 2026

A chargeback can swing on one small detail, the code attached to it. When a transaction dispute is initiated, the issuing bank assigns a specific label to the case; send the wrong proof, and even a valid sale can lose.

Think of chargeback reason codes like labels on a case file. The label tells the bank what went wrong, and it tells your team what evidence matters most. Match your evidence to the chargeback reason codes, and your response gets much stronger.

Key Takeaways

• Match your evidence precisely to the chargeback reason code—fraud codes need auth and device data, non-receipt wants delivery scans, disputes require proof of agreement and fulfillment.
• One-size-fits-all responses lose cases; tailor proof to the code’s story, like EMV logs for chip fraud or service logs for quality issues.
• Act fast within 20-30 days using templates, but prevent disputes earlier with tools like Ethoca alerts via Chargebase.
• Banks reward relevance over volume—build a tight timeline linking the code to your proof for stronger representments.

Why the reason code should guide your response

Every chargeback starts with a story. Fraud, non-delivery, duplicate billing, or a canceled subscription can look similar in a dashboard. Still, the issuing bank treats them as different disputes, and every transaction dispute follows rules set by the card networks.

That is why one evidence package never fits every case. Login records can help in a fraud claim. They do little for a “goods not received” case. A signed delivery scan can help with non-receipt. It won’t fix a duplicate processing error.

As of April 2026, Visa, Mastercard, American Express, and Discover have not made a major overhaul to their chargeback reason codes systems. Visa still groups many cases under 10.x, 11.x, 12.x, and 13.x. Mastercard still relies on its 48xx series. If you need a refresher on the full dispute path, see understanding chargeback processes.

The naming can still feel messy across networks and processors. That’s why teams often keep a simple internal cheat sheet beside a broader network-by-network explanation.

Chargeback reason codes cheat sheet with evidence by code

Use this table as a first-pass playbook, not a final legal brief.

The code isn’t paperwork. It’s the bank telling you what proof it expects.

A few patterns show up fast. Fraud codes usually need transaction, device, and identity data. Non-receipt codes lean on shipping scans or service-access logs. Cardholder dispute codes work best when you show what the buyer agreed to, what you delivered, and what your policy said at checkout.

Authorization issues, point of interaction error, and processing codes need different proof

Not every dispute is about fraud or delivery. Visa 11.x and 12.x families often point to authorization issues or processing mistakes, such as duplicate processing, credit not processed, wrong transaction data, or missing approval. In those cases, banks want approval codes, batch timestamps, refund records, and proof that only one valid transaction was submitted. When the issue is clerical, customer emails rarely help.

For deeper review, compare your cases with this Visa reason code reference and Mastercard’s own merchant dispute guide.

What compelling evidence looks like in real cases

Winning compelling evidence is usually simple, but it has to line up with the reason code. Many merchants lose because they send a thick folder instead of a clear story. Banks don’t reward volume. They reward relevance. Providing this compelling evidence forms the core of the representment process, where your rebuttal letter must clearly link the proof to the specific code.

For customer disputes involving fraudulent transactions, build a tight timeline. Show the authorization result, the device or IP match, address verification service confirmation, the login history, and any sign the same customer used the account before without trouble. For delivery claims, show carrier scans, signature data if you have it, and customer messages that confirm receipt or scheduling. For canceled recurring transaction cases, renewal notices, cancellation clicks, and a clear billing descriptor matter more than a polished invoice.

Friendly fraud makes this harder. A buyer may know the purchase but still file a dispute because the descriptor looked unfamiliar, the trial renewed, or support felt slow. In those cases, your checkout wording, cancel flow, and support record can make or break the response.

Most acquirers impose strict time limits of 20 to 30 days for merchants to respond during the representment process. So speed matters almost as much as compelling evidence quality. Keep templates ready for your most common codes, and review them by product line. Also, update them when your processor changes how it labels a dispute. A short internal playbook, plus strategies for lowering chargeback ratios, can save your team hours each month.

Frequently Asked Questions

What are chargeback reason codes?

Chargeback reason codes are labels assigned by issuing banks to disputes, signaling what went wrong like fraud, non-delivery, or processing errors. They guide merchants on the exact evidence needed, such as device data for fraud (Visa 10.x) or shipment proof for non-receipt (Mastercard 4855). Matching your response to the code boosts win rates.

How do I choose the right evidence for a code?

Review the code first: fraud (10.x, 48xx) uses EMV, 3DS, AVS/CVV; non-receipt (13.1, 4855) needs tracking and access logs; disputes (4853) show product terms and delivery. Avoid generic folders—link proof directly to the code’s issue in a clear timeline. Use network guides for deeper details.

What are the most common chargeback codes?

Visa 10.4 (CNP fraud), 13.1 (not received), and Mastercard 4837 (no authorization), 4853 (disputes), 4855 (not received) top the list. Fraud leans on identity data, delivery on scans, quality on policy proof. Codes haven’t changed much as of 2026.

How can I prevent chargebacks before they happen?

Use early alerts from Ethoca, Verifi, or Visa RDR via Chargebase to refund or resolve disputes pre-chargeback. It connects quickly to your gateway for automated workflows and pay-per-alert pricing. This stops reason codes from ever arriving.

What’s the timeline for responding to chargebacks?

Acquirers give 20-30 days for representment—speed matches evidence quality. Prep templates by code and product to respond fast. Pair with prevention to cut volume.

How Chargebase helps reduce chargebacks before the code ever arrives

The best cheat sheet still starts late if the dispute is already live. That’s where Chargebase helps. Chargebase is chargeback management software for e-commerce and SaaS companies that want fewer disputes, less manual work, and better revenue protection.

Instead of waiting for a formal reason code, Chargebase helps merchants act earlier through programs such as Ethoca, Verifi CDRN, and Visa RDR. It connects to your payment provider in about two minutes, supports no-code setup, and sends real-time alerts only when quick action can still stop the case. It also supports a fully automated workflow, with more than 10 automation rules available through RDR, including preventing a canceled recurring transaction from becoming a formal chargeback. Because the pricing is pay-per-alert, the model stays performance-based and easy to track.

That early-warning model matters because a refunded alert often never becomes a network chargeback at all; chargeback reason codes can be avoided entirely if customer disputes are caught early. For many companies that accept card payments through gateways or other fintech systems, that is the cleanest way to cut chargebacks before an evidence package is even needed. You can read more about how Ethoca alerts stop chargebacks.

A reason code looks small, but it sets the path for the whole case. Match the code to the right proof, and your response becomes tighter, faster, and easier to defend.

If your team still handles every dispute the same way, fix that first. Then pair a clear evidence playbook with chargeback prevention tools that stop more disputes before they hit your queue. Effective chargeback management requires both a prevention tool and a strategy for handling chargeback reason codes when they do occur.