IDKit PEP/Sanctions - Powered by Acuris/ION

Specification used for IDKit Integration

IDKit PEP and Sanctions, powered by Acuris/ION, supports compliance efforts by screening datasets to verify that individuals are not politically exposed persons or under sanctions. This tool helps manage reputational and regulatory risks by ensuring individuals do not have these risk factors. The search outcome is to ascertain whether an individual's first name, last name, or date of birth matches any entry within the dataset, subsequently flagging or passing the results as appropriate.

The result of the search will include some basic information about the profile – enough for you to identify whether or not the match is, in fact, the profile you searched for.

Integration Notes

There are some things that you need to know for the integration:

• Data used for validation: name + date of birth.
• Datasets (pepTiers) used: [PEP,SAN,REL,RRE]. See the description below:

• The ION endpoint is called /individuals.
• With reference to the SearchIndividualsRequest schema found here in the ION API Specification, we are using all default values.

📘

Note:

• Please refer to the Reseller documentation for instructions on how to configure the IDKit PEP/Sanctions Data Provider.
• Please refer to the API documentation for IDKit PEP/Sanctions - Powered by Acuris/ION.

Example Results in IDKit

Failed result – Portal

If there’s a match found for name + date of birth in any of the pepTiers i.e. [PEP,SAN,REL,RRE], the transaction will be flagged. See the example below:

Passed result – Portal

If there’s no match for name + date of birth of birth found in any of the pepTiers i.e. [PEP,SAN,REL,RRE], the transaction will pass. See the example below:

Flagged Txn Redacted result - Portal

See the example below:

💬 We Are Here to Help!

If you encounter an issue, a bug, or require assistance, please contact our support page here to find the solution. Don't forget to provide any important information on the issue.