The Card Dispute Lifecycle: From Reason Code to Arbitration (2026)

The card dispute lifecycle is the sequence of steps a contested card payment follows under scheme rules: the cardholder’s claim, the issuer’s dispute with a reason code, the merchant’s response with evidence, a second exchange called pre-arbitration, and, if the parties still disagree, a final ruling by the card network.

For PSPs, PayFacs and platforms, managing this lifecycle is a daily operation in 2026. Dispute volumes keep rising, deadlines are short, and each lost case counts in scheme monitoring ratios. Merchants expect their provider to tell them which cases are worth fighting, to collect the right evidence and to submit it in time. Operators that handle disputes by email lose cases they could win.

What is the card dispute lifecycle?

The card dispute lifecycle is the formal process by which an issuer contests a transaction on behalf of a cardholder and the acquirer responds on behalf of the merchant. Each card network defines its own stages, reason codes, evidence rules and deadlines.

Visa organizes disputes in four categories, set out in its Dispute Management Guidelines for Visa Merchants: Fraud (category 10), Authorization (11), Processing Errors (12) and Consumer Disputes (13). Since April 2018 all Visa disputes run through the Visa Claims Resolution process, with two workflows. Fraud and authorization disputes follow "allocation", where liability is assigned from transaction data. Processing errors and consumer disputes follow "collaboration", where the parties exchange information.

Mastercard’s Chargeback Guide describes a cycle with a chargeback, a second presentment by the acquirer, a pre-arbitration case and an arbitration case.

The process exists because cards promise something cash does not: a cardholder who is charged wrongly can get the money back without going to court. The networks act as a private dispute system between issuers and acquirers. Cardholders and merchants are not parties to it directly. They are represented by their bank and their acquirer, which is why the quality of the acquirer’s or PSP’s dispute handling matters so much to a merchant.

Related notions:

• Dispute: the generic term, used by Visa, for a transaction contested by the issuer.
• Chargeback: the reversal of funds from the acquirer to the issuer that a dispute triggers. See our episode on the chargeback.
• Reason code: the code that states why the transaction is contested.
• Representment: the merchant’s response with evidence. Visa calls it a dispute response, Mastercard a second presentment.
• Compelling evidence: documents or data that show the cardholder took part in the transaction or received the goods.
• Pre-arbitration: a second exchange between issuer and acquirer before the network is asked to rule.
• Arbitration: the final decision by the card network.
• First-party misuse: a dispute raised by the genuine cardholder on a legitimate purchase, also called friendly fraud.

Visa vs Mastercard: how do the dispute stages compare?

Both networks follow the same logic with different names. The list below aligns the stages.

• Stage 1, the claim: Visa calls it a dispute. Mastercard calls it a chargeback. The issuer sends it with a reason code and the merchant’s account is debited.
• Stage 2, the merchant’s answer: a dispute response at Visa, in the collaboration workflow. A second presentment at Mastercard.
• Stage 3, the second exchange: pre-arbitration at both networks. In Visa’s allocation workflow, the merchant’s first answer is already a pre-arbitration, because liability was assigned at the start.
• Stage 4, the ruling: arbitration, decided by the network. The losing party pays the disputed amount and the filing fees.
• Fraud reason codes: Visa uses 10.1 to 10.5. Mastercard uses 4837 for no cardholder authorization and 4870 and 4871 for chip liability shift.
• Consumer dispute codes: Visa uses the 13 series. Mastercard uses 4853 for cardholder disputes.
• Other Mastercard families: 4808 for authorization-related chargebacks and 4834 for point-of-interaction errors.

The reason code shapes everything that follows. A fraud code asks whether the cardholder took part in the transaction. A consumer dispute code asks whether the merchant delivered what was promised. A processing error code asks whether the transaction was submitted correctly. The evidence, the workflow and the chance of success all depend on which question is asked.

Most disputes never reach stage 3. The merchant accepts the loss or wins at stage 2. Arbitration is rare, because the fee often exceeds the amount at stake.

How does the dispute lifecycle work step by step?

A dispute moves between the same parties as the original payment, in the opposite direction. The steps are:

1. Complaint. The cardholder contacts the issuer about a transaction: not recognized, not received, not as described, charged twice or cancelled.
2. Pre-dispute. Where the merchant is enrolled, the issuer’s inquiry can be answered or refunded before a dispute exists, through the tools described in RDR and CDRN.
3. Dispute. The issuer files the dispute with a reason code. The network debits the acquirer, which debits the merchant and usually adds a fee.
4. Notification. The acquirer informs the PSP or payment facilitator, which informs the merchant with the reason code and the deadline.
5. Decision. The merchant accepts the dispute or decides to contest it.
6. Representment. The merchant submits evidence through its PSP and acquirer. The network returns the funds to the acquirer provisionally.
7. Issuer review. The issuer accepts the response, or continues with pre-arbitration and new information from the cardholder.
8. Pre-arbitration response. The acquirer accepts liability or declines.
9. Arbitration. One party asks the network to rule. The network reviews the file and assigns liability and fees.

