Quick answer
Chargeback reason codes tell you why a dispute was filed — but the code does not decide whether you win. Your evidence has to match what that specific code requires. Most merchants lose representments not because they are guilty but because they submitted the wrong type of proof.
Why reason codes matter for high-risk merchants
Every chargeback arrives with a reason code. That code controls the evidence requirements, the time limits for response, and whether a representment is even worth filing. High-risk merchants often receive the same reason codes repeatedly — which means a pattern in your codes is a map to the root cause of your dispute problem.
Visa and Mastercard use different code systems. Amex and Discover run their own dispute programs. Most high-risk merchants deal primarily with Visa and Mastercard, so this guide covers both in depth.
Visa chargeback reason codes (2026)
Visa uses a numerical code system under four dispute condition categories: Fraud (10.x), Authorization (11.x), Processing Errors (12.x), and Consumer Disputes (13.x). The most common codes for high-risk merchants fall in 10.4 and 13.x.
Defense: Show EMV chip authorization or 3DS authentication data.
Defense: Provide AVS match, CVV result, IP, device fingerprint, and shipping address confirmation.
Defense: Not directly disputable — reduce fraud at the source.
Defense: Show authorization approval code; dispute if authorization was granted.
Defense: Show batch settlement was within the allowed window.
Defense: Prove the two charges are separate transactions with separate order IDs and delivery.
Defense: Provide delivery confirmation, tracking, signed receipt, or digital access logs.
Defense: Provide the cancellation policy, confirmation that no cancellation request was received, or proof the product was delivered after cancellation.
Defense: Provide product photos, description accuracy evidence, return policy, and any refusal to return.
Defense: Provide the original offer terms, checkout screenshots, and any prior customer communications.
Defense: Provide proof the refund was issued and the expected processing timeline.
Defense: Provide cancellation policy, proof service was not cancelled per terms, or evidence of product delivery before cancellation.
Mastercard chargeback reason codes (2026)
Mastercard uses 4-digit codes. The most common in high-risk categories are 4853 (not as described), 4855 (non-receipt), and 4837 (no authorization). Code 4863 is especially common among merchants with unclear billing descriptors.
Defense: Provide AVS, CVV, 3DS result, device data, IP, and signed agreement if available.
Defense: Show all transactions are separate orders with distinct delivery.
Defense: Provide product description accuracy, return policy, and refusal to return.
Defense: Provide all order, delivery, and communication records.
Defense: Provide tracking, delivery confirmation, or digital access proof.
Defense: Provide service delivery documentation, login records, or appointment confirmation.
Defense: Provide refund transaction ID and timeline evidence.
Defense: Provide descriptor match, receipt, IP geolocation, and device data.
Defense: Show EMV chip authorization was processed.
Defense: Jurisdiction-specific — follow acquirer guidance and provide full order records.
How to use reason codes to find root causes
If 40% of your disputes are 10.4 (card-absent fraud), your fraud screening is the problem — not your customer service. If 13.3 (not as described) is dominant, your product descriptions, photos, or offer clarity need fixing. If 4863 (not recognized) is frequent, your billing descriptor is the culprit.
Track your reason code distribution monthly. Look for shifts after campaigns, product launches, or fulfillment partner changes. A reason code spike is a business signal, not just a payment problem.
For more on building a full prevention system, see our chargeback prevention playbook. For how to fight the ones worth disputing, see the representment guide.
Time limits by network
Visa dispute response windows are typically 30 days from the chargeback date. Mastercard varies by reason code but is often 45 days. Missing the window means automatic loss regardless of your evidence. Build a dispute queue workflow that flags approaching deadlines.
Where HighRiskIntel fits
HighRiskIntel surfaces your dispute reason code distribution alongside chargeback ratio, refund rate, and authorization health. When a code pattern spikes, the platform flags it so your team can act before the ratio triggers processor concern. If you want to understand your current code exposure, start with the free risk audit.