What is the end to end processing time for Asynchronous screening?

We are planning to implement Asynchronous screening APIs. In
Claims system, we screen entities (individual/organization) when a Payment is
issued. Currently, we are calling Synchronous API when a system user is trying
to post Payment to verify if Payee is flagged. If there is a strong match, we
throw a business error indicating that Payee entity is flagged. A world check
one admin later on resolves the case that allows user to post such Payment. We
would like to keep same process with Asynchronous screening for all entities
those are screened before. Based on our knowledge, Asynchronous screening is a
multi-step process where we will making several API calls. We would like to
know what is the ideal end to end time duration (in seconds) to get screen results.
If you have are some clients who have implemented this process, can we get
some statistics from your Production environment? Let us know if you have any
query on this.
Best Answer
-
Each API call have their own response time. As in async screening, multiple API calls are involved, the time taken to complete the screening will be the combined sum of the request + response time for each API call.
Also, the time would depend on the time spent in propagating the hops between the client and the API server. This again is a variable that depends on the client's server location.
In addition to this, I would recommend to wait at least 20 seconds after sending the screening request and before calling the audit event API to find out if the case has been screened.
The best recommended step here would be to use the pilot environment and test the response time for each API call and total time taken to screen a case asynchronously.
0
Answers
-
Batch-processing end-to-end time totally depends upon the API used in the system. Along with that, it is necessary to check the performance of technology that supports API. In this way, we can estimate the time required for the speed of functioning of the payment system. If necessary, to perform the overall evaluation of the financial systems, it is a must to get in touch with the SMEs as well. API Ecosystem Strategy is an ideal one to choose payment modes.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 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
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