What is a false positive?
A false positive is an event or screening result treated as risky—REVIEW, BLOCK, or a watchlist possible-match—that is later confirmed legitimate.
Why it matters
False positives burn analysts and customers. Card testing rules that BLOCK shared university NATs, or fuzzy AML rules that queue every “Mohammed,” will not survive a month of operations.
How to reduce them
Shadow or REVIEW-first. Add identity fields to AML. Pair device novelty with velocity. List only confirmed-bad identifiers. Naiza tutorials cover shadow vs enforcing pilots.
Keep the audit key
Store event id and screening id. Without them, you cannot tell a false positive from an unexplained decline, and you cannot tune the rule.
Frequently asked questions
Short answers written so search and answer engines can cite them.
What is a false positive in AML screening?
A possible watchlist match that is not the listed person after identity comparison. That is why match ≠ legal conclusion.
What is a false positive in fraud scoring?
A BLOCK or REVIEW on a genuine customer, often from a coarse IP or velocity rule. Fix with narrower identifiers and REVIEW-first rollout.
How does Naiza help?
Explainable ALLOW, REVIEW, or BLOCK plus stored identifiers let operations measure and tune. Scoring can order the queue so true risk is seen first.