Skip to main content

Microblink Platform release notes

You can now use verification links without self-hosting anything. Create a workflow, click Try verification link, and send the link to your users.

v1.10.0​

Upgraded dependencies for the Scan ID and Scan Payment Card capabilities.

Scan ID now uses BlinkID v7.8, and Scan Payment Card now uses BlinkCard v3000.

SDK release notes​

Continuous watchlist monitoring​

Continuous Watchlist Monitoring is now available.

After a user is accepted through a workflow, CWM automatically re-screens them against compliance watchlists (AML, sanctions, adverse media, and PEP lists) on an ongoing basis. Their status is shown in their user profile.

If a user's compliance score changes, you receive a webhook notification. You can also query and manage monitors via the Agent API.

To enable CWM, turn on the Ongoing user monitoring flag in your workflow configuration.

API update: Basic Auth​

Starting with April 23, 2026, the Agent API supports HTTP Basic Auth as its primary authentication scheme.

New behavior​

This means that any keys generated after this date cannot be used with the previous Bearer scheme. If you use our transaction proxy and you generate new keys, you must update to v2.0.0 of the proxy.

If you don't use our proxy, and you generate new keys, make sure that the mechanism you use to contact the Agent API now uses basic authentication:

Authorization: Basic {base64(client_id:client_secret)}

Client IDs in new keys are prefixed with sa_.

Support for old keys​

The Agent API is backwards compatible.

If you have keys that you have generated before April 23, 2026, they will continue working with the Bearer token scheme.

If you use our transaction proxy with old keys, keep using v1.0.0 of the proxy. The v2.0.0 of the proxy is not backwards compatible. Do not upgrade to it unless you also create new keys.

If you don't use our proxy, and use old keys, your authentication scheme remains unchanged.

Our recommendation: upgrade

If you already have API keys, we recommend that you delete them and reissue them, and that you upgrade your integration with the Agent API to use Basic Auth.

The new keys are better supported and offer more stability.

v1.9.0​

What's new​

We've added two new features: Upload & Verify ID and Upload Non-ID.

These capabilities enable your users to securely upload both identity and non-identity documents as part of your onboarding, compliance, or KYC workflows—whether as a primary method or as a fallback when live capture is not possible. They accept government-issued IDs and employment-related (I-9 form supporting) non-ID documents: I-94, DS-2019, DS-2019, I-20, DS-1350, I-797C, birth certificate.

SDK release notes​

v1.8.0​

What's new​

  • Results from running personal data checks have been improved, including adding a "deceased" check, which is a useful check for fraudulent onboarding attempts.

  • You can now additionally configure the Scan ID step:

    • Scan unsupported back: by default, we no longer scan the second side of documents where we don't support the second side. However, you can still toggle this setting and explicitly require the step to scan the second side of documents with an unsupported back.
    • Scan passport data page only will set the step to scan only pages of a passport where there is a machine-readable zone. If this is not set, then users will also need to scan the second page of certain passports.

    Note that these settings are also exposed on the Scan & Verify ID step, however, in that case, only the web SDK will respect this configuration. Mobile SDKs do not support these fields.

  • On the web SDK, you can now customize the start, and, and progress screens. This is accomplished by using the startScreen(), endResultScreen(), or progressScreen() props. Read more in the Web SDK documentation.

  • You may also see an Additional data extraction field inside the Scan ID and Scan & Verify ID capabilities. While not bound to this release, this is a new field that we introduced recently. It is used to extract any work authorization restrictions for US social security cards. Toggle it on in case you need this information as part of your workflows.

Coming soon​

In the UI, you might see two new capabilities greyed out: Upload & Verify and Upload Non-ID. These are two new capabilities that we are currently working on, which will allow you to upload both ID and non-ID documents, and customize their processing. These capabilities are planned for one of our next releases.

Bug fixes​

  • We fixed a bug where results provided by the Scan & Verify ID capability weren't fully passed through the Platform, which led to confusion around why this step failed
  • Some fixes in the workflow builder reducing misconfigurations.
  • Fixed issues around email invites and verification links.
  • General error and status reporting fixes.

SDK release notes​

v1.7.0​

What's new​

If you don't collect a personal data collection consent from your users and provide it to us via API, we will now display a consent collection screen of our own.

Users can accept or reject giving data collection consent directly in the SDK. If consent is rejected, the session is immediately terminated.

Breaking changes​

SDKs now need to provide a full proxy object when starting a transaction.

Previously, you provided the full API transaction endpoint for your proxy, for example: https://www.myproxy.com/api/v1/transaction.

Now, you need to pass your proxy's base domain + API suffix, without the final URL path. For example: https://www.myproxy.com/api/v1.

The SDK then constructs the rest of the URL based on the action that is performed (transaction creation, cancellation, or simply getting info on its status).

You need to update your proxy to accommodate this change. If you're using our proxy, update it to the latest available version.

SDK release notes​

v1.5.0​

What's new​

  • Added kiosk mode support. This is helpful in applications where a tablet device is mounted on a wall and users are expected to scan their documents using the front camera only.
  • PDF file uploads are now supported when using the manual input capability.

Updates​

Updated BlinkID Verify and BlinkCard dependencies:

  • The "Scan & Verify ID" capability now uses BlinkID Verify 3.14.1.
  • The "Scan Payment Card" capability now uses BlinkCard 2.12.0.

To read more about the new features supported by these upgrades, see the release notes for BlinkID Verify and BlinkCard.

SDK release notes​

v1.4.2​

Breaking changes​

The MicroblinkPlatformServiceSettings configuration has been updated. The URL field has been renamed and now requires the full API transaction endpoint instead of just the base domain.

  • Before: accepted only the base domain, e.g. https://www.myapi.com
  • After: must include the full endpoint, e.g. https://www.myapi.com/api/v1/transaction

See the SDK-specific release notes for the exact field name change on each platform.

SDK release notes​

v1.4.1​

Improvements​

  • Improved extraction of first and middle names for certain ID types.

SDK release notes​

v1.4.0​

Improvements​

  • Face capture now performs additional validation checks:
    • Eyes closed
    • Image too dark
    • Face blurry
    • Mouth open
    • Sunglasses detected
  • Improved card scanning performance and reliability.
  • Enhanced document extraction with additional extracted fields.

SDK release notes​

v1.3.0​

New features​

  • Added support for the payment card scan capability.
  • Added support for multiple steps of the same type.

SDK release notes​

v1.2.0​

New features​

  • Added support for manual user input capability.

SDK release notes​

v1.1.0​

New features​

  • Added support for BlinkID.

SDK release notes​

v1.0.0​

Initial release​

  • Initial release of the Microblink Platform SDK.

SDK release notes​