Visa Chargebacks in 2026: A Complete Guide for Merchants

‍

Visa processes more card transactions than any other network globally, which means most merchants will encounter Visa disputes more frequently than those from Mastercard, American Express, or Discover. 

However, Visa's dispute ecosystem has undergone substantial changes over the past year, including new monitoring thresholds, updated evidence standards, and a restructured enforcement framework that places more accountability on acquirers and, by extension, the merchants they support.

This guide covers how Visa's dispute process works from start to finish, outlines the current rules, and provides guidance on how merchants can stay ahead of them.

‍

What is a Visa Chargeback?

A Visa chargeback occurs when a cardholder disputes a charge with their issuing bank, and the bank determines the claim has enough merit to reverse the transaction. When that happens, the transaction amount is debited from the merchant's account and temporarily credited back to the cardholder while the dispute is investigated. 

Visa officially refers to chargebacks as "disputes," though both terms are used interchangeably across the industry. Regardless of how a dispute is ultimately resolved, merchants are typically assessed a chargeback fee by their acquiring bank. 

These fees vary depending on the processor agreement and whether the merchant operates in a high-risk vertical, with industries like travel, digital goods, and subscription services tending to face higher fee structures. The fees exist partly as an incentive for merchants to keep dispute volumes low, though they also reflect the administrative cost of processing the dispute through the network.

When a merchant believes a chargeback is invalid, they can challenge it through a process called representment, where the transaction is re-presented to the issuing bank along with evidence supporting its legitimacy. If the issuer accepts the evidence, the chargeback is reversed, and the merchant recovers the funds. If the evidence is rejected, the dispute can escalate further through pre-arbitration and ultimately to Visa arbitration, where Visa makes a binding ruling.

The entire process operates within the Visa Claims Resolution (VCR) framework, which dictates how disputes are routed, reviewed, and resolved depending on the type of claim involved.

Chargeback vs. Dispute: What’s the Difference?

At ChargebackStop, we use the terms “dispute” and “chargeback” to refer to two different parts of the chargeback process:

• Dispute: When a cardholder contacts their bank to initiate a chargeback.
• Chargeback: When the bank reverses the actual payment.

It’s important to separate the two because if a merchant can step in and prevent a dispute from turning into a chargeback, such as by using pre-chargeback tools, their chargeback volumes and ratios are unaffected. 

‍

How the Visa Claims Resolution Process Works

Visa Claims Resolution is the framework Visa uses to standardize how disputes flow through the system. Rather than running every dispute through the same manual review process, VCR routes cases through one of two distinct workflows based on the dispute category.

Allocation vs. Collaboration Workflows

The allocation workflow handles fraud disputes (Category 10) and authorization disputes (Category 11). In this workflow, liability is assigned automatically based on Visa's rules. If a merchant didn't use 3D Secure for a card-not-present transaction, for example, or if an available EMV chip wasn't used for an in-person transaction, liability falls on the merchant without a manual evidence review. The merchant can still challenge the outcome through pre-arbitration, but the initial decision is rules-based and automated.

The collaboration workflow handles processing error disputes (Category 12) and consumer disputes (Category 13). These go through a more traditional evidence-based review, where the merchant has the opportunity to submit compelling evidence during representment before a decision is made. This workflow is closer to what most merchants picture when they think about the chargeback process — a back-and-forth between the merchant and the issuing bank, with evidence determining the outcome.

Merchants facing a high volume of fraud disputes routed through the allocation workflow need to focus on authentication and prevention tools rather than relying solely on representment, because the window to present evidence comes later and under less favorable conditions. Collaboration workflow disputes, on the other hand, reward thorough documentation and fast response times.

‍

Visa Dispute Categories and Reason Codes

Visa organizes its disputes into four broad categories, each covering a different type of cardholder claim. Every dispute is assigned a reason code that falls within one of these categories, and the reason code determines what kind of evidence a merchant needs to submit if they want to challenge it.

Category 10: Fraud

