
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
Visa chargeback reason codes are the alphanumeric identifiers (like 10.4 or 13.1) that tell you exactly why a cardholder disputed a transaction. Visa sorts them into four categories — Fraud, Authorization, Processing Errors, and Consumer Disputes — and each code carries its own evidence requirements and response deadlines. Get the code right and you respond with the right evidence; get it wrong and you forfeit the dispute.
This 2026 guide breaks down every active Visa reason code, the time limits attached to each, and how to prevent and fight them. For deadlines and fees in depth, see our Visa Chargeback Dispute Playbook; to keep your dispute volume from triggering enrollment penalties, review the latest Visa VAMP rules.
| Code | Category | What It Means | Merchant Response Window |
|---|---|---|---|
| 10.1 | Fraud | EMV liability shift — counterfeit fraud | 30 days |
| 10.2 | Fraud | EMV liability shift — non-counterfeit fraud | 30 days |
| 10.3 | Fraud | Other fraud — card-present | 30 days |
| 10.4 | Fraud | Other fraud — card-absent (CE 3.0 eligible) | 30 days |
| 10.5 | Fraud | Visa Fraud Monitoring Program | 30 days |
| 11.1 | Authorization | Card recovery bulletin | 30 days |
| 11.2 | Authorization | Declined authorization | 30 days |
| 11.3 | Authorization | No authorization | 30 days |
| 12.1–12.7 | Processing Errors | Late presentment, incorrect amount/currency/account, duplicate, invalid data | 30 days |
| 13.1–13.8 | Consumer Disputes | Goods not received, cancelled recurring, not as described, credit not processed | 30 days |
Cardholders generally have up to 120 days from the transaction or expected delivery date to file a dispute, with a maximum of 540 days for select reason codes. Merchants receive a uniform 30-day window to respond at each phase of the dispute.
A Visa chargeback reason code is a set of numbers and letters that financial institutions use to specify the cause of a payment dispute on a Visa card. They standardize the dispute process. When a customer disputes a charge on their Visa card, banks rely on Visa reason codes to decide whether to initiate a chargeback.
Reason codes also help merchants, card networks, and banks track and analyze chargeback trends to make better decisions. Categorizing disputes into specific codes gives card networks better oversight of chargeback incidents, so they can proactively adjust risk models and protect the integrity of the global payments ecosystem.
Chargeback reason codes are designed to foster transparency in chargeback processing. Unfortunately, there are no uniform reason codes across the networks — each card brand has its own. Even though the principal function is to track and communicate the reason for disputes, such disjointed numerics often cause significant confusion for merchants.
Furthermore, reason codes don't always reveal the cardholder's true intent. A bank may issue a Transaction Unauthorized chargeback when, in reality, the cardholder's family member made the purchase and the cardholder is using a chargeback to avoid paying for it. According to Mastercard: “When a friendly-fraud dispute is coded as genuine fraud, it can lead to an uptick in false declines—where cards are denied due to suspected fraud, even though they shouldn't be.”
Until there's a better system to fix the inefficiencies, you can't ignore the current codes. Let's explore the Visa chargeback reason codes and how to use them to reduce risk and respond effectively.
Visa revamped its chargeback reason codes in April 2018, consolidating them into four categories: fraud, authorization errors, processing errors, and customer disputes. The structure below remains current in 2026.
Visa chargeback reason code 14.1 speaks to multiple unauthorized transactions, often resulting from fraudulent activities or unintended double billing. Merchant errors that could lead to double billing include a checkout glitch delaying confirmation of a successful transaction; the customer's subsequent attempts often lead to double billing for the same order.
To avoid it, do not force authorization on failed transactions, break down high payment volumes when required by your acquirer, and use distinct identifiers for multiple transactions of the same value.
Visa chargeback reason code 10.5 identifies chargebacks initiated by the card issuer for merchants enrolled in the Visa Fraud Monitoring Program (VFMP). Cardholders rarely initiate this category — issuers receive directives from Visa to file these cases. Limit exposure with authorization holds, request a separate authorization for additional payments, and keep an eye on your fraud-to-transaction ratio.
Visa uses reason code 10.4 for transactions the cardholder claims were performed without authorization in a card-not-present environment. It stems from two culprits: true fraud (stolen cards) and friendly fraud (a buyer disputing valid charges as unauthorized). This is the single most common e-commerce fraud code — and the only one eligible for Compelling Evidence 3.0, which lets you prove a prior history of undisputed transactions to shift liability back to the issuer.
Limit exposure by requesting authorization for all recurring billing and card-absent orders regardless of dollar value, and by using fraud-prevention tools to close loopholes.
Reason code 10.3 applies to fraud-related chargebacks on card-present transactions where a merchant failed to swipe the card or read the chip, neglected to obtain a manual imprint for a key-entered transaction, or did not adequately mark a transaction as card-present. Upgrade your terminals and ensure in-person transactions are not keyed in manually so built-in protections like chip and stripe reading can work.
Reason code 10.2 represents disputes where a cardholder claims someone used their lost or stolen card for an unauthorized transaction. To prevent it, process PIN-preferring cards with EMV terminals, obtain an imprint for every card-present transaction, and require cardholder validation with signature or PIN.
Reason code 10.1 pertains to disputes where the cardholder claims a counterfeit chip card was used at a non-EMV-compliant terminal. The surest way to avoid 10.1 disputes is to ensure your terminals are EMV compliant, obtain cardholder verification, and follow best practices on terminal handling.
Reason code 11.3 involves transactions completed with insufficient or no authorization. Ensure transactions receive timely approval, request alternate payment methods for failed approvals, and process only the authorized amount.
Reason code 11.2 indicates the merchant received a Decline or Pickup response but processed the transaction anyway. If you get a decline, discontinue the transaction or request a different payment method — never force payment on a declined card.
Reason code 12.1 identifies a transaction not presented to Visa within the required time limit. Forward completed transactions to your processor within the timeframe in your merchant agreement — ideally the day of the sale.
Reason code 12.2 applies to processing a transaction with an incorrect transaction code (e.g., a sale instead of a credit). Train staff on processing credit, debit, and reversal transactions, and double-check entries before processing.
Reason code 12.3 applies to currency conversion errors or Dynamic Currency Conversion (DCC) disputes. Let customers know when local currency differs from payment currency, disclose any additional fees, and allow payment in local currency when applicable.
Reason code 12.4 covers transactions posted to an incorrect account number. Upgrade your Visa-approved terminal, process adjustments quickly, and double-check entries before processing to limit human error.
Reason code 12.5 identifies disputes where the transaction amount differs from the authorization amount. Review entries and totals before authorization, train staff on proper procedures, and refrain from altering completed transaction amounts.
Reason code 12.6 covers a transaction processed two or more times (12.6.1 for double processing; 12.6.2 for transactions charged through other means). Examine receipts before depositing, present batches one at a time, and issue refunds promptly for double billing.
Reason code 12.7 applies to chargebacks caused by incorrect transaction data — wrong date, Merchant Category Code, transaction type, or country/state code. Review all transaction data before clearing, and address faulty hardware or network glitches that can corrupt transmitted data.
Reason code 13.1 represents chargebacks where the customer claims merchandise or service was not delivered on the promised date. Mitigate risk by notifying cardholders of delays, shipping with insurance and tracking, maintaining a clear refund policy, and requesting proof of delivery.
Reason code 13.2 applies when the cardholder claims they were charged for a recurring billing after cancelling. Prevent it with transparent billing practices, clear subscription terms, easy cancellation, and robust fraud detection.
Reason code 13.3 covers disputes where the customer claims the merchandise has an undisclosed defect or differs from your description. Review orders before shipping, package fragile goods carefully, and keep product descriptions accurate.
Reason code 13.4 pertains to disputes where the merchandise is identified as counterfeit. Source from reputable manufacturers, avoid misleading descriptions or images, and explicitly disclose non-affiliation with brands when relevant.
Reason code 13.5 applies when the customer claims you misrepresented a transaction or used false advertising. Ensure accurate, precise product/service descriptions and include photos or videos for illustration when possible.
Reason code 13.6 applies when a customer says you issued a receipt for a void or credit, yet the transaction remains unprocessed. Ensure the cardholder understands your return policy, process refunds promptly, and confirm issued credits.
Reason code 13.7 identifies disputes where a cardholder returned merchandise or cancelled a subscription but hasn't received the corresponding credit. Outline your return/cancellation policy before checkout, process credits quickly, and communicate delays.
Reason code 13.8 is a shorthand for disputes where the cardholder claims you did not process a voided transaction; it applies to merchants in Europe and inter-regional territories. Familiarize yourself with the laws governing original credit transactions in your jurisdiction and maintain accurate records.
Identify the reason code, gather the specific compelling evidence Visa requires for that code, and submit your representment within the 30-day window. For card-absent fraud (10.4), Compelling Evidence 3.0 lets you submit proof of two prior undisputed transactions sharing matching data points to shift liability to the issuer. Missing the deadline forfeits the dispute automatically — and adds a non-response fee.
Visa groups its reason codes into four categories — Fraud (10.x), Authorization (11.x), Processing Errors (12.x), and Consumer Disputes (13.x) — covering roughly two dozen active codes since the April 2018 restructure.
Merchants get a uniform 30 days to respond at each phase of a Visa dispute, beginning the day after Visa initiates the phase.
Most friendly fraud surfaces under reason code 10.4 (Other Fraud — Card-Absent Environment), which is eligible for Compelling Evidence 3.0.
Chargeback resolution requires mastery of the reason codes, the evidence each one demands, and the representment process. Use this guide as your quick reference, and get full background on each code in our reason-code database. A companion guide covers the full list of Mastercard chargeback reason codes.
Chargeflow automates evidence gathering and submission across every reason code, with a 100% submission rate and pay-only-if-we-win pricing. Start for free or contact our team to recover chargebacks on autopilot.

Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.