BlinkID SDKs in Verify
Verify builds on top of BlinkID, in the sense that the server-side extraction of fields from documents is performed using BlinkID.
This article maps the version of Verify with the version of the used underlying extraction engine, as well as which versions of mobile SDKs are compatible with any given version of Verify.
Using BlinkID as a capture source
If you already have a BlinkID integration and can't migrate to the Verify SDK, you can use BlinkID to capture images and pass them directly to the Verify API. We still recommend migrating to the Verify SDK when possible—it is purpose-built for Verify, guarantees image quality, and will produce better outcomes for your users.
If you are using the cloud API, always use the latest version of BlinkID to ensure compatibility. For self-hosted deployments, use the matching version from the table below.
When passing images from BlinkID to Verify, do not use lossy compression. Encode images as lossless PNG. See Extract document images for how to retrieve and encode images from a scanning session.
Version compatibility
The following table lists which self-hosted Extraction API is compatible with each Verify release, along with the compatible mobile BlinkID SDK version.
| Verify API | Extraction API | BlinkID SDK |
|---|---|---|
| 3.22.x | 5.1.0 | 7.8.x |
| 3.21.x | 5.1.0 | 7.8.x |
| 3.20.x | 5.0.0 | 7.7.x |
| 3.19.x | 4.7.0 | 7.6.x |
| 3.18.x | 4.7.0 | 7.6.x |
| 3.17.x | 4.6.0 | 7.6.x |
| 3.16.x | 4.4.0 | 7.4.x |
| 3.15.x | 4.4.0 | 7.4.x |
| 3.14.x | 4.4.0 | 7.4.x |
| 3.13.x | 4.3.0 | 7.3.x |
| 3.12.x | 4.1.0 | 7.1.x |
| 3.11.x | 3.15.0 | 6.13.x |
| 3.10.x | 3.15.0 | 6.13.x |
| 3.9.x | 3.15.0 | 6.13.x |
| 3.8.x | 3.15.0 | 6.13.x |
| 3.7.x | 3.14.0 | 6.12.x |
| 3.6.x | 3.13.0-lite | 6.11.x |
| 3.5.x | 3.12.0-lite | 6.10.x |
| 3.4.x | 3.11.0-lite | 6.9.x |
| 3.3.x | 3.11.0-lite | 6.9.x |
| 3.2.x | 3.10.0-lite | 6.8.x |
| 3.1.x | 3.10.0-lite | 6.8.x |
| 3.0.x | 3.9.x-lite | 6.7.x |
| 2.7.x | 3.8.0-lite | 6.6.x |
| 2.6.x | 3.8.0-lite | 6.6.x |