Every chargeback that hits your merchant account arrives with a reason code. That code is not just administrative labeling. It tells you exactly what the cardholder claimed, what category of dispute you're dealing with, and most importantly, what evidence you need to fight it. Merchants who don't understand reason codes submit the wrong evidence, miss the deadlines that apply to their specific code, and lose disputes they should win.
This reference covers the most common Visa and Mastercard chargeback reason codes, what each one means in plain language, and what your response needs to address to give you a realistic chance of winning the representment.
How Reason Codes Work
When a cardholder disputes a charge, their issuing bank assigns a reason code based on the cardholder's stated complaint. That code is what the merchant sees on the chargeback notification. Visa and Mastercard use different numbering systems, but their categories map to similar dispute types.
The reason code determines three things: the dispute category, the evidence requirements for representment, and the response deadline. Deadlines vary by code and network, typically ranging from 20 to 45 days from the chargeback notification date. Missing the deadline is an automatic loss regardless of how strong your evidence is.
One important caveat: reason codes reflect what the cardholder told their bank, not necessarily what actually happened. A customer committing friendly fraud will claim unauthorized transaction or item not received because those codes are easy to file. Your response is to the code, not to what you know the customer actually did.
Visa Chargeback Reason Codes
Visa reorganized its reason code system into numbered categories in 2018. The categories most merchants encounter:
10.4 — Other Fraud: Card Absent Environment. This is the most common chargeback reason code for ecommerce merchants. The cardholder claims they did not authorize an online, phone, or mail order transaction. The key word is "card absent" — the card was not physically present at the point of sale.
To fight a 10.4 chargeback, your evidence must establish that the legitimate cardholder made the purchase. The strongest evidence: AVS match result (billing address matched), CVV match result, IP address of the transaction matching the cardholder's known location, device fingerprint, the order confirmation email delivered to and opened from the cardholder's verified email address, and prior undisputed transaction history from the same card. Visa's Compelling Evidence 3.0 framework specifically allows prior undisputed transaction history to be used as representment evidence for this code.
13.1 — Merchandise / Services Not Received. The cardholder claims they never received what they paid for. For physical goods, your response requires carrier tracking confirmation showing delivery to the billing or shipping address on file. A signature confirmation is stronger than a delivery scan alone. For digital goods, server logs showing the download, login, content access, or license activation after the purchase are your primary evidence.
13.2 — Cancelled Recurring Transaction. The cardholder claims they cancelled a subscription but were billed again. To dispute this, you need to show either that no valid cancellation was received before the billing date or that the cancellation occurred outside the terms the customer agreed to at signup. Your evidence: the terms of service and cancellation policy the customer accepted at signup (with the specific clause governing billing cutoff timing), communication logs showing no cancellation request was received, and ideally the login or activity records showing the account was still active at the time of the charge.
13.3 — Not as Described or Defective Merchandise. The cardholder claims the product or service materially differed from what was advertised or arrived damaged. Your response needs to show that what was delivered matched the description. Evidence: screenshots of the product listing at time of purchase, product specifications, shipping records showing the item left in good condition, and any customer communication prior to the dispute that didn't raise concerns about the product's condition or accuracy.
13.6 — Credit Not Processed. The cardholder claims a refund was promised but never issued. If you did process a refund, your response is simply the refund confirmation and processing record. If you didn't issue a refund because the customer wasn't entitled to one, your evidence is the refund policy they agreed to and documentation that the return or refund conditions weren't met.
13.7 — Cancelled Merchandise / Services. Similar to 13.2 but applies to one-time purchases rather than recurring billing. The cardholder claims they cancelled an order before fulfillment or returned goods but were still charged. Evidence of shipment before the cancellation request, or documentation that the return wasn't received in the condition required by your policy, is your response.
Mastercard Chargeback Reason Codes
Mastercard uses a four-digit code system. The codes most frequently seen by ecommerce and high-risk merchants:
4853 — Cardholder Dispute. Mastercard's 4853 is a broad category covering several dispute types including not as described, cancelled recurring transaction, and services not rendered. The specific sub-reason matters. Read the chargeback notification carefully to identify which sub-type was filed, as it determines what evidence you need.
For not as described: match your product description to what was delivered. For cancelled recurring: same approach as Visa 13.2 above. For services not rendered: documentation that the service was performed as agreed — signed service agreements, appointment confirmations, completion records.
4855 — Goods or Services Not Provided. The cardholder claims they didn't receive what they purchased. Equivalent to Visa 13.1. Carrier tracking for physical goods, access logs for digital goods, and service delivery documentation for service businesses.
4863 — Cardholder Does Not Recognize. The cardholder claims they don't recognize the transaction. This is often a precursor to a full unauthorized claim and can stem from an unrecognizable billing descriptor rather than actual fraud. Your evidence establishes that the legitimate cardholder made the purchase — same data as the Visa 10.4 response above.
4837 — No Cardholder Authorization. The cardholder claims no authorization was given. The strongest defense is 3D Secure authentication: if the transaction was authenticated through 3DS (Verified by Visa / Mastercard Identity Check), the liability for unauthorized transaction chargebacks shifts to the issuing bank. Without 3DS, your evidence is the same transaction data and prior history used for Visa 10.4 disputes. Note that 3DS liability shift only applies when both your processor and your payment gateway support 3DS for that specific processor connection.
4841 — Cancelled Recurring or Digital Goods Transactions. The cardholder claims a recurring charge was billed after cancellation, or that digital goods were cancelled but still charged. Response mirrors Visa 13.2: cancellation policy terms, no-cancellation-received documentation, account activity records.
4850 — Installment Billing Dispute. Applies to installment payment plans where the cardholder disputes one or more installments. Your response ties the specific installment to the signed installment agreement and documents the payment schedule the cardholder agreed to.
Reason Codes That Signal Friendly Fraud
Certain reason codes are disproportionately used for friendly fraud compared to legitimate disputes. 10.4 (Visa) and 4837 (Mastercard) top the list — "I didn't authorize this" is the easiest claim for a customer to make and the hardest for an issuer to disprove without merchant evidence. 13.1 and 4855 (item not received) are heavily used for digital goods where delivery is invisible on the customer's side.
When you see these codes, approach the representment with the assumption that the transaction was legitimate and build your evidence to prove it. Our guide on how to write a chargeback rebuttal letter walks through structuring your response for maximum effectiveness.
Tracking Your Reason Code Distribution
The reason codes appearing most frequently in your chargeback data are a diagnostic tool. A high concentration of 10.4 or 4837 chargebacks (unauthorized) suggests either true fraud (address your fraud screening) or friendly fraud (address your authorization evidence collection and 3DS deployment). A high concentration of 13.2 or 4841 (cancelled recurring) points to subscription management issues: billing descriptor clarity, pre-charge reminders, or cancellation process friction.
Understanding your reason code distribution lets you target your prevention resources where they'll have the most impact, rather than applying generic chargeback reduction advice to a specific problem. CyoGate's chargeback prevention services include monitoring tools that track your dispute patterns over time.
If chargebacks are threatening your processing relationship, or if you need a merchant account with built-in fraud prevention and chargeback management tools, apply with CyoGate and describe your current situation.