# Visa Compelling Evidence 3.0: The Two Prior Transactions That Shift Liability

Source: https://bondproof.com/blog/2026-11-15-visa-compelling-evidence-3-chargebacks.html

[Home](../index.md) / [Blog](index.md)


November 15, 2026 - BondProof

**Short answer:** Under Visa's Compelling Evidence 3.0, a merchant can challenge a reason code 10.4 fraud dispute by showing the cardholder completed two or more earlier undisputed transactions on the same device, IP address, or shipping address. If the evidence matches, liability shifts back to the issuer. The catch is the evidence library: without one, the framework is unusable.

## What CE 3.0 actually does

Compelling Evidence 3.0 is Visa's framework for fighting card-absent fraud disputes under reason code 10.4. The idea is simple and, for once, favorable to merchants who keep records. If the cardholder previously completed two or more transactions with you that were never disputed, using the same device ID, IP address, or shipping address as the disputed transaction, you can present those as compelling evidence that the cardholder authorized this one too. When the evidence qualifies, Visa allows the liability to shift back to the issuer, even when the cardholder claims the transaction was unauthorized.

Early adopters report 30 to 40 percent improvements in win rates on fraud-related chargebacks, according to the representment guides tracking the framework. That number is plausible precisely because the bar is mechanical: two matching prior transactions, not a judgment call about whether the buyer looks honest. The framework rewards the merchant who can produce the records on demand, and it does nothing for the merchant who cannot.

## Why most merchants cannot use it yet

The blocker is the evidence library. CE 3.0 requires a database of prior transaction details, device IDs, IP addresses, shipping addresses, and login IDs, retrievable quickly when a dispute lands. Visa and Mastercard give merchants a narrow window to file representment, typically 7 to 10 days from notification on the acquirer side, and up to 30 days for Visa and 45 days for Mastercard at the network level. A team that has to dig through three systems to assemble two prior transactions will miss the window or file a thin package.

The second blocker is data retention. Device IDs and IP addresses are exactly the fields privacy teams want to minimize, and the fields CE 3.0 needs you to keep. The merchants who win with CE 3.0 settled that tension in advance: they keep the four qualifying data elements, tied to the transaction, for the life of the dispute window, and they can pull them by cardholder in minutes. Everyone else discovers the gap when the chargeback arrives.

## Build the library before the next dispute

Start with the four elements Visa counts: IP address, device ID or fingerprint, user or login ID, and shipping address. Store them with every transaction, indexed so a dispute pulls the cardholder's history in one query. Then set the alert: when a reason code 10.4 dispute arrives, the first check is whether two prior undisputed transactions match on any of those elements. If they do, file under CE 3.0. If they do not, fight on the other evidence, delivery proof, communication history, and the billing descriptor, and do not waste the window pretending CE 3.0 applies.

One more thing the framework does not do: winning a chargeback does not fix your ratio. Visa's VAMP program counts fraud reports plus disputes when they post, and Mastercard's Excessive Chargeback Program counts first-presentment chargebacks, and neither recalculates for representment outcomes. CE 3.0 recovers the money. Preventing the dispute is what keeps you out of a monitoring program. For the evidence that wins the other kinds of disputes, [friendly fraud chargebacks](https://bondproof.com/blog/2026-11-14-friendly-fraud-chargebacks.md) covers the three-way match between order, device, and delivery, and [the one-dollar charge that is not a sale](https://bondproof.com/blog/2026-11-13-card-testing-small-charges-checkout.md) explains the card-testing pattern that fills your dispute queue in the first place.

## Frequently asked questions

### What is Visa Compelling Evidence 3.0?

It is Visa's framework for fighting reason code 10.4 fraud disputes. A merchant shows the cardholder completed two or more earlier undisputed transactions on the same device, IP address, or shipping address, and if the evidence qualifies, liability shifts back to the issuer.

### How many prior transactions do I need for CE 3.0?

Two or more undisputed transactions using the same device ID, IP address, or shipping address as the disputed transaction. Fewer than two does not qualify, no matter how strong the rest of the evidence is.

### How long do I have to file representment?

Visa allows up to 30 days from the chargeback notification at the network level, and Mastercard up to 45 days, but acquirers usually set a shorter internal deadline, often 7 to 10 days. Confirm your acquirer's deadline before assuming you have the full window.

### Does winning a chargeback fix my dispute ratio?

No. Visa VAMP and Mastercard's Excessive Chargeback Program count disputes when they post and do not recalculate for representment outcomes. Winning recovers the money; preventing disputes is what keeps you out of a monitoring program.

## See your own numbers.

A free bot-traffic audit shows the human-automated split in your live traffic - no code changes, no commitment.

[Get a free bot-traffic audit](mailto:hello@bondproof.com?subject=Free%20free%20bot-traffic%20audit)