World Check - different results when screening using portal and via API call

Hi, With respect to Worldcheck integration, would want to understand why the search results that we see manually (as a user) look different than the search results received when making an API call
For example, when the same individual is searched via API Request, we can see FIELD LEVEL matching (API Response is as attached below), whereas as a manual user, the response comes into categories of whole record as UNRESOLVED, FALSE, POSITIVE, POSSIBLE (screenshot attached).
Can you please clarify why are they shown differently and why as a user, we cannot see field level matching when using the portal
Thank you
Regards,
Joseph
SEQ-case-investigate-results: Get screening results
{{protocol}}{{gateway-host}}{{gateway-url}}cases/{{case-system-id}}/results
[
{
"resultId": "0a3687d0-6855-1dd2-9a1a-c507004d073a",
"referenceId": "e_tr_wci_2182105",
"matchStrength": "STRONG",
"matchedTerm": "Puthan Neduvakkatt Chenthamaraksha MENON",
"submittedTerm": "Puthan Neduvakat Chinthamarakshy MENON",
"matchedNameType": "PRIMARY",
"secondaryFieldResults": [
{
"field": {
"typeId": "SFCT_1",
"value": "MALE",
"dateTimeValue": null
},
"typeId": "SFCT_1",
"submittedValue": "FEMALE",
"submittedDateTimeValue": null,
"matchedValue": "MALE",
"matchedDateTimeValue": null,
"fieldResult": "NOT_MATCHED"
},
{
"field": {
"typeId": "SFCT_2",
"value": null,
"dateTimeValue": "1948-12-12"
},
"typeId": "SFCT_2",
"submittedValue": null,
"submittedDateTimeValue": "1948-12-12",
"matchedValue": null,
"matchedDateTimeValue": "1948-12-12",
"fieldResult": "MATCHED"
},
{
"field": {
"typeId": "SFCT_3",
"value": "ARE",
"dateTimeValue": null
},
"typeId": "SFCT_3",
"submittedValue": "ARE",
"submittedDateTimeValue": null,
"matchedValue": "ARE",
"matchedDateTimeValue": null,
"fieldResult": "MATCHED"
},
{
"field": {
"typeId": "SFCT_3",
"value": null,
"dateTimeValue": null
},
"typeId": "SFCT_3",
"submittedValue": "ARE",
"submittedDateTimeValue": null,
"matchedValue": null,
"matchedDateTimeValue": null,
"fieldResult": "UNKNOWN"
},
{
"field": {
"typeId": "SFCT_4",
"value": "IND",
"dateTimeValue": null
},
"typeId": "SFCT_4",
"submittedValue": "IND",
"submittedDateTimeValue": null,
"matchedValue": "IND",
"matchedDateTimeValue": null,
"fieldResult": "MATCHED"
},
{
"field": {
"typeId": "SFCT_5",
"value": "IND",
"dateTimeValue": null
},
"typeId": "SFCT_5",
"submittedValue": "IND",
"submittedDateTimeValue": null,
"matchedValue": "IND",
"matchedDateTimeValue": null,
"fieldResult": "MATCHED"
}
],
"sources": [
"b_trwc_PEP N"
],
"categories": [
"PEP"
],
"creationDate": "2019-01-20T11:45:07.293Z",
"modificationDate": "2019-01-20T11:45:07.293Z",
"resolution": {
"statusId": "0a3687d0-65b4-1cc3-9993-d3e6000019cf",
"riskId": null,
"reasonId": null,
"resolutionRemark": null,
"resolutionDate": null
},
"resultReview": {
"reviewRequired": false,
"reviewRequiredDate": "2018-04-24T00:00:00.000Z",
"reviewRemark": null,
"reviewDate": null
}
}
]
Best Answer
-
@dda63e54-bba3-45ee-ac5d-b08b71f10546_deprecated_9a13b0d1-564e-4ce1-82b4-b233965042b1
Secondly, you can check the field level matching or comparison of the submitted and matched data by clicking on the match that you're interested in followed by the clicking on the show more option as highlighted in the screenshot(FieldLevel.png , Fieldcomparison.png).
Let me know if this helps and feel free to reach out if you need a further detailed explanation.
Regards,
Mehran Khan
0
Answers
-
@dda63e54-bba3-45ee-ac5d-b08b71f10546_deprecated_9a13b0d1-564e-4ce1-82b4-b233965042b1
Hi,
The fields UNRESOLVED, FALSE, POSITIVE, POSSIBLE that you see in the UI provide you the resolution details about the case screened such as how many matches are marked positive, false or auto-resolved etc.
If i search for Donald Trump and I mark a match as positive you will see a corresponding entry in the POSTIVE field as 1(screenshot attached- markedpostive.png), similarly if i resolve other matches as FALSE or POSSIBLE they will show up against their respective fields.
It basically tells you if you have resolved any of the matches in the case as POSITIVE, FALSE etc.fieldcomparison.png
Secondly, you can check the field level matching or comparison of the submitted and matched data by clicking on the match that you're interested in followed by the clicking on the show more option as highlighted in the screenshot(FieldLevel.png , Fieldcomparison.png).
Let me know if this helps and feel free to reach out if you need a further detailed explanation.
Regards,
Mehran Khan
0 -
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 630 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 86 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