Real-Time Fraud Scoring Latency: What 47ms Actually Means
Originally published at Riskernel. Fraud vendors love to say they are fast. The problem is that “fast” usually means one cherry-picked number with no context. If you are evaluating real-time fraud ...

Source: DEV Community
Originally published at Riskernel. Fraud vendors love to say they are fast. The problem is that “fast” usually means one cherry-picked number with no context. If you are evaluating real-time fraud scoring for checkout, instant payments, payout approval, or account takeover flows, the only latency number that matters is the one your customer actually feels when the system is under load. That is why “47ms” is useful only if you understand what sits behind it, and why averages by themselves are usually the wrong way to compare vendors. Average latency is the easiest number to game A product demo can produce a beautiful average. Production traffic usually does not. P50 tells you what the middle of the distribution looks like. P95 tells you what happens when the system is a bit stressed. P99 tells you whether the tail is ugly enough to affect real users and downstream systems. A vendor can still claim “sub-100ms average” while giving you a P99 that spikes into the high hundreds. That may be