Available Third Party Verification Services Offered by IDScan.net
Services Enabled by Default
- Address Validation Check
If you wish to add additional third party verification checks to be performed on the data sent to DIVE, there are several options available listed below.
Optional Services that can be Added for a Fee
DMV Data Verification
IdentiFraud
Shufti Pro for International Documents
DMV (Department of Motor Vehicles) is a government agency that administers motor vehicle registration and driver licensing. The DMV Data Verification Service allows an organization that is presented with a license or ID card to verify that the data on the card matches the data held by the jurisdiction that issued the document. The Driver’s License data verification check users will submit the data on a license and the service will return a boolean value for each data element that indicates if the element matches the data they have in their database.
IdentiFraud is a third party check that can verify a person's identity is legitimate. By submitting consumer-provided information (i.e. First Name, Last Name, Address, City, etc), IdentiFraud will provide a detailed report as to whether or not the submitted data is from someone who actually exists.
These third party checks can be enabled in the DIVE API Web Portal in the Settings section.
If the customer uses API endpoints (POST /v4/verify) to make verification requests it is possible to set corresponding DMV and IdentiFraud parameters there.
These services can be applied to check both sides of the document (front and back) or one side of the document (front or back).
The customer may have the following statuses of the services (https://dvs2.idware.net/api/docs/v4/swagger.json):
Status: -1,
Status: 0,
Status: 1,
Status: 2
- Status: -1. The third party check has been disabled in the settings.
Status: 0. The status is returned if the third party check was configured to run, but failed to for some reason.
Status: 1. The services are configured to run, and were able to successfully complete.
- Status: 2. This status is used for several reasons: a) The third party check has been configured to run but the customer has used all available DMV or IdentiFraud requests.
b) The third party check has been configured to run, however they are not run, because the total confidence of the document is below an internal threshold that all documents must pass in order to warrant the use of third party check. This avoids sending a document to a third party service when it has no chance of passing the check and will fail based on the DIVE API's analysis alone.
c) Some states do not support running the DMV Verification third party check and so submissions for documents from those states will have this status in the response.
Shufti Pro service is an additional external verification of data parsed by OCR for such international documents (document type 7) as international DL/IDs. The customer sends Front Image for verification and optionally Back Image for additional verification, and empty values for Name, DOB, IssueDate, ExpiryDate, DocumentNumber and Gender and the Shufti Pro system verifies the provided document for authenticity.
New International ID parsing strategy provides an option to send requests to Shufti Pro only if MRZ is not recognized. The value is true (isShuftiSucess = true) provided at least one of the following fields FirstName, MiddleName, LastName is returned in the response.
When the customer sends the request for the document type: 7, but the back side of the document (with MRZ) is not recognized, however, the front side of the document is recognized by the Shufti system and returns at least one of the above mentioned fields, then the isShuftiSuccess = true.
When the customer sends the request for the document type: 7, but the back side (with MRZ) of the document is not recognized, and no fields (FirstName, MiddleName, LastName) are returned to the response by the Shufti system, then the isShuftiSuccess = false.
When the customer sends the request for the document type: 7, and the back side (with MRZ) of the document is recognized, then the Shufti system is not run, isShuftiSuccess = null.
If the Shufti system also fails to recognize the document (isShuftiSuccess = false) the strategy returns an MRZ error.
If the customer selects another document type by mistake the Passport parsing strategy is applied which provides an option to check the document type for every request and change the initial type if the value is a Passport.
Questions
Find out more information about adding additional third party checks to your DIVE deployment by reaching out to our team at support@idscan.net