This category covers transactions disputed due to unauthorized use. It includes situations where stolen card details were used in either a card-not-present or card-present environment, where an available EMV chip wasn't used for authorization, and transactions flagged by Visa's fraud monitoring programs.

Visa Reason Code 10.4 (Other Fraud — Card Absent Environment) is by far the most common in this category, and one of the most frequently encountered Visa reason codes overall. The cardholder claims they didn't authorize or participate in the transaction. 

While this can result from genuine card theft, it's also one of the primary vectors for friendly fraud, where the cardholder did make the purchase but either doesn't recognize the charge on their statement or is deliberately seeking a refund while keeping the goods or services.

Category 11: Authorization

Disputes in this category involve transactions processed without proper authorization, either without any authorization at all, against a declined authorization response, or in violation of a Card Recovery Bulletin. 

• Visa Reason Code 11.1 — Card Recovery Bulletin
• Visa Reason Code 11.2 — Declined Authorization
• Visa Reason Code 11.3 — No Authorization

These are less common for most online merchants but can become a recurring issue for businesses running on legacy payment processing infrastructure or manual authorization workflows.

Category 12: Processing Errors

This category covers operational and technical mistakes that occur during transaction processing. Common scenarios include duplicate processing (where a single transaction is charged twice), incorrect transaction amounts, wrong currency codes, late presentments, and invalid data. These disputes are often highly preventable with proper payment infrastructure, reconciliation processes, and quality controls during checkout.

Visa Reason Code 12.5 (Incorrect Amount), for example, arises when the cardholder believes they were charged a different amount than what they agreed to pay, which can stem from data entry errors or confusion about taxes and fees in the final price. 

Visa Reason Code 12.6.1 (Duplicate Processing) covers double charges, which are typically caused by technical glitches or checkout flow issues rather than deliberate overbilling.

Category 13: Consumer Disputes

This is the broadest category and the one that generates the highest dispute volume for most merchants. It covers the various ways a transaction can go wrong from the cardholder's perspective, even when no fraud or processing error is involved.

• Visa Reason Code 13.1 — Merchandise/Services Not Received: This is filed when the cardholder claims they never received what they paid for. This can result from genuine delivery failures, but it also frequently occurs when shipping communication is poor or when a merchant bills before the item has shipped. 

• Visa Reason Code 13.2 — Canceled Recurring Transaction: This applies when a merchant continues to process billing after the cardholder has canceled a subscription — an issue that's entirely preventable with proper cancellation workflows and billing system hygiene. 

• Visa Reason Code 13.3 — Not as Described or Defective: This covers situations where the product or service didn't match the merchant's description or arrived damaged.

What's worth noting about Category 13 disputes is that most of them stem from operational gaps rather than bad faith on either side. Unclear return policies, slow or failed refund processing, vague product descriptions, and poor post-purchase communication are all common root causes. Addressing these issues at the operational level tends to be more effective than trying to win the disputes after the fact.

‍

What are Visa’s Chargeback Time Limits and Deadlines?

Every stage of Visa's dispute process operates within strict time limits, and missing a deadline can mean forfeiting the right to challenge a chargeback entirely. The timelines apply to cardholders, merchants, and issuers, and they differ depending on the type of dispute and the stage of the process.

Cardholder Filing Windows

Cardholders have 120 days from the transaction date or expected delivery date to file most disputes with their issuing bank. A shorter 75-day window applies to certain processing errors and authorization-related issues.

There’s also a notable exception under reason code 13.1 for situations where goods or services aren't expected until well after the purchase date. Event tickets bought months in advance, travel bookings, pre-orders, and custom-manufactured items all fall into this category. In these cases, Visa extends the filing window up to 540 days from the original transaction date, recognizing that the cardholder may not discover a problem until long after the standard 120-day window has closed.

Merchant Response Deadlines

Merchants have 30 calendar days to respond at each stage of the dispute process. Visa defines "day one" as the day after the dispute progresses to a new stage, so the clock starts ticking the day after a chargeback is initiated, not the day of.

