Know who matched.
Prove why.
Sanctions, PEP and entity screening with the source versions, matching evidence and decision context behind every result.
Northwind Maritime LLC
company · TR
- OFAC
- UK
- UN
- BIS
4 lists · versions pinned
3 reviewed
1 carried · 2 discounted
ESCALATE
alias match · 6b1f…c904
sha256:2d7e…a41f
Illustrative example · not live customer data
Every screening records the lists checked and their versions at that moment.
The decision pipeline
- 01
INPUT
A name and an entity type. Normalised, transliterated and prepared for matching — the raw query is kept exactly as submitted.
- 02
RETRIEVAL
Every configured list is retrieved and its version pinned. A source that is stale or unavailable is recorded as such, never treated as clear.
- 03
MATCH
Candidates are generated across exact, fuzzy, phonetic and alias paths, then scored against the normalised identity.
- 04
EVIDENCE
For each candidate the engine records what supported the match and what counted against it — including the ones it rules out.
- 05
DECISION
Policy turns the scored evidence into an outcome. The policy version that produced it is recorded alongside.
- 06
RECORD
Inputs, versions, evidence, outcome and reviewer action are sealed under a hash and retained for ten years.
- query
- Northwind Maritime LLC
- type
- COMPANY
- lists_pinned
- 4
- ofac_sdn
- 6b1f…c904
- candidates
- 3
- top_score
- 94
- alias_matched
- NORTHWIND MARITIME L.L.C.
- discounted
- 2 · grounds recorded
- decision
- ESCALATE
- policy
- p2
- engine
- verifex-screening-v5.0
- sha256
- 2d7e…a41f
The decision pipeline
INPUT
A name and an entity type. Normalised, transliterated and prepared for matching — the raw query is kept exactly as submitted.
- queryNorthwind Maritime LLC
- typeCOMPANY
RETRIEVAL
Every configured list is retrieved and its version pinned. A source that is stale or unavailable is recorded as such, never treated as clear.
- lists_pinned4
- ofac_sdn6b1f…c904
MATCH
Candidates are generated across exact, fuzzy, phonetic and alias paths, then scored against the normalised identity.
- candidates3
- top_score94
EVIDENCE
For each candidate the engine records what supported the match and what counted against it — including the ones it rules out.
- alias_matchedNORTHWIND MARITIME L.L.C.
- discounted2 · grounds recorded
DECISION
Policy turns the scored evidence into an outcome. The policy version that produced it is recorded alongside.
- decisionESCALATE
- policyp2
RECORD
Inputs, versions, evidence, outcome and reviewer action are sealed under a hash and retained for ten years.
- engineverifex-screening-v5.0
- sha2562d7e…a41f
A result is not enough
A label is an outcome.
Evidence is a decision you can defend.
Match
94%
High risk
Decision record
9f2a4c7e1b3d5a8c
- matched
- NORTHWIND MARITIME LLC
- alias
- NORTHWIND MARITIME L.L.C.
- source
- OFAC SDN · 6b1f…c904
- supported by
- legal form matches, jurisdiction matches, alias exact after normalisation
- counted against
- no registration date on record
- discounted
- 2 candidates · grounds recorded
- engine
- verifex-screening-v5.0
- policy
- p2
- decision
- ESCALATE
- sha256
- 2d7e…a41f
- Why did it match?
- Which alias matched?
- Which source version was checked?
- Which fields supported the decision?
- What was discounted, and why?
- Which engine version produced it?
- Can the same record be inspected later?
One decision, five surfaces
The same record, read five different ways.
request_id 9f2a4c7e1b3d5a8c
verifex-screening-v5.0 · policy p2 · sha256:2d7e…a41f
- decision
- ESCALATE
- risk_level
- high
- matched
- NORTHWIND MARITIME LLC
- score
- 94
- screened_at
- 2026-08-06 14:02:11Z
- retention
- 10 years — 31 CFR 501.601
Integration
One request. A response you can file.
Request
POST /v1/screen HTTP/1.1
Host: api.verifex.dev
Authorization: Bearer $VERIFEX_API_KEY
Content-Type: application/json
{
"name": "Northwind Maritime LLC",
"type": "entity"
}Response
identity
- request_id
- "9f2a4c7e1b3d5a8c"
- risk_level
- "high"
matching
- total_matches
- 1
- top_confidence
- 94
provenance
- lists_checked
- ["OFAC","UK","UN","BIS"]
- coverage
- "complete"
record
- engine_version
- "verifex-screening-v5.0"
- decision_hash
- "sha256:2d7e…a41f"
99.36%
Recall
100%
Precision
99.68%
F1
0 / 3
False pos / neg
Known limitations
- Benchmark result on synthetic cases, not a guarantee of real-world performance.
- Coverage and update frequency vary by source; a stale source is reported as stale, never treated as clear.
- Replay verifies recorded metadata and provenance, not exact historical engine re-execution.
Provenance over time
The source changes. The record does not.
- T0
Sources retrieved
4 lists pinned with their versions
- T1
Screening executed
verifex-screening-v5.0 · policy p2
- T2
Analyst reviewed
escalated · reason recorded
- T3
Source changed upstream
new list version published
- T4
Decision reopened months later
original versions, evidence and hash still attached
Decision recorded · sha256:2d7e…a41f