Chargeback process
What is the chargeback process?
Chargeback process is the sequence of steps a card payment goes through once it's disputed, from the 's initial claim with their bank to the final decision on who absorbs the loss. It runs on card scheme rules rather than merchant policy, so each stage carries a defined response window and a fixed set of participants.
A is usually raised by the cardholder, though the issuing bank () can file one itself for technical reasons such as a processing error or a duplicate charge. From there the case moves between five parties: the cardholder, the , the issuer, the acquiring bank (), and the card network once a case escalates past the issuer's own decision. Each handoff carries a deadline set by scheme rules.
Key facts
- Also known as: dispute process, lifecycle
- Triggered by: a cardholder claim filed with the issuer, or an issuer-initiated filing for a technical error
- Participants: cardholder, merchant, issuer, acquirer, card network
- Coded by: a assigned at filing, which sets the evidence the issuer expects back. Fraud claims in a card-absent environment map to Visa 10.4 and Mastercard 4837.
- Filing window: varies by scheme and reason code. Visa's dispute rules allow up to 120 days from the transaction date for most fraud and consumer dispute categories.
- Possible outcomes: merchant accepts, representment reverses the chargeback, the issuer files a , or the network rules in
How it works
- The cardholder files a dispute. The cardholder contacts the issuer and states why the charge is wrong. The issuer assigns a reason code, which determines the rules the rest of the case follows.
- The chargeback reaches the merchant. The issuer pulls the funds through the network from the acquirer, which debits the merchant and sends a with the reason code and the response deadline attached.
- The merchant accepts or challenges. Accepting closes the case: the cardholder keeps the money and the debit stands. Challenging moves the case to representment.
- The merchant submits representment evidence. The merchant sends back through the acquirer to the issuer, matched to what the reason code calls for. The issuer reviews it and decides whether to reverse the chargeback.
- The issuer upholds or reverses. A returns the funds to the merchant. If the issuer upholds the dispute, it can file a second chargeback, and the case moves into .
- The network rules. In arbitration the card network issues a binding decision and assigns the case fees to the losing side.
Why it matters
- Missing a response deadline isn't neutral. A chargeback that goes unanswered is accepted by default, which makes it permanent and non-contestable regardless of the evidence the merchant holds.
- Evidence is judged against the reason code, not against the merchant's version of events. A response that documents delivery won't reverse a dispute filed as unauthorised use.
- Disputes count toward the merchant's at the point they're filed, and that filed count is what measure.
- Each escalation stage adds , and arbitration adds a network fee charged to whichever side loses the ruling.
Common issues
- Deadlines differ by scheme and stage. A that's valid for one network's reason code doesn't transfer to another, and third-party alerts or deflection services change when a merchant first hears about a case.
- . A cardholder disputes a purchase they actually made, so the merchant is defending a transaction that was authorised and delivered correctly.
- Thin transaction records. Representment depends on data captured at the time of sale, and evidence that was never collected can't be produced months later. A arriving before a formal dispute is the earliest point at which those records are called for.
