Skip to content
All KYC services
Screening · KYC

Sanction Screening

Sanction Screening has its own entitlement, provider connection, request, usage attribution, and result history. It never runs PEP Screening in the background.

What it does

Screen a person against sanction-related records without triggering a PEP search.

Available when the service is licensed, installed, and connected to a compatible provider.
Common workflows

Where Sanction Screening fits.

Customer onboarding

Periodic sanctions review

Enhanced due diligence

Request

Ask for only what the service needs.

The selected provider service determines the exact fields available in OneView. Sensitive identity data should be handled according to the client’s approved purpose and policy.

First and last name
Middle name
Date of birth, nationality, and gender when supported

Supported providers

PremblyCompatible services
OpenSanctionsCompatible services

Availability depends on the installed release, licence entitlement, environment, and an active compatible connection.

Workflow

A consistent path from request to review.

01

Submit

Identity details

02

Execute

Selected provider

03

Normalize

Bounded response

04

Review

History and result

Result

Focused context, protected by access controls.

OneView stores the verification history in the client environment and limits full sensitive-result access to authorized users.

Result overview

Screening outcome
Match count
Match confidence, when supplied
Manual-review status
An automated candidate match does not establish that a person is sanctioned. Review the available identity context and follow the organisation’s approved escalation process.

Start a conversation

Bring Sanction Screening into your OneView workflow.

See how OneView can fit your deployment, provider, and compliance workflow.

Request a demo