What Is Order Insight? Visa's Pre-Dispute Lookup, Explained

Who this helps: a vendor is selling you Order Insight, or you are reading your processor's dispute prevention settings, and you want to know what it does, what it costs, and whether your payment data is good enough for it to work.

Most dispute prevention works by giving the money back. An alert arrives, you refund, the dispute goes away and so does your revenue. Order Insight works differently. It answers the customer's question while they are still asking it, and if the answer satisfies them, there is nothing to refund.

What is Order Insight?

Order Insight is a Visa service, run by Verifi, that lets a customer's bank see your order details at the moment the customer questions a charge. Verifi is a Visa company, acquired in 2019, and the service was previously called VMPI, or Visa Merchant Purchase Inquiry. Nothing about it involves refunding anyone.

The distinction worth holding on to: an alert tells you a dispute is coming. Order Insight tells the customer what they bought.

What the bank receives falls into four groups. The order: date, order number, subtotal, shipping, total, product description, unit price and quantity. The customer: first and last name, email, account ID, and how many months they have been your customer. The delivery: billing address, delivery address, shipping carrier and tracking number. The context: your business name, URL, support phone, cancellation terms, and the IP address the purchase came from.

When does an Order Insight lookup happen?

At the one moment you normally cannot reach: the customer is looking at a charge they do not recognize and deciding whether to dispute it.

Visa gives banks two ways to run that lookup. Order Insight Digital puts it inside the bank's own app, so the customer sees the order details themselves, which Visa notes removes “the need for call center interactions.” Order Insight via VROL puts the details in front of a call center agent, who reads them back over the phone. VROL is Visa Resolve Online, the system disputes travel through, and Visa has been sharing Order Insight details there since 2019. Which one your customer gets depends on their bank, not on you.

How is Order Insight different from RDR, CDRN and Ethoca?

By whether you keep the money. Everything else is detail. RDR, CDRN and Ethoca all end the same way: the customer gets their money back, and you avoid the dispute and its fee. Order Insight is the only one of the four where a satisfied customer costs you nothing.

That trade reads differently at different order values. Refunding a $49 order to avoid a dispute and its fee is usually sensible. Refunding a $900 order to avoid the same fee is not. Order Insight is the only option on that list that does not force the choice, which is why it belongs alongside alerts rather than instead of them.

How does Compelling Evidence 3.0 block a dispute before it is filed?

On one specific dispute type, yes, and it is the strongest thing in the prevention toolkit. Visa's Compelling Evidence 3.0 rules, usually described as a way to win a fraud dispute after it lands, can also be applied before one is filed.

The two sources word the outcome differently, and the difference is worth knowing. Visa's own readiness document says the pre-dispute use “is designed to eliminate the dispute from being filed altogether.” Stripe states the result more firmly: where the criteria are met, “the issuer must block the dispute,” the dispute is never filed, and you incur no dispute fees and no increase to your dispute rate. Visa describes the intent, Stripe describes the obligation.

Two limits keep this in proportion. The block applies to Visa dispute condition 10.4, which Visa names Other Fraud, Card Absent Environment, and which is the friendly fraud case. The lookup itself is broader: Visa notes that “Order Insight data can be used for all reason codes, not just Dispute Condition 10.4.”

What are the Compelling Evidence 3.0 requirements?

Four conditions, and most merchants fail on the third or fourth without knowing it. Visa requires two previous transactions by the same customer that:

1. Are at least 120 days old and no older than 365 days, counted from the dispute date.
2. Carry no active fraud report and no active fraud dispute of their own.
3. Match the disputed transaction on at least two of four data points: a user ID, which is the account identifier your customer would recognize and is usually their email, the IP address, the shipping address, or the device ID.
4. Include, among those matches, either the IP address or the device ID. One of the two is mandatory.

The first condition is the one nobody mentions. A customer's first two orders from last month cannot qualify, however clean your data is. The history has to have aged.

Maya bought from you in June and again in August, then disputed a $120 charge the following April as fraud. Both earlier orders sit inside the 120 to 365 day window, neither was ever disputed, and both came from the same IP address as the April purchase, with the same email on file. That clears all four conditions, and her bank is obliged to block the dispute. Had she first bought in February, nothing would qualify, and you would be answering a 10.4 chargeback instead.

