July 2025

User Verification

Risk labels logic

We have updated the logic behind the Similar applicants with different data (sameFaceWithDifferentData) risk label.

Now, when triggered by FaceMatch, the risk label checks for the presence of text data for both applicants. If both applicants have the text data and there is a discrepancy—the label will be applied.

Document Subtype settings

We have added the ability to configure document subtypes both in Global Settings and at the settings of a specific level.

For each country and document type, you can now define how subtypes should be handled, using the following options:

• Accept all subtypes (selected by default) — all document subtypes are accepted by default. No list required.
• Accept only selected subtypes — only specified subtypes will be accepted. If the subtype is undefined or not on the list, the document will be rejected. The list should not be empty.
• Reject only selected subtypes — only listed subtypes will be rejected. All others, including undefined ones, will be accepted. The list should not be empty.

Sumsub Lite levels

As a Sumsub Lite client, all new levels you create will automatically use the Lite check mode.

NFC documentation

Documentation for NFC verification is now available in our Help Center

• NFC-based ID verification
• NFC supported documents

Crypto Monitoring

New Crypto Monitoring provider

We have integrated a new blockchain analytics provider—TRM Labs. As a BYOK integration, TRM Labs requires API keys to get started with the service.

Case Management

Workflow Builder cases creation

We have delivered the all-in-one update for the Case Management—you can now create cases via Workflow Builder, linked to any KYC or KYB level.

With Workflow Builder, you can also set all conditions and segmentations in order to delegate applicants for investigation automatically.

The feature is available to clients on the Basic and Growth plans and requires Case Management 2.0.

SDK

MobileSDK update

A new MobileSDK version has been released — 1.36.1.

Changelog:

• iOS
• Android

Non-Doc Verification

BankID release for Norway

Sumsub has implemented a new Non-Doc Verification product for Norway—BankID.

Product benefits:

• >97% adult population coverage via the participating banking institutions.
• Seamless UX via a simple login that is familiar to most Norwegian citizens.
• High Level of Assurance that delivers both eIDAS and AML-compliant verification.

Business Verification

Associated party roles merge with overlapping levels

We have simplified the verification process for applicants who hold multiple roles.

Previously, if your applicant was both a Director and a UBO, they had to complete two separate verification flows.

Now, Business Verification has become smarter—it can identify a superior role and request only one verification, while linking the secondary roles.

Alternative company names in SDK

We have added support for alternative company names in the Company Data step of the SDK. This allows us to collect trade names or brand names and include them in AML screening.

If corporate databases or documents provide additional names, they will be automatically appended and included in the screening process as well.

Dashboard

AML Screening layout

We have renamed the All AML Cases block to AML Screening, and moved it to a new section in the main Dashboard menu.

New calendar design

We have improved the design of the calendar. Redesigned version includes the following:

• In the version where users only select a date without time, extra buttons, inputs, and other elements have been removed.
• To keep date selection easy, the month and year are now clickable.
• In the version where both date and time are selected, inputs remain for convenient keyboard entry.

Questionnaire

Risk scoring by countries

Now, you have an option to specify risk scoring for fields of the Country and Multi-country types in the questionnaires.

This feature is enabled by a separate toggle in Questionnaire builder in Country type of the question, which allows assigning risk scores to the selected countries.

SDK

New pre-filled phone number setting in WebSDK

A new option is now available in the phone verification step settings to prevent applicants from changing a phone number that has been pre-populated. When this option is enabled:

• Pre-filled number is locked — applicants cannot edit the phone field if it was provided by the client.
• Manual entry remains possible if no number was pre-filled.

Travel Rule

Data Comparison Settings — Sumsub Protocol

We have introduced a better way for VASPs to specify which data points they want to be compared during Travel Rule data exchange transactions. These settings are relevant strictly to Sumsub Protocol incoming or mirrored transactions and include the following:

• Separate fields for individuals and companies with different comparisons for each.
• Multiple settings for fuzziness logic with more details about how specific fields, such as DOB, are compared.

Case Management

Case Management 2.0 for KYB applicants

New case management now shows preview of a KYB page with:

• Company structure
• Extracted company data

Business Verification

New Global source for corporate checks

We have improved the automated corporate registry check (basic) with better coverage and datapoints. This update includes the following:

• Covers 200+ countries.
• Supports search by name and pre-fill.
• Includes some economic insights like past year revenue and number of employees.

SDK

New language in SDK

Tajik has been added to Web and Mobile SDK.

Database Validation

Verification solution for Indonesia

We have released the Indonesia Dukcapil Verification, providing an additional method for verifying NIK numbers directly through the government database (DUKCAPIL).

You can now verify applicant’s NIK numbers by collecting their KTP cards.

The solution’s benefits:

• Direct verification through the government database (DUKCAPIL) in Indonesia.
• Full compliance with Indonesian regulatory requirements by combining document collection, identity verification, and selfie validation into a single streamlined flow.
• Enhanced accuracy in matching applicant information between the document and the government database data.

Dashboard

Updated Countries and Territories settings

The Countries and Territories settings have been redesigned to make configurations more intuitive.

How it works now:

• Accept applicants from all countries option—a dedicated radio choice lets you explicitly allow every country.
• Refined restriction modes—the existing Accept applicants from selected countries and Reject applicants from selected countries options remain unchanged, allowing the same fine-tuned control when filtering by location.

