Screening assurance infrastructure
Compliance screening decisions you can test, replay, explain, and defend.
Verifex gives fintech and compliance engineering teams benchmark-driven matching, differential evidence, source provenance, and replayable audit records across sanctions, PEP, KYB, and supplier-risk workflows.
View an Evidence Capsule·Free developer plan. No sales call to start.
Screened entity (synthetic)
NORTHWIND MARITIME LLC · company
- Request ID
- req_9f2a4c7e1b
- Source snapshot
- src_ofac_sdn · 6b1f…c904
- Algorithm version
- v3.0.0
- Policy version
- pol_2026.05
- Decision hash
- sha256:2d7e…a41f
- Capsule hash
- sha256:9c05…1e8b
- Created
- 2026-05-17 14:03:02 UTC
Benchmark figures reflect Verifex’s published engine v3.0.0 run (May 17, 2026); see the methodology for scope and limitations.
A match score is not a defensible decision.
A screening result tells you there was a hit. It does not tell you what was checked, which source version produced it, or how the decision holds up months later under review.
- Black-box screening changes are hard to audit after the fact.
- Source updates and matching changes can silently move results.
- Screenshots are not evidence a reviewer can re-verify.
- Regulated teams need to know what changed, why, and under which source, model, and policy version.
Screening assurance
Screen → Compare → Explain → Preserve → Verify.
The same evidence layer runs under every screening, so a decision can be re-examined by another engineer, a compliance officer, or an auditor — without institutional memory.
- 01
Screen
Generate candidates and calibrated decision signals.
- 02
Compare
Evaluate decision and evidence differences over time.
- 03
Explain
Source, score, policy, and version reasoning.
- 04
Preserve
Write an evidence artifact with provenance.
- 05
Verify
Replay metadata and checksum integrity later.
Verify confirms provenance and checksum linkage; it does not re-execute the historical matching engine.
Evidence Capsule
Every screening leaves behind an artifact you can inspect.
A structured, point-in-time record another engineer, compliance officer, or auditor can retrieve by ID — instead of relying on screenshots or institutional memory.
- request_id
- req_9f2a4c7e1b
- source_snapshot_id
- snap_6b1fc904
- source_checksum
- sha256:6b1f…c904
- algorithm_version
- v3.0.0
- policy_version
- pol_2026.05
- decision_hash
- sha256:2d7e…a41f
- capsule_hash
- sha256:9c05…1e8b
- replay_verification
- provenance + checksum verified
Differential evidence
When a result changes, know exactly why.
A different outcome can come from the data, the engine, the policy, a reviewer, or the provenance. Differential evidence attributes the change instead of leaving you to guess.
- Source data change
- Matching-engine change
- Policy threshold change
- Reviewer action
- Metadata / provenance change
algorithm_version v3.0.0
- policy_version pol_2026.04 (threshold 0.90)
+ policy_version pol_2026.05 (threshold 0.92)
- decision match · 0.91
+ decision review · 0.91
source_checksum unchanged · 6b1f…c904
Illustrative synthetic diff. Available differential fields map to the screening and evidence API.
Matching assurance
Matching changes ship behind a benchmark gate.
A published fixture set measures matching quality and calibration before a change reaches production, so an engine update cannot silently regress your decisions.
- Regression fixtures across false-positive classes
- Adversarial safety suite for name-obfuscation variants
- Exact-match recall and calibrated confidence
- Deterministic evidence stability as a release gate
Developer workflow
Screen, retrieve evidence, and diff — from your own stack.
A documented REST API and SDKs for Python, Node, Go, and Rust. Screen a party, fetch the evidence record by request ID, and compare decisions across versions.
# Screen an entity
curl -X POST https://api.verifex.dev/v1/screen \
-H "Authorization: Bearer $VERIFEX_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "query": "Northwind Maritime LLC", "type": "company" }'
# Retrieve the evidence record for a past decision
curl https://api.verifex.dev/v1/screenings/req_9f2a4c7e1b \
-H "Authorization: Bearer $VERIFEX_API_KEY"Source provenance
Source-backed results, with attribution you can cite.
Provenance is content-checksum based: a decision can be tied to the source version it used. It is not raw-file archival, and it does not offer exact source-file replay.
Source identity & freshness
Every result carries the source it came from and how recently that source was refreshed.
Checksum provenance
A content checksum and version attribution link a decision to the exact source content it used.
Sync & state attribution
Active, manual, and frozen source states are distinguished — no source is silently treated as fresh.
Workflows on one evidence layer
Merchant onboarding, supplier screening, and ownership review.
Use Verifex underneath your onboarding, supplier, and counterparty workflows without replacing your case-management or identity stack.
KYB & UBO
Legal-entity identity with GLEIF context and ownership traversal.
Ownership risk
Beneficial-ownership context with OFAC 50% rule traversal.
Supplier risk
Sanctions, debarment, and PEP screening for vendors and counterparties.
Continuous monitoring
Re-screen watched parties as sources and designations change.
Where Verifex sits
Infrastructure under your compliance stack — not another workflow suite.
Product surface
The modules that make a decision defensible.
Priced by maturity, from evaluation to enterprise.
Developer evaluation
Free plan for testing the API and evidence records.
Production screening
Higher volume with monitoring and evidence retrieval.
Assurance workflows
Differential evidence, benchmarks, and audit records.
Enterprise validation
Broader source coverage and retention for regulated teams.
Frequently asked questions
What does “replay” verify?
Replay verifies that a decision’s evidence is intact: the referenced source snapshot exists and its content checksum matches what was recorded, alongside the algorithm and policy versions. It does not re-execute the historical matching engine — exact engine rerun is not offered.
Does Verifex store the raw source files?
No. Source provenance is content-checksum based: a decision is tied to the source version it used through a checksum and version attribution. Verifex does not archive raw source bytes, so it does not offer exact source-file replay.
Is a no-match result a guarantee of no risk?
No. A clear result means no match was found in the screened sources at screening time. It is not a guarantee of a clean counterparty, and risk can change after screening.
Is Verifex legal or compliance advice?
No. Verifex provides screening assurance infrastructure and data-derived results, designed to support compliance workflows. Final compliance decisions remain with your team; consult counsel for applicable obligations.
How do the benchmark numbers stay honest?
The figures shown come from Verifex’s published fixture set (engine v3.0.0, 500 cases, verified May 17, 2026). Matching changes are gated against this benchmark before release. Methodology and limitations are documented.
Can I integrate without replacing my stack?
Yes. Verifex runs server-side underneath onboarding, supplier, and counterparty workflows via API and SDKs, without replacing your case-management or identity systems.
Verifex provides screening assurance infrastructure and data-derived results, not legal or compliance advice.
Make your next screening decision defensible.
Free developer plan · documented API and SDKs · evidence on every decision.