Visa Compelling Evidence 3.0 can win fraud chargebacks on your app's web checkout, but only with data you saved months ago
Visa Compelling Evidence 3.0 shifts a card-not-present fraud chargeback to the bank when two earlier undisputed purchases match the disputed one. Here's what qualifies, which data to log today, and what a won or lost dispute costs an app with a web checkout.

Key takeaways
- Visa Compelling Evidence 3.0 only applies to dispute condition 10.4, Other Fraud in a card-absent environment, where the cardholder says they didn't authorize or take part in the purchase.
- To qualify under Visa Compelling Evidence 3.0, a merchant needs at least two earlier undisputed transactions on the same card, made 120 to 365 days before the dispute, with no fraud report attached.
- Visa Compelling Evidence 3.0 works by matching data: the disputed purchase and both earlier purchases must share data elements such as IP address, device ID or fingerprint, account ID, or shipping address.
- When a dispute qualifies under Visa Compelling Evidence 3.0, liability shifts from the merchant to the card issuer, and Visa says the matching fraud record (TC40) is removed.
- A first-time buyer can never qualify for Visa Compelling Evidence 3.0, because Visa says there's no way to build a history of two prior transactions.
- Visa Compelling Evidence 3.0 doesn't apply to App Store or Google Play in-app purchases, where Apple and Google are the merchant and their own evidence flows (CONSUMPTION_REQUEST and orders.reviewrefund) are the only way in.
- On Stripe in the US, a lost dispute costs the charge plus a $15 dispute fee that's never returned, plus a $15 countered fee that comes back only if you win.
Visa Compelling Evidence 3.0 is the one card network rule that lets a merchant beat a "that wasn't me" chargeback with plain log data. If the same card bought from you twice before, between 120 and 365 days earlier, and those purchases match the disputed one on things like IP address, device or account ID, the fraud claim fails and the bank keeps the loss. It's been live since April 2023. It matters more to app developers now, because more of them take card payments directly.
Since Apple's App Review Guidelines stopped requiring an entitlement for purchase links on the United States storefront, a lot of iPhone apps send buyers to a web checkout. Android apps sold on the web were already there. On those sales you're the merchant. The disputes come to you, and so does the chance to win them. The catch is in the rule's design. You can only prove a purchase was real with records you kept long before anyone complained.
What Visa Compelling Evidence 3.0 actually covers
The rule is narrow. Visa's own merchant FAQ says the new remedy applies only to dispute condition 10.4, Fraud in a card-absent environment, meaning the cardholder told the bank they didn't authorize or take part in the purchase. That's the reason code behind most friendly fraud: the subscriber who forgot they signed up, the parent who didn't know a teenager used the card, the buyer who'd rather call the bank than ask for a refund.
A dispute filed as "not as described" or "cancelled recurring" isn't a 10.4 dispute, and Visa Compelling Evidence 3.0 won't help with it. Those still run on ordinary evidence: your terms, your cancellation flow, proof of delivery.
| Rule element | What Visa requires | Where it comes from |
|---|---|---|
| Dispute type | Condition 10.4, Other Fraud, card-absent | Visa merchant FAQ |
| Prior purchases | At least 2, undisputed, no fraud report (TC40) | Visa merchant FAQ, Visa CE3.0 overview |
| Age of prior purchases | 120 to 365 days before the dispute | Visa merchant FAQ |
| Same parties | Same card (underlying PAN) and same merchant descriptor | Visa merchant FAQ |
| Matching data | At least 2 elements shared across the purchases | Visa CE3.0 overview |
| First-time buyer | Never eligible | Visa merchant FAQ |
| Outcome | Liability shifts to the issuer, fraud record removed | Visa CE3.0 overview, Visa merchant FAQ |
Which data elements count?
Visa lists four: account ID, IP address, shipping address, and device ID or device fingerprint. Visa says that if goods aren't shipped, the billing address can't stand in for the shipping address, so a digital app has three usable elements. Stripe splits them into main elements (purchase IP, and device fingerprint or device ID) and secondary ones (shipping address, email address, account ID). Stripe accepts two main elements, or one main plus one secondary. Device fingerprint plus device ID isn't a valid pair.
For an app, the practical pair is your account ID plus either the purchase IP or a device ID you record at checkout. Both earlier purchases have to match the disputed one, not just each other.
Does it work for subscription renewals?
Yes. Visa's FAQ says Visa Compelling Evidence 3.0 is available for recurring merchant-initiated transactions, and that the merchant supplies the data elements from the initial setup. A renewal charged by your server has no buyer IP of its own. The IP and device from the day the subscription started stand in for it.
Why your App Store and Google Play sales are out of scope
Visa Compelling Evidence 3.0 is a remedy for the merchant of record. On an in-app purchase that's Apple or Google, not you. Only two refund flows anywhere ask an app developer for evidence. Apple sends a CONSUMPTION_REQUEST and gives you 12 hours to answer with Send Consumption Information. Google Play opens a chargeback review you answer through orders.reviewrefund within 24 hours. Everything else on the stores, from Google Play's 48-hour self-service refunds to support refunds and voided purchases, is decided without you.
That makes the web checkout the only place where card network rules work for you directly. It's also the only place where every dispute fee lands on you from the first sale.
What a fraud chargeback costs in money
Stripe's US pricing since June 17, 2025 has two dispute fees. The $15 dispute received fee is charged when the dispute opens and is never returned. The $15 dispute countered fee is charged when you submit evidence and comes back if you win. Stripe also holds the disputed amount for the whole case, which Stripe says usually runs 60 to 75 days after you answer.
| Outcome on a $49.99 annual plan | Money that leaves | What comes back |
|---|---|---|
| You accept the dispute | $49.99 plus the $15 received fee | Nothing |
| You counter and lose | $49.99 plus $15 received plus $15 countered | Nothing |
| You counter with qualifying CE 3.0 data and win | $15 received fee | $49.99 and the $15 countered fee |
| You refunded on an early fraud warning instead | $49.99 | No dispute fee, no dispute on your record |
The fees are the visible part. Behind a year of a paid plan sit the bills you already paid to serve it: GPU time for every generation, paid API calls for every lookup, storage for every file kept, payouts to creators whose content was unlocked. A lost fraud dispute hands the money back and leaves every one of those bills paid. That's why the rule is worth wiring up. A won 10.4 dispute recovers the full charge, and Visa says the fraud record that would count against your monitoring ratios goes away too.

