@microblink/blinkid-verify@4000.0.0

What's new

• New Injection Attack Check: Added sdkPayloadIntegrityCheck for multipart SDK payloads, validating signed images and request fields and returning Reject when tampering is detected during API processing.

• Capture resolver: When a document is successfully captured, a resolver is provided. That resolver can submit the verification request, and it can also return a v3-compliant payload for manual submission.
  Previously, a result was provided on capture completion as images to be sent to the API.

• Facilitated API submission: The captured frame can be submitted immediately by the SDK when scanning finishes, or submitted later through the resolver. Requests are sent to {base_url}/api/v3/verify. The page origin is used when no base URL is set. The receiving server forwards the body unchanged and adds the API key in the Authorization header.
  Note: A failed automatic submit is not retried. The same resolver can be used to resubmit while the session is still active.

• Improved capture feedback: Each processed frame reports the document side and whether the background is interfering with verification. The warning shown by the feedback UI is “Move the document to a plain background”.

• Runtime enhancement: Browsers that support relaxed SIMD load the required WebAssembly build faster and automatically while being downloaded. The help tooltip is shown after 10 seconds.

• Most up to date document coverage: The full list of newly supported documents can be found here, below the release notes for October 2026: https://docs.microblink.com/blinkid/release-notes

• The capture pipeline is replaced with the v3 session, consent, and Verify API flow. Setup, capture, and submit are covered by a single component.
  Note, more information on the v3 API can be found here: https://docs.microblink.com/verify/migrate-v3

1. Verification setup

Session settings accept a configuration object in the same shape as the v3 API. The configuration covers the verification policy, sensitivity thresholds, image-quality handling, extraction, and redaction.

2. Consent and Consent UI

From the roll out of the v3 API, explicit end-user consent is required for verifications prior to capture. Three options are provided, in all cases, when that dialog is declined, the SDK is terminated.

a. The built-in consent dialog can be shown.

b. The built-in consent dialog can be customised.

c. When consent has already been gathered before Verify is started, a consent object can be supplied before capture and the consent dialog is skipped.

More information on Consent Management can be found here: https://docs.microblink.com/verify/consent

Bugfixes & Improvements

• Updated additional number format checks for Western Australia driver licenses.
• Resolved false rejection issue with Philippine eIDs, now both digital and physical versions are accepted.
• Added new date formats for Irish passports and passport cards.
• Removed documentNumber logic check for AUSTRIA//DL/2006 which was causing false rejections.
• Fixed an issue where extraction processingStatus was returning incorrect values for certain multi-side documents.
• Fixed an issue where barcode ExtractionResult was returned for certain documents without barcode.
• Fixed a validation issue for dateOfIssue on Ireland rigid passports, and dateOfBirth and dateOfExpiry on Ireland residence permits.
• Fixed an issue where barcode read checks for Tennessee 2018 and North Carolina 2008 Under 21 driver licenses was previously returning NotPerformed.
• Fixed an issue where NONE would sometimes appear as part of the firstName extraction result.
• Fixed issues with document number formats for Wyoming DLs and Indonesia passports.
• Fixed issue with date formats for Brazil IDs.
• Fixed issue with barcode authenticity checks for Ontario DLs.