Screen an individual
In this tutorial, you'll understand what information is required to screen an individual's name against J.P. Morgan sources.
Before you begin
To retrieve the status of a Validation Services request, you will need the following:
- A registered and fully onboarded Developer Account on the J.P. Morgan Payments Developer Portal.
- An active profile that provides you with the credentials to make a request.
Screen an individual
The screening process automates the verification of client counterparty data, including personal identity data such as name, date of birth, address, and government-issued ID number(s) by comparing it against internal and third-party sources. To initiate screening, call a POST
request to the /v2/validations/entities
endpoint. The following example shows the required fields for verifying an individual using a government-issued ID:
Example of screening an individual
Json
[
{
"requestId": "individualPepSanctionsClear",
"entity": {
"individual": {
"firstName": "RAJ",
"lastName": "ROB",
"nameSuffix": "Jr",
"associatedCountries": ["US"],
"postalAddress": {
"addressLine": [
"10 S Dearborn"
],
"townName": "Chicago",
"countrySubDvsn": "IL",
"country": "US",
"postalCode": "60606"
},
"identification": [{
"idType": "PASSPORT",
"id": "E92821"
}
],
"gender": "M",
"dateOfBirth": "19900318"
}
}
}
]
The following example shows a CLEAR Sanctions and PEP response for an individual’s identity.
Example response for a government-issued ID verification request
Json
[
{
"requestId": "individualPepSanctionsClear",
"responses": [
{
"codes": {
"individualScreening": {
"code": 4509,
"message": "Clear"
}
},
"provider": "JPMC_SCREENING",
"details": {
"providerResponse": {
"realTimeResponseSchemas": [
{
"searchResponse": [
{
"searchConfigId": "EVS-SANCTIONS",
"result": {
"recordState": {
"state": "CLEAR"
}
},
"listName": {
"United States of America (the)": {
"BXA": "USA - BXA - Bureau Ind and Sec Denied Persons List",
"BISN": "BUREAU OF INTERNATIONAL SECURITY & NONPROLIFERATION SANCTIONS",
"CAPTA-561": "USA - CAPTA-561- OFAC CAPTA List",
"FSEL": "FOREIGN SANCTIONS EVADERS LIST",
"BXAENT": "USA - BXAENT - Bureau of Industry and Security - Entity List",
"BXAMEU": "USA - BXAMEU - Bureau of Industry and Security - Military End-User List",
"BXAUNVER": "USA - BXAUNVER - Bureau Industry and Security - Unverified List",
"NS-CAATSA-RUSSIA": "USA RUSSIA LIST",
"NS-IRAN": "USA-NS-IRAN – NON SDN List Iran (EO13599)",
"NS-PEESA": "USA - NS-PEESA - Protecting Europe's Energy Security Act",
"NS-PLC": "OFAC - PALESTINIAN LEGISLATIVE COUNCIL LIST",
"OFAC": "OFAC SDN LIST (OFFICE OF FOREIGN ASSETS CONTROL)",
"OFAC_NONSDN": "USA - OFAC-NONSDN - OFAC NON SDN List",
"SDTEL": "US STATE DEPARTMENT - TERRORIST EXCLUSION LIST",
"USCRAL": "USA - USCRAL - Cuba Restricted Accommodation List",
"USCRL": "USA - USCRL - Cuba Restricted list",
"USTREAS.311": "US TREASURY - US PATRIOT ACT SECTION 311",
"UN": "United Nations Sanctions"
}
}
},
{
"searchConfigId": "EVS-PEP",
"result": {
"recordState": {
"state": "CLEAR"
}
}
}
]
}
]
}
}
}
]
}
]
Related
- For more information about parameters, see Entity Validation parameters.
- For more information about the status responses and error codes supported by the Validation Services API, see Validation Services error response codes.
Next steps
- Learn how to verify a business entity.