The only multi-party money-reversal system in payments, mapped from the cardholder’s claim to the final allocation of liability.
Payments Architecture 101 touches chargebacks in a single module. This is the deep, standalone treatment of the most operationally painful system in payments, and the only one where liability genuinely moves between four parties.
We map the full lifecycle from the cardholder’s claim to representment and final liability, decode reason codes as a control language, and show how network monitoring programs and consumer-protection timers box in every decision you make.
A practitioner map of who can pull funds back, from whom, and when across the cardholder, issuer, acquirer, and merchant. The dispute mechanism is a settlement reversal, not a customer service decision.
Card-network reason codes are not labels, they are the rulebook that fixes which evidence the network will accept and which it will throw out. Read the code first, then build the case.
Most representments lose on process, not facts. This lesson breaks down how the second presentment actually works inside the four-party system and the procedural discipline that decides the outcome.
How Visa's CE 3.0 rule lets matching historical transaction data move chargeback liability back to the issuer, and how the same logic plays out before a dispute is ever filed.
How Visa and Mastercard measure dispute and fraud performance across the four-party system, the exact ratios and counts that flip a merchant into a program, and the penalty escalation that follows.
Two US consumer-protection rules sit above the card network dispute rules and set hard clocks the issuer cannot negotiate away. This lesson maps Reg E and Reg Z timers onto the four-party flow so you can see where law, not commercial preference, controls the outcome.
When the cardholder disputing a charge is the same person who made it, the dispute system turns against the merchant by design. Here is how first-party misuse moves through the four-party rails and where the mechanism gives you leverage to fight back.
Account-to-account rails settle instantly and irrevocably, which means the card dispute mechanism does not exist there. We map what replaces it, where the recourse gap sits, and what regulators are doing about it.
How to size, staff, and tool a dispute operation so win rate, deadline discipline, and unit cost hold steady as volume grows, with the math to decide build, buy, or outsource.
A practitioner's blueprint for designing the full dispute flow behind a new product, from the data you capture at checkout to the deadlines, automation, and reporting that keep the four-party mechanism working in your favor.