Visa Chargeback Reason Codes (2026 Guide for Merchants)

A Visa chargeback reason code identifies why the issuing bank disputed a payment. Start with the exact code on your processor’s notice. Then check the evidence it allows and the response deadline.

If what a chargeback is is still new to you, start there for the underlying mechanics, then come back here for Visa's specific codes.

Visa restructured its taxonomy in April 2018 under Visa Claims Resolution, consolidating a longer legacy list into four categories. In April 2024 it retired reason code 12.1 and folded late presentment into 11.3. The October 2026 Visa Core Rules then closed 11.1 to new disputes. All three updates are reflected in the tables below.

Reason codes were built to track payment issues, not to reveal intent. A code like 10.4 (Other Fraud, Card-Absent Environment) reads the same in two cases. The card may have been stolen, or the cardholder may be disputing a purchase they made and regret. The second pattern is known as friendly fraud.

That is why the evidence a merchant needs to win depends far more on the underlying story than on the code number itself. For the codes merchants see most often, start with the most common chargeback reason codes.

{{cta}}

Visa Chargeback Reason Codes: Current and Historical Reference

Use this table to identify the dispute condition and records to review. Evidence examples are starting points, not a complete response checklist or a guarantee of winning. For examples across other networks, see our overview of chargeback reason codes.

October 2026 status: Visa’s published rules limit condition 11.1 to disputes processed through October 23, 2026. It remains below for historical cases. Condition 12.1 is also historical. Late presentment moved to 11.3 for transactions completed on or after April 13, 2024. Source: Visa Core Rules, 24 October 2026 edition, section 11.9.

Cardholders generally have up to 120 days to file a dispute, counted from the transaction or expected delivery date. Authorization codes and 12.7 get 75 days, and select consumer codes can stretch to a 540-day maximum. Under Visa's rules, the acquirer gets 30 calendar days at each response stage. Your processor usually sets a shorter internal deadline.

Track every network's dates in one place with our chargeback calendar. For the full breakdown of fees and time limits by phase, see our guide to Visa chargeback dispute rules, fees, and time limits.

Visa Chargeback Rules: Time Limits by Reason Code

Each Visa reason code carries its own filing window. This is the time the issuer has to raise the dispute, counted from the transaction processing date unless noted. The figures below come from the 24 October 2026 edition of the Visa Core Rules.

The merchant side runs on a separate clock. Visa splits disputes into two workflows, and each stage gives the acquirer 30 calendar days:

1. Allocation (codes 10.x and 11.x). The issuer files and the dispute is settled on submission. There is no first response; the merchant challenges it through a pre-arbitration attempt within 30 days.
2. Collaboration (codes 12.x and 13.x). The merchant submits a dispute response within 30 days of the dispute processing date, often called chargeback representment.
3. Pre-arbitration. The other side has 30 days to accept or reject the pre-arbitration attempt.
4. Arbitration. Either side can file with Visa within 10 days of the pre-arbitration response.

Visa counts these days from the processing date of the previous step. Your processor needs time to package and send your evidence, so its deadline will usually be several days earlier.

What Changed in the October 2026 Visa Rules

The 24 October 2026 edition of the Visa Core Rules brought four changes merchants should know:

• 11.1 closed to new cases: Card Recovery Bulletin disputes apply only to disputes processed through October 23, 2026.
• 10.4 counts payment credentials: the 35-dispute limit now counts per payment credential. The prior-transaction test now covers the card and any linked credential, such as a token, used at one or more merchants. Prior undisputed transactions must still match on device ID, device fingerprint or IP address, plus another identifier.
• 10.5 updated: the condition, now titled Visa Monitoring Programs, gets updated provisions. Its 120-day window starts on the date of the program report.
• New minimum for Visa Accept: from October 24, 2026, Visa Accept disputes need a transaction or dispute amount of at least USD 25. US domestic transactions and codes 12.5, 12.6 and 13.6 are excluded.

What Changed in 2024: Reason Code 12.1 Was Retired

Visa retired reason code 12.1 (Late Presentment) effective April 13, 2024. Every late-presentment case now falls under reason code 11.3, which Visa labels "No Authorization / Late Presentment."

If your chargeback reports still reference 12.1, or an older guide lists it as a standalone code, that information is out of date. The evidence requirement did not change: a valid authorization and timely settlement still defeat the claim. Only the code number and category did.

