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.

User Verification

South Africa Bank Account Verification

A new verification solution has been launched — South Africa Bank Account Verification.

You can now instantly verify if a bank account is real, active, and belongs to the exact person you are trying to pay or collect money from. This happens securely and in real-time by checking directly with the South African Reserve Bank (SARB).

Technical Specifications (API-based integration):

Input data:

• Last name
• Document number
• Bank account number
• Bank name (Absa, African, Capitec, FNB, Investec, Nedbank, Standard, Discovery, Sasfin, Grindrod, Tyme, Firstrand, Randmerchant, or RMB)

Output data:

• Document number (Match/Mismatch)
• Bank account (Found/Notfound)
• Last name (Match/Mismatch)
• Bank account status (Open/Close)
• Bank account accept credit (Yes/No)
• Bank account accept debits (Yes/No)
• Bank account opened over 3 months (Yes/No)

Potential rejection messages: [ACCOUNT_NOT_FOUND, ACCOUNT_NOT_OPEN, ACCOUNT_TYPE_MISMATCH, ID_NUMBER_MISMATCH, NAME_MISMATCH]

Note: This solution currently supports API integration only.

Travel Rule and Transaction Monitoring

BYOK for Crystal

We have added BYOK (Bring Your Own Key) functionality to our Crystal integration. You can now use your own API keys for this provider directly within our Dashboard.

It works across the Transaction Monitoring, Travel Rule, and Payment Methods products.

Crypto Monitoring

Crypto Monitoring: Investigations

We have introduced a new forensic add-on — Crypto Monitoring: Investigations. This feature gives you access to a dedicated Merkle Science dashboard where you can modify risk configurations, conduct searches, perform deep investigations, and more.

Note: This is only available to Sumsub clients who use Merkle Science as their default provider.

Dashboard

Dashboard system theme alignment

Now the Sumsub Dashboard can automatically detect your operating system’s light or dark mode and adapt to your visual preference.

What’s new:

• Auto mode (enabled by default) — The Dashboard theme syncs with your system automatically.
• Manual Light and Dark options are still available if you prefer a specific mode.
• Choice memory — If you switch away from Auto after the release, your choice will be saved. Note: Any theme preference set before the release will reset to Auto.

Self Purchase: Questionnaire

Owner accounts can now enable one additional service directly on the Solutions page — Questionnaire.

Important:

• After purchasing, you must add a Questionnaire step to at least one verification level.
• You will be charged upon the first use of the questionnaires, not immediately after purchasing the service.

New webhook setting: Rollout percentage

You can now roll out webhooks gradually. A new Rollout percentage field (0–100) is available in the Webhook manager. You can start with 10%, verify everything works as expected, then increase to 50%, and eventually to 100%.

How it works:

• 100 or empty → All events are delivered (default behavior)
• 0 → No events are delivered
• 30 → A stable 30% of entities are selected and delivered

Note: Existing webhooks will behave as if the Rollout percentage is set to 100% until you explicitly configure a different value. To learn more about this setting and its configuration, see the dedicated article.

New dashboard permissions

Two new permissions are now available to enable more granular access control in the Dashboard: Manage SSO settings and View applicants.

What's new:

• Manage SSO settings — Allows users to view, edit, and delete SSO configurations, as well as create, edit, and delete SSO group mappings.
  • Granted to all existing roles with the Manage client settings permission
  • Added to the Owner and Admin default permission sets
• View applicants — allows users to view applicants.
  • Granted to all existing roles and appTokens.
  • Added to the Owner, Admin, Developer, and Compliance officer default user permission sets.

User Verification

South Africa SAID Verification for iGaming operators

South Africa SAID Verification is now available for iGaming operators. This check helps operators verify users at the registration stage before triggering full KYC or additional identity verification checks. It flags invalid national ID, and whether identities belong to deceased persons.

The check can be used as an early gatekeeper in the onboarding flow to help prevent fake accounts and identify suspicious registrations before they move further through the user journey.

This gives iGaming operators in South Africa a faster and more efficient way to strengthen registration flows and reduce fraud risks.

New API Method: Check Applicant Existence by externalUserId

A new API method — Check Applicant Existence by externalUserId — is now available for checking whether an applicant already exists by externalUserId.

This method is recommended for clients who need to confirm applicant existence before creating or updating an applicant. It provides a clear response and helps avoid unnecessary error handling when an applicant is not found.

If the applicant exists, the response confirms it and returns the applicant data. If the applicant does not exist, the response simply confirms that no applicant was found.

Webhook logs: filter by webhook name

You can now filter webhook logs by webhook name in addition to its status and type. Select one or several webhooks to see deliveries for specific endpoints only.

The filter is available in the Dashboard in the following places:

• In the Dev space → Webhooks → Webhook logs section.
• On the Applicant page → the Events tab → Webhooks.

Business Verification

LEI verification

LEI verification is now available through an integration with GLEIF, the Global Legal Entity Identifier Foundation. This allows us to verify Legal Entity Identifiers using the official GLEIF API.

LEI is a unique 20-character global identifier used to identify legal entities, especially in cross-border financial, investment, and regulatory workflows.

LEI verification is currently implemented as a standard registry check. It can be used as a fallback source for standard checks or configured on separate levels where LEI verification is the only verification source.

Dashboard

Game sessions tab update

We have moved the Game sessions tab on the applicant page to Transactions.

Transaction Monitoring

Sandbox and Production rule separation

Transaction Monitoring rules are now managed separately in Sandbox and Production.

Previously, rules were shared between the two environments. This meant that changes made in Sandbox could also affect live Production rules.

Now, Sandbox rules are fully isolated from Production. You can safely configure and test rule changes in Sandbox without affecting live traffic.

• When the rules are ready, clients can move them to Production using the Publish to Production button.
• Published rules are added to Production in test mode, so you can review their behavior before using them in live decisioning.
• If a rule with the same name already exists in Production, the published rule is added as a new copy instead of replacing the existing rule.

Rule version history is also stored separately for each environment.