A new study from PYMNTS Intelligence landed with a number that should stop every business leader cold: nearly half of merchants report with false declines have cost them sales. Not fraud losses – false declines. Legitimate customers, turned away at the moment they were ready to buy.
The industry estimates the cumulative damage at $50 billion in annual lost revenue. Let that sit for a moment.
We spend enormous energy – and budget – talking about fraud prevention. We invest in tools, teams, and technology to stop the bad actors. That is absolutely the right priority. But when our fraud systems are so blunt that they can't reliably tell a fraudster from a loyal customer, we haven't solved the problem. We've just moved it.
I hear this framing occasionally: false declines are an acceptable tradeoff for keeping fraud out. I disagree with that premise, and the data backs me up.
When a good customer is declined, they don't quietly accept it and try again later. They leave. They go to a competitor. They tell other people. And in a world where switching costs are low and alternatives are one tap away, the tolerance for friction among legitimate customers is essentially zero. The PYMNTS report notes that 85% of merchants identify preventing fraud without degrading the customer experience as their top challenge. That is not a fraud problem. That is an identity problem.
Fraud tools fail customers when they can't answer a fundamental question with confidence:is this person who they say they are?
When that answer is uncertain, systems overcompensate. They apply friction broadly – to everyone – because they lack the precision to apply it selectively. That's how a good customer ends up flagged, declined, or stuck in a manual review queue while their purchase intent evaporates.
Most fraud discussions focus on the transaction layer: payment authorization, risk scoring, and behavioral signals. Those are important. But if the identity entering that pipeline hasn't been verified at the source, every downstream decision is built on an unstable foundation.
Here's the sequence that matters: fraud begins with a false identity. Once a fraudster gets past the identity check – or a legitimate customer is incorrectly flagged by the same check – every system downstream inherits that error. A fraudster authenticated as real moves freely through your systems. A real customer flagged as suspicious faces friction at every step.
The transaction layer can't fix what the identity layer got wrong. It can only pass the error forward.
This is where I'd push back on the narrative that fraud prevention and customer experience are fundamentally in tension. They don't have to be – if your identity verification is precise enough.
At Intellicheck, we built our service on a fundamentally different approach. Rather than pattern-matching against templates or relying on data signals that can be spoofed or synthesized, we authenticate identity against the authoritative information in DMV-issued ID barcodes. The security layers embedded there are known to Intellicheck because of our unique position as the sole AAMVA DL/ID Card Verification Program certification lab provider. Fraudsters are not able to replicate the security information on fake IDs. That distinction is binary. The ID is either authentic, or it isn't.
The result is negligible false positives and false negatives. Verified customers move through quickly, without friction. Fraudulent IDs are stopped at the source, before they become downstream losses.
Intellicheck delivers 99.975% decisioning in under a second. That’s a different category of precision entirely.
I wrote recently about the economics of identity verification, and the same logic applies here. The cost of false declines is rarely captured in a single line item. It compounds: the lost sale, the lost customer lifetime value, the cost of a support interaction if the customer calls in, the reputational damage when they share the experience. For high-volume merchants or financial institutions processing millions of transactions, even a fractional improvement in false decline rates translates to material revenue recovery.
Compare that against the per-transaction cost of a precision identity verification layer. The math is not close.
In my work with our clients, I come back to a simple principle: trust in the customer relationship is mutual. When a customer presents their ID, they are participating in a reasonable, security-minded exchange. When your system responds by wrongly rejecting them – or frustrating them in a slow and high friction experience – you've broken that trust.
The PYMNTS data tells us that nearly half of merchants are already feeling this. The question is whether the organizations that haven't yet acknowledged the problem will recognize it before their customers do.
The solution isn't softer fraud rules. It isn't accepting $50 billion in losses as the price of caution. It's building identity confidence at the start of the journey – so your fraud tools can be sharp where they need to be, and invisible everywhere else.
---
Intellicheck verifies identity in under one second with negligible false positives and false negatives, processing over 100 million IDs annually. Learn more at intellicheck.com.