Compelling evidence 3.0

What is compelling evidence?

Compelling evidence is the documentation a merchant submits to prove that a

disputed transaction

was valid and authorized by the

cardholder

. Card networks define which records qualify for each dispute type, and the

issuer

reviews them before deciding whether to reverse the

chargeback

Evidence requirements are tied to the

chargeback reason code

the issuer filed under. A claim that goods never arrived is answered with delivery records, while a claim that the cardholder never authorized the purchase is answered with data linking the same account, device, and IP address to earlier undisputed purchases. Documentation that doesn't map to the reason code carries no weight, however convincing it reads.

Compelling evidence enters the

chargeback process

once the issuer files the dispute, and the merchant answers within the window the scheme sets for that reason code.

Key facts

Also known as: dispute evidence, representment evidence
Submitted by: the merchant, through its
acquirer
or payment provider
Reviewed by: the issuer, which either reverses the chargeback or upholds it
Governed by: each
card network
's dispute rules, which list the required fields per reason code
Delivered as: an evidence package attached to a
chargeback rebuttal letter
Response window: set by the scheme and the reason code, counted from the date the chargeback is filed

Types of compelling evidence

Proof of delivery: carrier tracking, signature confirmation, and a shipping address matched by
address verification service
(AVS)
Digital fulfilment records: download logs, login timestamps, session IP addresses, and proof the account used the purchased service after the charge
Purchase history: earlier undisputed transactions carrying the same cardholder account, device ID, or IP address
Customer communication: emails, chat transcripts, and support tickets in which the cardholder confirms receipt or asks for service
Consent records: signup terms, subscription confirmations, and the cancellation policy accepted at checkout
Identity signals: device fingerprint,
card verification value
(CVV) and AVS match results, and the authentication result returned at checkout

Visa's Compelling Evidence 3.0 standard formalizes the purchase-history category for reason code 10.4 (other fraud, card-absent environment), matching device ID, IP address, and login credentials from prior undisputed transactions against the disputed one. For the full breakdown, see

Visa Compelling Evidence 3.0 (CE3.0)

Why it matters

The issuer rules on the file in front of it, so how the evidence package is assembled decides the case as much as the underlying sale does. Two merchants holding identical delivery records can get opposite outcomes when only one maps its documents to the fields the reason code lists.

A response that omits the fields the reason code requires is closed in the cardholder's favor, and the merchant absorbs the transaction amount on top of the
chargeback fees
the acquirer already deducted.
Evidence that meets the issuer's threshold reverses the chargeback and returns the funds. If the issuer rejects it, the case can move to
pre-arbitration
and then arbitration, where scheme filing fees apply on top of the disputed amount.
Fraud-coded disputes answered with matched purchase-history data are where
friendly fraud
gets separated from genuine fraud, since the same account, device, and IP address appear on transactions the cardholder never questioned.