Scenario: False Positive in Screening

The false-positive scenario: triage, decide, log — without breaking the payment flow.

The setup

A customer named "Mohammed Ali" matches an SDN entry in fuzzy name screening. Your workflow flags the payment for review.

The triage

1. Compare identifiers: date of birth, jurisdiction, aliases
2. Check the OFAC 50-percent rule — is the match entity-owned?
3. Decide: release (false positive) or escalate
4. Log the decision with the reasoning

Why false positives are the design

Name screening errs toward recall — flag first, review second. A false positive costs minutes; a false negative costs $356,000.

The automation

Wallet screening has no false positives (exact match). Name screening does — which is why the review queue is part of the workflow.