Cardholder Dispute Basics | Everything You Need to Know As A Merchant in 2026

Cardholder disputes have become a real burden across the payments ecosystem. A dispute rarely stays a dispute for long. About 60% escalate into full chargebacks. And once that happens, you've already lost the funds. You're now working to win them back, not just explain a charge.

A meaningful share of these disputes isn't fraud in the traditional sense. According to Mastercard, a quarter of all its chargebacks now stem from recurring transactions, where customers are trying to cancel a subscription or simply don't recognize a charge. Visa's research backs this up. 35% of cardholders mistake a legitimate transaction for a fraudulent one, and 70% of those who've disputed a charge assume that an unrecognized charge means fraud. That means a good chunk of cardholder disputes you're fighting could have been resolved with a cancellation flow, a clearer billing descriptor, or a pre-chargeback alert.

This guide explains why cardholder disputes happen. It also covers how Visa and Mastercard rules differ, and what the resolution timeline looks like. You'll learn how to read a reason code the moment it lands, so you spend less time fighting preventable cardholder disputes.

Understanding Cardholder Disputes

The term “cardholder dispute” carries three different meanings depending on who's using it.

To a customer, a cardholder dispute is the moment a charge looks wrong, and they call their bank. That’s the narrowest interpretation of the phrase. Merchants, processors, and even banks routinely treat “cardholder dispute” and “chargeback” as interchangeable. That's the second, broader sense of the term. Chase tells its merchant outright that a dispute is "also known as a chargeback." Bank of America frames it on the same principle: a cardholder disputing a transaction starts the chargeback process.

If you've seen "cardholder dispute" used this broadly, that's not a misuse. It's simply the dominant shorthand for chargebacks in commercial payments content.

Then there's the third narrowest, most technical sense: Mastercard's own documentation. Cardholder Disputes (reason code 4853) is the broadest of Mastercard's four reason code taxonomy. It covers everything from goods not received to a canceled subscription still showing on the statement. Here, "cardholder dispute" isn't the whole phenomenon. It's one category of chargeback among several. It sits alongside fraud, authorization errors, and processing mistakes.

Why does this matter? Well, because most chargebacks start with a dispute, but not every dispute turns into a chargeback. The two terms get used as synonyms so often that this gap disappears in most merchant content. But it's the gap that determines what you're dealing with at any given moment.

A Quick Refresher On The Cardholder Dispute Process

As we’ve covered in a previous guide, a cardholder's right to dispute a charge is provided by federal law. It's not the network being arbitrary; it's federal protection.

And so a dispute starts when a cardholder contacts their issuing bank to challenge a transaction. And if the bank agrees there might be a problem, it opens a formal investigation, and the cardholder often receives a temporary credit while the transaction stays in dispute. This stage happens entirely on the bank's side, before you're notified of anything. By the time a chargeback notification reaches you, the bank has usually already decided the claim is worth pursuing, which is why it can feel like it arrived out of nowhere, even though a full review already happened upstream.

Thus, you're not appealing to a company's goodwill when you respond. You're responding to a federally protected claims process with its own evidence standards. The rest of this guide walks through exactly what that process demands.

Common Reasons for Cardholder Disputes

Cardholder disputes do not all come from the same vector. So lumping them together is precisely why generic advice fails.

Some disputes are the fault of cardholders, deliberately or otherwise. Others are caused by merchants themselves. But most situations involve contributions from both sides. Knowing which bucket you're dealing with changes what you should do about it.

The Payment Dispute Taxonomy Unveiled

Genuine fraud sits at one end. Instances of pure fraud-driven payment disputes include when:

1. A cardholder's details get used without their permission, or
2. An authorization error gets triggered by a technical glitch, human error, or fraudulent activity.

These are the disputes you can't prevent through better customer service. They call for fraud detection and clean authorization data.

Merchant-caused disputes sit at the other end.

As Mastercard indicated, the biggest offender is the billing descriptor. Disputes caused by an unrecognizable descriptor are entirely preventable by the retailer, and optimizing descriptor recognizability is one proven way to dramatically lower dispute volume. Many merchants underestimate the problem: half of customers call their bank when they don't recognize a charge. Often, a confusing statement line triggers the entire dispute.

