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.
Where Sanction Screening fits.
Customer onboarding
Periodic sanctions review
Enhanced due diligence
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.
Supported providers
Availability depends on the installed release, licence entitlement, environment, and an active compatible connection.
A consistent path from request to review.
Submit
Identity details
Execute
Selected provider
Normalize
Bounded response
Review
History and 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
Start a conversation
Bring Sanction Screening into your OneView workflow.
See how OneView can fit your deployment, provider, and compliance workflow.