Does this work for subscription renewals?

This is where subscription businesses need to pay attention, and where the published rules are least clear.

A renewal is a merchant-initiated transaction. Nobody is sitting at a browser when it runs, so there is no IP address and no device fingerprint to capture. Condition four above demands one of exactly those two. Read literally, Visa's criteria are hardest to satisfy on precisely the transactions a subscription business has most of.

Three separate things are worth stating separately. What is known: Visa's readiness document requires the IP or device ID match and does not address recurring billing. What providers report: several chargeback vendors say the IP address and device ID captured at the original signup can serve as the match for later renewals, provided that first transaction was never disputed. What we cannot confirm: Visa has not published that allowance in the document we are citing.

The practical conclusion holds either way. The signup transaction is the one carrying your IP address and device data. If that data is missing at signup, no later renewal has anything to inherit.

What data do you need to be sending?

Four fields decide it: IP address, customer email, product description, and a shipping or customer address. Stripe names exactly those as what to include on every transaction to make blocks possible, and the same four are what any processor needs in order to answer a lookup with something useful.

Whether you already send them depends on how you take payments. Hosted checkout flows tend to collect device and IP data for you: Stripe says its Payment Links, Checkout, Elements and mobile SDKs “automatically collect important high-risk factor data, such as device information and IP addresses.” A direct API integration collects none of it unless you do the work. On Stripe that means client risk factors, meaning IP address, user agent and checkout URL, on the PaymentIntent, or a Radar Session, plus customer risk factors, meaning email, name and billing address, on the Customer object.

If you built your own checkout and create payments server side, this is the likeliest reason Order Insight does nothing for you. There is no IP address on the charge, so there is nothing to match, so no block can happen. It is usually a two-line change, and it is worth making before you evaluate any vendor.

How do you turn Order Insight on?

That depends on who processes your payments, and the answer splits cleanly in two.

On Stripe, there is nothing to build. Onboarding in the Dashboard collects your business name, URL, phone number and email, and from then on Stripe “automatically pulls any available data on a charge on your behalf and sends it to the issuer.” It explicitly “doesn't require you to build any integrations or maintain a real-time service.” That is unusual, and it is worth knowing if you have been told otherwise.

On every other processor and gateway, somebody has to answer Verifi's lookups in real time with your order data, and that somebody is a Verifi partner. This is the part most articles skip, and it is why Order Insight has a reputation for being hard to adopt.

Disputeless is a Verifi partner and supplies Order Insight, alongside CDRN and RDR on Visa and Ethoca on Mastercard. In practice that means one enrollment covering the lookup, the alert networks and the reporting, rather than three vendors and three contracts. The reporting is the part processors generally do not give you: which issuers and card ranges generate your lookups, how often a lookup is followed by a dispute anyway, and whether your transactions actually carry the four fields a mandatory block needs. You can see how that fits together on our alerts page.

What can Order Insight not do?

Three things, in increasing order of importance.

First, it is Visa only. Mastercard's nearest equivalent, Ethoca's Consumer Clarity, shows transaction detail inside the bank's app for Mastercard, but it is not part of Stripe's documented prevention lineup, which lists Order Insight, RDR and Ethoca Alerts. Your Mastercard volume needs its own answer.

Second, it does not clear a TC40. If the customer's bank already filed a fraud report, that report stands whatever the customer decides next, and it feeds the fraud count behind Visa's VAMP independently of whether a dispute follows. A deflected dispute and a cleared fraud report are different things.

Third, and largest, nobody can tell you whether it worked. Banks do not report back on what a lookup changed. You can see that a lookup happened and that no dispute arrived, but you cannot know whether the details you sent are what stopped it. That has a commercial edge: any vendor charging you a percentage of “successful” Order Insight cases is billing you against an outcome nobody can observe. A per-lookup or per-block fee can be checked against your own records. A success fee on a deflection cannot.

FAQ

Facts checked against Visa's Compelling Evidence 3.0 merchant readiness document (March 2023) and Stripe's documentation on how dispute prevention works, Compelling Evidence 3.0, risk factor completeness and pricing. Last reviewed September 21, 2026.