Then there's the gray zone in between called friendly fraud, where intent gets murky, and volume keeps climbing.

Subscriptions are the clearest current example of this, and the numbers shared in our intro on recurring-transaction chargebacks point directly at why. When a consumer has to choose between arguing with a business to cancel a subscription or simply disputing the charge with their bank, the dispute wins every time. In the words of Fraud Deflect CEO Scott Adams, consumers don't want the friction.

Each of these cases eventually gets filed under a specific reason code your processor uses to classify the dispute, and that code is where your actual response strategy starts. For deeper insights, read our guide on chargeback reason codes.

The Card Network Rules for Cardholder Disputes

The four major networks don't play by a single rulebook. For starters, they have distinct rules for who actively controls the dispute workflow. Visa and Mastercard work through separate issuing banks. American Express and Discover issue cards and run the network themselves.

Many have argued that since the entire cardholder dispute system was designed to protect the customer, merging the network and issuer roles, as Amex and Discover both do, only sharpens that. Zero-fraud liability guarantees that overwhelmingly favor cardholders are among the main reasons chargeback fraud is increasing. When the company issuing the card is also the one running the network, it has every incentive to side with its own customer over you in a dispute.

Reason codes diverge, too. Mastercard uses numeric codes grouped into four categories, the broadest classification being Cardholder Disputes. Amex uses 34 letter-number codes. Discover uses 26, mostly two-letter abbreviations. The same concept. But different formats by network.

Escalation paths matter even more, since they set the clock you're actually working against. Mastercard gives you 45 days to submit compelling evidence, the issuer 45 days to file a pre-arbitration case, and you 30 days to respond to that. Discover's process can run 60 to 90 days end-to-end, with a final arbitration ruling within 15 days, and a $475 fee if you lose. Visa and Amex's full paths beyond the initial response are worth a closer look in a dedicated piece. And we’ve done just that with our Visa chargeback playbook and Amex chargeback guide.

Another cardholder dispute policy worth highlighting is the thresholds. Visa flags merchants exceeding 1.5% dispute ratios for acquirer scrutiny regardless of how individual cases resolve. Mastercard's Excessive Chargeback Merchant threshold follows the same 1.5% ratio. It is paired with a minimum of 100 chargebacks in a calendar month, climbing to a 3.00% ratio and 300 chargebacks for the more severe High Excessive Chargeback Merchant tier. Amex triggers its Immediate and Partial Immediate Chargeback Programs at a 1% rate sustained for three consecutive months.

The caveat is that your acquirer’s internal cut-off usually stays far below the network thresholds. The image below shows a snapshot of the card network thresholds:

Cardholder Dispute Resolution Process

By the time a dispute notification reaches your inbox, you are already in the middle of the process. And so, your job from that point is to overturn it, not respond to an open inquiry.

Así es como se hace:

Intervene Before the Chargeback Exists

Before a chargeback is formally filed, some networks give you an inquiry window. That stage, when it appears, is your best chance to close the case before it moves further. A strong response at the inquiry stage closes the case entirely.

Amex uses this stage more explicitly than the other networks. But the principle applies across all four. The question isn't whether an inquiry is formally issued. The question is whether you have a process fast enough to intervene before a dispute hardens into a chargeback. Chargeback alerts exist precisely for this window. It notifies merchants the moment a dispute is initiated, with a 24 to 72-hour window to refund and close it entirely. Most merchants miss this stage not because they don't know it exists but because their internal routing isn't built to move that fast.

The Chargeback Notification is Where The Formal Clock Starts

When the inquiry stage doesn't resolve the dispute, or when the network skips it entirely, you get a formal chargeback notice. The issuer provisionally credits the customer and initiates a formal dispute through Visa Resolve Online, Mastercard Claims Manager, or equivalent systems for Amex and Discover. This is the moment most merchants treat as the beginning. It isn't. But it is the moment the merchant-side clock starts, and the deadlines from here are hard.

What Actually Moves The Needle in a Response

Compelling evidence isn't a document dump. Rather, it's a direct, specific rebuttal of the reason code on the notification. It’s a direct answer to the specific claim the reason code is making.

