Skip to main content

Offsite Integration

In this verification procedure, the client is required to provide Shufti with the end user's full name and date of birth. Leveraging this data, Shufti conducts thorough Anti-Money Laundering (AML) screening to validate user identity.

Parameters and Description

ParametersDescription
dobRequired: No
Type: string
Format: yyyy-mm-dd
Provide a valid date.
Example: 1990-12-31

Note: It is recommended to send dob for more accurate results.
nameRequired: No
Type: object
In name object used in background checks service, first_name required and other fields are optional. Parameters for name are listed here:
Example 1: { "first_name" : "John", "last_name" : "Doe" }
Example 2: { "first_name" : "John", "middle_name" : "Carter", "last_name" : "Doe"}
Example 3: { "full_name" : "John Carter Doe"}

Note: If full name is provided with first and last name priority will be given to full name.
biometric_search_imageRequired: No
Type: string
Format: Base64 encoded JPG, JPEG, PNG
Maximum: 5MB (decoded)
A base64-encoded facial image of the individual being screened. Used for biometric matching against records across connected AML databases to improve the accuracy of match assessments.
ongoingRequired: No
Accepted values: 0, 1
Default: 0
This Parameter is used for Ongoing AML Screening, and is allowed only on Production Accounts. If Shufti 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.
Note: Use fuzzy_match = 1 in the name object for better results for Ongoing AML Screening.
ongoing_adverse_mediaRequired: No
Accepted values: 0, 1
Default: 0
This parameter enables Ongoing Adverse Media Monitoring and is allowed only on Production Accounts. When set to 1, Shufti continuously monitors for changes in adverse media status and sends a webhook with event verification.status.changed when a change is detected.
Note: This parameter only takes effect when adverse-media is included in the filters array.
filtersRequired: No
Type: Array
Default: ["sanction", "warning", "fitness-probity", "pep", "pep-class-1", "pep-class-2", "pep-class-3", "pep-class-4", "adverse-media"]

This key includes specific filter types, namely, alert or warning, that are linked to the AML search. Use these filters within the search to refine and narrow down the results. All filter types are listed here.
match_scoreRequired: No
Type: String
match_score indicates the extent to which a search should accommodate variances between the search term and the terms being matched. A value of 0 signifies a loose match, while 100 indicates an exact match.
Note: It ranges from 0-100. By default value is 100.
Example: "100".
risk_score_engine_idRequired: No
Type: string
The ID of a custom risk-scoring engine to apply to the screening results. If none is provided, the default risk-scoring engine is applied. See Custom Risk Scoring Engine.
countriesRequired: No
Type: Array
Array of countries based on which you want to filters reports. See Countries.
Note: ISO 3166-1 alpha-2 country codes are supported.
Example: ['CA','IN']
alias_searchRequired: No
Type: Boolean
Alias search is used to specify whether user want to perform search within aliases or not.
Note: The default value of alias_search is '0'.
Example: "0".
rca_searchRequired: No
Type: Boolean
RCA search is used to specify whether user want to perform search within rca or not.
Note: The default value of rca_search is '0'.
Example: "0".
unique_idRequired: No
Type: string
A unique identification number of the subject, such as a passport number, national ID, company registration number, or business registry number, used to prioritise the most relevant records in the search results.
individual_faceRequired: No
Type: string
Format: JPG, JPEG, PNG, PDF
Maximum: 16MB
A facial image of the individual being screened, submitted as a biometric input to match against records across connected AML databases and improve the accuracy of match assessments.
contextRequired: No
Type: string
Additional information about the subject being screened, provided by the merchant to give the AI Compliance Agent richer context for a more accurate and targeted match assessment.

Run in Postman


background_checks-service-sample

//POST / HTTP/1.1 basic auth
//Host: api.shuftipro.com
//Content-Type: application/json
//Authorization: Basic NmI4NmIyNzNmZjM0ZmNlMTlkNmI4WJRTUxINTJHUw==

{
"background_checks": {
"alias_search": "0",
"rca_search": "0",
"unique_id": "",
"individual_face": "",
"context": "",
"ongoing": "0",
"match_score": "100",
"countries": ["gb", "cy"],
"name": {
"first_name": "John",
"middle_name": "Carter",
"last_name": "Doe"
},
"dob": "1955-07-26",
"filters": ["sanction", "warning", "fitness-probity", "pep", "pep-class-1", "pep-class-2", "pep-class-3", "pep-class-4", "adverse-media"]
}
}

info

OCR for name recognition in AML checks is exclusively conducted when utilized with services that incorporate OCR functionality, such as Document Verification, Document Two Verification, and Address Verification.