However, 30 days is the Visa-level rule. Individual processors have been shortening these windows, and as of mid-2025, some acquirers give merchants as little as 9 days in the U.S. and Canada to respond. The gap between Visa's official deadline and what a merchant's processor actually allows can be significant, which makes it important to understand not just the network rules but the specific terms of the acquiring agreement.

For pre-arbitration, the same 30-day response window applies. Arbitration filings, however, must be made within just 10 days. The financial stakes at these later stages are higher as well, because Visa increased the arbitration case filing fee to $600 as of April 2025, payable by the losing party. A $15 "dispute expired fee" was also introduced for cases where liability is assigned automatically because the merchant failed to respond in time.

‍

Representment and Compelling Evidence

When a merchant decides to fight a chargeback, they do so through representment — re-presenting the original transaction to the issuing bank along with evidence that the charge was legitimate. The type and quality of evidence required depends on the reason code, which means effective representment requires a tailored approach rather than a one-size-fits-all evidence package.

• Goods Not Received (13.1): The most compelling evidence is carrier documentation confirming delivery to the billing address on file.

• Canceled Recurring Transactions (13.2): Merchants need to show proof that the cancellation policy was communicated and that billing ceased in accordance with the terms. 

• Not as Described Claims (13.3): Product descriptions, photographs, and correspondence with the cardholder all carry weight.

• Credit Not Processed (13.6): Records showing the refund was issued, or evidence that the cardholder wasn't entitled to one. 

Fraud disputes under Visa Reason Code 10.4 have traditionally been the hardest to win through representment, because the burden of proving the cardholder authorized a card-not-present transaction is inherently difficult. That changed significantly with the introduction of Compelling Evidence 3.0.

Compelling Evidence 3.0 (CE 3.0)

Visa's Compelling Evidence 3.0, also referred to as the Compelling Evidence Data Program (CEDP), went live for automated qualification in October 2025 and specifically targets reason code 10.4 fraud disputes. It gives merchants a structured way to use historical transaction data to demonstrate that the cardholder has a legitimate, established purchasing relationship with the business.

To qualify under CE 3.0, a merchant needs to identify two prior undisputed transactions from the same cardholder that fall between 120 and 365 days before the disputed transaction. At least two data elements must match across all three transactions, and one of those two matching elements must be either the IP address or the device ID/fingerprint. The second matching element can be the user account ID or the shipping address. When a merchant successfully meets these criteria, the dispute is resolved in their favor. 

This matters beyond the individual transaction for two important reasons. 

First, disputes resolved through CE 3.0 are excluded from Visa's Acquirer Monitoring Program (VAMP) ratio calculations, which makes CE 3.0 a compliance tool as well as a revenue recovery tool. 

Second, it raises the bar for the kind of transaction data merchants need to collect and retain. Device fingerprints, login data, and IP addresses all need to be stored in a way that's accessible, consistent, and compliant with data protection requirements like PCI DSS and GDPR. Merchants whose systems don't currently capture this level of detail may need to evaluate their technology stack to take advantage of CE 3.0.

‍

Pre-Arbitration and Arbitration

The dispute process doesn't necessarily end after representment. If the issuing bank disagrees with the outcome, the case can be reopened through pre-arbitration, where additional evidence is introduced, or the merchant's original response is challenged.

How pre-arbitration works depends on the workflow:

• For collaboration workflow disputes (processing errors and consumer disputes), the issuer initiates pre-arbitration when they believe the merchant's representment evidence was insufficient. 

• For allocation workflow disputes (fraud and authorization), the acquirer initiates pre-arbitration on the merchant's behalf, since liability was assigned automatically at the outset, and the merchant is effectively challenging Visa's rules-based decision.

At the pre-arbitration stage, merchants face a straightforward choice of accepting liability and closing the case or challenging the pre-arbitration and escalating to arbitration. If the case goes to arbitration, Visa's dispute resolution team reviews the evidence from both sides and makes a final, binding ruling. There is no appeal.

