An experimental company analytics endpoint is available.\nYou can query it by date range, organization, and service key, such as blinkid.\nThe response is daily counts grouped by transaction status, service key, and organization.
Request access here.
\nInviting a user no longer fails when that person has no access to one of their existing memberships.
", "url": "https://docs.microblink.com/platform/release-notes/analytics-endpoint", "title": "Analytics endpoint", "summary": "What's new", "date_modified": "2026-10-28T12:59:00.000Z", "tags": [] }, { "id": "https://docs.microblink.com/platform/release-notes/accessibility", "content_html": "Web moved to v1.10.5, Android to v1.10.1, and iOS to v1.10.3.
\nThe React build (@microblink/platform-sdk/react) no longer shows a blank screen on the face-capture step in a React 19 app.\nUpload ID also checks the file contents before upload, so a .jpg file that is actually another format is rejected before the request fails with an invalid content type.
You can set an optional correlationId when you start a transaction.\nIt is sent with the API call.\nSee Correlation ID and partner analytics.
Accessibility is improved on both SDKs.\nOn Android, headings are exposed as headings, decorative images are hidden from screen readers, and buttons have distinct names.\nStatus changes are announced, including capture prompts, the \"center your face\" warning, and form validation.\nA rejected selfie is described in text, not only by a red frame.\nPlaceholder text, validation messages, and focus outlines meet clearer contrast and visibility rules, and the \"Add more details\" form marks required fields.\nThe email field supports autocomplete.
\nThe Swift package moved from the MicroblinkPlatform GitHub organization to microblink.
https://github.com/MicroblinkPlatform/microblink-platform-ioshttps://github.com/microblink/microblink-platform-iosScan & Verify ID and Upload & Verify ID show a clearer screen when Document Verification recommends Undeterminable or Retry.\nThe screen explains the status and, when the outcome is Retry, how to try again.
The default rule for those two steps now rejects an Undeterminable outcome instead of sending it to manual review.\nThat matches Undeterminable outcomes.
Date of birth on a user profile is shown as stored, without an extra formatting pass.
", "url": "https://docs.microblink.com/platform/release-notes/clearer-capture-results", "title": "Clearer capture results", "summary": "Improvements", "date_modified": "2026-10-20T12:59:00.000Z", "tags": [] }, { "id": "https://docs.microblink.com/platform/release-notes/undeterminable-outcomes", "content_html": "When Document Verification's recommended outcome is Undeterminable on Upload ID or Scan ID, the step now rejects the attempt.\nA migration applies this rule to existing workflow versions, not only to workflows you create after this release.
An admin can invite someone who already belongs to another partner or company.\nPreviously the invite failed when the admin could not see that other organization.\nThe permission check now looks at the company the person is being invited into.
", "url": "https://docs.microblink.com/platform/release-notes/undeterminable-outcomes", "title": "Undeterminable outcomes", "summary": "Improvements", "date_modified": "2026-10-16T12:59:00.000Z", "tags": [] }, { "id": "https://docs.microblink.com/platform/release-notes/recommended-outcome-retries", "content_html": "Upload & Verify ID and Scan ID now follow Document Verification's recommended outcome.
\nWhen that outcome is Retry, the step asks the person to capture the document again.\nIf Document Verification does not include an error code, the step uses NotScanned, which the SDKs already treat as a retry.
Image uploads on the form and start step no longer fail when the request includes a content length.\nVerification can continue past that step.
", "url": "https://docs.microblink.com/platform/release-notes/start-step-image-uploads", "title": "Start-step image uploads", "summary": "Bug fixes", "date_modified": "2026-10-10T12:59:00.000Z", "tags": [] }, { "id": "https://docs.microblink.com/platform/release-notes/cropped-images", "content_html": "Upload & Verify ID has a setting that accepts cropped images.\nThis is the console control for the hybrid capture support added in Hybrid capture for uploads.
\nOpening a user profile from the mobile layout works again.
", "url": "https://docs.microblink.com/platform/release-notes/cropped-images", "title": "Cropped images", "summary": "What's new", "date_modified": "2026-10-06T12:59:00.000Z", "tags": [] }, { "id": "https://docs.microblink.com/platform/release-notes/hybrid-capture-for-uploads", "content_html": "Capture conditions are now available on the Upload & Verify ID step.\nA workflow can use hybrid capture and accept cropped images at that step.\nWorkflows that do not use hybrid capture behave as they do today.
\nProvisioning an organization without a data retention period no longer sets retention to 365 days.\nA new organization keeps the default retention when you do not specify one.
", "url": "https://docs.microblink.com/platform/release-notes/hybrid-capture-for-uploads", "title": "Hybrid capture for uploads", "summary": "What's new", "date_modified": "2026-10-01T12:59:00.000Z", "tags": [] }, { "id": "https://docs.microblink.com/platform/release-notes/correlation-id-and-partner-analytics", "content_html": "You can pass an optional correlationId when you start a transaction.\nThe same value is returned by GET /transactions/{id} and included in analytics export, so you can match a Platform transaction to a record in your own systems.
Partner-scoped analytics now return daily completed transaction counts and usage per capability.\nWhen an account goes over its transaction limit, the subscription is marked as overage.
", "url": "https://docs.microblink.com/platform/release-notes/correlation-id-and-partner-analytics", "title": "Correlation ID and partner analytics", "summary": "What's new", "date_modified": "2026-09-22T12:59:00.000Z", "tags": [] }, { "id": "https://docs.microblink.com/platform/release-notes/v1.10.4", "content_html": "Upgraded the camera-manager package from v7.3.2 to v7.3.5.\nCapture uses that package, so the camera session is more reliable.
\nVoiceOver on macOS no longer reads controls that are hidden.\nA screen-reader user hears only what is on screen.
\nThe device-to-device capture app now times out a stalled scan after 2 minutes instead of 3.\nThe person can retry, or continue on another device, without waiting as long.
", "url": "https://docs.microblink.com/platform/release-notes/device-to-device-scan-timeout", "title": "Device-to-device scan timeout", "summary": "Improvements", "date_modified": "2026-09-10T12:59:00.000Z", "tags": [] }, { "id": "https://docs.microblink.com/platform/release-notes/social-security-cards-and-pep-aml-review", "content_html": "The Workflow Builder can turn on data extraction for Social Security cards on the Upload & Verify ID step.\nThat matches the setting already available on Scan & Verify ID.
\nThe transaction overview now opens a dialog with the full PEP and AML name-matching results, so you can review them while discounting a hit.
\nUpload & Verify ID now uses the same large language model extraction for Social Security cards as Scan & Verify ID.\nThis applies to Social Security cards in work-eligibility workflows.
\nThe Agent API for continuous watchlist monitoring accepts new filters on single checks and on monitors.\nThe monitor-results endpoint also takes a flag that returns the results without the associated files.
", "url": "https://docs.microblink.com/platform/release-notes/social-security-cards-and-watchlist-filters", "title": "Social Security cards and watchlist filters", "summary": "What's new", "date_modified": "2026-09-03T12:59:00.000Z", "tags": [] }, { "id": "https://docs.microblink.com/platform/release-notes/v1.10.2-ios", "content_html": "Localization keys for Scan & Verify ID now load and display.\nPreviously some of those strings were missing, so the step stayed in the default language.
\nMicroblinkPlatformTheme can now load custom strings from the host app.
localizationBundle: a bundle that contains translations which override the SDK strings.localizationTableName: an optional strings table name. Leave it unset to use the default Localizable table.Web v1.10.2 shipped earlier, on June 17, 2026.\nSee v1.10.2.
\nTransaction filters and the transaction grid now include an In progress status, so you can see verifications that are still running.
\nA missing value in a background check no longer makes the Trust Score fail.\nThe score is still returned when some of the underlying information is absent.
\nAccount setup also handles short identity-service interruptions more reliably, so provisioning a new account from the console is less likely to stop halfway through.
", "url": "https://docs.microblink.com/platform/release-notes/trust-score-incomplete-checks", "title": "Trust Score with incomplete checks", "summary": "Bug fixes", "date_modified": "2026-08-18T12:59:00.000Z", "tags": [] }, { "id": "https://docs.microblink.com/platform/release-notes/v1.10.3", "content_html": "Scan & Verify ID and Scan ID now upload payload images as JPEG instead of PNG.\nThe files are smaller, so uploads finish sooner on a slow connection.
\nFixed the BlinkCard integration.
\nAndroid v1.10.1 shipped later, on October 23, 2026.\nSee Accessibility.
\nFixed translation keys added with the BlinkID upgrade that were not mapped, so the SDK showed the English text regardless of the selected language.
\nThe new keys are available in German, Croatian, Spanish, and English:
\ncameraFeedbackOccluded: \"Keep the document fully visible\"cameraFeedbackTooDark: \"Move to brighter spot\"cameraFeedbackTooBright: \"Move to spot with less lighting\"helpDocInfoTitleDesktop: \"Get ready to scan\"helpDocInfoDescriptionDesktop: onboarding instructions for desktopscanUnsuccessfulTitle: \"Scan unsuccessful\"If you ship custom translations, add these keys.
\nUpgraded dependencies for the Scan ID and Scan Payment Card capabilities.
\nOn Web, Scan ID now uses BlinkID v7.8, and Scan Payment Card now uses BlinkCard v3000.
\nAndroid and iOS v1.10.0 shipped on July 3, 2026.\nScan & Verify ID now uses BlinkID Verify v3.21.0, and Scan Payment Card now uses BlinkCard v3000.0.1.
\nContinuous Watchlist Monitoring is now available.
\nAfter 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.\nTheir status is shown in their user profile.
\nIf a user's compliance score changes, you receive a webhook notification.\nYou can also query and manage monitors via the Agent API.
\nTo enable CWM, turn on the Ongoing user monitoring flag in your workflow configuration.
\nStarting with April 23, 2026, the Agent API supports HTTP Basic Auth as its primary authentication scheme.
\nThis means that any keys generated after this date cannot be used with the previous Bearer scheme.\nIf you use our transaction proxy and you generate new keys, you must update to v2.0.0 of the proxy.
\nIf 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:
\nAuthorization: Basic {base64(client_id:client_secret)}
Client IDs in new keys are prefixed with sa_.
The Agent API is backwards compatible.
\nIf you have keys that you have generated before April 23, 2026, they will continue working with the Bearer token scheme.
\nIf you use our transaction proxy with old keys, keep using v1.0.0 of the proxy.\nThe v2.0.0 of the proxy is not backwards compatible.\nDo not upgrade to it unless you also create new keys.
\nIf you don't use our proxy, and use old keys, your authentication scheme remains unchanged.
\nIf 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.
We've added two new features: Upload & Verify ID and Upload Non-ID.
\nThese 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.\nThey 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.
\nResults from running personal data checks have been improved, including adding a \"deceased\" check, which is a useful check for fraudulent onboarding attempts.
\nYou can now additionally configure the Scan ID step:
\nNote that these settings are also exposed on the Scan & Verify ID step, however, in that case, only the web SDK will respect this configuration.\nMobile SDKs do not support these fields.
\nOn the web SDK, you can now customize the start, and, and progress screens.\nThis is accomplished by using the startScreen(), endResultScreen(), or progressScreen() props.\nRead more in the Web SDK documentation.
You may also see an Additional data extraction field inside the Scan ID and Scan & Verify ID capabilities.\nWhile not bound to this release, this is a new field that we introduced recently.\nIt is used to extract any work authorization restrictions for US social security cards.\nToggle it on in case you need this information as part of your workflows.
\nIn the UI, you might see two new capabilities greyed out: Upload & Verify and Upload Non-ID.\nThese 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.\nThese capabilities are planned for one of our next releases.
\nFixed form values sent when the SDK is initialized.
\nIf 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.
\nUsers can accept or reject giving data collection consent directly in the SDK.\nIf consent is rejected, the session is immediately terminated.
\nSDKs now need to provide a full proxy object when starting a transaction.
\nPreviously, 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.\nFor 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).
\nYou need to update your proxy to accommodate this change.\nIf you're using our proxy, update it to the latest available version.
\nThe Scan ID capability now uses BlinkID v7.6.0.\nThat release adds support for scanning the barcode page of US passports.
\nLater v1.6 patches on Web:
\nUpdated BlinkID Verify and BlinkCard dependencies:
\nTo read more about the new features supported by these upgrades, see the release notes for BlinkID Verify and BlinkCard.
\nFixed an issue on some older Samsung devices where the SDK did not update after returning from document scanning.
\nThe 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.
https://www.myapi.comhttps://www.myapi.com/api/v1/transactionSee the SDK-specific release notes for the exact field name change on each platform.
\n