A live, interactive picture of every stage a screening request travels through — with reference-data and admin rails, an audit chain underneath, and a click-anywhere drill-down.
Core banking, payment switches, CRMs and onboarding portals are the upstream systems where a name first surfaces. Each has its own integration mode (manual, API, bulk).
Operators key a single name; integrated systems POST to our API; or a CSV file is dropped on the bulk endpoint. The downstream pipeline is identical.
Each input is matched against PEP, sanctions and adverse-media data drawn from the reference-data rail (left side of the board), with daily-delta updates.
Cultural-affinity classification, tokenization, canonical-form reduction and cross-script transliteration — the engine described on the Product Insight page.
Hits run through SNAP·AI for confidence scoring, attribute corroboration and an auto-drafted narrative — explainable per signal, not a black box.
A composite score and per-business-line threshold (set in the admin rail on the right) decides the next stop. High-risk corridors stay strict.
Cleared records go to the onboarding portal. Hits route to the Case Manager. Every step writes to the audit chain on the bottom rail.
Triage → investigate → 4-eyes / supervisor sign-off → resolved or escalated. Every action is captured to the audit chain with reviewer ID and timestamp.
Cleared and on-boarded subjects are re-screened against fresh data. The Examination Evidence Cluster (ECC) bundles every artifact for export.
When a Case Manager review concludes a regulatory filing is required, an STR, SAR or FINTRAC F2R submission is generated and despatched, with the ack code preserved.
Every decision (clear / hit / sanctions-block / further-review) is pushed back to the calling system in the same transaction so downstream workflows can branch on the outcome.
TLS 1.3 in flight, AES-256 at rest. Reference-data rail feeds Screening; the admin/config rail steers the Decision; the audit-chain rail captures every transition.
Body text.