Pre-Transaction Scoring: What It Means and Why It Matters
4 min
Prevention

Every chargeback tool on the market activates after the dispute is filed. Alerts, representment services, deflection tools — they all kick in once the bank has already pulled the money from your account. By that point, you're in recovery mode. You're paying fees to fight a problem that already happened.

Pre-transaction scoring works differently. It evaluates the risk of a transaction before the charge is created. Not after. Not during. Before.

The distinction matters more than it sounds like it should.

How most chargeback tools actually work

The typical chargeback prevention stack looks something like this:

A customer disputes a charge. The card network sends an alert to your prevention tool. Your tool either automatically refunds the customer before the dispute escalates (to keep it off your chargeback ratio), or it gathers evidence and submits a representment package to fight the dispute.

Both of those approaches have value. Alert-based deflection (through tools like Verifi or Ethoca) keeps your VAMP ratio lower by resolving disputes before they're officially counted. Representment recovers some portion of the lost revenue, though win rates across the industry average around 30%.

But here's the thing: by the time either tool activates, you've already shipped the product, paid for the fulfillment, and lost the customer's goodwill. The best outcome is getting your money back weeks later after your team spends time assembling evidence. The worst outcome is losing the money, the product, and the labor.

Neither of those is prevention. They're cleanup.

What pre-transaction scoring actually does

Pre-transaction scoring assigns a risk score to a transaction before it's authorized. The score is calculated using a combination of signals: device fingerprint, IP geolocation, behavioral patterns (how fast the customer filled out the form, whether they copy-pasted the card number), velocity checks (how many purchases from this device in the last hour), card-to-address mismatch patterns, and historical dispute data from similar profiles.

Based on the score, three things can happen:

Low risk: The transaction processes normally. No friction added. Customer never knows a check happened.

Medium risk: The transaction gets routed through additional verification — 3D Secure, for example, or a manual review queue. This adds a small amount of friction but dramatically reduces dispute probability.

High risk: The transaction is either declined or flagged for manual review before any money changes hands. No product ships. No chargeback fee. No representment.

The economic difference between these approaches isn't subtle. When you prevent a dispute before the charge is created, you avoid the chargeback fee ($20–$50), the product loss, the shipping cost, the representment labor, and the impact on your dispute ratio. When you deflect a dispute after it's filed, you still lose the product and shipping — you're just avoiding the ratio hit.

Why this changes the economics

Let's say you process 10,000 transactions a month and your dispute rate is 1.2%. That's 120 disputes. At an all-in cost of $150–$230 per chargeback (including fees, product, labor, and ratio impact), you're losing somewhere between $18,000 and $27,600 every month to disputes.

Now let's say pre-transaction scoring catches 40% of those before they happen. That's 48 transactions that either get declined, routed to manual review, or sent through additional authentication. Some of those will turn out to be legitimate customers — false positives happen — so you won't catch all 48 cleanly. But even at a 70% true-positive rate on those flagged transactions, you've prevented 33 chargebacks that would have otherwise gone through.

At $200 in average all-in cost per chargeback, that's $6,600/month in losses that never materialize. That's $79,200 a year.

And here's what makes pre-transaction scoring compound: every prevented chargeback also lowers your dispute ratio. A lower ratio means lower penalty risk, better processor terms, and a wider margin of safety before VAMP thresholds become a problem. Since April 2026, Visa's excessive threshold sits at 1.5% — and the formula now counts both fraud reports and disputes, meaning one bad transaction can hit your ratio twice if it triggers a TC40 fraud alert and then escalates to a TC15 chargeback.

Prevention before the charge is created is the only approach that addresses all of these simultaneously.

What to look for in a scoring tool

Not all pre-transaction scoring is the same. A few things to evaluate:

Data breadth. The score is only as good as the signals feeding it. Tools that rely solely on card data miss behavioral patterns. Tools that incorporate device fingerprinting, velocity, and cross-merchant fraud data produce better scores.

Threshold control. You need to be able to set your own risk thresholds. A score that works for a luxury goods merchant won't work for a $12/month subscription. If the tool doesn't let you tune the cutoff, you'll either block too many legitimate customers or let too many fraudulent ones through.

Latency. Scoring needs to happen in under 200 milliseconds to avoid impacting checkout conversion. If the check adds noticeable delay, customers drop off — and that costs you more than the chargebacks would have.

Feedback loop. The scoring model should improve over time based on your actual dispute data. A static model that doesn't learn from your specific customer base will drift in accuracy over months.

The shift that matters

The chargeback prevention market has spent years building better ways to respond to disputes. That infrastructure has value — alert networks and representment services are still worth running. But the economics point clearly in one direction: stopping a dispute before it happens costs a fraction of what it costs to fight one after the fact.

If your current stack only activates after the chargeback is filed, you're paying cleanup costs on problems that could have been caught at the door.