A dispute is a formal challenge to a payment transaction initiated by a cardholder through their issuing bank. When a cardholder contacts their issuer to question or contest a charge, the issuer opens a dispute case and begins an investigation process governed by card network rules. Depending on the outcome of that investigation, the dispute may result in a chargeback, where funds are reversed from the merchant, or it may be resolved in the merchant’s favor and closed without a reversal.
Disputes and chargebacks are closely related but technically distinct. A dispute is the broader process of contesting a transaction. A chargeback is the specific financial outcome of a dispute that results in a fund reversal. Not all disputes result in chargebacks — some are resolved through retrieval requests, pre-arbitration, or direct merchant-issuer communication before a formal reversal is issued.
Merchants who respond to disputes promptly and with compelling evidence have the best chance of preventing disputes from escalating into chargebacks and of winning representment when chargebacks do occur.
Diving Deeper into Dispute
The dispute process is the formal mechanism through which cardholders exercise their right to contest transactions under card network rules. It is one of the foundational consumer protections built into the card payment system and a significant operational consideration for merchants who accept card payments at scale.
Understanding the dispute lifecycle, the different ways disputes can be resolved, and how dispute management differs from chargeback management helps merchants protect their revenue more effectively and maintain healthy relationships with their acquiring banks.
The Dispute Lifecycle
A dispute begins when a cardholder contacts their issuing bank to question a charge on their account. The cardholder may not understand a charge, may believe it is fraudulent, or may have a legitimate grievance about goods or services received. The issuer’s first obligation is to investigate the claim.
Retrieval Request
In some cases, before initiating a formal chargeback, the issuer may send a retrieval request to the merchant’s acquirer asking for documentation about the transaction. A retrieval request is a request for information, not a chargeback. The merchant has a defined window to respond with transaction records, signed receipts, or other documentation. Responding to retrieval requests promptly can prevent disputes from escalating to chargebacks.
Retrieval requests have become less common as card networks have streamlined their dispute processes, but they still occur in certain dispute categories and with certain issuers.
Pre-Dispute and Dispute Notification
When the issuer determines a dispute has merit, they formally initiate the dispute and notify the acquiring bank. The acquirer passes the dispute notification to the merchant along with the dispute reason code, transaction details, and response deadline. This is the point at which the merchant must decide whether to accept the dispute or contest it.
Merchant Response
If the merchant accepts the dispute, the chargeback is processed and funds are reversed. If the merchant contests the dispute, they submit a representment package containing evidence that the transaction was valid. The quality and relevance of the evidence submitted at this stage largely determines the outcome.
Dispute Reason Codes
Card networks assign reason codes to disputes that indicate the cardholder’s stated basis for the dispute. These codes govern the dispute timeline, the type of evidence required for a successful representment, and whether liability shift applies.
Fraud Reason Codes
Fraud codes indicate the cardholder claims they did not authorize the transaction. These are the most common dispute type in card-not-present environments. For transactions where 3D Secure authentication was completed, liability shift typically protects the merchant from fraud chargebacks regardless of the outcome of the dispute.
Authorization Reason Codes
Authorization disputes arise when the transaction was processed without valid authorization, when the authorization was declined but the transaction was processed anyway, or when the transaction amount exceeded the authorized amount beyond permitted tolerances.
Processing Error Reason Codes
These cover duplicate transactions, incorrect amounts, credit not processed, and other technical errors. Processing error disputes are generally straightforward to resolve if the merchant can demonstrate the error was identified and corrected.
Consumer Dispute Reason Codes
Consumer disputes cover non-receipt of goods or services, goods or services not as described, and cancelled recurring transactions. These require the merchant to demonstrate delivery, accurate product representation, or proper cancellation handling depending on the specific reason code.
Dispute Resolution Outcomes
Merchant Wins
If the issuer reviews the merchant’s representment and finds it compelling, the dispute is resolved in the merchant’s favor. The chargeback is reversed and the funds are returned to the merchant. The dispute record remains but does not result in a net financial loss.
Issuer Upholds Dispute
If the issuer reviews the representment and upholds the dispute, the chargeback stands. The merchant can escalate to pre-arbitration or arbitration with the card network, but this is typically only worthwhile for high-value transactions given the cost and administrative burden involved.
Pre-Arbitration
Some card networks have a pre-arbitration stage between the initial dispute response and formal arbitration. Pre-arbitration gives both parties one additional opportunity to present evidence and reach resolution before the card network makes a binding ruling. Merchants who have strong additional evidence not included in their initial representment may benefit from the pre-arbitration stage.
Dispute Management Best Practices
Effective dispute management combines prevention, rapid response, and organized evidence management. Merchants who maintain clean transaction records, delivery confirmations, customer communication logs, and signed authorizations are far better positioned to contest disputes than merchants who reconstruct evidence after a dispute is filed.
Automated dispute management platforms can help merchants track dispute deadlines, organize evidence, and submit responses efficiently. For merchants with high transaction volumes, manual dispute management is operationally unsustainable and increases the risk of missing response deadlines — which results in automatic losses regardless of the merits of the merchant’s case.