Every fraud detection system makes mistakes. The question isn't whether you'll have false positives or false negatives—it's which ones you can live with. We're going to walk you through this tradeoff and show you how to actually calibrate your system instead of just accepting whatever numbers come out of the box.
What's the difference, really?
A false positive happens when your system flags a legitimate transaction as fraudulent. A legitimate customer tries to pay, and the system says "nope, this looks suspicious." You've caught nothing—you've just blocked a sale.
A false negative is the opposite: a fraudulent transaction slips through as legitimate. The bad actor wins, and you're left with a chargeback and unhappy customers.
The challenge isn't picking one. It's understanding what each one costs your business and building a system that optimizes for YOUR specific situation. A payment processor with 10,000 transactions per day has different tolerances than a boutique retailer.
Individual learning outcomes vary from person to person. The specific calibration that works best depends on your transaction volume, customer base, fraud patterns, and business model. These principles guide the thinking—you'll need to test and tune for your environment.
The cost of getting it wrong
False positives are visible. Customers call, complain, sometimes leave. You spend time on customer support. But there's a harder cost: friction. Some customers won't bother contacting you—they'll just shop somewhere else. You never know who they are. Studies across payment processors suggest 2-5% of customers will abandon a transaction if challenged.
False negatives are invisible until they're expensive. You eat the chargeback fee (typically $15-$100 per transaction). You lose the merchandise. You lose the customer's trust. If you're processing 500 transactions daily and your system misses just 0.5% of actual fraud, that's 2-3 chargebacks a day. That's $30-$300 in fees alone, plus inventory and time.
The math shifts depending on your margins. A high-margin business can afford to block more legitimate transactions to prevent fraud. A low-margin business needs to let more through or go broke on customer service.
How to actually calibrate your system
Most systems ship with a default threshold. If the anomaly score hits 0.75 or higher, it's flagged. But you shouldn't just accept that. Here's what we've seen work:
Measure your actual fraud rate
Look at 30 days of chargebacks, friendly fraud, and confirmed fraud cases. What percentage of your transactions are actually fraudulent? Most processors sit between 0.1% and 0.5%.
Test thresholds against historical data
Run your system at different sensitivity levels (0.6, 0.65, 0.7, 0.75, 0.8) against the last 90 days. Count false positives and false negatives at each level. This isn't theoretical—you'll see the actual numbers.
Calculate your acceptable loss
If false positives cost you 2% of revenue in abandoned transactions, and false negatives cost you 0.3% in chargebacks, you know which direction to lean. Pick the threshold that minimizes your total loss.
Implement graduated response
Don't block everything. Flag suspicious transactions for secondary verification instead. Ask for an extra confirmation, require a CVV, or send an SMS. This catches fraud without blocking legitimate customers.
What we've actually seen work
Payment processors processing 50,000+ transactions monthly typically run at 0.65-0.70 threshold. This catches about 70% of actual fraud while blocking 3-5% of legitimate transactions. They accept that 3-5% because their customer support can handle it, and the chargeback savings justify the effort.
E-commerce sites with high customer lifetime value run lower thresholds (0.55-0.60) because they can't afford to lose customers. They'd rather deal with slightly more fraud.
One retail processor we worked with realized their false positive rate was actually costing them 1.8% of revenue in abandoned transactions. They lowered their threshold from 0.75 to 0.68. Fraud incidents increased by 12%, but the net revenue gain was 0.9% because they retained so many customers. The math worked in their favor.
The balance is yours to find
There's no universally "correct" threshold. What works for a bank doesn't work for a marketplace. What works in 2026 might need adjusting in 2027 as fraud patterns shift.
The real skill is understanding your tradeoffs and making deliberate choices instead of accepting defaults. You'll want to revisit this every quarter. Fraud patterns change. Customer behavior changes. Your tolerance for risk might change.
Start with the actual numbers from your own business. Test different thresholds. Measure the real costs. Then pick the threshold that makes sense for you. That's not just theory—that's how you actually build a system that works.