Most teams treat a chargeback as an email from a processor and a request to "send proof." That framing hides the part that actually matters: a dispute is a movement of money through the same settlement plumbing that carried the original sale, run in reverse. If you understand where the funds sit at each step and which party has the right to move them, almost every downstream rule in this course stops being arbitrary.
This lesson maps the four-party model and the reversal flow that rides on top of it. We stay at the system level. Merchant-seat tactics for recurring billing live in the sibling course on subscriptions and dispute defense; here we care about the mechanism that applies to every card transaction.
The four parties, and what each one actually controls
A card transaction in the open-loop model involves four distinct roles, plus the network in the middle.
- Cardholder. Holds the card, initiates the purchase, and is the only party who can open a dispute against the issuer.
- Issuer. The bank that issued the card and holds the cardholder's account. It funds the original purchase and, critically, is the party that initiates a chargeback into the system.
- Acquirer. The merchant's bank or processor. It funds the merchant and absorbs the first hit when a chargeback lands.
- Merchant. Sells the goods or services and carries the financial liability at the end of the chain in most dispute scenarios.
The network (Visa, Mastercard, and others) is not a party to the money. It is the switch and the rulebook. It routes messages between issuer and acquirer and adjusts each side's net settlement position, but it does not hold the disputed funds itself.
The single most useful mental model: the issuer pulls funds, the acquirer is debited, and the merchant pays. The cardholder asks; the issuer acts.
Following the money on a normal sale
Before you can reverse a flow, you need to know which direction it ran.
On a card sale, the merchant captures the transaction and the acquirer submits it into clearing, also called first presentment. The network passes the clearing record to the issuer. At settlement, the issuer transfers funds, net of interchange and fees, to the network, which moves funds to the acquirer, which deposits into the merchant account. Clearing happens within hours; settlement typically posts over one to three days depending on batching.
So in steady state the issuer is out the money on behalf of the cardholder, and the merchant has been paid through the acquirer. A dispute exists to undo exactly that position.
The reversal flow, step by step
A chargeback is the issuer reaching back across the settlement rail to recover funds it advanced.
Step 1: The cardholder claims, the issuer initiates
The cardholder contacts the issuer and asserts a problem: fraud, goods not received, not as described, a billing error. The cardholder cannot debit the merchant directly. Only the issuer can act, and it does so by filing a chargeback under a specific reason code (the subject of the next module).
Step 2: The network reverses the settlement entry
When the issuer files, the network adjusts net settlement. It credits the issuer and debits the acquirer for the disputed amount. The Mastercard rulebook describes this plainly: a chargeback resolved in the cardholder's favor debits the transaction amount from the acquirer's net settlement and credits it to the issuer's net settlement. The acquirer is now short the money even though it never benefited from the sale.
Step 3: The acquirer passes liability to the merchant
The acquirer is not going to eat the loss. It debits the merchant's account for the disputed amount, usually plus a chargeback fee. At this point the merchant is funds-negative on a sale it already shipped. This is the moment most merchants first learn a dispute exists.
Step 4: The merchant can fight back through representment
The merchant can re-present the transaction with evidence that the charge was valid. That evidence flows merchant to acquirer to network to issuer, the reverse of the chargeback path. If the issuer accepts it, the settlement entry flips again and the funds return to the merchant. If not, the dispute can escalate to pre-arbitration and arbitration, where the network decides and assigns liability plus fees. Representment and the evidence that wins it are the third module.
A worked example
A cardholder buys a $200 pair of headphones online. The merchant ships, the acquirer settles, and roughly $194 lands in the merchant account after interchange and fees.
Six weeks later the cardholder tells the issuer the headphones never arrived. The issuer files a "merchandise not received" chargeback for $200. The network debits the acquirer's settlement $200 and credits the issuer $200. The acquirer debits the merchant the full $200 and adds a $15 chargeback fee, so the merchant is now $215 down on a $200 sale.
The merchant pulls the carrier's proof of delivery to the cardholder's verified address and submits representment through the acquirer. The issuer reviews it, agrees, and the settlement reverses once more. The merchant recovers the $200, though depending on the network and scheme the chargeback fee may not come back. Same rail, three passes, one mechanism.
When the clock runs, and why timing decides outcomes
Each party operates inside a different clock, and the windows are not symmetric.
The cardholder's right to dispute is bounded by network rules and by law. Under most Visa scenarios the cardholder has up to 120 days from the transaction or expected delivery date to dispute, with shorter windows for some categories. Separately, US Regulation Z, implementing the Fair Credit Billing Act, gives credit cardholders a statutory billing-error right when they notify the issuer in writing within 60 days of the first statement showing the error. Network rules and the regulatory overlay run in parallel, and the regulatory side is module six.
The merchant's clock is the tightest. Network response windows for representment are measured in days, not months, and missing the deadline forfeits the funds regardless of how strong the evidence is. A dispute lost on a calendar is the most avoidable loss in the entire flow.
The takeaway
A card dispute is a reversal of a settlement entry, executed by the network, initiated by the issuer, absorbed first by the acquirer, and ultimately carried by the merchant unless representment succeeds. The cardholder triggers it but never touches the merchant's money directly. Hold that flow in your head and the reason codes, evidence standards, monitoring programs, and regulatory rules in the rest of this course all attach to a structure you already understand.