Visa Chargeback Dispute Rules, Fees & Time Limits (2026 Playbook)

A Visa chargeback is a disputed card payment handled through the merchant’s acquirer or payment provider. The applicable condition and workflow determine the response options; use the deadline shown on the case. Visa monitoring requirements are a separate account-risk calculation.

Are you losing revenue to Visa chargebacks? You're not alone. Visa itself calls payment disputes a growing concern, draining billions from merchants each year.

Visa chargebacks occur when customers dispute completed transactions, prompting their card-issuing bank to reverse payments and withdraw funds from your merchant account.

This sudden reversal can disrupt cash flow, especially for small business owners. It also strains processor relationships and can even lead to costly penalties if not managed.

If you need the fundamentals first, our guide to what is a chargeback covers the mechanics that apply across every card network.

Visa has introduced policy changes to help merchants fight back. But these policies only address a fraction of the problem. Friendly fraud, repeat disputes, and complex evidence requirements still leave revenue at risk.

That's why a structured, proactive chargeback management strategy, grounded in clear chargeback rules, is essential for Visa merchants.

This playbook equips you with battle-tested tactics to minimize disputes, win more Visa chargebacks, and protect your merchant account. You'll learn how to transform Visa's chargeback system from a revenue threat into a manageable process.

{{cta}}

Visa Chargeback Fees and Time Limits at a Glance

Use this table to identify the service or case stage, then confirm the actual response deadline, time zone and applicable fee schedule with your provider. These are not mandatory sequential steps.

Cardholder filing and merchant response are different clocks. The filing limit and its start date depend on the dispute condition. Some future-delivery conditions have an outer limit; 540 days is not a general fraud extension. See our chargeback time-limit guide and the applicable Visa rule.

Where the 120-Day Rule Actually Comes From: Visa's Two Official Rulebooks

Merchants hear "120 days" so often that it starts to sound like folklore. It isn't. That deadline, along with every other Visa dispute rule referenced in this guide, is written into two documents Visa publishes and periodically re-dates: the Visa Core Rules and Visa Product and Service Rules (public edition, most recently republished 18 April 2026) and the Dispute Management Guidelines for Visa Merchants (June 2024 edition).

These aren't marketing pages. They're the same rulebooks your acquirer and processor pull from when they set your internal deadline, and that internal deadline is often shorter than Visa's own. When a processor tells you "you have 10 days to respond," ask which document and edition they're citing. Visa republishes both files under the same URL with a new date stamp, so an argument built on a stale edition number won't hold up with your acquirer.

Bookmark both documents. Citing the specific rule, section, and edition date is the difference between "the merchant said" and "Visa's rulebook says," and that difference matters the moment a dispute goes to pre-arbitration.

How Do Visa Chargebacks Work? A Complete Breakdown of the Dispute Process

Visa dominates the global payments landscape, with 4.48 billion active cards and over 233 billion transactions processed in 2024 alone. With that scale comes an equally complex dispute process. Visa's chargeback system has distinct rules, timelines, and monitoring thresholds, similar in spirit to Mastercard's chargeback monitoring programs. Every merchant must understand the nuances to protect their revenue in these times.

Possible services and case stages are outlined below. Availability and sequence depend on the condition, workflow and provider.

Before a Chargeback: Order Insight and Resolution Services

Timeline:

• Order Insight: transaction information can help a participating issuer clarify a purchase; it is not a universal manual-response stage.
• Resolution services: follow the service-specific instructions. CDRN uses a merchant-initiated refund window; RDR evaluates eligible Visa pre-disputes automatically.

Process:

Step 1: Cardholder contact: a participating issuer may use transaction clarification or a pre-dispute resolution service. Do not assume that every Visa chargeback is preceded by an inquiry or alert.

Step 2: Visa Merchant Purchase Inquiry (VMPI/Order Insight): The issuer submits an inquiry through Visa Resolve Online (VROL), generating an Extensible Markup Language (XML) message. This includes the transaction data to help you, the merchant, identify the transaction. Note: VMPI/Order Insight availability depends on the acquirer's integration with these tools; some issuers may bypass inquiries and initiate a chargeback directly.

Step 3: Merchant Response Options: You can:

• Provide additional transaction details to clarify the charge
• Issue an immediate refund to resolve the dispute
• Do nothing; accept that a chargeback is likely to be filed

Fees: ask the service provider about enrollment, resolution and refund-processing charges under your agreement.

Chargeback Notification and Merchant Response

Timelines:

• Cardholder filing: check the condition-specific rule and the event from which the filing period starts. This is separate from the merchant’s response deadline.
• Merchant response, Adyen example: Adyen documents 9 calendar days for Visa disputes opened from July 21, 2025 on locally processed U.S. and Canadian payments, and 18 days for earlier cases or other countries and regions. These are Adyen timeframes, not a universal Visa merchant entitlement; use the due date on your case.

Process:

Step 1: Initial Chargeback: The issuing bank (ideally) evaluates the cardholder's claim under the Visa Claims Resolution (VCR) framework. If valid, the issuer initiates a chargeback through one of two workflows:

• Allocation Workflow: Rules-based, automated decisions for clear-cut cases (e.g., fraud).
• Collaboration Workflow: Manual review for complex disputes requiring evidence evaluation.

The issuer debits the transaction amount from the acquirer, provides provisional credit to the cardholder, and submits a dispute reason code with supporting documentation.

