Integration journey · Step 1 of 5
Core screening principles
What watchlist screening is, why it is regulated, and how Neterium fits in.
Before integrating with the Jetscan or Jetflow API, a developer needs to understand what watchlist screening is, why it is regulated, and how Neterium's products fit into that landscape. This step establishes the domain concepts referenced throughout the rest of the journey.
What is watchlist screening
Watchlist screening is the automated comparison of names — individuals, entities, vessels, or other identifiers — against lists of parties subject to legal or regulatory restrictions. Financial institutions and other regulated entities perform this screening to detect and prevent dealings with sanctioned parties, politically exposed persons (PEPs), and other high-risk subjects.
Screening is a key part of Anti-Money Laundering / Countering the Financing of Terrorism (AML/CFT) and sanctions compliance globally. Institutions must meet applicable requirements across the jurisdictions in which they operate, and screening failures can result in significant legal and financial penalties.
Why organizations screen
Three obligations drive watchlist screening programs:
- Sanctions compliance. Prevent transactions or relationships with individuals, entities, or jurisdictions subject to sanctions.
- AML/CFT. Identify Politically Exposed Persons (PEPs) and other high-risk parties requiring enhanced due diligence.
- Reputational and operational risk management. Avoid association with parties linked to financial crime, even where no formal sanction applies.
Screening obligations apply at two distinct points in the customer and transaction lifecycle, which correspond to two distinct screening use cases:
Counterparty screening
Performed during client onboarding and at intervals throughout the relationship (ongoing monitoring), to assess who an institution is doing business with.
Transaction screening
Performed on individual payments or transactions in real time, to assess what is moving and to whom.
Types of watchlists
Screening lists typically fall into four categories:
Sanctions lists
Issued by bodies such as OFAC, the EU, the UN, and OFSI, listing designated individuals, entities, and vessels.
PEP lists
Politically exposed persons and their close associates and family members, requiring enhanced due diligence under FATF-aligned regulation.
Adverse media
Negative news coverage indicating potential links to financial crime, corruption, or other risk factors.
Internal or proprietary lists
An institution's own risk lists, built from prior investigations, regulatory findings, or internal policy.
Except for internal lists, list data is typically provided and commercially maintained by specialized data vendors (e.g. Dow Jones, LSEG, Acuris). These vendors monitor official sources and other relevant information, consolidate it into structured, screenable datasets, and update the data on an ongoing basis. With Neterium, content updates are fully managed for you, and you can add your own private lists to the list collections used for screening.
How screening works
At its core, screening is a name-matching problem. A screening engine compares an input name — a customer, a payment party — against the entries on one or more watchlists, and returns any matches above a defined confidence threshold.
This is not a simple exact-match lookup. Effective screening must account for:
- Transliteration and spelling variation — names originating in non-Latin scripts, spelling variants, and typographical differences.
- Fuzzy matching — algorithmic tolerance for partial matches, word order variation, and abbreviations.
- Scoring and thresholds — each candidate match receives a confidence score; only matches above the configured threshold are returned.
- False positive management — tuning match sensitivity to balance detection coverage against alert volume, since excessive false positives overwhelm compliance teams.
- Auditability — every screening decision must be explainable and defensible to a regulator after the fact.
The hit lifecycle
Understanding what happens after a match is essential for integration: the screening response is the start of a downstream process, not the end of it.
- Screening request
A customer record or a transaction is submitted to the screening engine, which compares it against the configured list collections.
- Hit or no hit
Matches that score above the confidence threshold are returned as hits, with the matched fields and audit information. No hit means the record can proceed.
- Alert
Hits generate alerts, which are handed over to a dedicated Alert Management or Case Management system.
- Review and decision
Compliance analysts review the alert to confirm or dismiss the match. The decision is recorded for audit and can be re-applied when the same hit is encountered again.
Neterium's screening solutions
Neterium provides two specialized screening solutions for the two use cases above: Jetscan for counterparty screening (client onboarding and ongoing monitoring) and Jetflow for transaction screening (payment screening). Both are built on the same core technology stack.
- Architecture. Both solutions are API-only and run entirely in the cloud, within an AWS Virtual Private Cloud. They are engineered for 24/7 high availability and horizontal scalability, and accessible via REST APIs using JSON over the public internet.
- Data privacy. No personal data from client transactions or customer records is stored. All screening operations are performed in memory and results are returned instantly without data retention, ensuring compliance with regulations such as GDPR by design.
- List content. Screening is performed against watchlist content from third-party vendors such as Dow Jones, LSEG or Acuris. Content updates are fully managed by Neterium. Clients can also supply their own private lists.
- Integration. API responses provide detailed screening results and audit information, structured for consumption by downstream Alert Management and Case Management systems. Beyond the core screening APIs, Neterium offers ancillary APIs for rules management, list management, and system monitoring.
In summary
Watchlist screening is a regulatory control, not an optional risk-management enhancement. It applies wherever an institution onboards a customer or moves a payment, and its effectiveness depends on list quality, matching accuracy, and auditability. Neterium addresses both core use cases through a common, privacy-by-design, API-first architecture. The next step looks at what integrating with it involves.