Watchlist Screening Dashboard Setup

Before you start

Make sure you have the following:

Access to the RiskOS™ Dashboard with the Watchlist enrichment enabled.

• Your account owner or administrator can enable this for you. If you're unsure who to contact, reach out to support for assistance.

A basic understanding of RiskOS™ workflows and components.

• If this is your first time working with workflows, review the Workflow overview to understand inputs, enrichments, routing logic, and decisions.

How it works

Watchlist Screening evaluates individuals or businesses against relevant sanctions, PEP, and adverse media watchlists and returns match data that can be used for compliance and risk decisioning.

👤 Screening individuals

Use Watchlist Screening to verify that an individual entity is not listed on any relevant watchlist before gaining access to your platform.

Workflow enrichments:

• Fraud checks — phone risk, email risk, Sigma Identity, Sigma Synthetic, First-Party Fraud, Graph Intelligence, and Device Risk
• Identity verification — use Verify to check core identity details against government sources (name, date of birth, national ID number, SSN, address)
• Document & biometric verification — for higher-risk cases, add document verification or biometrics (name, DOB, national ID)
• Watchlist screening — send at least the name; include additional identifiers (DOB, national ID, phone, email, IP address, address) when available for higher accuracy

🏢 Screening businesses

Use Watchlist Screening to verify that a business entity is not listed on any relevant watchlist before engaging in a financial or contractual relationship.

Workflow enrichments:

• Global KYB — confirm the primary business entity exists
• Ultimate beneficial owners (UBOs) — gather a list of all individuals or businesses with 25% or more ownership
• Individual screening — run KYC on individual UBOs and screen them against watchlists
• Business entity screening — run watchlist checks on the business name itself; if entity type is unclear, pass the name without type classification

How Watchlist Screening fits into a workflow

In RiskOS™, workflows are built by connecting reusable components. Watchlist Screening is added as an Enrichment step.

Once the enrichment runs, its outputs are available to downstream workflow components, such as:

• Conditions
• Decision rules
• Rule score cards
• Manual review steps
• Final decisions

Execution flow in RiskOS™

Watchlist Screening runs synchronously as part of a RiskOS™ workflow.

Input

Watchlist Screening

Routing logic

Decision

At a high level, the execution flow looks like this:

1. Input

You call the Evaluation API with individual or business entity data.

2. Watchlist Screening enrichment

RiskOS™ evaluates the entity against applicable watchlists and returns match data and reason codes.

3. Routing logic

The workflow evaluates match presence, categories, and reason codes.

4. Decision

The workflow returns a final outcome (for example, Accept, Review, or Reject).

Create a workflow for Watchlist Screening

Input step

The input step represents the data you send when you create an evaluation.

• No configuration is required for the input step.
• When you send an evaluation request, follow the guidance for required input fields for the Watchlist enrichment step.

Workflow components used by Watchlist Screening

Watchlist Screening uses a subset of standard RiskOS™ workflow components.

Configure Watchlist Screening

Add Watchlist Screening to a workflow

1. In the RiskOS™ Dashboard, go to Workflows and create a new workflow or open an existing one.
2. On the workflow canvas, select the plus (+) icon.
3. Add an Enrichment step and choose one of the following:
   • Socure Watchlist Standard
   • Socure Watchlist Plus
   • Socure Watchlist Premier

Each tier provides different screening depth and capabilities.

Configure routing logic

Use Condition steps to route evaluations based on Watchlist outputs.

Common routing strategies include:

• Routing any match to Manual Review
• Routing specific categories (Sanctions, PEP, Adverse Media) to different queues
• Combining Watchlist signals with other fraud or identity signals

Manual Review steps

You can add Manual Review steps as terminal workflow steps.

Manual Review steps:

• Route cases to queues in the RiskOS™ Dashboard
• Support multiple queues using decision codes (for example, separate queues for Sanctions, PEP, and Adverse Media)

📘 Note: You cannot currently approve a case and then send it to Manual Review in the same workflow path. However, you can use tags to label cases and apply additional review or approval logic in your own case management system.

Save and publish

Once your workflow is configured, publish it to go live.

Workflow testing checklist

Use this checklist to confirm accuracy, resilience, and completeness before going live.

Input validation:

Required entity fields (individual or business name) are provided.

Additional identifiers (such as date of birth, national ID, or address) are passed where available.

Entity type (individual or business) is correctly specified or inferred.

Routing and decisioning:

Watchlist matches are detected and evaluated correctly.

Reason-code-based routing behaves as expected.

Workflow routing reflects your intended compliance and risk strategy.

Operational readiness:

Watchlist match details and reason codes are accessible to relevant teams.

Manual Review queues and escalation paths are defined and monitored.