# Turn a name match into a finding you can assess.

> Review name and entity screening matches with their sources. Explore the scope and integration options of Legichain AML screening.

Canonical URL: https://legichain.com/en/aml-screening
Language: en
Other language: https://legichain.com/aml-screening

Compare customer and entity details against sanctions, PEP and related risk records. Manage your review process by assessing match likelihood and risk indicator separately.

- [Book a demo](https://legichain.com/en/contact?topic=demo)
- [Read the API documentation](https://legichain.com/en/developers)

_Interactive example (synthetic data): sample screening from full name, date of birth, country and type; two candidate records (sanctions list and PEP record), each with separate match confidence, risk indicator, system suggestion, source and team decision fields._

| Candidate | Source | Matched fields | Match confidence | Risk indicator | System suggestion | Team decision |
| --- | --- | --- | --- | --- | --- | --- |
| ALI ORNEK (SL-0419) | Sanctions list (sample source) | Full name, year of birth | 72% | High | Review | Pending |
| Ali Örnek Yılmaz (PEP-2210) | PEP record (sample source) | First name | 41% | Medium | Review | Pending |

## What do you check?

- **Sanctions records** — See possible matches against records in the supported sources.
- **PEP information** — Assess records associated with public functions in the customer's context.
- **Other risk records** — Clarify adverse media and related record types offered within the product scope in the evaluation call.

## Assess more than a name.

Similar names alone do not indicate the same person. Available additional identity details, the source of the record and the match details form the context of the review. Do not present results with missing data as definitive matches.

_Field comparison (synthetic): full name matched (spelling difference normalised); date of birth partial (year only); country and ID number not in the record; source record link available._

## Source, confidence and risk kept apart.

Three parts of the same sample result. Instead of a single unexplained percentage, each field answers its own question.

- **Source** — Review which record the finding rests on.
- **Match confidence** — Assess the indicators of how the result relates to the person or entity searched for.
- **Risk indicator** — Consider the record type and its significance for your institutional policy.

## Connect the check to your own flow.

Start the screening request from your integration. Link the result to the relevant customer record and pass it to your institution's review steps. Use the technical documentation for response fields and error states.

1. **Your integration** — Customer record or application event
2. **Screening request** — Name, identity fields, reference
3. **Result and source** — Candidate records, confidence, risk indicator
4. **Customer record** — Result linked by reference
5. **Review step** — Team decision and rationale

## See the screening scope in advance.

Sources, data types and product limits are part of the purchase evaluation. Clarify the sources and data types you need together with our team.

- [Book a coverage call](https://legichain.com/en/contact?topic=integration)
- **Sources** — Source name, record type, update approach
- **Data types** — Person, entity and available fields
- **Rescreening** — Initial screening and monitoring are separate capabilities
- **Report fields** — Record, rationale and decision record

## About AML screening.

### Does a match confirm that the customer is under sanctions?

No. The result is a finding that must be assessed with identity and source details.

### Is a PEP record grounds for automatic rejection?

PEP status on its own does not mean crime or automatic rejection. The related risk assessment is made within your institution's processes.

### Which lists are screened?

The current source list, record types and update information are shared in the evaluation call. An institution's name appearing on the site does not mean all of its datasets are supported.

### Is there ongoing monitoring?

Initial screening and rescreening/monitoring are different capabilities. Clarify the available monitoring scope in the technical evaluation.

## Let's define the flow that fits your needs.

Let's talk about the product scope, your integration requirements and your assessment process.

- [Book a demo](https://legichain.com/en/contact?topic=demo)
- [Read the API documentation](https://legichain.com/en/developers)

---
Legichain — technology for identity verification, AML and blockchain screening. Contact: contact@legichain.com