The $600 filing fee, paid by the losing party, makes arbitration a meaningful financial risk for lower-value transactions. When combined with the time and resources required to prepare a strong arbitration case, the cost-benefit calculation often favors accepting liability at the pre-arbitration stage unless the transaction value is substantial and the merchant has strong confidence in their evidence. 

That said, consistently accepting liability without challenging invalid disputes can create its own problems because it can embolden repeat friendly fraud and inflate dispute ratios over time.

‍

Visa's Acquirer Monitoring Program (VAMP)

One of the most significant changes to the way Visa handles disputes in recent years has been the consolidation of its monitoring programs into a single framework: the Visa Acquirer Monitoring Program, or VAMP.

Previously, Visa ran two separate monitoring programs:

• Visa Dispute Monitoring Program (VDMP), for merchants with high chargeback ratios. 
• Visa Fraud Monitoring Program (VFMP), for merchants with elevated fraud volumes.

Each had its own thresholds, tiers, and enforcement actions. As of April 2025, both were replaced by VAMP, which combines fraud and dispute monitoring into a single program with a single ratio.

How is the VAMP Ratio Calculated?

The VAMP ratio is calculated by dividing the total count of TC40 fraud alerts and TC15 disputes (both fraud and non-fraud) by the total count of Visa sales in a given month. 

This is a broader calculation than either of the old programs used individually, which means some merchants who were comfortably below the previous thresholds may find themselves closer to the new ones.

The old three-tier system for merchants — Early Warning, Standard, and Excessive — has also been eliminated. VAMP uses a single "Excessive" threshold. Merchant thresholds started at 2.2% when enforcement began in October 2025, with a stepping schedule that reduces the threshold to 1.5% by April 2026. As these thresholds tighten, the margin for error narrows.

What Happens When You Breach VAMP Thresholds?

Merchants who exceed the Excessive threshold face a range of consequences, such as per-dispute fines, enhanced monitoring requirements, potential restrictions on processing privileges, and, in severe cases, acquirer-initiated account termination.

VAMP's primary enforcement target is the acquirer rather than the merchant directly, because Visa holds acquirers accountable for the risk profile of their merchant portfolio. But acquirers pass those consequences downstream. A merchant whose dispute activity pushes their acquirer closer to its own portfolio threshold will face pressure, increased reserve requirements, or termination, regardless of whether Visa is fining them directly.

How Pre-Dispute Tools Affect Your VAMP Ratio

The good news is that pre-dispute resolution tools remain effective for managing the VAMP ratio. Disputes that are intercepted and resolved before they become chargebacks through mechanisms like Verifi's Rapid Dispute Resolution (RDR) reduce the TC15 dispute count in the VAMP calculation. Combined with CE 3.0 exclusions for resolved fraud disputes, merchants have several levers available to keep their ratio under control.

As of June 2025, this exclusion applies to resolutions processed through both Visa's own tools and third-party services, including Verifi and Ethoca, provided the resolution occurs before Visa's data extract.

Verifi RDR and Ethoca don’t suppress TC40s, though; those fraud reports still count toward the VAMP Ratio regardless of whether the underlying dispute was resolved. The only mechanism that currently allows a TC40 to be excluded from the calculation is Compelling Evidence 3.0, submitted through Order Insight and accepted by the issuing bank.

‍

Managing Your Visa Chargeback Risk with ChargebackStop

Visa's dispute rules are updated regularly, and the shift to VAMP in 2025 represents the most significant change to Visa's monitoring framework in years. Keeping chargeback ratios within acceptable limits requires real-time visibility into incoming alerts, automated matching of disputes to transactions, and a structured approach to representment that meets Visa's evidence standards.

As an authorized reseller, ChargebackStop provides merchants with direct access to Ethoca Alerts and Verifi RDR as an authorized reseller of both networks, alongside automated dispute recovery and a managed service for merchants who want an expert team handling evidence collection and submission. 

If you'd like to see how ChargebackStop can help you reduce your Visa dispute ratio and protect your processing health, book a free demo with our team today.