The Monitor API enables individuals and companies to be screened on an ongoing basis against our proprietary AML database. All information available through the KYC6 application is accessible, e.g. relationships, article summaries, and corresponding URLs.
The API provides access to the following datasets: PEPs, Sanctions, Regulatory Enforcement Lists, Profiles of Interest, Insolvency, Disqualified Director, Regulatory Enforcement List.
If I search "Donald Trump" and then search again a day later, is that two separate searches?
Yes, each search is considered unique as we don’t pass a “Search Id” as part of the request or response.
How do I get rid of false positives and automate the responses for on-boarding?
The nature of the data means that it’s impossible to eliminate false positives entirely as there is no specific unique identifier such as a passport number or national ID, but we can make suggestions to reduce false positives as much as possible. However this will need to be tested in-line with your risk-based approach. The best practice matching criteria for reducing false-positives is “Forename + Surname + DOB/YOB + Country” as this provides multiple data points to match on.
For on-boarding many clients just search against PEP & Sanctions rather than all data sets, and in particular adverse media as it is a much larger datasets which can introduce false positives. By nature, adverse media profiles aren’t always as complete as PEP or Sanction profiles because the evidence isn’t readily available. In the request, a “Threshold” can be set to filter out matches below a given score, the default we suggest is 70 however this could be increased using the matching criteria mentioned above. Again, this will need to be tested in-line with each client’s risk-based approach.
Once a query has been defined, logic can be implemented to say “IF Matches = Fail, further due-diligence required”. IF NO Matches = Pass, and add record to On-going Monitor via API. There needs to be an element of accountability required for matches above the “threshold” where a compliance professional decides whether to on-board a customer and accept risk, discount false positives, or terminate the relationship with a customer. Therefore, the process can’t be automated fully.
How do we filter the API query by PEP position for local jurisdictions? i.e. In Italy how do we filter out lower level PEPs such as Mayors of small towns?
There isn’t the ability currently to filter at a granular level such as by political position, or by sanction body. However, there is an element of post-response filtering that could be implemented using “PEP_Tier” or “Sanction_Body“. Using the example of lower-level Italian PEPs, there is a note on the profile referencing PILs – “Italian Public Administration”. For other jurisdictions, you can use the “PEP_Tier” and “Country” to filter out. All of the PEP Tiers mapped to the political position is available in Acuris Editorial Content Guide.
Where is the API hosted?
Both are based in London (Equinix and Powergate)
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
|__cfduid||1||29 days 23 hours 59 minutes||The cookie is used by cdn services like CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information.|
|cookielawinfo-checkbox-necessary||0||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-non-necessary||0||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Non Necessary".|
|JSESSIONID||1||13 days 23 hours 59 minutes||Used by sites written in JSP. General purpose platform session cookies that are used to maintain users'' state across page requests.|
|vuid||1||1 years 11 months 28 days 23 hours 59 minutes||This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.|
|XSRF-TOKEN||1||1 days 23 hours 59 minutes||The cookie is set by Wix website building platform on Wix website. The cookie is used for security purposes.|
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
|_ga||1||1 years 11 months 28 days 23 hours 59 minutes||This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site''s analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.|
|_gat_gtag_UA_45487328_32||0||This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.|
|_gat_UA-85023278-1||0||This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.|
|_gid||1||23 hours 59 minutes||This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form.|
|_omappvp||1||10 years 11 months 10 days 23 hours 59 minutes||The cookie is set to identify new vs returning users. The cookie is used in conjunction with _omappvs cookie to determine whether a user is new or returning.|
|_omappvs||1||9 minutes||The cookie is used to in conjunction with the _omappvp cookies. If the cookies are set, the user is a returning user. If neither of the cookies are set, the user is a new user.|
|bscookie||1||1 years 11 months 29 days 11 hours 37 minutes||This cookie is a browser ID cookie set by Linked share Buttons and ad tags.|
|ELQSTATUS||1||1 years 1 months||This cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from, and the pages they visited. Once consent is provided, through a form submission by the visitor, we can associate a visitor's ID to individual characteristics and past behavior.|
|li_sugr||1||2 months 28 days 23 hours 59 minutes||This cookie is used to make a probabilistic match of a user's identity outside the Designated Countries.|
|lissc||1||11 months 29 days 23 hours 59 minutes||This cookie is provided by LinkedIn. This cookie is used for tracking embedded service.|
|UserMatchHistory||1||29 days 23 hours 59 minutes||Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences.|
|i18next||1||11 months 29 days 23 hours 59 minutes||No description|
|KV_CLIENT_SESSION_ID||1||11 months 29 days 23 hours 59 minutes||No description|
|pap_session||1||1 days 23 hours 59 minutes||No description|
|pap_wcaid_288||1||5 days 23 hours 59 minutes||No description|
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
|bcookie||1||1 years 11 months 29 days 11 hours 37 minutes||This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page.|
|ELOQUA||1||1 years 1 months||The domain of this cookie is owned byOracle Eloqua. This cookie is used for email services. It also helps for marketing automation solution for B2B marketers to track customers through all phases of buying cycle.|
|lang||1||session||This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website.|
|lidc||1||23 hours 59 minutes||This cookie is set by LinkedIn and used for routing.|