Reason Codes 10.1-10.5: Fraud

10.1: EMV Liability Shift, Counterfeit Fraud

Reason code 10.1 applies when a cardholder claims a counterfeit chip card was used at a terminal that was not EMV-compliant. The surest way to avoid it is to keep terminals EMV certified, obtain cardholder verification, and follow best practices on terminal handling.

10.2: EMV Liability Shift, Non-Counterfeit Fraud

Reason code 10.2 covers disputes where a cardholder says someone used their lost or stolen card. To prevent it, run PIN cards on EMV terminals and take an imprint for every in-person sale. Ask for a signature or PIN.

10.3: Other Fraud, Card-Present Environment

Reason code 10.3 applies to fraud-related chargebacks on card-present transactions. Typical causes: the merchant failed to read the chip, skipped a manual imprint on a key-entered sale, or did not mark the sale as card-present. Upgrading terminals and avoiding manual key-entry lets built-in chip protections do their job.

10.4: Other Fraud, Card-Absent Environment

Visa uses reason code 10.4 for transactions the cardholder claims were made without authorization in a card-not-present setting. It covers two very different scenarios: genuine fraud from a stolen card, and friendly fraud, where a buyer disputes a purchase they actually made. This is the single most common e-commerce fraud code.

It is also the only one eligible for Compelling Evidence 3.0, which can shift liability back to the issuer.

Under CE3.0 you submit two prior undisputed transactions, 120 to 365 days old. They must share at least two of four data points with the disputed order: user ID, IP address, shipping address or device fingerprint. One match must be the IP address or device fingerprint.

To limit exposure, get approval on every online and recurring order, whatever the amount. Capture AVS, CVV2 and device data at checkout.

10.5: Visa Monitoring Programs

Reason code 10.5, now titled Visa Monitoring Programs, marks chargebacks the issuer raises when Visa flags a merchant in a monitoring program. It was historically branded the Visa Fraud Monitoring Program (VFMP) and folded since April 2025 into the Visa Acquirer Monitoring Program (VAMP). Cardholders rarely trigger this category directly; issuers act on directives from Visa.

To limit exposure, use authorization holds and get a new approval for add-on charges. Watch your combined fraud and dispute ratio closely.

Evidence merchants need to win representment:

• AVS and CVV2 match confirmation from the original authorization
• EMV chip-read data and terminal certification records for card-present fraud (10.1-10.3)
• For 10.4, two prior undisputed transactions meeting the Compelling Evidence 3.0 matching criteria above
• IP address, device fingerprint and proof of delivery that tie the cardholder to the order
• Documented fraud-prevention controls (3-D Secure, velocity limits) if flagged under reason code 10.5 (formerly VFMP, now part of VAMP)

Common merchant mistakes that lose this dispute:

• Skipping AVS and CVV2 checks on card-not-present orders to reduce checkout friction
• Keying in a card-present sale instead of reading the chip, which gives up EMV protection
• Not keeping IP, device and order data long enough to build a Compelling Evidence 3.0 case
• Treating every 10.4 dispute as criminal fraud when a large share are friendly fraud disputes that need a different evidence strategy

Reason Codes 11.1-11.3: Authorization

11.1: Card Recovery Bulletin (Historical)

Visa limited this condition to disputes processed through October 23, 2026, with a 75-day filing window. It covered sales made without approval while the card number was listed on the Card Recovery Bulletin. Retain it for older case records; do not describe it as a current condition for newly processed disputes.

11.2: Declined Authorization

Reason code 11.2 means the merchant received a decline or pickup response but processed the sale anyway. On a decline, end the transaction or request a different payment method, never force a declined card through.

11.3: No Authorization / Late Presentment

Reason code 11.3 now covers two scenarios. The first is a transaction completed with insufficient or no authorization. The second, since April 2024, is a transaction not submitted for settlement within the required processing window, the case formerly handled by reason code 12.1.

Get timely approval on every transaction and ask for another payment method when approval fails. Send completed sales to your processor the same day when possible.

Evidence merchants need to win representment:

• The valid authorization approval code, amount, and timestamp
• Proof the transaction settled within the required processing window
• Proof the settled amount was not more than the approved amount, or that a new approval was obtained
• Records showing the card was not listed on the Card Recovery Bulletin at time of sale

