Visa Compelling Evidence 3.0 (CE 3.0) is Visa's rule for answering "I didn't make this purchase" disputes from buyers who did, in fact, buy from you before. It applies to one reason code, Visa 10.4, and it turns a customer's own purchase history into evidence. This guide covers the qualifying criteria, what CE 3.0 changes, and how to use it on Stripe.
What CE 3.0 is for
Reason code 10.4, Other Fraud: Card-Absent Environment, is the most common fraud code for online stores. Many of these disputes are not stolen cards. They are buyers who forgot the order, a family member who used the card, or someone who regrets the purchase. Stripe describes CE 3.0 as a tool to fight this kind of first-party misuse, often called friendly fraud.
The rule took effect in April 2023 (Qualpay's notice gives April 18, 2023). Before it, showing a buyer's earlier orders was a judgment call for the issuer. CE 3.0 defines exactly what history counts, so the evidence is either qualifying or not.
The qualifying criteria
Stripe's documentation lists the conditions a dispute must meet:
- The disputed payment is a Visa transaction with reason code 10.4.
- There are at least two earlier transactions on the same payment method that were paid and not disputed. Validation charges (card checks) do not count.
- Those earlier transactions are 120 to 365 days older than the disputed one. Stripe's support article says 120 to 365 calendar days before the disputed transaction's processing date; Stripe's API guide says 120 to 364 days. Aim for the narrower window if you are building your own matching.
- You give a product description for the disputed payment and for each earlier one, and say whether the disputed one was merchandise or services.
- The disputed payment and both earlier ones match on the required data elements, below.
Which data elements must match
| Main elements | Secondary elements |
|---|---|
| Customer purchase IP address | Shipping address |
| Customer device fingerprint or device ID | Customer email address |
| Customer account ID (login) |
All three transactions must match on either two main elements, or one main element and one secondary element. So at least one of IP address or device ID is always required. Stripe adds one trap: device fingerprint and device ID together are not a valid pair, because they count as the same main element.
The common failure is not the history, it is the data. Stores that do not save the buyer's IP address or account ID on each order cannot prove the match, even when the buyer has ordered ten times.
What CE 3.0 shifts
CE 3.0 works at two points.
After a dispute is filed
You submit the CE 3.0 data as part of your response. Stripe says qualifying evidence increases the chance that the issuer reverses the dispute in your favor, but it does not guarantee an automatic win. Stripe also notes a rare catch: if an issuer later files a delayed fraud report on one of the earlier transactions, that transaction can stop qualifying.
Before a dispute is filed
If you are enrolled in Visa's Order Insight, an issuer's agent can look up the transaction while the buyer is on the phone or in their banking app. Stripe's documentation says Visa then selects the 2 to 5 most recent non-fraud earlier transactions and asks for data on them. If at least two have complete product descriptions, matching IP addresses and at least one matching email or delivery address, the issuer must block the dispute. No dispute is filed, so there is no dispute fee and nothing added to your dispute rate. Stripe lists a Visa Compelling Evidence 3.0 block at USD 15 each on its US pricing page.
Effect on VAMP
Visa's VAMP fact sheet excludes fraud reports (TC40) that qualify for Compelling Evidence 3.0 from the VAMP ratio, "contingent on the timing of the data extract". For stores near a monitoring threshold this matters as much as the dispute itself. See the Visa VAMP guide.
How Stripe supports CE 3.0
Stripe checks your payment history for qualifying transactions automatically, flags eligible disputes in the dispute email and a Dashboard banner, and fills in what it can. All the earlier transactions must have been processed on Stripe.
In the API, the data lives in evidence.enhanced_evidence.visa_compelling_evidence_3:
disputed_transaction: the customer's purchase IP, device ID, email, account ID and shipping address, plusproduct_descriptionandmerchandise_or_services.prior_undisputed_transactions: an array with thechargeID of each earlier payment, its matching data elements and itsproduct_description.
The dispute's enhanced_eligibility_types includes visa_compelling_evidence_3 when it applies. Progress shows inevidence_details.enhanced_eligibility.visa_compelling_evidence_3:
| Status | What it means |
|---|---|
requires_action | Something is missing. The required_actions array names it, for example missing_merchandise_or_services. |
qualified | The evidence meets the rules and is ready to submit. |
not_qualified | After submission, the evidence did not qualify. It is still sent, through the normal evidence flow. |
Three practical rules from Stripe's documentation:
- Leave the autofilled values alone. Stripe's support article warns that editing them can affect whether the matched transactions still qualify.
- Fill in the regular evidence too. If CE 3.0 does not qualify, the dispute goes through the standard flow and only the normal evidence fields are used. The Stripe dispute response guide covers those.
- Stage before you submit. Updating with
submit: falsesaves the evidence without sending it. In test mode, card 4000000404000038 creates a CE 3.0 eligible dispute.
What to set up now
- Save the buyer's IP address on every order, with the order record, not only in server logs.
- Encourage accounts or logins for repeat buyers, and keep the account ID with the order.
- Save a device ID or fingerprint if your checkout or fraud tool provides one.
- Write product descriptions a buyer would recognize, not internal SKUs. They show up both in CE 3.0 data and in Order Insight lookups.
- Keep at least 13 months of order data, so the 120 to 365 day window is always covered.
CE 3.0 only helps buyers with history. For first-time buyers disputing as fraud, the usual 10.4 evidence still applies: 3D Secure results, AVS and CVC checks, and the buyer's own messages. A buyer who wrote to your support asking where the parcel was is hard to call a stranger, which is where a helpdesk that keeps the conversation with the order earns its place. The rebuttal letter guide shows how to put it together.
Questions
What is Visa Compelling Evidence 3.0?
A Visa rule, in force since April 2023, for fraud disputes under reason code 10.4. If the same card paid you at least twice before, 120 to 365 days earlier, without disputing, and those orders match the disputed one on specific data such as IP address or device ID, you can show the buyer has a history with you.
Which disputes does CE 3.0 apply to?
Only Visa reason code 10.4, Other Fraud: Card-Absent Environment. It does not apply to not received, not as described or other consumer disputes, or to Mastercard, Amex or Discover.
Does CE 3.0 guarantee I win?
No. Stripe says qualifying evidence does not guarantee an automatic win; the issuer still decides. Before a dispute is filed, though, a qualifying Order Insight response requires the issuer to block the dispute.
Does CE 3.0 help with Visa VAMP?
Yes. Visa's VAMP fact sheet excludes fraud reports (TC40) that qualify for Compelling Evidence 3.0 from the VAMP ratio, depending on when the data is extracted.
How do I use CE 3.0 on Stripe?
Stripe flags eligible disputes and fills what it can in evidence.enhanced_evidence.visa_compelling_evidence_3. You add product descriptions and merchandise or services, check evidence_details.enhanced_eligibility for required actions, and submit when the status is qualified.
Sources: Stripe: Visa Compelling Evidence 3.0 disputes,Stripe support: how Stripe supports CE 3.0,Stripe: how dispute prevention works,Stripe pricing (US),Visa VAMP fact sheet andQualpay: CE 3.0 and April 2023 changes, checked October 29, 2026.
Keep the evidence before you need it
Rebutdesk is an open-source helpdesk where Stripe and PayPal disputes open inside the buyer's support case, so the conversation, refunds and shipping events are already in order when the deadline starts. See how it works.
14 days free, no card needed. Already have an account? Sign in
More guides
- How to write a chargeback rebuttal letter
- How to respond to a Stripe dispute
- PayPal disputes for sellers: how to respond and win
- American Express chargebacks: how inquiries and disputes work
- PayPal chargebacks: what happens when the buyer goes to their bank
- Shopify chargebacks: how to respond and what Shopify does for you
- Chargeback time limits by card network
- Chargeback representment: what it is and how to win it
- Pre-arbitration chargebacks: what happens after your first response
- Chargeback vs refund: what's the difference for merchants?
- Chargeback fees: who pays and how much
- Billing descriptors: how to stop 'I don't recognize this charge' disputes
- Chargeback alerts: Ethoca, Verifi CDRN and Rapid Dispute Resolution
- Visa VAMP: the ratio, thresholds and fees for merchants
- Customer service email templates for online stores
- How does a chargeback work? The process from dispute to decision
- PayPal Seller Protection: what it covers and how to qualify
- Credit card decline codes: what each one means and when to retry
- Friendly fraud: what it is, how to spot it and how to win
- Ecommerce customer service: a playbook that also prevents chargebacks