Cards & Merchant Payments / Learning brief
Chargebacks and disputes, end to end
Your notes
In simple terms / 01
What this means in plain language
The card dispute lifecycle from the cardholder's claim to final liability: reason codes, the chargeback that moves money back first, the merchant's evidence and representment, and the pre-arbitration and arbitration endgame — plus how a chargeback differs from a refund.
A chargeback is the card system's formal undo: the issuer reverses a settled transaction under scheme rules, tagged with a reason code that says why — fraud, goods not received, a processing error such as a duplicate, or a missing authorisation. Money moves back to the issuer first; the argument happens afterwards. The acquirer debits the merchant and asks for evidence. If the merchant contests, the acquirer re-presents the transaction — the representment — with that evidence, and the issuer reviews it against the reason code's requirements. Unresolved cases can escalate through pre-arbitration to arbitration, where the network decides and the losing side pays case fees. A chargeback is not a refund: a refund is the merchant returning money voluntarily, while a chargeback takes it back under the rulebook.
Key takeaways / 03
Three things to remember
- 01
Chargebacks are issuer-initiated, reason-coded, and value-first: the money returns before the argument is settled.
- 02
Representment is the merchant side's evidence-backed rebuttal; pre-arbitration and arbitration are the costly final stages the fee schedules are designed to discourage.
- 03
Reason codes frame everything — evidence, deadlines, and monitoring ratios — and the exact codes, time limits, and fees are scheme-specific.
Practical use cases / 04
Where you would use this
Building a merchant's dispute-response playbook: which evidence to keep (terminal journals, delivery proof, EMV data) mapped to reason-code families.
Deciding whether to fight or accept a small chargeback once dispute fees and win odds are weighed against the amount.
Using prompt refunds and clear billing descriptors to stop disputes from becoming chargebacks at all.
Worked example / 05
Put the idea into a real situation
Illustrative example (SYNTHETIC / TRAINING ONLY): Maya Chen finds two EUR 3.80 charges from Demo Coffee Ltd for one coffee and calls Bank Alfa, her issuer. Bank Alfa raises a chargeback with a duplicate-processing reason code through Cardnet — a fictional card network standing in for Visa- or Mastercard-style networks. Meridian Bank, the acquirer, debits Demo Coffee EUR 3.80 and requests evidence. Demo Coffee's terminal journal shows a single tap captured twice in the batch, so it accepts the chargeback rather than re-presenting; Maya keeps her re-credit and Demo Coffee fixes its end-of-day process. Had the journal shown two genuine taps, Meridian would have re-presented with the journal as evidence, Bank Alfa would have reviewed it — and pre-arbitration and Cardnet arbitration remained available if the banks still disagreed.
Operational sequence / 06
Follow the message and decision path
This compact sequence is a learning model. Exact routing and rulebook behavior can vary by scheme, participant, and implementation.
Read the steps as text
- 01MessageMaya disputes the chargeMaya Chen (cardholder) → Bank Alfa (issuer)
Maya tells Bank Alfa she does not recognise the EUR 42.50 booking on her statement. The issuer records the claim and, for many claim types, first asks whether she has tried to resolve it with the merchant directly.
- 02MessageBank Alfa raises a chargeback with a reason codeBank Alfa (issuer) → Cardnet (card network) · chargeback record
The issuer sends a chargeback record into the network carrying a reason code — the claim's category, such as 'transaction not recognised' or 'goods not received'. The reason code fixes what evidence can answer it. Many issuers also re-credit the cardholder provisionally while the case runs.
- 03MessageCardnet routes the chargeback to Meridian BankCardnet (card network) → Meridian Bank (acquirer) · chargeback record
The network checks the chargeback is validly formed — reason code allowed, raised within the time limit its rules set — and delivers it to the acquirer that presented the original sale.
- 04SettlementThe disputed amount settles back through the network cycleMeridian Bank (acquirer) → Bank Alfa (issuer)
A chargeback is not only a case file — it is a money movement. In the next network settlement cycle the disputed amount is charged to the acquirer's net position and credited to the issuer's, reversing the direction the original sale settled in.
The interbank leg reverses first; whether the merchant or the issuer finally bears the loss is decided later by the case.
- 05PostingMeridian Bank debits Demo Coffee and asks for evidenceMeridian Bank (acquirer)
The disputed amount is pulled from the merchant's account while the case runs — in a chargeback, the money moves first and the argument follows. The acquirer passes the case to Demo Coffee with the reason code and a deadline to respond.
- DR Demo Coffee Ltd settlement account at Meridian Bank — EUR 42.50
- 06MessageDemo Coffee responds with evidenceDemo Coffee Ltd (merchant) → Meridian Bank (acquirer)
The merchant answers the reason code with proof: the signed receipt, the terminal's EMV chip data showing the card was present, and the catering delivery note. Evidence that does not address the reason code does not count, however thick the file.
- 07MessageMeridian Bank re-presents the transactionMeridian Bank (acquirer) → Cardnet (card network) · representment record
The acquirer sends the case back through the network as a representment — literally a second presentment of the sale, now with evidence attached — asserting the original charge was valid.
- 08MessageCardnet delivers the representment to Bank AlfaCardnet (card network) → Bank Alfa (issuer) · representment record
The network checks the representment is validly formed and passes it — evidence attached — to the issuer that raised the original chargeback.
- 09ProcessingBank Alfa reviews the representmentBank Alfa (issuer)
The issuer weighs the evidence against Maya's claim and the reason code's requirements. This review decides the case for most disputes — escalation beyond it is the exception, not the rule.
- 10SettlementThe interbank chargeback settlement unwinds in the acquirer's favourBank Alfa (issuer) → Meridian Bank (acquirer)
Because the representment succeeds, the earlier acquirer-to-issuer movement reverses: in the next settlement cycle the disputed amount is charged back to Bank Alfa's net position and credited to Meridian Bank's, undoing the chargeback's original settlement. The acquirer is made whole between the banks before it re-credits the merchant.
The money returns to the acquirer's side first; only then does Demo Coffee get its debit reversed.
- 11PostingThe case closes — liability lands with the evidenceMeridian Bank (acquirer)
Bank Alfa accepts the representment: the chip data shows Maya's card was present, so the charge stands. With the interbank leg reversed, Meridian Bank re-credits Demo Coffee, and Bank Alfa reverses Maya's provisional credit and explains the outcome to her. Liability followed the evidence.
- CR Demo Coffee Ltd settlement account at Meridian Bank — EUR 42.50
Evidence & review / 07
Evidence & review
Dispute handling on four-party card schemes generally; reason codes, time limits, evidence lists, and fees are scheme-specific and change over time.
What this brief simplifies: Presents one generic lifecycle with scheme-neutral stage names and no exact time limits or fee amounts; fraud-monitoring programmes and scheme-specific cycle variations are out of scope.
Sources for this brief2
- Market practiceMarch 2003 edition
A glossary of terms used in payments and settlement systems ↗ — CPSS (now CPMI), Bank for International Settlements
Terminology has evolved since this edition; newer CPMI publications refine some definitions.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.