RiskOS™ Dashboard Setup

Set up Verify or Verify Plus in the RiskOS™ Dashboard

Before you start

Make sure you have the following:

How it works

Socure Verify and Verify Plus are identity verification enrichments available in RiskOS™. They check identity inputs like name, date of birth, and national ID against authoritative sources to return a decision.

Both products return:

Feature flags and data eligibility

Some datasets used in Verify and Verify Plus require additional configuration or eligibility steps. These features are controlled by Socure's account team.

One example is the eCBSV service, a U.S. Social Security Administration (SSA) integration that verifies a person’s name, date of birth, and SSN against SSA records.

To use eCBSV:

• Your organization must complete a registration and approval process with Socure and SSA.
• A special consent disclosure and provisioning step must be completed before this service is active.
• Your API request must include consent to trigger the eCBSV lookup.

Until all requirements are met, this data source won’t be active in your workflow - even if the Verify or Verify Plus module is in place. Once provisioned, eCBSV data is included automatically in the enrichment process. It can improve match coverage, but it does not alter the structure of the response. Learn more about eCBSV requirements and registration steps.

How Verify and Verify Plus fit into a workflow

In RiskOS™, workflows are built by connecting reusable components. Verify and Verify Plus are added as Enrichment steps.

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

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

For more detail on these components, see Workflow Steps.

Execution flow in RiskOS™

Verify and Verify Plus run synchronously as part of a RiskOS™ workflow. There is no user handoff or pause in execution.

flowchart LR
    A[Input]
    B[Verify / Verify Plus]
    C[Routing logic]
    D[Decision]

    A --> B --> C --> D

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

1. Input
   You call the Evaluation API with identity attributes.

2. Verify / Verify Plus enrichment
   RiskOS™ evaluates the inputs against configured data sources and match tolerances.

3. Routing logic
   The workflow evaluates decisions, field-level results, and reason codes.

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

Workflow components used by Verify and Verify Plus

Verify and Verify Plus use a subset of standard RiskOS™ workflow components.

Configure Verify or Verify Plus

Configure match tolerances

Verify and Verify Plus include configurable match tolerances that control how strictly identity attributes are evaluated.

These settings are applied at the account level and affect all Verify evaluations.

Examples include:

📘

Note:

Use these settings to align match strictness with your policy. Default is lenient - tighten only where needed.

Exceptions:

For international workflows, partial national IDs are not accepted. The U.S. is the exception - either the last four digits or the full nine-digit SSN can be used. When only the last four are submitted, an exact match is always applied. If the full SSN is provided, your account’s match settings determine whether exact or fuzzy matching is used.

Standard match settings

Set match tolerances for Socure Verify and Verify Plus on the Settings > KYC tab in the RiskOS™ Dashboard.

The settings configured on this page apply to all Socure Verify evaluations for your account.

Add Verify or Verify Plus to a workflow

1. In the RiskOS™ Dashboard, go to Workflows and create a new workflow or open an existing one.
2. Add an Enrichment step.
3. Select one of:
   • Verify
   • Verify Plus

Configure inputs and routing

Typical required inputs include:

• Name
• Date of birth
• National ID

Optional inputs may include feature-gated sources such as eCBSV.

Common routing strategies include:

• Blocking or failing when required inputs are missing
• Escalating to additional verification when identity signals conflict
• Re-prompting users to correct or complete inputs
• Routing edge cases to manual review

Reason codes and field validations can be used to inform these routing decisions.

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.