Dispute Evidence
What Is Dispute Evidence? Definition and How It Works
Definition
Dispute evidence is the documentation and information a merchant submits when contesting a chargeback, demonstrating that the transaction was valid, the goods or services were delivered as described, or the cardholder's claim is not supported by the facts. The quality and completeness of dispute evidence directly determines the outcome of chargeback representment: strong evidence wins disputes; weak or missing evidence results in the chargeback being upheld and the merchant losing the transaction amount.
How it works
Dispute evidence is assembled in response to a specific chargeback reason code. Each reason code (representing a different type of dispute: fraud, non-delivery, not as described, duplicate charge, subscription cancellation) requires different categories of evidence, and the merchant must provide evidence that specifically addresses the reason stated in the chargeback.
For fraud chargebacks (where the cardholder claims the transaction was unauthorised), relevant evidence includes: 3DS authentication records confirming the issuer authenticated the cardholder; AVS and CVV match results confirming the card details were verified; delivery confirmation with signature for physical goods; IP address and device data consistent with the cardholder's location and device profile; and prior transaction history with the same cardholder showing consistent purchase patterns.
For non-delivery chargebacks (goods not received), evidence includes: shipping tracking records confirming delivery to the address on file; carrier proof of delivery with recipient signature; communication records (emails, chat logs) showing the customer acknowledged receipt or requested delivery changes; and for digital goods, server logs showing the download or access event.
For not-as-described chargebacks, evidence includes: the original product listing or description at the time of purchase; photographs or documentation confirming the item was accurately described; communication records showing the customer did not raise a quality concern before filing the chargeback; and refund policy documentation confirming the policy was disclosed at checkout.
Dispute evidence is submitted within scheme-specific deadlines (typically 20 to 45 days from the chargeback notification date). Late submissions are rejected regardless of quality.
Why it matters
Win rates on chargeback representment vary from below 20% for merchants submitting weak or generic evidence to above 60% for merchants with strong, case-specific documentation. The quality of evidence gathering and management systems determines whether a merchant recovers transaction revenue from disputed transactions or absorbs the loss. At meaningful chargeback volumes, this difference is financially material.
Dispute evidence requirements are determined by the chargeback reason code, which is set by the issuer and may not accurately reflect the cardholder's actual complaint. A merchant receiving a fraud chargeback on a transaction where the cardholder genuinely received the goods but simply does not recognise the charge (a friendly fraud pattern) must submit evidence addressing the fraud claim, not the delivery question. Understanding the specific evidence required for each reason code is essential for representment success.
Proactive dispute prevention through strong transaction documentation reduces the evidence burden. Merchants who collect delivery signatures, send order confirmation emails with clear merchant descriptor information, and use 3DS authentication generate the evidence at transaction time without needing to reconstruct it during a dispute. The cost of prevention is lower than the cost of assembling evidence post-hoc.
With PXP
PXP centralises dispute data and transaction-level evidence to support representment within scheme deadlines. Talk to our team about how PXP can support your dispute management.
Frequently asked questions
What happens if a merchant misses the dispute evidence deadline?
Missing the dispute evidence submission deadline results in the chargeback being automatically upheld in the cardholder's favour. The merchant loses the transaction amount, the dispute fee, and any associated costs. Scheme deadlines are strict and non-negotiable: evidence submitted one day late is treated identically to no evidence at all. Merchants should build automated alerts into their dispute management workflows to ensure representment responses are initiated immediately upon chargeback notification.
What is the difference between a retrieval request and a chargeback?
A retrieval request (also called a copy request) is the issuer asking the merchant for transaction documentation before a formal chargeback is filed. The cardholder has queried a transaction and the issuer wants to see the original sales receipt or transaction evidence to resolve the query. If the merchant responds with satisfactory evidence, no chargeback is filed. If the merchant fails to respond or the evidence is insufficient, the issuer may then file a chargeback. Retrieval requests are an early warning opportunity to resolve disputes before they become chargebacks.
How does 3DS authentication help win fraud chargebacks?
3DS authentication records provide cryptographic evidence that the cardholder's issuer authenticated the transaction at the time of payment. When a cardholder files a fraud chargeback claiming they did not authorise a transaction that was authenticated via 3DS, the merchant can submit the authentication record as evidence. Under the liability shift rules of 3DS, an authenticated transaction shifts liability to the issuer: the issuer authenticated the cardholder and authorised the transaction, so the issuer bears the fraud cost rather than the merchant. A strong 3DS authentication record is among the most powerful fraud chargeback evidence available.
Revolutionize your business with PXP
Take complete control of your commerce and payments with one platform.
Get Started