Common merchant mistakes that lose this dispute:

• Forcing a sale through after a decline or pickup response
• Settling for more than the original hold without a new approval
• Letting too much time pass between authorization and batch settlement
• Assuming 12.1 still applies, and pulling the wrong evidence for what is now an 11.3 case

Reason Codes 12.2-12.7: Processing Errors

12.2: Incorrect Transaction Code

Reason code 12.2 applies when a transaction was processed with the wrong transaction code, a sale instead of a credit, for example. Train staff on the difference between sale, credit, and reversal codes, and double-check entries before processing.

12.3: Incorrect Currency

Reason code 12.3 covers currency conversion errors or Dynamic Currency Conversion (DCC) disputes. Say when the local currency differs from the payment currency and show any added fees. Let buyers pay in local currency where you can.

12.4: Incorrect Account Number

Reason code 12.4 covers transactions posted to the wrong account number. Keep terminals up to date and double-check entries to limit human error.

12.5: Incorrect Amount

Reason code 12.5 identifies disputes where the settled amount differs from the authorized amount. Check totals before approval. Never change a completed amount without new consent.

12.6: Duplicate Processing and Paid by Other Means

Reason code 12.6 splits into two sub-conditions. 12.6.1 covers a transaction processed two or more times. 12.6.2 covers a purchase the cardholder paid through another method. Examine receipts before depositing, present batches one at a time, and refund duplicate charges promptly.

12.7: Invalid Data

Reason code 12.7 applies to chargebacks caused by incorrect transaction data, the wrong date, Merchant Category Code, or country or state code. Check transaction data before clearing. Fix faulty hardware or network issues that can corrupt the data sent.

Evidence merchants need to win representment:

• The original receipt and settlement batch record showing the correct code, currency, account number, and amount
• Settlement logs proving a transaction was not submitted twice (12.6.1)
• Proof the cardholder did not already pay through another channel (12.6.2)
• A currency notice or DCC consent screen shown before the sale closed (12.3)
• Records confirming the correct MCC, transaction date, and country or state code (12.7)

Common merchant mistakes that lose this dispute:

• Keying the wrong transaction code (sale instead of credit or reversal)
• Re-running a transaction "just in case" the first attempt failed
• Applying DCC without a documented cardholder opt-in
• Batching and settling late, especially around holidays or system outages

Reason Codes 13.1-13.9: Consumer Disputes

13.1: Merchandise/Services Not Received

Reason code 13.1 covers chargebacks where the customer says merchandise or a service was not delivered by the promised date. To reduce risk, tell buyers about delays and ship with insurance and tracking. Keep a clear refund policy and get proof of delivery.

13.2: Cancelled Recurring Transaction

Reason code 13.2 applies when the cardholder says they were charged for a recurring payment after cancelling. Prevent it with transparent billing, clear subscription terms, easy cancellation, and fraud detection on renewal charges. See our full breakdown of Visa reason code 13.2 for the complete evidence checklist.

13.3: Not as Described or Defective Merchandise/Services

Reason code 13.3 covers disputes where the customer says the merchandise has an undisclosed defect or differs from your description. Check orders before shipping and pack fragile goods with care. Keep product descriptions accurate.

13.4: Counterfeit Merchandise

Reason code 13.4 applies when merchandise is identified as counterfeit. Buy from trusted makers and avoid misleading images. If you are not tied to a brand, say so.

13.5: Misrepresentation

Reason code 13.5 applies when the customer claims you misrepresented a transaction or used false advertising. It is covered in full in our guide to fighting reason code 13.5. Keep product and service descriptions accurate and include photos or video where it helps.

13.6: Credit Not Processed

Reason code 13.6 applies when a customer says you issued a receipt for a void or credit, yet the transaction was never reversed. Make sure the cardholder understands your return policy, process refunds promptly, and confirm issued credits with a reference number.

13.7: Cancelled Merchandise/Services

Reason code 13.7 covers disputes where a cardholder returned merchandise or cancelled a subscription but has not received the matching credit. Show your return and cancellation policy before checkout. Process credits quickly and tell buyers about delays.

13.8: Original Credit Transaction Not Accepted

