June 2025

User Verification

Payment Method Check Advanced update

Applicants no longer need to cover their bank card data with their fingers when uploading document images.

ID check after document upload

The ID check that triggers immediately after document upload is now enabled for both the MobileSDK and the WebSDK 2.0.

This update reduces the waiting time and speeds up the verification process.

SDK

WebSDK 1.0 disabling

As of June 1, 2025, WebSDK 1.0 is no longer supported by Sumsub. All new features, future development, bug fixes, and enhancements will be released only on WebSDK 2.0.

We strongly recommend that you migrate to WebSDK 2.0, which receives continuous technical support, regular updates, and new feature releases. You can find detailed migration instructions in our WebSDK documentation.

Support for custom final rejection comments in SDK

New functionality for configuring final rejection comments has been delivered.

Key points of the update:

• A new Reject review comments tab has been added to the SDK Translations interface, where you can modify final rejection comments for Applicants, Actions, and Companies.
• By default, standard rejection comments will be shown on the new tab. When you edit and save custom rejection text, the new strings will appear above the default ones.
• If you customize the rejection comments in SDK, those will be prioritized over both standard and custom comments set in the moderation comment pack.

Travel Rule

Travel Rule SDK launch

We have released the Travel Rule SDK solution, which is a simpler method for VASPs to collect information from their users about the transaction counterparties.

It is built on WebSDK 2.0, includes inbuilt unhosted wallet verification flows, and can be white labeled based on client preferences.

Dashboard

Unified Notes format

Previously, notes were presented in different formats in several tabs. We have now unified all notes into a single format. No matter which tab you are on, notes look and behave the same way, which creates a smoother and more intuitive experience.

New format includes the following:

• Attaching files and tags to your notes.
• Clear visibility of who the note is for.
• Pin important notes: highlight key notes by pinning them to the top. Applicable only to client notes.

Case Management

Feature launch

Sumsub Case Management updated solution allows to manually investigate alerts and displays all applicant data in one place. It comes with the following features:

• Each team can have their own investigation flow using a Case Blueprint — a configured case page and team case queue.
• Teams can escalate cases to each other.
• Regulatory reports can be created from a case page if it is a valid threat.
• Case can be escalated to a supervisor for observation.

Business Verification

Interface improvements

We have made several visual updates for a more user-friendly experience:

• All the major KYB requirements, like optionality of document groups, roles, their appointed verification levels and thresholds, are now shown as hints to Company steps in the side-bar.
• A chip with KYB type underneath the KYB level name.
• Roles are now displayed in header links on the Applicant page. Since one person may be involved with multiple companies, we added a compact overlay hint with details.

Calculated percentage of direct ownership

If we do not get the ownership percentage from a source, we start calculating it on our end, using a plain specification of company shares.

In addition, we have started to display beneficiallyHeld attribute.

Risk labels update

New Business verification risk labels include:

• Additional company fields are absent in the database — we could not cross-check additional attributes, like legal address, registration date, website, tax ID as they are not present in corporate DBs.
• Mismatch of additional company fields in the database — additional fields mismatched against data provided by a user.
• Required company fields are absent in the document — company OCR could not extract expected fields according to the document type.
• Mismatch of additional company fields in the document — additional fields (registration date, legal address, tax ID) mismatched against data in corporate DBs.

User Verification

Crucial updates in rejection logic

As a part of our ongoing commitment to improving platform integrity and usability, we’re fine‑tuning how our system interprets certain internal indicators, such as patterns previously associated with elevated risk, so we can cut downon possible false-positive rejections and improve our precision even further.

1. Blocklist logic (16.05.2025). The Respect blocklist hits only from the key group option is now default behavior. Previously rejected users will remain rejected on your project. However, such users will be eligible for re-verification in the new applicant.
2. Forgery label logic (06.06.2025). The Forgery label duplicates will no longer cause automatic rejections unless added to your local blocklist. Previously rejected users will remain rejected on your project. However, such users will be eligible for re-verification in the new applicant.

Reusable KYC improvements

A bunch of Reusable KYC updates have been delivered to improve the product’s security and scaling abilities.

Statistics and identifying Reusable KYC applicants

• As a Reusable KYC customer, you can now view the graphs of usage of the Reusable identity product in the Analytics section of the Dashboard.
• In the Dashboard, applicants can be filtered by Reuse scope, which indicates whether the Reusable Identity product was used during verification—either via Sumsub ID or Reusable KYC.
• The timeline in the applicant profile now shows whether documents were reused via Reusable KYC or Sumsub ID.

