WC1 API - Perform Synchronous Screening: Resolution/MatchStrength/Keywords

Hi,

We already raised a support ticket, Case:08269366, but got redirected to this community for the technical part of our questions.

We would like to know how the Synchronous Screening API can be used to:

  • Expose Resolution value on the returned results ?
  • Filter the results based on the MatchStrength on WC1 side, so they are not returned as results ?
ex: "matchStrength": "STRONG",
  • Sources value structure: Only the last part corresponds to the World-Check Keyword Abbreviation Lists. What are the other parts in this value ?
ex: "sources": [
"b_trwc_RUPGO"
           ],

Regards,

Stijn Coppens.

Sort by:
1 - 1 of 11
    User: "Irfan.Khan"
    Accepted Answer

    Regarding Watchlist:

    I am sorry to break this to you but you will have to seek update about this on the support case you raised with Refinitiv.


    Regarding Resolution:

    Please find my answers below;

    • In both cases ("auto resolve as FALSE" & "remove from result") this setting ONLY applies on the matching of the secondary identifier values.----Yes
      So this has no impact on the "name" value matching?----Yes
    • A "mismatching" is detected when:
      The provided value is not equal to the WC DB value and can be configured using the "Manage the outcome of auto resolution" matrix?----Yes
      When the secondary identifier is checked, for a particular source, and a value mismatching is detected it will auto-resolve that match (to False or Remove). Correct?----Yes
    • "auto resolve as FALSE" : only usable in UI because this resolution-value is not exposed in API result.----No. We expose this information in the endpoint "SEQ-case-investigate-results: Get screening results". So with each match you will have resolution values for them too which would tell if a particular match is auto resolved. In version 2 of the API, this information will be available in the endpoint "SEQ-screen-sync-simple: Perform Synchronous Screening" too.
    • But "remove from result" : that result is totally removed and so also removed from the API screening result?----Yes
    • Can you provide me some additional info regarding the "Resolution Toolkit", how this plays a role in all this?----Yes. So any match that is auto resolved due to mismatch of the secondary identifier will have the resolution state marked as "False" while "Reason" state will be NULL/Blank and "Risk" state will also be NULL/Blank. This is how you can identify if the case was auto resolved. Please check the screenshot.

    image


    Thanks.