Chargeback reason codes
that actually matter,
ranked by category

A chargeback notification rarely explains itself. It shows up in a portal or a merchant-statement line item as a dollar amount, a description like "Fraud - Card Absent," and a short alphanumeric code -- and that code, not the merchant's read of what actually happened, is what decides which evidence a bank will accept in representment. Fight a fraud-coded dispute with a return policy and it goes nowhere; fight a fulfillment dispute with an AVS match and it goes nowhere just as fast. Understanding how the two major networks actually organize their codes -- and which categories show up most in card-not-present retail -- is the difference between a representment packet that has a real shot and one that's dead on arrival. This is the natural next layer on top of what we've covered on chargebacks as a hidden tax and the two liability-shift frameworks in the EMV shift and 3-D Secure.

Visa Claims Resolution: the four-category framework

Visa replaced its old, longer list of numeric reason codes in April 2018 with Visa Claims Resolution (VCR), a framework built around four dispute categories instead of dozens of loosely related codes. According to Visa's own published dispute-conditions guidance and the network's chargeback-management partners, the four VCR categories are Fraud, Authorization, Processing Errors, and Consumer Disputes, and each carries a set of numbered "dispute conditions" rather than the old flat reason-code list. Codes beginning with 10 are Fraud, 11 are Authorization, 12 are Processing Errors, and 13 are Consumer Disputes -- a numbering convention that's held steady since the 2018 rollout and is still Visa's live framework as of 2026.

VCR also changed how disputes move, not just how they're labeled. Fraud and Authorization disputes run through what Visa calls an "allocation" workflow, where Visa's system pulls funds and assigns liability more automatically based on rule-based criteria before the merchant ever responds. Processing Errors and Consumer Disputes run through a "collaboration" workflow, closer to the traditional back-and-forth representment process, where the merchant has a real opportunity to submit compelling evidence before liability is finalized. That distinction matters operationally: a fraud dispute often needs a fast, narrow rebuttal (proof of authentication) because the allocation clock moves quickly, while a consumer dispute has more room for a documentation-heavy response.

VCR category	Code prefix	Workflow	What it's actually disputing
Fraud	10.1 – 10.5	Allocation	The card or account itself was compromised, or the transaction wasn't authorized by the legitimate cardholder
Authorization	11.1 – 11.3	Allocation	The transaction was processed without a valid authorization, or after a decline
Processing Errors	12.1 – 12.7	Collaboration	A technical mistake in how the transaction was processed -- duplicate charge, wrong amount, wrong currency, late presentment
Consumer Disputes	13.1 – 13.9	Collaboration	The cardholder disputes the underlying purchase itself -- goods not received, not as described, credit not issued, cancelled service still billed

Mastercard's parallel system: fewer, broader codes

Mastercard runs its own four-digit reason-code system, structured differently from Visa's category-and-condition model. Mastercard began simplifying and consolidating its codes starting around 2016, folding a longer list of narrow, overlapping codes into a smaller set of broader ones. The three codes that show up most often in merchant-facing chargeback tooling and vendor documentation are:

• 4837 -- No Cardholder Authorization: the cardholder states they didn't authorize, approve, or participate in the transaction. This is Mastercard's core fraud code and functions similarly to Visa's 10.x series.
• 4853 -- Cardholder Dispute: a broad, catch-all non-fraud category covering recurring billing disputes, goods or services not as described, non-receipt, and credits that were promised but never posted. Mastercard's 4853 maps loosely onto several of Visa's individual 13.x consumer-dispute conditions rolled into one code.
• 4863 -- Cardholder Does Not Recognize -- Potential Fraud: the cardholder sees an unfamiliar transaction on their statement and suspects fraud, distinct from 4837 in that the cardholder isn't flatly denying authorization -- they're flagging something they don't recognize, which sometimes resolves without ever becoming a true fraud claim once the merchant's descriptor is clarified.

Because 4853 is so broad, it's common for a Mastercard merchant to see far more disputes land under that single code than under any individual Visa 13.x condition -- not necessarily because Mastercard cardholders dispute more, but because Mastercard's simplified taxonomy doesn't split "goods not received" from "not as described" from "credit not processed" the way Visa's numbered conditions do.

The code is the argument you're allowed to make. Send authentication evidence to a fulfillment dispute, or a shipping receipt to a fraud claim, and the bank isn't confused -- it just discards evidence that doesn't answer the actual question the code is asking.

Which categories actually hit card-not-present retail hardest

Visa and Mastercard don't publish a public, code-by-code frequency table, so any specific percentage claiming "X% of chargebacks are code Y" should be treated skeptically unless it's tied to a named, sourced study. What's consistently and credibly described across chargeback-management vendors -- Chargebacks911, Kount, Sift, and others who process large volumes of disputes across many merchants -- is a qualitative ranking that holds up across sources:

1. Fraud-category codes (Visa 10.4, Mastercard 4837/4863) are described as the highest-volume category in card-not-present retail and e-commerce specifically. Visa's 10.4 (Other Fraud: Card-Absent Environment) is repeatedly cited as the single most common individual code in online selling. A meaningful share of what lands under these fraud codes is "friendly fraud" -- a cardholder disputing a transaction they or an authorized user actually made -- rather than true stolen-card fraud; industry sources estimate friendly fraud makes up a substantial majority of fraud-coded disputes, though exact figures vary by vendor and merchant category and should be verified against your own processor's dispute data rather than assumed.
2. Consumer Disputes (Visa 13.x, Mastercard 4853) run a close second in retail and e-commerce, led by "merchandise/services not received" (13.1) and "not as described" (13.3) -- the two conditions that map most directly onto ordinary shipping delays, damaged goods, and buyer's remorse dressed up as a dispute.
3. Processing Errors (Visa 12.x) show up less often but are the category most within a merchant's direct control to prevent -- duplicate charges, incorrect amounts, and late presentment are operational mistakes, not customer behavior, and are usually the easiest disputes to win outright since the transaction record itself proves or disproves the claim.
4. Authorization disputes (Visa 11.x) are the least common in most retail verticals, typically appearing when a transaction was processed after a decline or without a valid authorization response, which points to a gateway or terminal configuration issue rather than customer intent.

