%201.svg)
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
600+ reviewsTL;DR:
- Reason codes identify dispute conditions, not final findings of fraud or fault.
- Read the network code alongside the provider category and case description.
- Match evidence to the specific allegation and current response deadline.
- Track code, outcome, and operational cause separately.
Chargeback reason codes identify the condition under which a card payment is disputed. They help merchants select the relevant evidence and response process, but they do not independently establish fraud, fault, or the final outcome.
Read the Code With the Network and Case Description
A processor may display a simplified category alongside the network code. Preserve both. The same general complaint can have different codes across networks, and one code can contain several distinct conditions.
| Example | Meaning | Useful evidence focus |
|---|---|---|
| Visa 10.4 | Other fraud in a card-absent environment | Relevant authorization, authentication, and customer records. |
| Visa 13.1 | Merchandise or services not received | Delivery agreement and fulfillment outcome. |
| Visa 13.3 | Not as described or defective | Purchase-time description and the alleged discrepancy. |
| Visa 13.6 | Credit not processed | Refund amount, date, and reference. |
| Mastercard 4837 | No cardholder authorization | Records addressing authorization. |
| Mastercard 4853 | Cardholder dispute, with specific underlying conditions | Read the condition before selecting delivery, return, or billing evidence. |
These are selected examples, not a complete code list. Consult the Visa merchant guide and Mastercard merchant guide, then confirm the current condition with your provider. Do not universally map Mastercard nonreceipt claims to an older standalone code.
Keep Other Networks in Their Own Framework
American Express has its own dispute reference guide. Discover also uses a distinct framework. The Amex guide and Discover guide explain merchant routing. Do not translate a code by matching its digits to another network.
Turn the Reason Into a Specific Evidence Question
- What exactly does the cardholder allege?
- Which payment and amount are disputed?
- What condition permits the dispute?
- Which record supports your answer to that condition?
- What deadline and submission options appear in the case?
For unauthorized transactions, an approval code alone is not proof of consent. For nonreceipt, show the destination and delivery outcome. For product-description disputes, answer what allegedly differed from the promise.
Use standard evidence categories to organize records without sending an identical response for every case. A policy screenshot does not replace proof that the specific policy applied to the purchase.
Keep Codes Separate From Fraud Findings and Monitoring
A fraud reason means an authorization complaint has been raised; it does not prove deliberate customer misuse. Likewise, a delivery dispute can reflect a genuine fulfillment problem. Record the allegation separately from your investigation finding.
Monitoring programs use their own definitions and thresholds. A reason-code table cannot tell you whether a merchant account is compliant. Review chargeback rules and your provider’s monitoring notices separately.
Use Outcomes to Improve the Next Response
Track the original code, provider category, evidence submitted, outcome, and underlying cause. If the case changes stage or a new request arrives, read the current instructions. Winning a response does not mean every future claim with that code is challengeable.
Compare cases by both reason and business process. Repeated refund complaints may reveal a reconciliation problem; repeated nonreceipt claims may identify a delivery issue. You can organize supported case responses with Chargeflow’s automated recovery.
Frequently Asked Questions
Does a chargeback reason code prove fraud?
A chargeback reason code identifies the dispute condition. It does not independently prove fraud or decide the final outcome.
Do all card networks use the same codes?
Card networks use different reason-code frameworks. Merchants should read the network, code, description, and underlying condition together.
What evidence should a merchant send for a reason code?
Send evidence that answers the specific allegation and applicable condition. A general policy or approval record may not answer delivery, product, or refund complaints.
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
.png)