A reason code for goods not received requires proof of delivery to the cardholder's address, not proof that the item was shipped. A reason code for a canceled recurring transaction requires proof that the cardholder agreed to the billing terms and that cancellation wasn't requested, not a copy of the terms of service page. The evidence has to match the code.

Misaligned evidence is the most common reason merchants lose disputes they should win. The bank reviewing the response isn't reading your narrative. They're checking whether your evidence directly contradicts the reason code. If it doesn't, the chargeback stands regardless of what else you've submitted.

That's why automated chargeback management matters. As Mastercard and Datos Insights put it in their 2025 global chargeback report, issuers and merchants that re-examine their approach, implement advanced automated technologies, and prioritize the customer experience will reap the rewards of reducing chargebacks while improving customer satisfaction and loyalty.

Pre-Arbitration and Arbitration: The Stages Where the Cost of Being Wrong Compounds

If the issuer contests your initial positions, the case moves to pre-arbitration chargeback. At this stage, you are no longer just trying to recover funds. You are also managing the risk of the case going to chargeback arbitration, which carries fees that dwarf the original disputed amount in many cases.

Amex sits outside this framework. Unlike Visa and Mastercard, which offer more formalized escalation paths, Amex's chargeback process leaves merchants with limited avenues for further review once a chargeback is issued and upheld. There is no arbitration path to fall back on. The decision is effectively final, which is why the inquiry stage matters disproportionately for Amex specifically.

What Resolution Looks Like

A case closes in one of three ways. The chargeback is reversed, and the provisional credit clawed back from the cardholder, meaning the funds return to you. The chargeback stands, and the funds are permanently gone, with the provisional credit converted to a permanent one for the cardholder. Or the cardholder withdraws the dispute before it reaches a formal decision, particularly when a merchant issues a refund early in the inquiry window.

The third outcome is underused. Not every dispute deserves a representment. Some deserve a refund at the inquiry stage and nothing more.

How Long Does a Cardholder Have to Dispute a Transaction

Across all four major networks, 120 days from the transaction date or expected delivery date is the standard cardholder filing window. But "standard" does a lot of work in that sentence. Every network has categories where the clock starts later, runs shorter, or extends well past 120 days, depending on what's being disputed. Let’s examine the network time limits carefully:

Visa Cardholder Dispute Filing and Response Threshold

Visa cardholders generally have 120 days from the transaction date to file a dispute, though the window can be as few as 75 days depending on the situation and reason code. The 75-day window applies specifically to card recovery bulletins and authorization-related issues. At the other end, select Visa dispute reason codes allow up to 540 calendar days from the transaction processing date, specifically for future-delivery transactions and travel services.

In context, a customer who books a flight in January and disputes it in October is operating within Visa's rules. Visa starts the clock the day after the transaction processing date, not on the day itself.

Merchants get considerably less room. Visa gives merchants 30 days from the “day one” of each phase. They define day one  as the day after each phase is initiated. If they wish to escalate to arbitration, they get 10 days. The published 30-day window is the outside limit, not the working limit. Processors like Adyen shortened merchant response windows to 9 days for US and Canada, and 18 days for other regions effective July 2025. Your acquirer's internal deadline governs your response, and it is almost certainly tighter than what Visa's rules allow on paper.

Mastercard Cardholder Dispute Filing and Response Threshold

Similar to Visa customers, Mastercard cardholders generally have 120 days from the transaction date or expected delivery date to file a dispute. This extends to 540 days for travel services and future-delivery items. Authorization-Related and Point-of-Interaction Error categories carry a shorter 90-day window, and account numbers not on file and warning bulletin disputes drop further to 45 days. Mastercard starts the clock on the transaction date itself, unlike Visa, which starts the day after.

Merchants have 45 days from the chargeback notification to submit a second presentment. The issuer has 45 days to file a pre-arbitration if they reject the outcome. And the merchant gets 30 days to respond to a pre-arbitration filing. The 45-day merchant window is the most generous of the four networks. But the same acquirer-internal caveat applies: acquirers and processors also need time to handle submissions, so build in at least a week before the actual Mastercard deadline.

American Express Cardholder Dispute Filing Threshold