The pattern is consistent with the broader card-not-present risk profile we cover in e-commerce's true blended rate: online and phone transactions lack the physical card presence and PIN or signature capture that make card-present fraud comparatively rare, so both true fraud and the friendly-fraud variant of fraud-coded disputes concentrate disproportionately in CNP channels.

What to actually do about each category

The right response -- and the right prevention investment -- differs by category. Treating every dispute the same way, or fighting every one regardless of category, wastes representment fees on disputes that were never winnable and misses easy wins on the ones that are.

• Fraud (Visa 10.x, Mastercard 4837/4863): Representment needs proof of authentication and legitimate purchase intent -- AVS and CVV match results, 3-D Secure authentication data if used, device fingerprinting, IP-to-billing-address consistency, and order history showing the same customer made prior undisputed purchases. Prevention is the higher-leverage move here: strong AVS/CVV enforcement, 3-D Secure on higher-risk orders (with its own liability-shift tradeoff, covered in 3-D Secure: liability shift vs conversion cost), and velocity checks that flag unusual order patterns before they ship.
• Authorization (Visa 11.x): Usually a technical/process fix rather than a fight -- audit your gateway's handling of declined and expired authorizations, and confirm your POS or e-commerce platform isn't capturing transactions after an authorization has lapsed or failed.
• Processing Errors (Visa 12.x): These are often winnable outright with clean transaction records -- proof of the correct amount charged, confirmation there was no duplicate submission, and timestamps showing presentment within the required window. Prevention means tightening batch and settlement processes, not customer-facing changes.
• Consumer Disputes (Visa 13.x, Mastercard 4853): Representment needs proof of fulfillment and disclosure -- tracking numbers with delivery confirmation, itemized product descriptions matching what was advertised, signed service agreements, and a clearly disclosed cancellation/refund policy the customer agreed to at purchase. Prevention leans on clear product photography and descriptions, proactive shipping-delay communication, and a visible, easy-to-use refund process that gives a customer a reason to contact you before they contact their bank.

Why the code matters more than the customer's story

A cardholder calling their bank to dispute a charge doesn't select a reason code -- the bank's representative assigns one based on the cardholder's stated reason, and that assignment is sometimes imprecise. A customer who says "I never got this" might get coded 13.1 even if the real issue was a late delivery that arrived the next day, and a customer who says "I don't recognize this charge" might get coded as fraud (10.4 or 4863) even when they simply forgot making the purchase or didn't recognize the billing descriptor. This is part of why billing-descriptor clarity is one of the cheapest chargeback-prevention levers available: a descriptor that clearly matches the merchant name customers actually recognize reduces the volume of "I don't recognize this" disputes that get coded as fraud before anyone confirms whether fraud actually occurred.

Whatever code arrives, the practical first move is the same: read the code before drafting a response, confirm which VCR category or Mastercard code family it belongs to, and pull the evidence type that category is actually asking for -- not the evidence that feels most persuasive to a human reading the case.

Frequently asked questions

What is Visa Claims Resolution (VCR)?

Visa Claims Resolution is the dispute-handling framework Visa introduced in April 2018, replacing the network's old numeric reason-code system with four dispute categories -- Fraud, Authorization, Processing Errors, and Consumer Disputes -- each with its own set of dispute conditions (like 10.4 or 13.1) and its own resolution workflow. VCR is still Visa's current framework as of 2026; it hasn't been replaced, though individual dispute conditions and timelines have been refined since 2018.

Which Visa chargeback reason code is most common in card-not-present retail?

Reason code 10.4 (Other Fraud: Card-Absent Environment) is widely cited by chargeback-management vendors as the single most common code in online and phone-order retail, because it captures both true stolen-card fraud and "friendly fraud" -- a cardholder disputing a charge they actually made. Reason code 13.1 (Merchandise/Services Not Received) is the next most cited in card-not-present retail specifically.

What are Mastercard's main chargeback reason codes?

Mastercard's most-cited codes are 4837 (No Cardholder Authorization, its core fraud code), 4853 (Cardholder Dispute, a broad category covering not-as-described goods, non-receipt, and unprocessed credits), and 4863 (Cardholder Does Not Recognize -- Potential Fraud). Mastercard simplified and consolidated its reason-code set starting in 2016, folding many older, narrower codes into these broader categories.

Can a merchant fight a fraud-category chargeback the same way as a service chargeback?

No. Fraud-category disputes (Visa 10.x, Mastercard 4837/4863) usually require proof the transaction itself was authenticated and legitimate -- AVS/CVV matches, 3-D Secure results, device and shipping-address history. Processing-error and consumer-dispute categories (Visa 12.x/13.x, Mastercard 4853 and its sub-reasons) require proof of the underlying transaction and fulfillment -- receipts, tracking numbers, refund policies the customer agreed to, delivery confirmation. Using fraud evidence on a non-fraud dispute, or vice versa, is the most common reason representment packets lose.