Disputes and chargebacks

IN ONE LINE

An everyday analogy: a chargeback is the card system's built-in small-claims court.

Maya Chen finds a charge from Demo Coffee Ltd she does not recognise — or paid for goods that never arrived — and instead of chasing the shop, she goes to her own bank.

Bank Alfa, her issuer, can pull the money back through the Cardnet network (a fictional stand-in for Visa- or Mastercard-style networks), citing a numbered reason.

The claim lands on Meridian Bank, the acquirer, which passes it to the merchant with a choice: accept the loss, or answer with evidence.

Receipts and records travel back the other way, someone decides, and the loss finally comes to rest — on the cardholder, the merchant, or one of the banks.

(SYNTHETIC / TRAINING ONLY — all names fictional.) That path is the cardholder's safety net; the discipline it imposes on merchants is its price.

WHAT IT ACTUALLY IS

A dispute begins when a cardholder contests a posted transaction with their issuer.

If the issuer finds the claim eligible under the network's rules, it raises a chargeback: a reversal through the network carrying a reason code — a numbered category such as fraud, goods not received, or duplicate processing — which fixes which rules and which evidence will apply.

The acquirer receives it, normally debits the merchant at once, and forwards the case.

The merchant's reply is representment: presenting the transaction again with evidence that the charge was valid — an authorisation trail, proof of delivery, a signed receipt.

The issuer reviews and either accepts the evidence, returning the money to the merchant's side, or maintains the dispute.

Liability follows the reason code and the paper: for each code, the network's rules say what proof wins and who bears the loss when no one clearly does.

HOW IT WORKS

Practitioners run disputes as a pipeline of deadlines and documents.

Every stage has a response window, measured in days from precise events — the processing date, the chargeback date — and set by each network's rules; miss the window and the case is lost regardless of its merits, so dispute teams live by these clocks.

Reason codes drive the work: evidence that defeats a 'goods not received' claim is useless against a fraud code, and the networks publish per-code documentation requirements.

Not every disputed charge becomes a chargeback — networks operate pre-dispute stages where the issuer requests information first or the merchant refunds voluntarily, settling the matter before the formal machinery starts.

And beyond case-by-case losses, merchants are scored: a dispute ratio above network thresholds pulls them into monitoring programmes, with fines and, at the far end, loss of card acceptance altogether.

THE WORDS

Chargeback

The issuer reversing a card payment under scheme rules — pulling the money back from the acquirer, and usually the merchant, after a cardholder dispute or rule breach.

Chargeback reason code

The scheme-defined code stating why a chargeback was raised — fraud, goods not received, duplicate — which fixes the rules, evidence, and time limits for the case.

Representment

The merchant's rebuttal to a chargeback: the acquirer presents the transaction a second time, with evidence that the charge was valid.

Arbitration

The final stage of a card dispute: when issuer and acquirer cannot settle a chargeback between them, the network rules on the case and allocates the loss — and fees.

READ FIRST

• Clearing and settlement for cards

CONNECTED TO

• FLOW Chargeback lifecycle
• CHECKPOINT Card fundamentals checkpoint
• COMPARE Chargeback vs SEPA R-transaction

SOURCES

• A glossary of terms used in payments and settlement systems — CPSS (now CPMI), Bank for International Settlements
• Payments Signal editorial teaching models — Payments Signal