Amex cardholders also have 120 days from the original transaction date to dispute a charge, and can file no more than two disputes on a single order. For defective products, the clock starts from the delivery date rather than the purchase date. There are no extended 540-day categories equivalent to Visa and Mastercard's travel and future-delivery provisions.

Merchants have 20 days to respond, either accepting the dispute or proving the chargeback is meritless. Missing that deadline means automatic loss regardless of the merits of the case. Twenty days is the shortest merchant response window of any major network. The clock starts from Amex's Central Site Business Date, which is set when Amex processes the case, not when the merchant reads the notification.

Discover Cardholder Dispute Filing Threshold

Discover cardholders generally have 120 days from the original transaction date to file a dispute, with exceptions possible based on specific circumstances and Discover's policies. Merchants have 20 days to respond to an initial inquiry and 20 days to respond once a formal chargeback is filed, with a 10-day window if either party wants to pursue arbitration.

What the Asymmetry Means

The pattern across all four networks is identical in structure, even where the numbers differ:

1. Cardholders get months, merchants get weeks, and processors quietly take a slice of those weeks before the file reaches you.
2. Merchant representment windows are nominally 20 to 45 days, but usable time is often shorter due to internal processing delays.

The operational implication isn't just "respond faster." It's that your internal dispute workflow needs to be built around the tightest plausible window, not the published maximum. If you're routing dispute notifications through email, waiting for manual approval, or treating each case as a fresh triage problem rather than a pre-configured, automated response process, the clock is running out before you've started. A transaction from fourteen months ago can generate a legitimate Visa or Mastercard dispute today. Your records need to be there when it does.

Preventing and Avoiding Cardholder Disputes

Dispute prevention advice of fixing your descriptor, simplifying your cancellation flow, and sending a pre-billing notification is not incorrect. It’s also covered earlier in this guide. Because those are causes, not necessarily a prevention strategy. Prevention strategy starts where cause analysis ends:

Manage Ratios, Not Just Disputes

Winning disputes doesn’t protect your chargeback ratio. A merchant with a strong representment win rate and a climbing dispute ratio is still heading toward a monitoring program that strips response rights and triggers acquirer intervention that’s difficult to reverse.

Dispute volume and dispute outcomes are two distinct metrics requiring two separate management disciplines. Most merchants track outcomes. You need to track both, and they treat the ratio drift as a business problem that gets escalated before it crosses a threshold.

Invest in AI-Powered Identity Intelligence

Most fraud prevention tools are built around one question: Is this card stolen? That's the right question for true fraud. It's the wrong question for the dispute category growing fastest.

These aren't stolen card cases. They're real buyers who've decided disputing is easier than resolving, and traditional fraud detection doesn't catch them because they're using their own credentials. The return policy gaps, cancellation flows, and billing descriptors are table stakes. The remaining gap is detection: identifying customers who've already demonstrated abusive behavior before you fulfill their next order and absorb another dispute.

This is what the industry now calls digital shoplifting. Customers who abuse chargebacks, returns, and refund policies to keep products without paying. It's the mechanism behind a significant share of the dispute volume we’ve described throughout this guide.

Chargeflow Prevent was built for this. It analyzes post-purchase signals against a global merchant network to flag transactions likely to become disputes before they do. It identifies known digital shoplifters the moment they appear, blocking stolen card fraud and detecting serial returners and refund abusers in real time.

Chargeback prevention at this level isn't about being more cautious at checkout. It's about knowing which customers have already cost other merchants money and acting on that intelligence before they cost you.

Prevention Has a Ceiling

Even a well-run operation will see chargebacks. That's a given. Prevention reduces volume. It doesn't eliminate exposure. Mastercard's own research found that a quarter of merchants across countries report annual chargeback volumes above 1 million transactions, and for 13% of merchants, that volume runs at 2% or more of total transactions. At that scale, prevention isn't optional infrastructure. It's the difference between a manageable cost of doing business and a ratio that puts you in front of an acquirer.

That's why the two systems matter more than either one alone. A pre-bank intervention framework, the kind that flags a digital shoplifter before you fulfill their order or catches a friendly-fraud pattern before it reaches the issuer, is what keeps that volume from climbing in the first place. And a precise response process wins the disputes that get through anyway. Those are separate systems, and you need both.

Want help building both systems? Talk to our experts today.