World-Check one api result analyze
1: I called the API and passed in my name, birthday, and ID information. I hope to return results that meet all the above conditions, but in fact, a lot of fuzzy matching data is returned. For example, I entered James Smith, but the returned results include James Davies. Do I need to filter the results myself? Or how to set it up when calling the API to meet my needs.
2: I need to know whether the user is involved in financial crimes such as anti-money laundering. How can I get this data from the results of the world check one API.
Best Answer
-
Hi @nike.wang,
Thank you for reaching out. Below is the response to your questions:
To Question 1:
Below are the World Check screening settings that you can configure to help reduce the screening results you are receiving for the screened entity.
Matching Threshold: Log in to your WC1 UI and navigate to the admin section. There, you will find the “World Check Settings” section, where you can configure the matching threshold. This setting can range from “fuzzy” to “exact.” For example, if you set the matching threshold to “fuzzy,” you will see a broader range of results. Conversely, setting it to “exact” will display a narrower set of results. Note: We highly recommend testing the above under a testing group first and adjusting the matching threshold based on your risk appetite.
Auto Resolution Settings: You have two options that you can configure for auto resolution:
- Auto Resolve as False: If this option is selected, during the screening process, records that do not match the secondary identifiers you have provided (such as date of birth, gender, country, etc.) will be automatically resolved as false.
- Remove from Results: If this option is selected, records that do not match the secondary identifiers provided will be excluded from your results response.
To Question 2:
When you screen an entity using the
screeningRequest
endpoint, you can check the “category” field in the API response to determine the category under which the record falls. For more specific details about the record and to understand its source, use thereferenceId
of the matched World Check record and utilize therecords
endpoint. In the API response, the “sources” array will indicate the source identifier from which the record originates.I hope this helps! If you have any further questions or need additional assistance, please feel free to ask.
1
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