Visa Claims Resolution is the standardized framework every merchant, acquirer, and issuing bank follows when a cardholder disputes a Visa transaction. It routes every dispute into one of two workflows based on the reason code the issuer files under: an automated Allocation track for fraud and authorization claims, and a document-driven Collaboration track for processing errors and consumer complaints. Each track has its own deadlines, evidence standards, and escalation path, and missing a step at any point means the disputed funds are gone for good.1Visa. Dispute Management Guidelines for Visa Merchants
The Four Dispute Categories
Every Visa dispute falls into one of four numbered categories, and the category is what determines which workflow applies.
- Fraud (10.x): the cardholder says they never authorized the charge. Codes cover counterfeit chip transactions, card-present fraud without a chip, and card-not-present fraud such as unauthorized online purchases.
- Authorization (11.x): the merchant processed a transaction without a valid approval, ran a charge after a decline, or skipped authorization entirely.
- Processing Errors (12.x): technical failures like duplicate charges, wrong amounts, currency conversion errors, or late presentment.
- Consumer Disputes (13.x): the cardholder recognizes the charge but has a problem with it, such as merchandise never received, defective goods, or a credit that was promised but never appeared.
Fraud and Authorization cases move through Allocation. Processing Errors and Consumer Disputes move through Collaboration. That routing decides how much of the process is automated, how much time you have, and what kind of evidence is going to matter.
The Allocation Workflow
Allocation is largely automated. Visa’s system pulls transaction data and assigns liability based on what happened at the point of sale, not on who argues more persuasively afterward.2Visa. Visa Claims Resolution – Efficient Dispute Processing for Merchants It checks for authentication markers such as 3-D Secure verification, electronic commerce indicators, and whether the merchant followed Visa’s secure processing protocols. If those markers are missing, the merchant absorbs the loss automatically.
There is no preliminary negotiation here. You can challenge an Allocation outcome, but only with compelling evidence that directly contradicts Visa’s data assessment. General policy arguments do not move the needle.
The 3-D Secure Liability Shift
For online merchants, 3-D Secure authentication is the single most important protection against fraud chargebacks. When a card-not-present transaction is successfully authenticated through Visa Secure, fraud liability shifts from the merchant to the card-issuing bank.3Visa. Visa Core Rules and Visa Product and Service Rules The logic: if the issuer’s own authentication system cleared the cardholder and fraud still happened, the issuer bears the cost.
To qualify, the merchant must participate in the Visa Secure program and the transaction must have been successfully authenticated. The shift takes precedence over other fraud liability assignments for qualifying transactions. One caveat matters for subscription businesses: the liability shift generally does not apply to recurring transactions, so a single authentication at signup does not protect every future billing cycle.
Compelling Evidence 3.0
Even without 3-D Secure, merchants who sell to repeat customers have a tool for fighting card-not-present fraud disputes under reason code 10.4. Compelling Evidence 3.0 lets you prove the same cardholder made prior legitimate purchases from you, establishing a pattern that undercuts the fraud claim.4Visa. Compelling Evidence 3.0 Merchant Readiness
The requirements are specific. You need at least two previous undisputed transactions from the same merchant account, dated between 120 and 365 days before the dispute date. Those prior transactions cannot carry any active fraud reports or disputes. And at least two of four core data elements must match between the prior transactions and the disputed one: User ID, IP address, shipping address, or device ID/fingerprint. One of the two matching elements must be either the IP address or the device ID. Merchants with strong login tracking and customer account systems are best positioned to use this defense.
The Collaboration Workflow
Processing Errors and Consumer Disputes take a different route because they usually hinge on context that automated data cannot capture, like whether a product matched its description or why a shipment was late. Collaboration is a structured back-and-forth between the merchant, acquirer, and issuing bank.2Visa. Visa Claims Resolution – Efficient Dispute Processing for Merchants
It usually opens with an informal inquiry, where the merchant can provide context, issue a refund, or supply proof of service before the dispute formally escalates. Resolving the issue in this window avoids the chargeback entirely and keeps it off your record. If no resolution is reached, the issuer files formally, and the merchant submits a documented response through the acquirer.
Credit Not Processed (13.6)
Reason code 13.6 catches merchants who promised a refund but never delivered. If the cardholder has evidence of an agreed credit, such as an email confirmation or a return receipt, and no credit appears on the statement, the issuer can file under 13.6.5Visa. Updates and Clarifications to Dispute Rule Language The issuer must wait at least 15 calendar days after the original processing date before filing, giving the merchant time to actually process the credit.
If you already issued the refund, your defense is direct: provide proof of the credit including the amount and date processed. When multiple credits were issued across different transactions, the issuer must identify exactly which transaction each credit applied to using the Acquirer Reference Number. Vague explanations like “the credit does not apply” are not acceptable under the rules.
Documentation and Evidence
The evidence that wins a dispute depends on what you sell and how you deliver it. Visa’s guidelines lay out specific requirements by transaction type, and falling short on even one element can sink an otherwise winnable case.1Visa. Dispute Management Guidelines for Visa Merchants
For physical goods, you need proof of delivery showing the merchandise was shipped to the correct address, ideally with carrier certification or a signature from the cardholder. A tracking number alone is often insufficient if it does not confirm delivery to the billing address. Service-based businesses should keep signed contracts, usage logs, or correspondence showing the cardholder actively participated in the service. Subscriptions need clear records of the cardholder’s agreement to recurring billing terms and evidence they used the service after the disputed charge.
Digital goods have their own standard. You need a description of what was downloaded, the date and time of the download, and at least two additional data points from among the purchaser’s IP address and geographic location, the device ID and name, or the cardholder’s account login history tied to the transaction. Server logs are the backbone of digital dispute responses.
All evidence is submitted through Visa Resolve Online (VROL), the portal where disputes are managed electronically.6Visa Developer. Visa Resolve Online Each dispute has a case folder with a questionnaire tailored to the assigned reason code. You populate the form with the original Transaction ID, Merchant ID, and specific response codes justifying your rebuttal, then attach supporting documents as digital files before submitting. Incomplete packages get rejected, and there is rarely a second chance to supplement.
Response Deadlines
Visa’s timelines leave very little room. Merchants generally have 30 days to respond to Allocation disputes by submitting compelling evidence that overturns the initial liability assignment. Collaboration disputes carry strict response windows as well. Miss a deadline and the funds are permanently lost, plus your acquirer will typically assess a chargeback fee on top of the lost revenue. Those fees commonly range from $15 to $100 per case depending on your processor and industry.
On the cardholder’s side, the window to initiate a dispute is 120 calendar days from the transaction date for most reason codes.3Visa. Visa Core Rules and Visa Product and Service Rules For merchandise not received (13.1), the 120-day clock starts from either the transaction date or the expected delivery date, whichever is later. A delayed shipment therefore extends the cardholder’s dispute window, which is another reason tracking and delivery confirmation matter.
Pre-Arbitration and Arbitration
When the issuer rejects a merchant’s dispute response, the case can escalate to pre-arbitration. This is the final negotiation stage before Visa itself decides. The responding party has 30 calendar days from the processing date of the pre-arbitration filing to submit a response.3Visa. Visa Core Rules and Visa Product and Service Rules Either the parties settle here, or the case moves to formal arbitration where Visa issues a binding decision.
Arbitration is expensive by design. Visa charges a case filing review fee of around $500, paid by the losing party. If Visa determines one side violated its operating rules during the dispute, an additional technical penalty of around $250 can apply. These fees discourage frivolous escalations, and they work. Most disputes that reach pre-arbitration settle there because neither side wants to gamble on the arbitration outcome. The practical takeaway for merchants: your initial response needs to be strong enough that you never have to test it at arbitration.
The Visa Acquirer Monitoring Program
Winning individual disputes matters, but Visa also monitors your overall dispute volume. The Visa Acquirer Monitoring Program (VAMP) replaced the legacy Fraud Monitoring Program and Dispute Monitoring Program by combining fraud reports and chargebacks into a single risk ratio.7Equifax. The Visa Acquirer Monitoring Program (VAMP) – What New Rules Mean for Acquirers and Merchants The ratio measures your total disputes, including fraud reports and chargebacks across all reason code categories, against your overall transaction count.
As of April 2026, the merchant “excessive” threshold drops to 1.5% (150 basis points), down from 2.2%. You must also exceed a minimum monthly count of 1,500 combined fraud reports and disputes before the thresholds apply. Merchants flagged as excessive face per-dispute fees passed through by the acquirer. If the problem persists, Visa can instruct the acquirer to terminate the merchant’s processing agreement.
Acquirers also have their own portfolio-level thresholds, which creates pressure from both directions: Visa penalizes the acquirer, and the acquirer passes that pressure to the merchant. Acquirers with clients chronically above threshold may end the relationship rather than absorb escalating penalties.
Dispute Prevention Tools
The cheapest chargeback is the one that never gets filed. Visa offers two tools that intercept disputes before they enter the formal resolution process.
Order Insight
When a cardholder calls their bank about an unrecognized charge, Order Insight feeds the issuer enhanced transaction details in real time, including itemized order information and purchase specifics that help the cardholder or the bank’s agent recognize the charge.8Visa. Order Insight Many disputes start as simple confusion over how a merchant name appears on a statement, and Order Insight resolves that on the spot. According to Visa’s internal reporting, participating merchants have deflected 40 to 45 percent of confirmed first-party-misuse disputes through Order Insight, with some subscription merchants reaching deflection rates as high as 90 percent.
Rapid Dispute Resolution
Rapid Dispute Resolution (RDR) takes a different approach. Instead of providing information to prevent the dispute, it automatically resolves qualifying disputes by issuing a merchant-initiated credit before the formal chargeback process begins.9Visa. Rapid Dispute Resolution – Proper Identification of RDR Transactions and Service Activation Merchants configure rules that define which disputes they are willing to accept liability on automatically. When a dispute matches those rules, RDR processes the refund and the transaction never counts as a formal chargeback.
The trade-off: you give up the money on those transactions. But the dispute does not hit your VAMP ratio, does not incur a chargeback fee, and does not consume staff time building a response package. For merchants close to monitoring thresholds or handling high volumes of low-dollar disputes where the cost of fighting exceeds the transaction amount, RDR is often the smarter financial move.