When building a DVS application following the enhanced integration workflow you will be responsible for building two applications
- Client Side Application
- Backend Application
Your client application will make requests directly to the DVS server using the Public Key provided by
IDScan.net. The DVS server will return a request ID to the client application that will then be sent to your backend application. Your Backend Application will then make a request to the DVS server using the Secret Key and passing along the requestId and it is this request that will kickoff the processing of the request made by the Client Side Application.
The Enhanced Integration option enables increased efficiency of request processing by adding the results of each request to a queue which your backend application can then request the results from, as opposed to the Simple Integration option, where your application must simply wait on the request to receive a response.
The keys you were provided by IDScan.net will be used in the following way
|Client Side Application||Public Key|
|Backend Application||Secret Key|
When your Backend Application is making requests to the DVS server for document verification it will be required to use the
IDScan.net has provided you.
Web Library License Key
The License Key you were provided by IDScan.net will be used in your Client Side Application. This License Key is meant to be used on a single domain where the client side application is hosted.
|Client Side Application||License Key|
During testing you can host your application at localhost with any License Key no matter what domain it is configured to be used with.
Use the Public Key to create a Verification Request and upload ID image(s) and a selfie image to the DVS server.
The DVS server will return the requestId and the status of the request you have just created to the Client Side Application.
The Client Side Application will pass the requestId to your Backend Application.
The Backend Application will send the requestId using the Secret Key to the DVS server via the Verify API to receive the results of the verification process, including the general level of trust.
The Backend Application will then forward any results that need to be shared with the Client Side Application.