What is
Compelling evidence?

The short answer

"Compelling evidence" is card-network shorthand for the specific types of documentation a merchant can submit to win a chargeback representment. Each network (Visa, Mastercard, Amex, Discover) defines its own evidence categories in its operating rules. Submitting generic proof — "the customer bought it" — does not win. Submitting the specific evidence categories the network defines for the specific chargeback reason code does.

Visa CE 3.0 (launched April 2023)

Visa's "Compelling Evidence 3.0" is the most merchant-favorable evidence standard in card networks today. For disputes under reason code 10.4 (fraud — card-absent environment), a merchant can win by submitting evidence of two prior undisputed transactions from the same cardholder:

• Two transactions at least 120 days old
• Same card number as the disputed transaction
• Same merchant account
• Same IP address, device ID, shipping address, or account login
• No prior chargebacks on those two transactions

If you have two clean prior transactions meeting these criteria, Visa CE 3.0 shifts liability back to the issuer. You win. This is the single highest-leverage representment tool in the card network ecosystem right now.

Mastercard First-Party Trust (October 2023)

Mastercard's analog to Visa CE 3.0. For first-party fraud claims (reason code 4837 / 4863), merchant can submit:

• Proof of prior undisputed relationship (similar to Visa)
• Customer login metadata tying the disputed transaction to the cardholder's account
• Delivery confirmation to an address the cardholder has used before
• Session data showing the cardholder authenticated before the purchase

Generic compelling evidence (applies across networks)

• Signed delivery confirmation to the cardholder's billing address (physical goods).
• IP address + geolocation matching the cardholder's known locations.
• Device ID fingerprint matching the cardholder's prior sessions.
• Email correspondence where the customer acknowledged the purchase or received confirmation.
• Login timestamps + account activity showing the cardholder used the product after the charge.
• Refund policy acceptance. Screenshot of the checkout showing the customer checked a box agreeing to the refund policy.
• 3DS authentication records. If the charge was authenticated via 3DS 2.0, liability shifts to the issuer.
• Prior successful transactions. Especially under Visa CE 3.0 rules.

What does NOT count as compelling evidence

• "The customer bought it and we shipped it" — without documentation of each step
• Screenshots with no timestamps or no URL context
• Signed terms of service not specifically tied to this transaction
• Account emails sent to a different address than the one on file
• Delivery confirmation to an address different from the billing address (unless the cardholder provided it)

Operational workflow

1. Chargeback lands. You have 10-30 days to respond depending on network and reason code.
2. Identify the reason code. Each code has its own evidence requirements. Don't submit fraud evidence on a "goods not received" dispute.
3. Pull the evidence templates. Every acquirer has templates organized by reason code. Use them.
4. Submit through the chargeback portal. Your processor or acquirer provides one.
5. Track outcome. Wins remove the chargeback from your ratio. Losses stay on it.

Why multi-brand operators care

Every dispute you win via compelling evidence keeps your chargeback ratio clean, keeps you out of VAMP / ECM, and preserves your acquirer relationship. For operators at scale, 30-50% representment win rates are achievable with disciplined evidence submission. On $500k/mo volume, that's the difference between steady processing and an acquirer termination letter.