The dispute lifecycle in numbers (2026)

Volumes, costs and deadlines are documented by the networks. Key figures:

• 261 million: chargebacks estimated worldwide in 2025, expected to reach 324 million in 2028, according to Mastercard’s analysis of the cost of chargebacks, which values them at 33.79 billion dollars in 2025.
• USD 9.08 to 10.32: cost for an issuer to process one disputed transaction, in the same analysis. The average chargeback is worth 110 dollars in the US.
• 120 days: Visa’s usual dispute window, counted from the transaction or from the expected service date, up to 540 days from processing in some cases.
• 30 days: time to challenge a Visa dispute since Visa Claims Resolution shortened it, according to a J.P. Morgan briefing on dispute resolution. Acquirers give merchants less.
• USD 600: filing fee for the party that takes a Visa case to arbitration, charged on top of the dispute amount, according to Adyen’s documentation on Visa chargebacks.
• 79%: share of merchants who say card brand compelling evidence updates have blocked friendly fraud disputes, in the 2025 Global eCommerce Payments and Fraud Report.

What are the risks and limits of the dispute lifecycle?

The process is designed to protect cardholders, and it puts the burden of proof on the merchant.

• Short deadlines. A response sent one day late is lost, whatever the evidence.
• Evidence gaps. Merchants often lack what the reason code requires: proof of delivery, proof of use, a signed agreement or the refund policy shown at checkout.
• First-party misuse. Genuine customers dispute legitimate purchases. Visa’s Compelling Evidence 3.0, in effect since April 15, 2023 for fraud disputes on card-absent transactions, lets a merchant show two earlier undisputed transactions with the same customer. They must be between 120 and 365 days old and share at least two data elements, one of which is the IP address or the device ID.
• Authentication changes liability. A transaction authenticated with 3-D Secure generally moves fraud liability to the issuer, as explained in 3-D Secure and SCA exemptions. Without it, fraud disputes are hard to win.
• Every dispute counts. A case won in representment still counts in monitoring ratios. See card scheme monitoring programs.
• Cost of fighting. Fees, staff time and arbitration risk mean that small disputes are often cheaper to accept.
• Legal rights on top. National law can give cardholders further claims. In the UK, covered in our guide to payment methods in the United Kingdom, credit card purchases also carry statutory protection that is separate from scheme rules.
• Network differences. Each network has its own codes, stages and deadlines. A process built for one does not fit the others.

The dispute lifecycle: what changes for PSPs, PayFacs and platforms

Operators stand between acquirers and merchants at every step. Five areas decide the outcome.

Notification and deadlines

Dispute data arrives from each acquirer in its own format. The operator must normalize it, calculate the real deadline for the merchant and send reminders. Platform supervision should show open cases, due dates and status for the whole portfolio.

Prevention before the dispute

The cheapest dispute is the one that never opens. Pre-chargeback alerts let a merchant refund or answer an inquiry before a dispute is filed. The articles on automatic transaction matching for pre-chargeback alerts and on manual matching explain why speed matters at this stage. The choice between refund and dispute is covered in refund vs reversal vs chargeback.

Evidence collection

Each reason code calls for specific evidence. An operator that stores order data, authentication results, device information, delivery confirmation and customer messages with the transaction can assemble a response in minutes. Templates per reason code help merchants send what the issuer will read.

Merchant experience

Merchants see disputes as lost money and lost time. A clear case page helps: what the customer claims, what evidence is expected, how long remains and what the likely outcome is. Automatic acceptance below a set amount, chosen by the merchant, removes the cases nobody should spend time on.

Triage

Not every dispute should be contested. Rules based on amount, reason code, evidence available and past win rate tell merchants where effort pays. For a PayFac, the decision may sit with the facilitator when sub-merchants are small.

Reporting and learning

Win rates per reason code, per issuer and per merchant show what causes disputes: unclear descriptors, late delivery, weak cancellation flows. Mastercard’s First-Party Trust program, announced in October 2023, and Visa’s compelling evidence rules both reward merchants that share good data. The #TheShot episode Efficiency vs protection: finding the balance discusses the trade-off, and the Payments Library lists the Fraudology podcast for practitioners.

Is fighting disputes worth it in 2026?

Sometimes. Prevention pays almost always, representment pays when the evidence matches the reason code, and arbitration pays rarely. The rules now favor merchants who keep data: authentication results, device and account history, delivery proof. They also favor speed, since inquiries answered within hours often never become disputes. An operator’s value lies in making both possible for merchants that have neither a dispute team nor the tools. What it means by player:

• PSPs: give merchants one dispute workflow across acquirers and networks, with deadlines calculated for them.
• PayFacs: decide who handles disputes for small sub-merchants, and track ratios per sub-merchant and for the portfolio.
• ISOs: make sure merchants know where dispute notices arrive and how fast they must answer.
• ISVs and platforms: keep order, delivery and customer data linked to each payment, because that is the evidence.

The dispute lifecycle gives each side a turn to speak, and merchants who can show proof quickly rarely need the last step.