Reason code 13.8 applies when an Original Credit Transaction, a push payment sent to a card, was not accepted. Either the recipient refused it, or local law prohibits that type of credit. It applies in all Visa regions. Confirm OCTs are permitted in the recipient's country and keep records of the recipient's consent.

13.9: Non-Receipt of Cash at an ATM

Reason code 13.9 is titled Non-Receipt of Cash at an ATM in the current rules. Its former name was Non-Receipt of Cash or Load Transaction Value. It applies when a cardholder says an ATM did not give out the cash. It can also cover a load to a prepaid or gift card that never posted.

Keep ATM dispense logs and load-transaction confirmations on hand. Reconcile terminal cash counts promptly after any reported shortfall.

Evidence merchants need to win representment:

• Tracking and signature-confirmed proof of delivery matching the billing or shipping address (13.1)
• Subscription terms, renewal notice, and cancellation timeline (13.2, 13.7)
• The product description shown at checkout, matched against what was delivered, plus photos (13.3, 13.5)
• Sourcing and authenticity documentation from the manufacturer or authorized distributor (13.4)
• Refund or credit confirmation with date, amount, and reference number (13.6)
• Proof the recipient took the Original Credit Transaction, or that it was allowed (13.8)
• ATM dispense logs or load-transaction confirmation showing the value was delivered (13.9)

Common merchant mistakes that lose this dispute:

• Not saving checkout-page copy, so there is no record of what the buyer agreed to
• Making cancellation difficult enough that customers dispute instead of cancelling directly
• Giving a refund with no reference number the bank can match to the sale
• Ignoring an early alert that could have fixed the issue before a formal chargeback

Legacy Visa Reason Codes and Their Current Equivalents

Older acquirer reports, processor exports and training material still use two-digit Visa reason codes. These existed before Visa Claims Resolution took effect in April 2018. If a notice shows reason code 30, 53, 83, or 85, this table translates it to the dispute condition Visa uses today.

Source: Visa's dispute conditions quick reference as republished in acquirer VCR guides, including TD Merchant Solutions' Visa Claims Resolution FAQ. Legacy codes not listed here were retired without a direct successor. For the current cardholder and merchant time limits attached to each condition, see the time limits table above.

Visa vs. Mastercard Reason Codes: What Changes for Dual-Network Merchants

Merchants who take both networks soon notice that the same complaint gets a different code on each one. The categories map closely, but the numbers do not. A rule built around a Visa code will not automatically catch the Mastercard equivalent.

For the full breakdown of every individual Mastercard code and the evidence each one needs, see our companion guide to Mastercard chargeback reason codes. For first-party fraud defenses on both networks, compare Visa CE3.0 vs Mastercard First-Party Trust. American Express uses letter codes such as F29 and C08 instead; see the Amex chargeback reason codes guide.

Why Reason Code Accuracy Matters More in 2026

Getting the reason code wrong at intake means pulling the wrong evidence. It is one of the most common reasons a winnable dispute is lost. The stakes are rising. Mastercard estimates that chargebacks cost merchants $33.79 billion globally in 2025, and that about 45% of chargeback volume is fraud-related, based on Datos Insights research.

Network monitoring adds more pressure. Under the Visa Acquirer Monitoring Program (VAMP), standard Excessive Merchant criteria changed on April 1, 2026, in Asia Pacific, Canada, Europe and the US:

A merchant must meet both the ratio and the count. The VAMP ratio is the TC40 fraud count plus the TC15 dispute count, divided by settled card-not-present transactions (TC05) in the same month. Reason-code labels alone do not decide the numerator. Some pre-dispute resolutions and qualifying CE3.0 records are excluded, and one payment can appear in both reports.

These standard criteria apply when the acquirer is not itself Above Standard or Excessive. Regional and acquirer rules can differ. Check the Visa fact sheet and your acquirer's notice before assuming fees or enrollment. Staying below the thresholds does not rule out acquirer or processor review.

Compelling Evidence 3.0 has specific eligibility rules for condition 10.4. Matching an IP address or a successful CVV check alone is not enough. See Visa’s CE3.0 merchant guidance and confirm the current permitted submission with your acquirer.

How to Respond to a Visa Chargeback Reason Code

Respond to a Visa reason code in four steps.

