Skip to main content

PEP and Sanctions Check

Screen an identity against global Politically Exposed Persons and sanctions lists.

The PEP and Sanctions Check step screens a BasicIdentity data block against Politically Exposed Persons (PEP) and sanctions lists via a configured third-party provider. It returns two boolean flags — isPEP and isSanctioned — indicating the screening outcome.

This step is not user-facing and does not render any Player UI.


Key features

  • Lightweight screening: Returns two boolean flags rather than a rich match list. For full match details, ranked risk labels, and watchlist coverage, use the AML Screening step instead.
  • Single route: Always routes to continue regardless of the screening result; downstream logic (e.g. a Choice step) can branch on the isPEP or isSanctioned values.
  • Provider-backed: Requires nCino credentials configured on the Organisation.

Configuration

OptionTypeRequiredDescription
provider"NCINO"NoScreening provider. Currently only NCINO is supported. When omitted, the environment default is used.
inputSourcesObjectNoSpecifies the workflow step IDs to use for sourcing data. If omitted, the node uses the latest available data blocks from the workflow. See Input mapping.
inputSources.basicIdentityStringNoThe ID of the step providing the BasicIdentity data block.

Input data blocks

Data blockRequiredDescription
BasicIdentityYesIdentity data used for screening. familyName and givenName are mandatory. birthDate and birthPlace are used when available to improve match accuracy.

If BasicIdentity is not available, the flow fails validation.


Routes

RouteDescription
continueScreening completed. Inspect isPEP and isSanctioned in the output data block to determine the result.

Output data blocks

RouteData blocks producedNotes
continuePepAndSanctionsResultsContains isPEP and isSanctioned booleans.

Example payloads

PepAndSanctionsResults — subject is a PEP

{
"isPEP": true,
"isSanctioned": false
}

PepAndSanctionsResults — no match

{
"isPEP": false,
"isSanctioned": false
}