June, 2026

Dashboard

Self purchase: PoA Verification

One more service is now available for Self Purchase — Proof of Address Verification. Go to the Solutions page of the Dashboard to get a new solution for your verification.

Self purchase: Non-Doc Verification

Clients with Owner functionality can now enable Non-Doc Verification directly from the Solutions page.

After enabling the product through the modal, you get access to 12 databases. To start using them, you need to set up a level — this is the enabling condition for the Non-Doc Verification card on the Solutions page.

User Verification

Sumsub ID updates

We continue to improve the core feature set of Sumsub ID to increase trust, utility, and subsequent product usage.

Users can now edit their Sumsub ID avatar. This change is cosmetic only and does not affect verification results.

Welcome emails are now clearer and more transparent:

• The email now shows the client name where the Sumsub ID was created.
• The sender name has changed from Sumsub support to Sumsub ID.
• Users who create a Sumsub ID without documents now receive a dedicated welcome email.

Document management is now available in id.sumsub.com. After completing selfie-based authentication, users can:

• View document details.
• Delete documents.
• Download documents.
• Download all their personal data from the settings.

Selfie authentication is not required again in future sessions on the same device.

Live Capture for bank cards

Live Capture for bank cards is now available to all clients.

This feature lets applicants verify bank cards through a real-time camera capture flow instead of uploading files. It helps improve data integrity and reduce fraud risks during bank card verification.

You can configure this experience in the Payment methods section of the level settings. You can choose between File upload and Live capture, and specify whether applicants need to capture one side or both sides of the card.

Business Verification

New company bundles for Transaction Monitoring rules

We have added two company bundles to Transaction Monitoring rules:

• Company risk scoring — you can now use rules that assess company-related risk factors, such as jurisdiction, company tenure, ownership structure complexity, company type, and other attributes. The scoring can also include weighted scores of individuals in the company structure.
• Document expiration tracking — you can now track the validity of company documents, such as Commercial or Trading licenses, Proof of Address, and Power of Attorney. When used with ACDR, this helps monitor document expiration automatically.

Corporate registry block redesign

We have redesigned the Corporate registry block to make company data easier to review and navigate.

The block now includes three separate sections:

• Corporate registry check
• Company Structure/Registry data
• Control and ownership insights

Each section now shows its version and the data source used. This helps clients understand where the information came from and when it was collected.

Empty columns are now hidden by default, making the block cleaner and easier to read.

UBO detection from complete ownership structures

If we get a complete ownership structure, we can avoid full unwrapping in order to detect UBOs. When clients enable this option in Global settings, Sumsub links the detected UBO directly to the primary company. Sumsub then uses the UBO’s information for pre-fill and cross-checks.

Associated Parties pre-fill from documents

Sumsub can now pre-fill Associated Parties while analyzing documents for legal entities that do not have official registration records, such as funds or sole traders in certain jurisdictions.

To use this feature, clients need to add Associated Parties as a separate level before the Company Documents step. This setup triggers OCR, so the uploaded document must also have a defined OCR template.

SDK

New consent document translations

We have added new translations for the Privacy Notice and Notification to Processing of Personal Data for WebSDK and MobileSDK.

Applicants can now view both consent documents in the following languages:

• English
• Portuguese (Brazil)
• Portuguese (Portugal)
• Spanish
• French
• Italian
• Latvian
• Polish
• Greek
• German
• Bahasa
• Serbian
• Hungarian
• Slovenian
• Croatian

Applicants will see the translated versions when their SDK language matches one of the supported locales.

Transaction Monitoring

Transaction Monitoring rules: auto-mute after first alert

You can now reduce repeated Transaction Monitoring alerts by muting rules after the first alert.

This is useful for AML scenarios where the first alert identifies the point of concern, while repeated alerts for the same applicant and rule may add noise without additional value.

There are now two ways to mute a rule:

• Rule-level auto-muting after the first alert. You can configure a rule to trigger only once per applicant. The first alert is created as usual, while all subsequent matches for the same applicant and rule are automatically muted for a configured number of days.
• Transaction-level muting. You can manually mute a rule for a specific applicant directly from a matched transaction. They can also apply an optional transaction-data filter, such as muting the rule only when the IBAN matches.

In both cases, the rule still appears in matched rules for audit visibility. However, its score, actions, and applicant level changes are fully suppressed.

Related transactions in Transaction Monitoring

The Related transactions tab now shows only the transactions that contributed to the scoring of the selected transaction.

Previously, this tab showed all client transactions, which duplicated the transactions list page.

Now, clients can use it to understand which transactions triggered aggregation-based rule conditions:

• The Related transactions tab shows the transactions that matched rules took into account during scoring.
• The Matched rules filter lets clients filter related transactions by one or more matched rules.
• The Matched rules column shows which rule aggregation each related transaction contributed to.

If the tab shows no related transactions, the matched rules did not use aggregations. In this case, scoring only used the current transaction and applicant data.