Transaction Monitoring

MCC (Merchant Category Code) support

You can now use Merchant Category Codes as part of rules logic and risk scoring via the data.info.mcc = '1234' condition.

Why this matters:

• More precise risk detection—transactions can have a flag or score based on the merchant type (e.g., casinos vs. supermarkets).
• Improved compliance—industry-specific monitoring requirements are supported (e.g., banking, fintech, regulated sectors).
• Enhanced flexibility in rule-building—more granular and dynamic transaction rules can be enabled by merchant type.

Case Management

New countries for FIU STR reports

We have expanded the list of countries available for regulatory reports. You can download these reports directly from the Case page for any triggered transaction.

Expanded country coverage:

• Tanzania
• South Africa
• Indonesia
• Iraq
• UAE
• Croatia
• Trinidad and Tobago
• Kenya
• Uganda
• Zimbabwe
• Monaco
• Mongolia
• Bhutan

AML Screening

AML API launch

New AML-related endpoints have been delivered:

• Use the Get AML case data method to gather AML case information via API. The endpoint currently has a limit of 10 requests per minute.
• Modify the review status of specific AML hits with the Update AML Hit Review method.

User Verification

Email Verification messages update

Starting today, emails will be sent from [email protected] and will include updated text clarifying that no response is required.

SDK

WebSDK read-only preview

When you click on the WebSDK preview button on the applicant page, a fully non-interactive view is now displayed. This feature allows you to:

• Safely inspect which steps applicants need to fix without advancing their session.
• Avoid false IP-distance rejections by preventing any action in preview.
• Ensure true device fingerprinting—only the first SDK initialization by the applicant counts, if the client previously created links using this button.

WebSDK 2.0 migration

To simplify the migration to WebSDK 2.0 and reduce unnecessary alerts, we are introducing automatic application of the read-only mode to selected levels.

A level will be marked as readOnly if all the following conditions are met:

• It was created more than 6 months ago.
• It is not used in any workflow.
• There have been no applicants on the level for more than 6 months.

You can:

• View and open the level.
• Migrate the level to WebSDK 2.0.

This feature does not allow you to:

• Initialize the level (via API, Dashboard, or generated links).
• Edit, duplicate, or export the level.
• Move applicants to a read-only level.

Device Intelligence

Removal of the Remote Access Detection signal

Browsers are making changes that limit the ability to detect remote access without interfering with the user experience. Considering this, we have removed the Remote Access Detection risk signal from the Device Intelligence.

Dashboard

Questionnaire block redesign

We have improved the Questionnaire block on the Applicant page with the following features:

• To make it easier to navigate the Applicant page, you can collapse the Questionnaire block, and we will remember your choice. Next time, it will be folded for you by default.
• The layout of the buttons has become more convenient.
• Questions are numbered and visually separated.
• Answers show up right next to the questions.
• Edit mode has also been updated.
• If a question was answered before but then removed from the Questionnaire, you will still see it, but with a special notice.

Applicant page updates

We have redesigned the Applicant page with clearer buttons and the ability to move the window around the screen.

Moreover, now we will show a modal window with the selected reject labels and the Approve applicant button. Users can disable this window for 24 hours.

New structure of the Applicants menu

We have removed the drop-down menu from the Applicants section. All tabs are now available at the top of the Applicants page.

Notes updates

Notes have been improved with the following features:

• We now remember if you expanded the notes list — all future applicants will be loaded with the full list expanded until you collapse it again, which we will also remember.
• The note input field now adjusts to content size.
• For case or transaction notes, we now save your input text even if you accidentally close the drawer — no more lost drafts.

Reorganization of the Review panel

We have moved Applicant re-checks to the Applicants section. Re-checks will be available to clients who have been using it recently.

Review panel is no longer available.

Business Verification

Company-specific email templates for KYB notifications

We have created company-specific variants of the email templates. Also, we have added a notification of the company for which beneficiary verification is requested.

You may find new templates in the Email translations with the _COMPANY suffixes.

Captions under role names in the Associated parties step

We have added captions that describe the roles of parties expected to be enlisted under each category. By default, we specify percentage of ownership for UBOs and shareholders.

AML Screening

New AML screening settings

We have delivered the setting for Case Management 2.0 that allows you to see and resolve AML cases and hits for both applicant and transaction screening from the same case.

They are separated for more clear understanding which entity was screened and hit, but still united under the hood of the same case for easy access of the full AML background of an applicant.

User Verification

Payment Method Check Advanced: enhanced settings for Action Level and SDK 2.0

From now on, you can set up mandatory payment method types that you want your applicants to verify.

If you want the applicant to choose between a bank card, a bank account and an e-wallet — select them and applicants will see the selection in the SDK.

Payment Method Check Advanced: auto-checks for checksums

Now we perform checks for checksums automatically. If you want to verify a wallet or a bank account of an applicant, the flow contains the following:

You send us the checksum.
Applicant uploads the proof of this payment as a statement in the SDK.
We perform an autocheck that this payment was indeed made.

To enable this check, you need to select E-Wallet or Bank Account in the Action Level settings and send us a checksum that we need to find in a statement. Alternatively, you can pass eWallet and bankStatement types via API call.