Step 2: Merchant response: use the provider’s supported accept or challenge option, submit permitted evidence by the case deadline, and retain the submission confirmation. Response rights differ between Allocation and Collaboration.

The acquirer submits the merchant evidence to the issuer, who may:

• Accept the representment and reverse the chargeback.
• Reject it and escalate the case to pre-arbitration.

Fees: confirm received-dispute, countered-dispute, acceptance and expired-case charges in your current provider schedule. Keep network assessments and provider charges separate, and reconcile any fee returned after the outcome.

Evidence Quality and Submission:

• Manual responses: select records that answer the particular allegation and condition.
• Automated evidence compilation: organize relevant records and check submission quality, coverage and deadlines.

Common Visa Chargeback Evidence Requirements by Reason Codes

Visa periodically updates its chargeback reason codes. Below are the standard types of evidence most commonly required to support representment for frequent Visa dispute categories:

• Fraud (10.4: Other Fraud - Card-Absent Environment): Provide Address Verification Service (AVS)/Card Verification Value (CVV) match results, IP address verification, device fingerprinting, delivery confirmation, and proof of cardholder communication.
• Authorization (11.1: Card Recovery Bulletin): Submit Authorization codes, terminal logs, and proof of proper card processing procedures.
• Authorization or late presentment (11.3): review the applicable condition, transaction dates and authorization records. Visa’s current rules combine No Authorization/Late Presentment; 12.1 is a legacy late-presentment condition.
• Consumer Disputes (13.1: Merchandise/Service Not Received): Submit delivery confirmations, tracking information, proof of digital delivery, or service completion documentation.

Compelling Evidence 3.0 (CE3.0): The Fast Path for Reason Code 10.4

Compelling Evidence 3.0 is Visa's expedited remedy for reason code 10.4 (Other Fraud: Card-Absent Environment), the code issuers use for most "I didn't make this purchase" claims. Instead of building a full representment packet, a merchant can shift liability back to the issuer by proving the cardholder has a real transaction history with the merchant. It exists specifically to counter first-party misuse, cardholders who made the purchase and disputed it anyway, without requiring a merchant to accuse anyone of anything.

CE3.0 only applies to 10.4. It does not cover other fraud codes, processing-error codes, or consumer-dispute codes, and it does not replace representment for those categories.

The practical takeaway for merchants: CE3.0 defense lives or dies on whether account ID, device fingerprint, IP address, and shipping address are logged and retrievable per order at the time a dispute lands. A merchant who can't pull two matching prior orders in the 120-to-365-day window loses access to the fastest liability-shift path Visa offers for 10.4 claims, and falls back to a full manual representment packet instead.

Collaboration vs. Allocation: Which Visa Workflow Actually Decides Your Dispute

Not every Visa dispute is decided the same way. Visa Claims Resolution (VCR), introduced in April 2018, routes every case into one of two workflows, and knowing which one applies changes how you should spend your time.

Allocation covers fraud and authorization conditions and uses rules-based liability assignment. Do not assume a universal 30-day merchant submission window: confirm available response rights and the case due date with your acquirer.

Collaboration covers processing-error and consumer-dispute conditions and allows issuer/acquirer exchange of the relevant information. Your provider’s case instructions identify the permitted response, stage and deadline.

The practical takeaway: if your reason code falls in the 10.x or 11.x series, don't spend your first-line response building a courtroom-grade case. The system has already run its automated check, and pre-arbitration is where you get a real hearing. If it's 12.x or 13.x, your initial representment carries more weight, since there's no automated liability assignment to overturn later.

Legacy Visa Reason Codes and Their Current Equivalents

Older processor statements, legacy gateway exports, and some acquirer portals still show pre-2018 numeric reason codes. Visa Claims Resolution (VCR) replaced them with the category codes used throughout this guide. Use this table to translate:

These six are the legacy codes merchants most often still encounter on older processor statements. Visa retired dozens of others in the same 2018 migration, so if a code you're looking at isn't listed here, check it against the Visa Core Rules and Visa Product and Service Rules referenced earlier, or ask your acquirer which of the four current categories, 10.x, 11.x, 12.x, or 13.x, it now falls under.

{{cta}}

VAMP: Check Region, Counts and Exclusions

Visa’s VAMP fact sheet sets an excessive-merchant ratio of at least 150 basis points (1.5%) from April 1, 2026 in AP, Canada, Europe and the U.S., with a monthly count of at least 1,500 fraud reports plus disputes. Those merchant criteria are conditional on the acquirer not being Above Standard or Excessive; other regions and acquirer-level criteria differ.

The count-based ratio uses TC40 fraud plus TC15 disputes against settled CNP transactions. Pre-dispute resolutions and qualifying CE3.0 fraud exclusions depend on the data-extract timing. Confirm your region, calculated count, exclusions and any assessments with your acquirer; a ratio alone is not a complete compliance test.

Turning Visa's Rulebook Into a Repeatable Process

Visa's chargeback rules run to hundreds of pages, but the working version most merchants need fits on one page: know the deadline at every stage in the table above, keep the account ID, device ID, IP address, and shipping address that CE3.0 depends on logged and retrievable per order, and track your VAMP ratio before your acquirer flags it. Manual representment can still win a meaningful share of well-documented cases, and it wins more consistently when it's paired with the monitoring discipline that keeps a merchant account out of the excessive tier in the first place.

If disputes are already cutting into revenue, Chargeflow automates that discipline, compiling reason-code-specific evidence and tracking VAMP exposure so the deadlines above are never the reason a case is lost.