Find relevant records
Search stored sanctions names and aliases and inspect names, countries, and identifiers before deciding what needs a closer look.
Bring sanctions information, individual monitoring, and connected notifications into one clear workspace.
Built for compliance, due diligence, and risk monitoring workflows.
Import sanctions information from supported official lists.
Screen subscriptions against the stored sanctions data.
Investigate candidates and receive configured notifications.
A straightforward workflow for your team and the systems you already use.
Search stored sanctions names and aliases and inspect names, countries, and identifiers before deciding what needs a closer look.
Create a subscription for an individual, including a name that does not appear in your current search results.
Review candidates, source references, name similarity, and the explanation behind each match.
Create subscriptions from your backend using the REST API. Receive screening results through configured webhooks and review delivery history.
Search for a record or create monitoring for the name you want to follow.
Use available email or webhook channels to receive screening results.
After a screening run, inspect potential candidates and their matching details.
Later screenings send notifications when results change, including removed matches.
Coverage depends on the sources imported into the platform.
Consolidated financial sanctions
Consolidated sanctions data
OFAC SDN and non-SDN lists
Consolidated sanctions data
NSDC sanctions on individuals
Consolidated sanctions list
Potential sanctions matches need an identity check. Review names, identifiers, and source information together. “No identified match” describes the stored data checked during a screening run.
A potential match is a candidate for review. Names can be shared by different people. Compare the available identifiers and source information before making a decision. A name similarity score describes the match; it is not an identity probability.
API-created subscriptions are queued for screening as soon as they are saved. Subscriptions are also checked after sanctions imports or when an administrator runs a separate subscription check. Configured channels receive initial results and later changes. When scheduled jobs are enabled, the platform supports daily imports followed by screening.
Yes. Create a key on API integrations, send subscription requests from your backend, and configure a webhook for results. Keys stay on your backend. The integration page includes the request model, examples, and a downloadable OpenAPI specification.
The platform retries delivery and records each HTTP attempt. Your organization can inspect outcomes, response previews, and errors, and retry eligible failed deliveries from the request details.
Search looks at names and aliases in the sanctions data currently stored in the platform. An empty search is not a sanctions clearance. You can still monitor the name so subscription screening can check it against the stored data.
Create a workspace, invite your team, and connect your systems.
Learn how sources, name matching, daily monitoring, and webhook delivery work together.