Skip to article
ecomservices.io
Chargebacks · How to run this
MatchingNot on this page yetPricingCalculatorIntakeCalculatorReason codesCalculatorRepresentmentCalculatorThresholdsCalculatorAllocationCalculatorOptimisationCalculatorPrevention stackCalculatorProviders

Library · Chargebacks · How to run this

Compelling Evidence 3.0: two prior transactions

How to run thisChargebacks5 steps
GuideCE 3.0 prior-transaction checklist · Calculator lives in the articleOpen

Compelling Evidence 3.0 is a Visa 10.4 job. The cardholder says they did not do this card-absent sale. You show prior undisputed sales with the same person, not a 3DS log from this ticket alone.

Pair: CE 3.0 prior-transaction checklist on Chargebacks. First sale vs rebill shape: CE 3.0 CIT vs MIT. What to send for other families is a different job: Build the fight packet the family needs. Order Insight fields are a different job: Fill the Order Insight payload.

How many, and what has to match

You need at least two prior transactions. They have to be undisputed and not fraud. One prior is a hole.

Visa can ask for two to five of the most recent non-fraud priors on an Order Insight lookup. Stripe’s prevention write-up is the dated source for that range and for the match rule below. We do not fill a lucky number of priors.

Those priors need complete product descriptions. They need a matching IP on the prior sales and the disputed sale. They also need a matching email or ship-to. IP without an email or delivery is a hole. Email without a matching IP is a hole.

If Order Insight can send that prior-sale data at lookup, the issuer is supposed to block the dispute from being filed. That is the pre-dispute path. If the chargeback already posted, you still need those same priors in the fight packet. Do not invent a third sale to make the count pretty.

What this is not

This is not Mastercard 4837. This is not Visa 13.1 or 13.3. A carrier scan does not become two prior sales. A 3DS success on this ticket does not become two prior sales.

If the portal renamed the reason, read the network code. If it is not 10.4, use the family packet. If you only have one prior, refund or write it off. Do not send a thin CE 3.0 file.

Tick each part in the checklist when it is actually in the packet or the Order Insight payload. Boxes start off.

Related: Order Insight (the lookup that can carry the priors), 3DS (authentication on this sale, a different job).

Procedure

  1. Read the network code. Stop if it is not Visa 10.4.
  2. Pull two to five of the most recent non-fraud priors.
  3. Confirm product descriptions, matching IP, and matching email or ship-to.
  4. Put that in Order Insight if the dispute is not filed yet. Put it in the fight packet if it is.
  5. If you have one prior, refund or write it off.

Failure modes

  • Sending one prior and calling it Compelling Evidence 3.0.
  • Matching IP with no email and no ship-to.
  • Using a 3DS log from this ticket as the packet.
  • Fighting a consumer code with CE 3.0 priors.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

CE 3.0
Visa 10.4 card-absent fraud. At least two prior undisputed sales with matching IP and a matching email or ship-to.
Prior
An undisputed non-fraud sale to this cardholder before the disputed sale. One prior is a hole.

Work with us — We run this job on your accounts. Services

FAQ

How many prior transactions do I need?
At least two undisputed non-fraud sales with this cardholder. Visa may ask for two to five of the most recent. One prior is not enough.
Does 3DS count as Compelling Evidence 3.0?
No. 3DS is authentication on this sale. CE 3.0 is prior sales that match IP and email or ship-to.
Does this win not-as-described?
No. This rule is Visa 10.4 card-absent fraud. Consumer codes still need the family packet.