You get a chargeback notification. There's a code attached. Maybe it says "4853" or "UA02" or "10.4." And unless you know exactly what that means, you're already behind.
Chargeback reason codes are short identifiers assigned by card networks to classify why a customer disputed a charge. They tell you what the cardholder claimed, what card network rule applies, and most importantly, what evidence you need to submit to win. Get the wrong evidence in front of the wrong code, and your dispute gets rejected, no matter how legitimate the original transaction was.
What Chargeback Reason Codes Actually Tell You
Every reason code maps to a specific claim. The four major card networks each have their own system:
- Visa uses numeric codes (e.g., 10.4 for fraud, 13.1 for merchandise not received)
- Mastercard uses 4-digit codes starting with 48xx (e.g., 4853 for cardholder disputes)
- American Express uses alphanumeric codes (e.g., F29 for card-not-present fraud)
- Discover uses alphanumeric codes (e.g., UA02 for card-not-present fraud)
Each code falls into one of a few broad categories: fraud, authorization issues, processing errors, or customer disputes. The category alone shapes your entire response strategy.
The Most Common Chargeback Reason Codes Merchants Face
Most disputes you'll deal with cluster around a handful of codes. Here are the ones that show up most often:
Fraud-related codes:
- Visa 10.4 / MC 4837: Card-absent fraud (the most common online dispute type)
- Amex F29: Card not present fraud
- Discover UA02: Card-not-present fraud
Customer dispute codes:
- Visa 13.1: Merchandise not received
- Visa 13.3: Not as described or defective
- Visa 13.6: Credit not processed
- MC 4853: Mastercard's broad cardholder dispute code covering merchandise not received, not as described, credit not processed, improper recurring charges, and more
Authorization codes:
- Visa 11.3 / MC 4808: No authorization obtained
Fraud codes are trickier to fight. Customer dispute codes are more winnable, especially when you have strong delivery confirmation, clear product descriptions, and documented customer communication. Knowing which category you're dealing with is step one to building a chargeback evidence packet that holds up.
Building a Chargeback Evidence Packet That Actually Works
A chargeback evidence packet is the collection of documents you submit to your acquirer (your payment processor's bank) when fighting a dispute. What goes into it depends entirely on the reason code.
For a "merchandise not received" code, you need proof of shipment and delivery. For a fraud code, you need proof that the cardholder authorized the transaction. For "not as described," you need product documentation and any customer service exchanges.
Submitting the wrong documents wastes your response window and hands the dispute to the cardholder by default.
Here's what a solid evidence packet looks like across common dispute types:
- Proof of delivery (carrier tracking with confirmed delivery)
- Signed order confirmation or terms of service acceptance
- IP address and device fingerprint logs (for online transactions)
- Customer communication records (emails, chat transcripts)
- Photos or descriptions matching exactly what was listed at checkout
- Refund or return policy documentation
Every document you include should directly counter the specific claim in the reason code. Relevance matters more than volume.
Want to stop building these manually? Book a demo with Chargeblast and see how it maps evidence automatically.
Why Most Merchants Lose Chargeback Disputes (And How to Win Them)
The biggest reason merchants lose when trying to win chargeback disputes isn't lack of evidence. It's submitting the wrong evidence, missing the response window, or not understanding what the reason code actually requires.
Each network sets strict deadlines. Visa gives merchants 30 days to respond, though your acquirer's internal deadline is often shorter, sometimes as little as 5 to 10 days by the time the dispute filters through to you.
Mastercard's window varies by code. Miss it, and the dispute closes against you automatically. On top of that, acquirers have their own formatting requirements. A well-documented case rejected on a technicality is still a loss.
A few things that consistently hurt merchants:
- Using generic responses that don't address the specific code
- Missing deadlines because disputes weren't caught early
- Submitting incomplete packets without the code-specific evidence required
- Not tracking patterns across multiple disputes to identify fraud trends
The merchants who consistently win chargeback disputes treat them like a process, not a one-off scramble. They have templates ready, they know their reason codes, and they respond fast.
Final Thoughts: Stop Losing Winnable Disputes
Chargeback reason codes aren't just bureaucratic labels. They're the instructions for how to fight back. When you know what each code means and what your chargeback evidence packet needs to include, you stop losing disputes you should win.
The merchants who win chargeback disputes consistently are the ones who understand the system, respond quickly, and submit the right evidence for the right code, every time. If you're still piecing this together manually, you're spending hours you don't have on a process that can be streamlined.
FAQ: Chargeback Reason Codes and How to Win Disputes
What are chargeback reason codes?
They're short identifiers assigned by card networks (Visa, Mastercard, Amex, Discover) that classify why a customer disputed a transaction and what evidence is needed to fight it.
Can I win a chargeback dispute if the reason code is fraud-related?
Yes, but it's harder. You'll need strong transaction data, IP and device logs, and signed authorization proof to counter a fraud claim successfully.
What goes into a chargeback evidence packet?
It depends on the reason code, but generally includes proof of delivery, order confirmation, customer communication, and product documentation that directly addresses the specific claim.
How long do I have to respond to a chargeback?
It varies by network -- Visa gives merchants 30 days, but your acquirer's internal deadline is often much shorter, sometimes just 5 to 10 days. Tracking disputes early is critical.
Does every chargeback require a different response?
Yes. Each reason code has specific evidence requirements. A response that works for "merchandise not received" won't hold up against a fraud code.
Stop Letting Reason Codes Cost You Money
Chargeblast takes the guesswork out of chargeback disputes. Real-time alerts, automatic reason code mapping, and pre-built response workflows mean you spend less time fighting and more time running your business.
Book a demo today and see how merchants are winning more disputes with less effort.
