Common Issues & Troubleshooting
Document verification is a very complex process, and BlinkID Verify offers a lot of levers to pull to get the best results for your specific use case. It's not rare that the default options don't yield the best results for your documents, and cause responses that don't make too much sense at first glance. After all, the default options are designed to satisfy the average customer and the average use case as closely as possible.
It's critical, and easy, to tweak Verify to give you results that are more aligned with your expectations, but the first step is to understand what's happening, why, and what you can do to get what you need.
Let's start by looking at some of the more common issues that you might encounter when using the BlinkID Verify API.
Authorization issues
If you're using our cloud, you need credentials tied to your license and to the region it was issued for. If you have authorization issues, you might need to check:
- whether you're using the correct region/URL
- your license key (for your region)
- your license type
- your license status
- your license expiration date
- your license usage
Fully cropped images
You might have sample images that you want to use for testing, but if they're just images of documents without any background, we consider them unverifiable. We can extract data from these images, but one of the core design principles of Verify is to expect the actual document owner to be able to present their real, live document in a real, live situation. A fully cropped image of a document is not a real, live situation, and Verify will completely refuse to process outcome for such images by default.
This issue is completely mitigated by the BlinkID Verify client-side SDK, which will ensure images are captured in live conditions, and will not allow fully cropped images to be submitted.
However, if you aren't able to control your end users' capture conditions (because you don't use any kind of client-side SDK), more details are available in processing cropped images.
Image quality issues
In order to be verified, or verifiable, document images need to satisfy some basic quality requirements. Those are outlined in more detail here.
Funnily enough, you're probably going to be doing your testing in an environment that makes satisfying these requirements difficult. Harsh overhead lighting, common in offices, can cause glare and reflections that make the image unverifiable.
In production, it might not always be possible to have perfect conditions, and depending on your use case, you might want to relax some of the requirements.
If you run into issues with image quality:
- While testing, you might want to be more mindful of your capture conditions, especially if they're not typical for your end users.
- In production, you might want to change the image quality match levels.
Unexpected results
If everything seems fine from a technical perspective, but you don't feel you're getting the results you expect, you might want to play around with some options.
Don't hesitate to reach out to our support team if you need help.