AML screening (basic) (v1)

Deprecated

AML screening (basic) (v1) is deprecated. Use AML screening (advanced) (v1) instead. It covers PEP and sanctions screening with ranked match details through a single AML configuration. Replace this step with AML screening (advanced) (v1) in your existing flows.

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 (advanced) (v1) step instead.
• Single route: Always routes to continue regardless of the screening result; downstream logic (e.g. a Conditional routing (v1) step) can branch on the isPEP or isSanctioned values.
• Provider-backed: Requires nCino credentials for your organisation. If they aren't set up yet, Studio warns you about missing credentials, and you can't launch a session or promote the flow until they are configured. Contact your Account Manager to have them configured.

---

Configuration

Option	Type	Required	Description
provider	string	No	PEP and sanctions screening provider. Currently only NCINO is supported. When omitted, the environment default is used. Accepted values: NCINO.

Example configuration

{
  "provider": "NCINO",
  "inputSources": {
    "basicIdentity": "collect-identity"
  }
}

---

Input data blocks

Data block	Required	Description
BasicIdentity	Yes	Identity data used for screening. familyName and givenName are mandatory. birthDate and birthPlace are used when available to improve match accuracy.

If no earlier step in the flow produces a BasicIdentity data block, the flow fails validation. To fix this, add a step that produces BasicIdentity before this one, for example an ID document verification step.

---

Routes

Route	Description
continue	Screening completed. Inspect isPEP and isSanctioned in the output data block to determine the result.

---

Output data blocks

Route	Data blocks produced
continue	PepAndSanctionsResults

Example payloads

PepAndSanctionsResults — subject is a PEP

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

PepAndSanctionsResults — no match

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

---