GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
04 / CARDS & MERCHANT PAYMENTS15 MIN

Disputes and chargebacks

What happens when a cardholder disputes a charge: reason codes, the chargeback, the merchant's representment, and where liability finally lands.

NOT STARTED

L0 Explain simply

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.

L1 Core concepts

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.

L2 Practitioner view

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.

L3 Technical details

When representment fails, the formal ladder continues. The issuer that rejects the merchant's evidence can pursue pre-arbitration — a last structured exchange in which one side usually accepts liability — and, failing that, file for arbitration, where the network itself rules on the case and the loser typically pays filing and administration fees that can exceed a small transaction's value. The scheme manuals define the whole state machine: which reason codes exist, what each stage may claim, which documents count, and the time limits at every hop. Two practical consequences follow. First, economics: because arbitration fees are material, most low-value cases end at representment or pre-arbitration by simple cost logic. Second, discipline: the same manuals let networks fine participants who abuse the process — chargebacks raised without eligibility, or representments with recycled evidence — because the dispute system only works while its signals stay honest.

Sources & standards2
  1. Market practiceMarch 2003 edition

    A glossary of terms used in payments and settlement systemsCPSS (now CPMI), Bank for International Settlements

    Standard definitions for payment, clearing, and settlement terminology used across BIS committee reports and referenced by glossary entries on this site. · Checked 2026-07-12

    Terminology has evolved since this edition; newer CPMI publications refine some definitions.

  2. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    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.

SEE THE PAYMENT MOVE

Chargeback lifecycle — swimlane diagramMaya Chen disputes the EUR 42.50 charge from Demo Coffee Ltd. Bank Alfa raises a chargeback, Demo Coffee answers with evidence, and the case decides who bears the loss — through Cardnet, a fictional card network standing in for Visa/Mastercard-style networks. (SYNTHETIC / TRAINING ONLY) The full step-by-step description follows this diagram as text.
MESSAGECLEARING OBLIGATIONSETTLEMENTPOSTING
Chargeback lifecycle. One dispute, one reason code, one round. Real chargeback flows vary by network and reason code — time limits, required evidence, fees and even the number of cycles differ, and network rules generally govern each stage. The provisional-credit and fee movements between the banks are described in prose rather than drawn as lanes. PLAY IT STEP BY STEP →
Read the steps as text
  1. 01Message
    Maya 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.

  2. 02Message
    Bank 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.

  3. 03Message
    Cardnet 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.

  4. 04Settlement
    The 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.

  5. 05Posting
    Meridian 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 BankEUR 42.50
  6. 06Message
    Demo 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.

  7. 07Message
    Meridian 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.

  8. 08Message
    Cardnet 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.

  9. 09Processing
    Bank 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.

  10. 10Settlement
    The 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.

  11. 11Posting
    The 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 BankEUR 42.50
Sources for this topic2
  1. Market practiceMarch 2003 edition

    A glossary of terms used in payments and settlement systemsCPSS (now CPMI), Bank for International Settlements

    Standard definitions for payment, clearing, and settlement terminology used across BIS committee reports and referenced by glossary entries on this site. · Checked 2026-07-12

    Terminology has evolved since this edition; newer CPMI publications refine some definitions.

  2. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    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.

Deepest material on this page: L3 Technical details. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.

COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.
WHAT ARE YOU SHARING?

Public discussion

LOADING

Loading the discussion…