Qual ID: We've tried with document pictures of different sizes against Identity Verification API endpoint (https://api.globaldatacompany.com/verifications/v1/verify), and we noticed it's always taking more than 2 mins to respond. Does it only occur in sandbox environment or is it also expected in prod environment? Attached is the Postman collection to replicate our testing case.
Results for Qual-ID Document Verification (IDV) transactions are returned in seconds and is typically returned under 20 seconds in a normal scenario. However, it can take longer (sometime more than a 2 minutes) and the processing time is dependent on several factors:
-The type of document
- Availability of a government-issued attribute such as an MRZ text on Passports or a Barcode on Driver's
- The quality of the image
- The speed of the internet connection
- A complete end to end transaction from capturing all three images (front and back of document and selfie)
takes approximately 30-45 seconds in a normal scenario. It shouldn’t go anything more than 120 seconds and that would normally happen if the service is failing over from automated to manual review. This is where asynchronous call should help.
The Document Verification service follows 2 tiered system i.e. if the first tier (automatic check) doesn’t pass the first automatic tier, it waterfalls to the manual source so the job processing time can be anywhere from 2 minutes upwards. Because of this extended transaction time, the customer portal may not always be suitable for document verification as the interface may time out but the transaction will complete.
The most effective way to utilize these services is to send an asynchronous API request. Usually, when a document fails first tier (automatic verification service) but passes on the second tier (manual verification), it is usually down to the quality of the image uploaded
In order to utilize the asynchronous API request, I suggest you use Callback URL element in the API request which could eliminate the latency issue that you may have encountered. Once the asynchronous request is invoked, it would generate the transaction ID on the callback url that you will provide. Using that transaction ID, you should be able to retrieve the response through Get Transaction Record API call