Pre-dispute versus post-dispute
There are two ways in. Pre-dispute, the bank checks Visa through Verifi's Order Insight while the cardholder is still on the phone. If your data qualifies, Visa's overview says the dispute is blocked and liability shifts to the issuer before anything is filed, so it never reaches your dispute ratio. Post-dispute, your acquirer submits the matching data in response to an open dispute. Visa says that route also shifts liability, but the dispute still counts in your dispute ratio.
Most app developers on Stripe will use the post-dispute route. When Stripe sees an eligible Visa dispute it tries to autofill the evidence from earlier charges, and its API reports a status of qualified, requires_action or not_qualified. Stripe's rule is that it must have processed every one of the earlier transactions, which mirrors Visa's own requirement that historical purchases come from the same acquirer.
What if the data doesn't qualify?
The dispute isn't lost by default. Stripe says evidence that fails Visa Compelling Evidence 3.0 is still submitted through the standard flow, so fill in the ordinary evidence fields as well: usage logs, login history, delivery records and your refund policy.
What to log at checkout starting today
- Your own account ID on every charge, in the processor's metadata, so a purchase ties to a person in one lookup.
- The buyer's IP address at the moment of purchase, captured server-side from the request, not from the client.
- A device ID or device fingerprint, if your checkout or processor collects one. Pick one of the two and stay consistent.
- The email address on the account at the time of purchase, as a secondary element.
- A plain product description for every charge. Stripe requires one for the disputed purchase and for both earlier ones.
- Retention of at least 365 days for all of it. Visa says merchants must keep order data available for up to 365 days.
None of this costs much to store, and none of it can be rebuilt after the fact. A customer who files a 10.4 dispute in November needs your logs from last winter.
RefundHalt answers every CONSUMPTION_REQUEST and every Google Play chargeback review inside its window with your real usage data, for the sales Apple and Google process. For the card payments you take yourself, the same records that prove consumption to a store prove a returning customer to Visa. Log them once, keep them a year, and send them wherever the dispute lands.
Frequently asked questions
- What is Visa Compelling Evidence 3.0?
- Visa Compelling Evidence 3.0 is a Visa dispute rule, live since April 2023, that lets a merchant defeat a card-absent fraud chargeback by showing two earlier undisputed purchases on the same card that match the disputed one. When the data qualifies, liability shifts from the merchant to the card issuer.
- Which reason code does Visa Compelling Evidence 3.0 apply to?
- Only Visa dispute condition 10.4, Other Fraud in a card-absent environment. Visa's merchant FAQ says the new rules provide a remedy for that condition alone, so consumer disputes such as not as described or cancelled recurring still need ordinary evidence.
- How old do the prior transactions have to be for CE 3.0?
- Between 120 and 365 days. Visa's FAQ says transactions 120 to 365 days from the dispute date can be used, and Stripe applies a window of 120 to 364 days before the disputed transaction. Both prior purchases must be undisputed and carry no fraud report.
- Can I use Visa Compelling Evidence 3.0 for App Store or Google Play purchases?
- No. Apple and Google are the merchant for in-app purchases, so card disputes go to them. The only ways for a developer to send evidence on store purchases are Apple's CONSUMPTION_REQUEST, answered within 12 hours, and Google Play's chargeback review through orders.reviewrefund, answered within 24 hours.
- Does Visa Compelling Evidence 3.0 work for subscriptions?
- Yes. Visa says the rule covers recurring merchant-initiated transactions, and the merchant supplies the data elements from the initial subscription setup. The subscriber still needs two undisputed charges between 120 and 365 days old, so a brand-new subscriber can't qualify.
Sources and further reading
- Visa: Evolution of Compelling Evidence, Client FAQs (October 2022)
- Verifi, a Visa solution: Compelling Evidence 3.0 overview
- Verifi, a Visa solution: Visa Compelling Evidence 3.0
- Stripe Docs: Visa Compelling Evidence 3.0 disputes
- Stripe Docs: How disputes work
- Stripe Support: June 2025 pricing updates for disputes
- Apple Developer: App Review Guidelines
RefundHalt
The refund autopilot for the App Store and Google Play
Keep reading
Brazil is now checking which games still sell loot boxes to kids, and loot box refunds are where the bill lands
Brazil's justice ministry asked the data protection authority to monitor six games that sell loot boxes without age checks. Here's what the law requires, what Apple and Google already demand, and how to price and handle loot box refunds when the box is already open.
Accidental in-app purchases are the refunds you can't win, so the fix belongs on your purchase screen
Accidental in-app purchases come back as refunds on both stores, and no usage evidence proves a tap was meant. Here's how Apple and Google label them, what each one costs you in compute and payouts, and the purchase screen design that stops them before the charge exists.