GoldenCard and VehicleOwnershipCertificate document types.VehicleNumber, PassportNumber, and TrafficParticipantNumber field types in v3.injectionAttackCheck group and the sdkPayloadIntegrityCheck check for multipart SDK payloads in v3.\nThe check validates signed images and request fields, and returns Reject when it detects tampering./verify-generic-image.\nIt runs generative AI detection on any image, including images of non-ID documents.\nFor details on functionality and licensing, contact sales.This release aligns the bundled extraction engine with the September 2026 BlinkID document update.
\ndocumentClassInfo.country, documentClassInfo.region, and documentClassInfo.type fields in v3 are now documented in the OpenAPI spec as open enums.\nThe schema lists the known PascalCase values, but new values can be added at any time, so handle unrecognized strings.Croatia, Id, and None, instead of the previous CROATIA, ID, and NONE.PhotoCopy and ScreenPresence checks are overridden for the InPerson verification context.processingStatus returned incorrect values for certain multi-side documents.ExtractionResult was returned for certain documents without a barcode.dateOfIssue on Irish polycarbonate passports, and for dateOfBirth and dateOfExpiry on Irish residence permits.This release bundles the Verify 4000.0.0 API and the BlinkID 8001.0.0 extraction engine.
\nIf you're moving from the standalone self-hosted extraction API, see Migrate from self-hosted extraction API.
This release introduces the v3 endpoint, /api/v3/verify.\nBoth the request and the response have changed significantly, and numerous fields have been renamed.\nThe most important changes are:
verdict in the response.failedChecks array that lists the checks the document failed.passesAtOrBelowSensitivity, the highest sensitivity at which they would still pass.imageAssessment.imageQualityCheck result.\nBlinkID and Verify now use the same module.pipeline object with a separate status for the extraction and verification stages.portraitForgerySensitivity is re-tuned to Level5.For the rest of the extraction engine changes, see the BlinkID 8001.0.0 release notes.
\nThe deployment ships as a new image, on our own container registry rather than Dockerhub:
\ndocker pull us-docker.pkg.dev/document-verification-public/on-prem/core:4000.0.0
Your existing license continues to work with the new image.
\nImage tags follow the epoch versioning scheme, {EPOCH * 1000 + MAJOR}.MINOR.PATCH.\nSince the previous Verify image tag was 3.22.3, the new image tag 4000.0.0 rather than 4.0.0.
/api/v3/extract and /api/v3/extract-barcode alongside /api/v3/verify.\nThese are not available in the Verify cloud deployment.consent object is required.\nConsent is a cloud-only requirement.runtime fields: workerIndex, workerCount, licenseExpiry, licenseId, and executionId.For the API changes between v2 and v3, see Migrate to Verify v3.\nThe notes below are specific to on-prem deployments.
\nThe image now bundles the standalone self-hosted extraction API, and has changed its name.\nSee Deployment for the new image.
\nThe new GitHub repo with the Helm charts and other deployment-related information is here.
\ngit clone https://github.com/microblink/on-prem-ops.git
Your existing licenses and license environment variables are unchanged.
\nIf you're still on a release earlier than 3.19.0, you're moving from the multi-service stack at the same time.\nRemove the old conf/doc-ver-api, conf/doc-ver-runner, and conf/bundle-doc-ver directories as part of that move.\nSee On-prem deployment for how the current image is deployed.
The container reports its own sizing in the runtime object of every response (workerCount, inflightLimit, cpus, ram, and others), which is useful when you are capacity planning against v2 numbers.
The new 503, 413, and 429 behavior described in Migrate to Verify v3 applies to on-prem deployments too.
V2 was verification-only.\nV3 adds an extraction-only endpoint, POST /api/v3/extract, which runs the extraction half of the pipeline and skips verification.
It's the right endpoint if you only need the data off the document and don't need a verdict.\nThe extraction results are identical in shape to the extraction object of a verification response, so you can move between the two endpoints without changing your parsing.
The extraction endpoint accepts only the extraction and imageAssessment sections of the configuration; verification settings are rejected.\nThere is also a barcode-only endpoint, POST /api/v3/extract-barcode.
If you are coming to this endpoint from the standalone self-hosted extraction API rather than from Verify v2, see Migrate from self-hosted extraction API, which covers that migration in full.
\nNotPerformed.NONE sometimes appeared in the firstName extraction result.