Skip to main content

Introduction

What is BlinkID Verify?

BlinkID Verify is an end-to-end document verification solution that can be used to verify the authenticity and liveness of documents. In addition to verifying the authenticity and liveness of documents, it also extracts data from the document and can be seen as a superset of BlinkID.

As an end-to-end verification (and extraction) solution, BlinkID Verify comes in two modules, the API and the client-side SDK, and we recommend using both for optimal performance.

API

The BlinkID Verify API is where all the document verification magic happens. At a high level, it's a RESTful API that takes in images, or an image of a document, and returns a JSON response with the verification results plus extracted document data.

The API can be used by itself, but for best results, we recommend using it in conjunction with the client-side SDK. That said, if you're just looking to get started quickly, the API is a great way to get started. It's available in many regions [link to regions page] around the world, and we handle all the complexity of running the service for you.

Client-side SDK (BlinkID Verify SDK)

The client-side Verify SDK is our most robust solution for capturing document images, optimized for Verify. It ensures any images you send to the API are high quality, verifiable, and provides a smooth user experience.

The SDK is available for both iOS, Android, with Web (desktop and mobile) coming soon.

Key design principles

Flexibility

We've designed Verify to be adaptable to a wide range of use cases, from basic in person verification, to high assurance remote use cases.

This is accomplished through a layered system of configuration options which range from very abstract, but powerful parameters, to granular detailed options for fine tuning.

Because of this, Verify can be configured to have minimal impact on conversions, or to be extremely sensitive to potential fraud, and anything in between. Most customers will fit somewhere around our default settings, but a lot of legitimate use cases will benefit from customized configurations.

High conversions, low friction

One of our guiding principles is to reduce end user friction as much as possible. This is accomplished in lots of different ways, but let's go over some of the key ones.

Speed

Verify is one of the fastest document verification solutions on the market. The typical transaction takes around a second or two to process (including extraction), even though we run hundreds of checks and dozens of AI models.

Low FRR

FRR (or False Rejection Rate) is the silent killer of conversions. Every real user you reject is directly lost revenue and reputational damage. That's why we've optimized Verify to have as few false rejections as possible while still capturing fraud en masse.

This is possible through a combination of highly granular settings, smart defaults, state of the art AI models, comprehensive datasets, in-house document expertise and a lot of engineering effort.

Optimal capture

As mentioned, the Verify SDK is designed to provide the smoothest possible experience for your end users. It's unobtrusive, quick, comes with a tiny binary size hit, and provides all the features you need to reach and maintain high first time success rates.

Next steps