How to use World check one API result

vishwanath.kumar

Hi,

As i am using WC1 for KYC and as we are checking API and documentation i have few question like as :

1) getting more than one result for a case

1a) getting STRONG as strength for multiple matched result

1b) do we need to call Profile API for all matched result to confirm

1c) how to check which result is matching our search query, as it give result matching on different query like as one is matching with name, other with gender, another with DOB

2) in resolution toolkit we have status, risks and reasons with different value. How to use these to determine user background is positive or not? Is there any documentation for these, what is the meaning of these values?

Prabhjyot

@vishwanath.kumar,

Can you please use the passport document type as Passport?

{ "typeId":"SFCT_14", "value":"PASSPORT" }

Hope this helps.

Prabhjyot

@vishwanath.kumar,

Thank you for your query.

1. Getting more than one result for the case -

a & b. You may refer to the details of the STRONG and EXACT match in the results. If you find the information in the results is not enough for you /your compliance team to zero into your match, then you may use the API call - 'Get a World-Check profile' for further analysis of the match.

c. If you screen an entity with secondary identifiers, the resolution would depend on the value of the secondary fields. If the secondary field matches the submitted term, you may look into the details of the profile. However, if the hit does not matches the submitted secondary field value, the specific match gets resolved as false due to the auto-resolution toolkit. You can access the auto-resolution toolkit settings from the World-Check One UI, under Admin section.

You may also refer to the below link for more information - https://community.developers.refinitiv.com/questions/36946/few-queries-on-case-screening-request-api-to-help.html?childToView=36935#answer-36935

2. Resolution Toolkit: The resolution toolkit provides the values of the status, risk and reason. Each statusId will have risk and reason Ids associated to it and the same can be used for resolving the matches using the API. The resolution works in API exactly as it works in the UI. If you select a specfic status for a match, you can only use the corresponding value of risk and reason to resolve the match.

If you pick a statusId from the response of API call - 'Get the resolution toolkit for a group' and search for it in "resolutionRules", you will find the associated riskId and reasonId which can further be used for resolving the match.

Hope this clarifies your concern.

vishwanath.kumar

Thanks @Prabhjyot

i have another query : i am creating a case with name and passport details like as this

{
  "secondaryFields": [{ "typeId":"SFCT_1", "value":"FEMALE" },
  	{ "typeId":"SFCT_2", "dateTimeValue":"1964-01-17" },
  	{ "typeId":"SFCT_3", "value":"USA" },
  	{ "typeId":"SFCT_4", "value":"USA" },
  	{ "typeId":"SFCT_5", "value":"USA" },
  	{ "typeId":"SFCT_8", "value":"Michelle" },
  	{ "typeId":"SFCT_9", "value":"Obama" },
  	{ "typeId":"SFCT_10", "value":"FEMALE" },
  	{ "typeId":"SFCT_11", "value":"illinois" },
  	{ "typeId":"SFCT_12", "value":"USA" },
  	{ "typeId":"SFCT_13", "dateTimeValue":"1964-01-17" },
  	{ "typeId":"SFCT_14", "value":"P" },
  	{ "typeId":"SFCT_15", "value":"910239248" },
  	{ "typeId":"SFCT_16", "dateTimeValue":"2018-12-05" }],
  "entityType": "INDIVIDUAL",
  "customFields": [],
  "groupId":"{{group-id}}",
  "providerTypes": [
    "WATCHLIST",
    "PASSPORT_CHECK"
  ],
  "name": "Michelle Obama"
}

but i am getting 400 Bad request as response. Any reason for this?