PEP and sanctions screening for AML KYC compliance

Organisations searching for a PEP sanctions screening API are typically looking for an efficient way to identify potential politically exposed persons, sanctions matches and other name-screening risks as part of their AML and KYC processes.

A PEP and sanctions screening API is one way to connect screening data with an existing onboarding or compliance system. It is not, however, the only way to manage screening.

Cascade does not currently offer a standalone PEP or sanctions screening API. Instead, Cascade provides name screening within its core AML Software, allowing compliance teams to manage screening alongside client data, risk assessments and wider AML/KYC workflows.

Cascade runs daily name screening using data sources including LSEG World-Check, Dow Jones and Acuris Risk Intelligence.

What is a PEP and sanctions screening API?

A PEP and sanctions screening API is a technical interface that can allow another application to send information, such as a person’s or company’s name, to a screening service and receive potential match information.

Depending on the screening provider and implementation, this can be used to support checks involving:

politically exposed persons, or PEPs
sanctions lists
watchlists
adverse media or other risk information
individuals, companies and beneficial owners

For organisations building their own onboarding systems or compliance technology, an API can therefore be one possible way of incorporating PEP screening and sanctions screening into an existing technology stack.

However, compliance teams do not necessarily need a standalone sanctions screening API to manage these processes. Screening can also form part of a broader AML software workflow.

PEP and sanctions screening within Cascade AML Software

Cascade approaches PEP and sanctions screening as part of the wider AML KYC process rather than as a standalone API product.

The core Cascade AML Software brings together client and counterparty information, risk-based processes and ongoing compliance activities. Name screening is incorporated into this environment, helping teams keep screening activity connected to the relevant AML/KYC records.

Cascade’s current product information states that daily name screening is performed against sources including:

LSEG World-Check
Dow Jones
Acuris Risk Intelligence

This means organisations evaluating KYC screening tools can consider whether they need a standalone API or whether an integrated AML software approach better suits their operating model.

PEP and sanctions screening without a standalone API

A standalone sanctions screening API can make sense when an organisation has developed its own systems and specifically needs programmatic screening calls.

An integrated AML platform addresses the problem differently.

With Cascade, name screening forms part of the AML/KYC workflow instead of being offered as a separate PEP screening API. This allows compliance teams to work with screening results in the same environment used for client information and risk-based AML processes.

For organisations comparing screening solutions, an important question is therefore not simply, “Do we need a PEP sanctions screening API?”

It is also:

How should screening fit into our overall AML KYC process?

The answer will depend on the organisation’s technology architecture, compliance processes, screening volumes and regulatory obligations.

Managing name screening alerts

Identifying a possible PEP or sanctions match is only one part of the screening process. Compliance teams also need to review potential matches, determine whether they are relevant and maintain appropriate records of their decisions.

Cascade offers Automated Treatment of Name Screening Alerts as an add-on module to the core AML Software platform. It cannot be purchased as a standalone product.

The module can propose classifications for name-screening alerts and generate supporting narratives explaining the classification. Compliance analysts retain the ability to accept, edit or reject the proposed treatment, while actions are recorded with time and owner logs.

This can help organisations address an important operational challenge associated with PEP and sanctions screening: handling and documenting the alerts generated after screening takes place.

API screening versus integrated AML screening

Choosing between an API-based screening model and integrated AML software depends on how an organisation operates.

A PEP sanctions screening API may be considered when:

screening needs to be triggered programmatically from another application
an organisation has its own onboarding or compliance interface
screening is being incorporated into a custom technology architecture
developers need direct system-to-system screening functionality

Integrated AML software may be considered when:

compliance teams want screening connected to client and counterparty records
screening forms part of a broader AML/KYC workflow
risk assessment and ongoing monitoring need to be managed alongside screening
teams want to review screening information within their compliance platform rather than building a separate screening workflow

Cascade follows the second approach. It provides PEP and sanctions name screening within its AML Software platform, rather than selling a standalone PEP and sanctions screening API.

Taking a risk-based approach to PEP and sanctions screening

Technology can support screening, but it does not remove the need for appropriate compliance judgement.

Organisations should establish screening procedures that reflect their risk exposure, customer base, applicable sanctions obligations and AML requirements. Potential matches should be assessed appropriately, with decisions documented according to the organisation’s policies and regulatory responsibilities.

The appropriate approach can differ by industry and jurisdiction, particularly for financial services firms, asset managers, fund professionals, corporate service providers, law firms and other regulated organisations.

Organisations operating in Luxembourg or elsewhere in the EU should assess their PEP and sanctions screening processes against the legal and regulatory requirements applicable to their activities.

Frequently Asked Questions

Does Cascade offer a PEP sanctions screening API?

No. Cascade does not currently offer a standalone PEP sanctions screening API. PEP and sanctions name screening is provided within the Cascade AML Software.

Does Cascade support PEP and sanctions screening?

Yes. Cascade’s AML Software includes daily name screening, and Cascade’s current product information identifies LSEG World-Check, Dow Jones and Acuris Risk Intelligence among the data sources used for screening.

Is a sanctions screening API necessary for AML compliance?

Not necessarily. An API is one technical method of incorporating sanctions screening into another system. Organisations can also use AML software where screening forms part of the wider compliance workflow.

What happens when name screening generates an alert?

Potential matches need to be reviewed and treated according to the organisation’s AML and sanctions procedures. Cascade also offers Automated Treatment of Name Screening Alerts as an add-on module requiring the core AML Software platform. The module supports alert classification and documented treatment while keeping analysts involved in the final decision.

Explore Cascade’s PEP and Sanctions Screening Capabilities

If you are researching a PEP sanctions screening API because you want to improve screening within your AML and KYC processes, a standalone API is not the only option.

Explore how Cascade’s AML Software brings name screening together with broader AML/KYC workflows, or learn more about the Automated Treatment of Name Screening Alerts add-on for supporting the treatment and documentation of screening alerts.