Testing in sandbox

• You can test Reusable KYC sharing within the same key in Sandbox without any extra configuration—both Donor and Recipient is the same key.
• A shareToken can now be generated directly from an applicant profile and included in a verification flow using verification links, simulating API calls.
• Testing the email-matching implementation of Reusable KYC via SDK now requires using the Sandbox verification presets.

SDK

SDK toggle visibility

Only users having the Team Lead role or higher will be able to see the toggle for switching a verification level from SDK 1 to SDK 2. WebSDK 2.0.

New version of MSDK

We’ve released the new MSDK version 1.36 with updates for both iOS and Android platforms.

Changelog

• iOS
• Android

Features and products supported on both systems (iOS & Android):

• AllDocs
• The multi-select Country question type in the Questionnaire step
• New setting in the Proof of Address (PoA) step: Accept PoA documents with multiple pages
• New setting in the Non-Doc step: Allow skipping of the Non-Doc step

Android-specific updates:

• Kotlin updated to 1.9.25
• Minimum supported API level is now 23

iOS fixes:

Resolved issue where consent text was missing when only one consent should be shown.

Travel Rule

New country rule bundles

Two new Travel Rule bundles for Japan and Hong Kong have been added, and the bundle for EU countries has been revamped.

This brings the total number of supported bundles to 10.

Dashboard

Marketplace page launch

We’ve launched the new Marketplace page, replacing the old Integrations section. This page serves several purposes:

• Clearly showcases the wide range of partner integrations available
• Displays Sumsub products that can be enabled
• Supports configuration of BYOK (Bring Your Own Key) integrations—such as Chainalysis or World-Check

Status labels:

• Disabled — the product is not yet active.
• Set up required — the product is enabled but needs configuration.
• Active — the product is enabled and fully configured.

The SSO Login page has been moved to Settings→Team.

Non-Doc Verification

USA Non-Doc Identity and Address Verification news

We’ve rolled out an improvement to alias name matching for the USA Non-Doc Identity Verification (SSN) product.

We now receive a list of known aliases associated with an individual and intelligently select the best match, improving approval rates.

Business Verification

Trials for production

It’s now possible to configure the Business Verification trial limits—and this works even for production accounts.

Dashboard

List of ID document expiration extension rules

All rules related to ID document expiration extensions are now visible directly in the Dashboard.

On the User Verification page, in the ID document expiry settings, you can now access:

• Government document rules — international regulations based on global frameworks (e.g. COVID-related exceptions).
• Local regulation document rules — include Government rules and additional rules specific to a country or document type.

Invoice page update

We have redesigned the Invoice page for deposit clients to make our billing page more transparent. The updates include the following:

• The Total section at the bottom of the page will now be fixed while scrolling, making it easier to keep track of overall spend.
• You can also expand the Total section to view a breakdown of the expenses for the selected period — including total spend, amount deducted from the deposit, and taxes.

Check Sources page update

We have launched a new version of the Check Sources admin panel page. The new design includes:

• Improved and more convenient filtering.
• Ability to view Input and Output fields by clicking on a Check Source.
• Ability to add and edit keys by clicking the pencil icon.

Non-Doc Verification

Counties list updates

We have refined the content of most of the previously added countries in our Solution Compliance Assessments to reflect national AML/CTF regulatory changes. At the same time, we have added several new countries in our assessments.

New countries in Non-Doc Identity Verification:

• Canada
• Kazakhstan
• Poland
• Japan

New countries in Non-Doc Address Verification:

• Tanzania
• Saudi Arabia
• Taiwan
• Kazakhstan
• Poland
• Japan
• Canada

South Africa SAID Verification update

From now on, clients can enable South Africa SAID Verification as a Non-Doc step. It allows extraction of a user’s full name directly from the Department of Home Affairs (DHA) without requesting an ID card copy.

Unhosted Wallet Verification

Supported chains update

We have added digital signature verification support for 3 additional chains:

• Tron (TRX)
• Aptos (APTOS)
• Sui Network (SUI)

This brings the total number of supported chains to 17.

User Verification

Device Intelligence feature launch

We have introduced a new feature – Device Intelligence. It enables the identification of devices used during KYC processes and transactions, and detects risky patterns such as:

• Reusing the same device across different users
• Using an unfamiliar device
• Automation tools
• Remote access software
• etc.

By collecting and analyzing device signals, you can ensure a smooth experience for legitimate users while proactively detecting and acting on fraud, such as:

• Bot activity
• Account takeovers
• Multi-accounting

KYB Relations in KYC PDF Report

The KYC applicant’s PDF report now includes a new section that shows any connections between this applicant and KYB applicants.

QES Verification update

We have improved our QES Verification solution with the following features:

• Unique document upload for each applicant: You can submit a unique document to be signed for each verified individual that may contain their personal information or purchased services.
• Document signature OTP autofill: Applicants no longer have to enter the OTP at the document signing step manually.
• Solution test enablement in Sandbox: Both the QES and Penny Drop Verification solutions can now be tested using mock/demo data in our Sandbox environment. Note that the phone and email data should be real.

Applicant actions

New API method for Questionnaire

The new API method enables a new flow with Actions that allows you to upload files to a Questionnaire.

User Verification

Document subtype management

Forbidden document types can be set up in the verification settings now.

Key points of the update:

• You can restrict document subtypes in both Global Settings and the settings of a specific verification level.
• Document subtypes are displayed in human-readable names (English only), instead of codes.
• Uploaded document subtype is now visible in the applicant profile.

Phone number normalization for Phone verification

We’ve implemented an improved phone number normalization system. This update ensures consistent formatting by removing irregularities such as:

• Extra spaces
• Leading zeroes
• Invalid or inconsistent country codes

This allows us to prevent issues associated with duplicate detection. For example, if an applicant has the +7 number and there is another applicant profile with the same number starting with 7 or 07, they will be considered duplicates.

Non-Doc Verification settings visibility

The setting Use Non-Doc method as an alternative to document upload has been moved to the Identity step.

The feature is available only in WebSDK 2.0.

Gender X support

From now on, Sumsub supports documents with the X gender marker, meaning individuals who do not identify as male or female can be verified using our services.

Dashboard

Alias name fix

Aliases are now shown in the interface. You can find an applicant’s aliases in the Personal Info block of their profile (if applicable).

Transaction Monitoring

Rule updates: Payment Methods

Several existing rules have been improved to enhance connection, accuracy, and consistency when dealing with payment method data.

Pre-scoring changes:

• Updated rule—Prepare Payment Method Aggregate Data
• Transactions that include Payment Method fields on the applicant side create a new Payment Method entity in the system. These payment methods are shown in the applicant profile under the corresponding tab.
• Payment Methods’ uniqueness is defined for each method using specific fields.
• All related rules rely on these Payment Method entities rather than on transaction fields.

Updated Scoring Rules:

• Reject Transactions When Duplicate Payment Method Used
• Reject All Transactions After Exceeding X Payment Methods
• Reject Transactions With New Payment Methods After The Limit Of X Has Been Reached
• NewPaymentMethodOnWithdrawal
• A withdrawal is identified when Data.info.type= withdrawal.

Sandbox

New testing templates

We have added new PoI and PoA testing templates that will always* cause the Rejected status. So, now we have a full pack of templates for a wide range of cases.

Templates for receiving the Approved status:

• ID card for China
• ADHAAR for India
• ID card and Passport for Germany (for testing a second ID)
• PoA for Germany

Templates that get the Resubmission requested status (by FastFail):

• Driver's license for California
• ID card for Spain
• PoA for Germany (Temporary rejection)

Templates causing the Rejected status:

• ID card for Cyprus
• PoA for the USA

*If the level has custom settings for verification testing, the testing templates will work according to these settings, ignoring the default behavior.

AML Screening

Exact Match setting in AML Screening

Sumsub’s AML Screening now includes a new option to narrow name-screening results. Unlike Strict Fuzziness, which still allows extra words, Exact Match returns only the exact name entered—no additions, omissions, or year-of-birth “fuzziness” applied.

The Exact Match option disables all fuzzy matching and pre-processing. It should only be used when the applicant’s name is taken from an official document and their country and year of birth are correct. Otherwise, valid matches may be missed.

You can enable Exact Match in Global Settings or in the AML Screening settings of the specific level.

Business Verification

Validation of API calls for Company create/import methods

We have implemented a set of validations to prevent incorrectly created Company applicants via the API. These enhancements address the following issues:

• Missing fixedInfo Company Data for KYB 2.0
• Missing role or applicantIId in the beneficiaries structure
• Linking beneficiaries without calling the link/unilink methods
• Putting the Associated Parties nested levels in the imported applicant profiles

PATCH fixedInfo/companyInfo API method

A new secure method has been added to handle companyInfo data.

PATCH https://api.sumsub.com/resources/applicants/{applicantId}/fixedInfo/companyInfo