Some disputes never need representment at all. With Visa Rapid Dispute Resolution, refund rules you set ahead of time can settle eligible cases before they become a formal chargeback. Most are 13.x consumer-dispute codes.

Fraud codes set a higher evidence bar than consumer disputes, so the fastest win is often prevention.

Stronger checkout-level defenses, the kind covered in our ecommerce fraud prevention guide, keep fewer 10.x disputes from reaching representment. A chargeback alert service can flag a dispute while it is still a bank inquiry. That gives you a window to refund or step in before Visa's formal chargeback clock starts.

One new problem for 2026 is purchases made by an AI shopping agent instead of the cardholder. Visa's reason codes were not written for that case. Merchants already ask how AI agent chargeback liability will work when an agent buys with a stored card and the cardholder never clicked "buy."

{{cta}}

Visa Chargeback Reason Codes FAQ

What is a chargeback reason code?

A chargeback reason code is the number a card network assigns to a dispute to show why the cardholder's bank reversed the payment. Visa uses numeric codes such as 10.4 or 13.1, grouped into fraud, authorization, processing errors and consumer disputes. The code tells the merchant which evidence can defend the transaction.

How many Visa chargeback reason codes are there?

Visa groups dispute conditions into fraud, authorization, processing errors and consumer disputes. Counts depend on the date and on whether 12.6 sub-codes count separately. This reference marks historical conditions explicitly: 12.1 is retired, and Visa limited 11.1 to disputes processed through October 23, 2026. That leaves 23 conditions for new Visa disputes when 12.6.1 and 12.6.2 count separately.

What happened to Visa reason code 12.1?

Visa retired reason code 12.1 (Late Presentment) effective April 13, 2024. Every case that would have been coded 12.1 now falls under reason code 11.3. Visa relabeled it "No Authorization / Late Presentment." The evidence needed to win did not change; only the code number did.

How long do merchants have to respond to a Visa dispute?

Under the Visa Core Rules, the acquirer has 30 calendar days from the dispute processing date to respond to a 12.x or 13.x dispute. It has the same 30 days to file pre-arbitration on a 10.x or 11.x dispute. Use the due date on your processor’s case notice, which is usually earlier.

Processor deadlines vary. For example, Stripe’s response guidance describes a usual merchant window of 7 to 21 days, depending on the card network. The cardholder’s filing window is a different clock.

Which Visa reason code covers friendly fraud?

Most friendly fraud surfaces under Visa reason code 10.4 (Other Fraud, Card-Absent Environment), which is the only Visa code eligible for Compelling Evidence 3.0. Some friendly fraud also appears as 13.1 or 13.3, when a buyer claims an item never arrived or was not as described.

What does Visa chargeback reason code 10.4 mean?

Visa chargeback reason code 10.4 means the cardholder says they did not authorize a card-not-present purchase, such as an online or phone order. It covers both true fraud with stolen card details and friendly fraud. The issuer has 120 days from the transaction processing date to file it.

What does Visa chargeback reason code 13.7 mean?

Visa chargeback reason code 13.7 (Cancelled Merchandise/Services) means the cardholder says they returned an item or cancelled a service but never got the promised credit. To defend it, show your cancellation or return policy as disclosed at checkout and proof that a credit was issued or was not owed.

What is Visa Compelling Evidence 3.0?

Compelling Evidence 3.0 lets a merchant defend a Visa 10.4 dispute with two prior undisputed transactions from the same cardholder, 120 to 365 days old. Each must share at least two of four data points with the disputed order: user ID, IP address, shipping address or device fingerprint. At least one match must be the IP address or device fingerprint.

What is Visa reason code 13.9?

Visa reason code 13.9, now titled Non-Receipt of Cash at an ATM, covers disputes where a cardholder says an ATM did not dispense the cash. Older rules also covered a load transaction, money added to a prepaid or gift card, that never posted the expected value.

Match the Code, Pull the Evidence, Win the Dispute

Chargeback resolution comes down to three steps. Find the right code, pull the evidence it asks for, and submit before the deadline. Use this guide as your quick reference. Pair it with our companion list of Mastercard chargeback reason codes if you process both networks.

Chargeflow Automation handles evidence gathering and submission across every reason code, with a 100% submission rate, and you pay only if we win. Contact our team to recover Visa chargebacks on autopilot.