Need To Know Expected Result and Behaviour

Hi,
I already done some reading on the documentation and perform one API call which is Perform a synchronous screening for a new case. Base on the JSON result return I would like to know these below items:
1. Base on the response, which JSON tag that will indicate that the case should not go through transaction. Is there any reason and status that we can find in response message?
2. By using pilot environment, it seems like it will return more than one case found by using only name field during screening process. Is this also expected behavior in production environment. Is there any method that need to be implemented to ensure that we found exactly matched for the case that we try to screen?
Thank You.
Best Answer
-
Thank you for your query.
1. In order to get the details of the resolution of a profile, you will have to use the API call - "SEQ-case-investigate-results: Get screening results". From the response of this API call, you can determine the resolution status of the match, which will contain reason, status and risk id. The definition of these ids can be obtained using the API call - "SEQ-pre-group-resolution-toolkit: Get the resolution toolkit for a group by provider"
2. You may utilize the secondary fields, which help help to narrow down the result. If the returned profile does not match any of the submitted secondary field value, then the result will be auto resolved as false. These auto resolution are based on the resolution toolkit settings, which can be manipulated via the Admin section of the UI. The skeleton of the fields can be obtained using the API call - "SEQ-pre-group-case-template: Get the case template for a group"
Please do let us know if you need further clarifications.
0
Answers
-
Hi.
Thanks for the answer from previous query.
However I got another question.
Can we said that we will need to do as below:
1. If matchStregth equals to EXACT, resolution field return with null, it safe to proceed with the transaction
2.If matchStregth equals to EXACT, resolution field is not null and riskId field is null, it safe to proceed with the transaction
3. If matchStregth equals to EXACT, resolution field is not null and riskId field is NOT null, we will need to reject/proceed with the transaction.
0 -
The resolution of the match within a case is to be performed from your end depending on your compliance logic or analysis. World-Check would only provide information on the profile.
You may alter the risk, reason and status from the Admin section of the UI.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 697 Datastream
- 1.5K DSS
- 632 Eikon COM
- 5.2K Eikon Data APIs
- 13 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 5 Trading API
- 2.9K Elektron
- 1.4K EMA
- 256 ETA
- 563 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 755 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
- 27 DACS Station
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 97 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