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.
For a deeper look into our World Check One API, look into:
4.2k
●7 ●5 ●6
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.
