What types of IDs and passports can be parsed using these tools?
The Java and C++ SDKs works for all North American government-issued IDs including the US, Canada, and Mexico. It also scans all global passports.
Can I used this SDK inside a web-based application?
For web-based applications we recommend using our digital identity verification engine (DIVE), which is an API product and better suited to web-based use cases. The Windows SDKs are for use in on-prem or standalone solutions.
Can the Windows SDK be used on images of IDs?
No. The Windows developer tools require the use of an ID scanning device. ID scanning hardware can typically detect when a copy of an ID is scanned, and copies may be too flimsy for motorized drop-in scanners. If you are scanning copies or images of IDs our DIVE API product will be a much better fit.
What is the difference between ID parsing and ID authentication?
ID parsing simply reads the fields stored in the barcode of the ID or MRZ on the passport. It is not confirming legitimacy of the document. ID authentication parses the document, but also performs hundreds of algorithmic checks to catch 95% of fake IDs.
What hardware do I need to integrate with?
We offer a wide variety of ID scanner options which are compatible with Windows operating systems. Shop Windows-compatible ID scanners.
Does this SDK use optical character recognition (OCR)?
No. Our .Net tools read the data stored inside the 2D barcode. The only time OCR is used is for front / back matching during ID authentication, which is only offered inside our off-the-shelf products, or as a .NET SDK.
Can you take a picture of the scanned ID?
No. These tools only reads the barcodes of IDs and does not capture images.
Can the Java SDK or C++ SDK scan digital IDs?
No. These SDKs can only work with physical identity documents at this time.
