Cardholder dispute
What is a cardholder dispute?
Cardholder dispute is a process initiated by a cardholder when they believe a transaction debited from their account was unauthorized or improperly processed. The cardholder raises the claim with their , which reviews it and, if it holds up, requests a to reverse the transaction.
Claims stem from fraudulent transactions, dissatisfaction with a purchase, or discrepancies in billing. Card networks treat this as one category of , filed separately from fraud claims: Visa groups it under category 13, "Consumer Disputes", and Mastercard under reason code 4853. Scheme rules reserve the mechanism for actual fraud, or for cases where the merchant has failed to uphold their part of the sales agreement and declines to issue a .
Key facts
- Also known as: consumer dispute, cardholder-initiated dispute
- Filed by: the cardholder, through their issuing bank rather than with the merchant
- Scheme categories: Visa category 13 (Consumer Disputes), covering codes such as 13.1 Merchandise/Services Not Received, 13.3 Not as Described or Defective Merchandise/Services, and 13.7 Cancelled Merchandise/Services; Mastercard reason code 4853
- Filing window: typically up to 120 days from the transaction or expected delivery date, extending further under some reason codes – see
- Outcome: a chargeback that reverses the funds, or a rejected claim that leaves the original standing
How it works
- The cardholder flags the charge. An unfamiliar , a subscription renewal they thought they'd cancelled, or goods that never arrived prompts a call to the issuing bank.
- The issuer reviews the claim. The issuer assigns a matching the stated problem and checks the claim against scheme criteria. Where scheme rules allow it, the issuer sends a for transaction details before escalating.
- The issuer debits the acquirer. Funds move back from the , which passes the debit and a down to the merchant.
- The merchant responds or accepts. Representment returns the case with : delivery confirmation, login and usage records, the terms the cardholder agreed to at checkout. Accepting means the debit stands.
- The case escalates or closes. If the issuer rejects the evidence, the case can move to a , then to and , where the network rules on it and charges the losing side a fee.
Why it matters
- Each upheld dispute costs the merchant the transaction amount plus a , whether or not the goods were delivered.
- Disputes count toward the chargeback ratios card networks monitor. Crossing a scheme's threshold moves a merchant into a monitoring program with escalating fines, and at the far end, loss of card acceptance.
- The reason code assigned at filing determines which evidence overturns the case. A 13.1 claim turns on proof of delivery; a 13.3 claim turns on what was described at checkout.
- Prevention networks such as and surface the claim before it becomes a chargeback, so purchase detail or a refund can settle it while the transaction is still reversible.
Common issues
- . A cardholder disputes a purchase they genuinely made, sometimes because a family member used the card, sometimes to avoid paying. It's filed under a consumer-dispute code, so it reads as a legitimate claim until the merchant produces evidence.
- Unrecognizable billing descriptors. A descriptor showing a legal entity name instead of the brand the cardholder bought from produces disputes that a clearer statement line prevents.
- Refunds issued after filing. A refund processed on a transaction that already has a chargeback in flight moves funds twice, and the merchant pays for the same order twice.
- Missed response deadlines. Response windows run from the notification date, and a case that isn't answered inside the window closes in the cardholder's favor by default.
