Do You Know Your Real Chargeback Recovery Rate?

Part of my job involves sitting on calls with merchants and showing them how their chargeback program is actually performing.That includes showing their real chargeback recovery rate.

There’s a moment on a lot of those calls where someone frowns. I’ve just put a recovery rate on the screen, and it isn’t the number they have. Sometimes it’s a few points off. Sometimes it isn’t close.

It’s one of the most common conversations I have.

The reason is almost never that someone did the math wrong. It’s that the report they built their number from wasn’t really designed to answer the question.

Payment processors are built to move money. Dispute reporting is a byproduct of that job, not the point of it. So when you export a dispute report, you’re not getting a clean scorecard — you’re getting an operational log, and you have to interpret it.

That interpretation is where it goes wrong. A few examples I run into constantly:

• What counts as a chargeback. Some processors file early fraud notifications right alongside real chargebacks. They look like disputes in the export. They aren’t.
• What counts as a win. On some reports, a refund and a won dispute carry the same status. From the processor’s side that’s reasonable — both are money going back. From yours, one is a victory and the other is a cost.
• What a row represents. Sometimes each stage of a dispute is a new row. Sometimes the original row gets updated in place. If you don’t know which, you can’t count cases correctly.
• When the report is final. Statuses lag, and wins tend to land later than losses. So your most recent months always look worse than they’ll end up.

None of that is a processor doing something wrong. Every one of those choices makes sense inside their own system. It just means the number sitting in their dashboard isn’t the number you think you’re reading.

If I could get every merchant to check one thing, it’s this.

A chargeback comes in. You fight it. You win. Your report marks it won.

Then the issuer comes back with more information and the case escalates to pre-arbitration. You lose it there. The money goes back out.

In a lot of reporting, that first win is never reversed. It just sits there as a win. Sometimes the case gets counted twice — once as the original win, once as the escalated case.

Now run that across a few thousand disputes a month. Your reported recovery rate isn’t slightly high. It’s systematically high, and it drifts further from reality the more of your cases escalate.

A merchant came to us confident their recovery rate on one processor was 22%. We asked for the raw file behind it and ran it ourselves.

The real figure was 6%.

The cause was one mapping decision. Their processor filed fraud notifications under a status that read as “dispute.” Those resolve easily, so they’d been padding the win column for months with cases that were never disputes at all.

Same merchant. Same book. Same period. One definition, and the number moved by nearly 4x.

They weren’t underperforming. They were unmeasured. Those are completely different problems, and only one of them gets better by fighting harder.

Everything above is one processor. Most merchants I work with are on three or four.

Each one has its own status vocabulary. Its own idea of what a row means. Its own reporting lag. Its own opinion on whether a fraud alert belongs in your dispute file. None of them line up.

So before you can produce a single company-wide recovery rate, someone has to reconcile all of it into one consistent definition — and then keep that reconciliation current as processors change their reporting and the card networks change their rules.

That’s a data engineering project, not a reporting task. Most merchants aren’t staffed for it. Honestly, they shouldn’t have to be.

It’s easy to treat this as reporting hygiene. It isn’t, for two reasons.

The first is money. If you’re resolving $2 million of disputed volume a month, three percentage points of recovery rate is about $720,000 a year. That’s not a measurement quibble. That’s a line item.

The second is strategy, and it’s the one that compounds. Your recovery rate is the input to every decision you make about disputes. Which cases are worth fighting for? Whether your evidence is working. Whether last quarter was actually better than the one before it. Whether to accept or contest — a call that got more expensive this April, when Visa’s tightened VAMP threshold meant the disputes you wave through now carry a compliance cost they didn’t carry before.

If the baseline is wrong, every one of those decisions is aimed slightly off target. And you won’t find out from your own reporting, because your own reporting is the thing that’s wrong.

Here’s the part merchants underestimate: this isn’t a problem you solve once.

Processors change their reporting. Card networks change their rules, their reason codes and their dispute flows — several times a year. A mapping that was correct in January can quietly stop being correct by June, and nothing announces it. The report keeps exporting. The numbers keep looking plausible.

We have chargeback experts whose job is keeping that mapping current across every processor we integrate with. When a processor changes a status or a network changes a code, that’s their problem to catch, not yours. It’s unglamorous work and it’s the foundation everything else sits on.

That’s what the Justt Hub is for.

Instead of four processor portals and a reconciliation spreadsheet, you get one place where every dispute across every processor is counted the same way. One definition of won, lost and pending. Real chargebacks separated from alerts and inquiries. One row per case at its latest stage, so a win that later reverses shows up as what it actually was. Closed months only, so you’re reading performance instead of settlement lag.

Then the real work starts. Our team takes that clean baseline and builds a strategy on it — which reason codes are genuinely winnable for your business model, where your evidence is thin, which cases aren’t worth contesting, which processor is underperforming and why. Because we do this across thousands of merchants, we’re not starting from zero on yours. We know what tends to work for a subscription business versus a marketplace versus a travel platform, which means you get to a strategy that works in weeks rather than quarters.

None of it is possible without the first step. You can’t optimize what you can’t measure.

You don’t have to take my word for any of this, and you don’t need to sign anything to find out.

Send us your chargeback data. We’ll run it through our mapping — the current version, maintained across every major processor — and show you what your recovery rate actually is. If it matches what you already have, that’s genuinely good news and you’ve lost nothing but an export.

If it doesn’t, you’ll know exactly where the gap is coming from. And you’ll finally have a number you can build a strategy on.

Want to know your true recovery rate? Send us your chargeback data and we’ll show you.