A dispute is one of the most consequential events in the payment lifecycle for any merchant. Understanding how disputes originate, escalate, and resolve is foundational to protecting revenue, maintaining healthy processing relationships, and building effective fraud operations.
How Dispute Works
A dispute follows a structured lifecycle across multiple parties — the cardholder, issuing bank, card network, and merchant. Each step has defined timeframes and rules that determine the outcome.
Cardholder Contacts Issuing Bank
The cardholder contacts their bank to challenge a transaction — citing reasons such as unauthorized use, non-receipt of goods, item not as described, or duplicate billing. The issuer assigns a reason code that governs the dispute rules and evidence requirements.
Issuer Reviews and Notifies Merchant
The issuing bank reviews the claim and, if it passes an initial threshold, forwards a dispute notification to the merchant's acquiring bank. The acquirer then notifies the merchant, typically via their payment platform or gateway dashboard.
Merchant Decides to Accept or Fight
The merchant reviews the dispute details and chooses to accept the reversal (concede) or contest it by submitting a rebuttal letter and supporting evidence. Accepting is appropriate when the claim is valid; contesting is appropriate when the transaction was legitimate and provable.
Evidence Submitted to Issuer
If contesting, the merchant uploads a structured evidence package — proof of delivery, communication history, AVS/CVV match records, fraud signals — within the network's response window (typically 20–45 days).
Issuer Renders a Decision
The issuing bank reviews the merchant's evidence and rules in favor of either the cardholder or the merchant. If the merchant wins, the funds are returned. If the merchant loses, the chargeback is finalized and fees are assessed.
Arbitration (If Escalated)
Either party can escalate to the card network for arbitration if they disagree with the issuer's ruling. Arbitration carries additional fees (often $250–$500) and the losing party bears all costs, making it a high-stakes final step.
Why Dispute Matters
Disputes represent a significant and growing operational cost for payment businesses. Their financial and reputational implications extend far beyond the face value of any single transaction.
According to Mastercard, the total cost of a disputed transaction — including processing fees, operational overhead, and lost merchandise — is approximately 2.4x the original transaction value. A $100 dispute doesn't cost $100; it costs closer to $240 when all factors are accounted for.
The scale of the problem is substantial. Global card dispute volume is estimated at over 615 million cases per year, with total losses to merchants exceeding $117 billion annually (Chargebacks911, 2023). For ecommerce merchants specifically, disputes are intensifying: card-not-present fraud rates are 6x higher than card-present, and digital commerce volumes continue to grow, widening the exposure window.
Beyond direct financial loss, dispute volume directly affects a merchant's standing with their acquirer. Visa's Dispute Monitoring Program triggers at a 0.75% dispute ratio, and merchants exceeding 1% are placed in the Excessive Dispute Program with elevated fees and potential account suspension.
Dispute Ratio Formula
Dispute Ratio = (Total disputes in a calendar month ÷ Total transactions in the same month) × 100. Card networks calculate this monthly, so a single high-volume month can push a merchant into a monitoring program.
Dispute vs. Chargeback
These two terms are often used interchangeably, but they describe distinct stages of the same process. Understanding the difference helps merchants allocate resources to the right intervention point.
| Attribute | Dispute | Chargeback |
|---|---|---|
| Definition | Cardholder challenge to a transaction | Forced reversal of transaction funds |
| Initiated by | Cardholder (via issuing bank) | Issuing bank (after unresolved dispute) |
| Stage | Pre-chargeback | Post-dispute escalation |
| Merchant impact | Notification + response window | Funds debited + fee assessed |
| Reversible? | Yes — can be resolved via evidence or rapid dispute resolution | Yes — via chargeback representment, but harder |
| Counts against ratio? | Not always (depends on resolution path) | Yes, always |
| Typical timeline | Resolved in days to weeks | Can take 45–120 days total |
The most cost-effective intervention point is always the dispute stage — before it escalates into a formal chargeback.
Types of Dispute
Not all disputes are alike. Card networks classify disputes by reason code, and each code carries different evidence requirements and win-rate benchmarks.
Fraud Disputes are the most common category, covering unauthorized transactions where the cardholder claims they did not authorize the charge. These are further divided into true fraud (stolen card) and friendly fraud (the cardholder authorized the transaction but denies it).
Authorization Disputes arise when a transaction was processed without proper authorization — for example, charging a card after an authorization expired, or processing a transaction without the required 3DS authentication.
Processing Error Disputes cover technical mistakes such as duplicate charges, incorrect amounts, currency conversion errors, or credits not processed to the account.
Consumer Disputes (also called "service" disputes) occur when a cardholder claims goods were not received, arrived damaged, or were materially different from what was described. These are common in ecommerce and marketplace environments.
Retrieval Requests are not formal disputes but precursors — the issuer requests transaction documentation before deciding whether to escalate. Responding promptly to a retrieval request can prevent a dispute from being filed at all.
Best Practices
Managing disputes effectively requires operational discipline at both the business and technical layers.
For Merchants
Keep shipping confirmation emails and tracking data tied to each order ID — this is the single most impactful piece of evidence in goods-not-received disputes. Use clear, recognizable billing descriptors so cardholders can identify charges before reaching for the dispute button; unclear descriptors are responsible for a disproportionate share of friendly fraud cases.
Establish a clear refund and cancellation policy and log when customers accept it. Implement proactive outreach: contact customers before they contact their bank. For high-value orders, consider requiring signature confirmation on delivery. Monitor your dispute ratio weekly, not monthly — by the time the monthly report is available, the damage may already be done.
For Developers
Integrate with pre-chargeback deflection tools such as Visa's Order Insight or Verifi — these APIs allow you to push transaction data to the issuer automatically when a cardholder inquires, resolving the inquiry before it becomes a dispute. Automate evidence packaging by building a pipeline that aggregates order data, shipping records, and authentication logs into a structured rebuttal on dispute receipt.
Log device fingerprints, IP addresses, and 3DS authentication outcomes at transaction time — these fields are frequently required in fraud dispute rebuttals. Set up webhook listeners for dispute notifications from your acquirer so response workflows trigger immediately rather than requiring manual review.
Common Mistakes
Ignoring the response deadline. Missing the network's evidence submission window results in an automatic loss regardless of how strong the merchant's case is. Set automated alerts at 50% and 80% of the deadline to ensure no dispute goes unanswered.
Submitting generic evidence. A rebuttal that doesn't directly address the specific reason code fails to convince issuers. Tailor every evidence package to the dispute type — a fraud dispute requires different evidence than a not-as-described dispute.
Accepting all disputes without analysis. Some merchants auto-accept every dispute to avoid operational overhead. This inflates chargeback ratios unnecessarily, since many disputes — particularly friendly fraud cases — are winnable with appropriate documentation.
Overlooking pre-chargeback resolution tools. Many merchants are unaware that Visa RDR, Ethoca Alerts, and Verifi Order Insight can intercept disputes before they become chargebacks. Not enrolling in these programs means paying higher fees and taking ratio hits on cases that could have been deflected automatically.
Failing to use dispute data for prevention. Each dispute is a data signal. Merchants who don't feed dispute reason codes back into their fraud scoring and order review rules miss the opportunity to prevent future identical disputes upstream.
Dispute and Tagada
Tagada's payment orchestration layer integrates directly with dispute management workflows, giving merchants centralized visibility and automated response tooling across multiple acquirers and card networks.
Dispute Handling via Tagada
Because Tagada routes transactions across multiple acquiring relationships, it can normalize dispute notifications from different acquirers into a single event stream. This means merchants get a unified dispute queue, consistent evidence submission workflows, and aggregated dispute ratio tracking — regardless of how many acquirers are active in their setup. For merchants scaling internationally across card networks and regions, this prevents the common failure mode of missing disputes buried in an unfamiliar acquirer portal.