How It Works?

Safeguard your organisation against money launderers, Blacklisted persons, and other bad actors who pose a high risk to your organisation's safety. Shufti Pro's comprehensive AML solution allows organisations to screen their users against 1700+ global watchlists, FATF lists, PEP lists, and Sanction lists to make sure you are well protected from the danger of money laundering.

AML user screening operates in two distinct ways.

• Search Based
  In this approach, key user details like Name and Date of Birth are provided by the end user and searched against AML data sources.

• Document Based
  This method involves extracting essential information, such as the end user's Name and Date of Birth, directly from the document provided by the end user.

AML Data Sources

ShuftiPro's AML data sources encompass 1700+ global watchlists, FATF lists, PEP lists, and Sanction lists, providing an extensive foundation for robust anti-money laundering measures. With millions of profiles from high-risk entities globally, we utilise data from 240+ countries and territories, sourced from reliable international databases, ensuring compliance with local and global standards. These sources encompass:

• OFAC Sanction list
• United Nations Consolidated List
• EU External Action Service Consolidated list of Sanctions
• Sanction Related Entities
• European Council Restrictive Measures in view of the situation in Belarus
• Interpol Wanted
• EU Most wanted warnings

tip

To gain access to the complete list of data sources utilized in our AML (Anti-Money Laundering) processes, please reach out to our technical support team for further assistance at [email protected].

AML Filters

Shufti Pro offers its clients the ability to tailor their Anti-Money Laundering (AML) screening process by customising the AML filters to target specific AML lists for more focused and relevant checks.

Shufti Pro supports different filter types in AML service. All the supported filter types are mentioned below.

Filters

	Filters
1	sanction
2	warning
3	fitness-probity
4	pep
5	pep-class-1
6	pep-class-2
7	pep-class-3
8	pep-class-4

Classic Adverse Media Taxonomy filters

	Classic Adverse Media Taxonomy filters
1	adverse-media
2	adverse-media-general
3	adverse-media-narcotics
4	adverse-media-fraud
5	adverse-media-terrorism
6	adverse-media-sexual-crime
7	adverse-media-violent-crime
8	adverse-media-financial-crime

FATF-aligned Adverse Media Taxonomy filters

	FATF-aligned Adverse Media Taxonomy filters
1	adverse-media-v2-other-minor
2	adverse-media-v2-other-serious
3	adverse-media-v2-other-financial
4	adverse-media-v2-violence-non-aml-cft
5	adverse-media-v2-financial-difficulty
6	adverse-media-v2-regulatory
7	adverse-media-v2-general-aml-cft
8	adverse-media-v2-cybercrime
9	adverse-media-v2-terrorism
10	adverse-media-v2-violence-aml-cft
11	adverse-media-v2-narcotics-aml-cft
12	adverse-media-v2-fraud-linked
13	adverse-media-v2-financial-aml-cft
14	adverse-media-v2-property

Ongoing AML

Ongoing monitoring is crucial in the fight against financial crimes and terrorism financing. It requires constant vigilance and adaptation to evolving global watchlists of money laundering and regulatory changes. Our continuous AML monitoring process ensures that applicant information stays up-to-date with real-time changes to global sanction lists and watchlists, so organisations can maintain the integrity of their operations.

info

Shufti Pro automatically detects changes in AML status, than it sends a webhook with the event "verification.status.changed". You can check the new AML status using the "get status" endpoint or from the back office. For improved ongoing AML results, use "fuzzy_match = 1" in the name of the object.

Parameters

Description

ongoing

Required: No Accepted values: 0, 1 Default: 0 This Parameter is used for Ongoing AML Screening, and is allowed only on Production Accounts. If Shufti Pro detects a change in AML statuses, then we will send you a webhook with event verification.status.changed. The new AML status can be checked using get status endpoint, or from the back-office. Use fuzzy_match = 1 in the name object for better results for Ongoing AML Screening.

Name Preference in AML

Name is an object and contains the following parameters

Parameters	Description
first_name	Required: No Type: string Minimum: 1 character Maximum: 32 characters Allowed Characters are alphabets, - (dash), comma, apostrophe, space, dot and single quotation mark. Example: John'O Harra
middle_name	Required: No Type: string Minimum: 1 character Maximum: 32 characters Allowed Characters are alphabets, - (dash), comma, apostrophe, space, dot and single quotation mark. Example: Carter-Joe
last_name	Required: No Type: string Minimum: 1 character Maximum: 32 characters Allowed Characters are alphabets, - (dash), comma, apostrophe, space, dot and single quotation mark. Example: John, Huricane Jr.
fuzzy_match	Required: No Type: string Value Accepted: 1 Provide 1 for enabling a fuzzy match of the name. Enabling fuzzy matching attempts to find a match which is not a 100% accurate.
full_name	Required: No Type: string Minimum: 1 character Maximum: 64 characters Some countries don't have the identity document holder name as their first, middle or last name instead its written in full. In such cases, you may provide the full name.

name-sample-object

{
  "name": {
    "first_name": "John",
    "middle_name": "Carter",
    "last_name": "Doe",
    "fuzzy_match": "1"
  }
}

name-sample-object

{
  "name": {
    "full_name": "John Carter Doe",
    "fuzzy_match": "1"
  }
}

Verification Data Parameters

The following parameters are verified in the case of verification accepted or declined

Parameters	Description
dob	This key contains the date of birth of the person/entity on whom background checks are performed.
name	This key contains the first, last and middle name of the person/entity on whom background checks are performed.
name.first_name	This key contains the first name of the person/entity on whom background checks are performed.
name.middle_name	This key contains the middle name of the person/entity on whom background checks are performed.
name.last_name	This key contains the last name of the person/entity on whom background checks are performed.