May, 2026

User Verification

Finland Non-Doc Verification

We have launched a new Non-Doc Verification method for Finland — FTN eID.

A single, seamless flow now incorporates all major Finnish banks and mobile IDs. This enables faster onboarding and higher acceptance rates while eliminating the need for complex due diligence and additional agreements.

Brazil Non-Doc Verification

Brazil Non-Doc Verification method has been updated with two new solutions for regulated Financial and iGaming industries with a broader coverage.

Partner levels

We have introduced Partner levels — a strategic feature designed to automate and standardize compliance requirements between partners.

This feature minimizes human mistakes in requirements synchronization between different Dashboards and provides full visibility of verification requirements to both parties within the Reusable KYC and Copy Applicant flows.

Reusable KYC updates

Reusable KYC service has been updated to support complex integration scenarios.

What’s new:

1. We have updated the Reuse Applicant API method and SDK to support the reuse of both documents and data (including email, phone, questionnaires, and applicant data) throughout the entire workflow, not just the initial level.
2. New webhooks that trigger on both successful consumption and consumption errors have been added — applicantShareTokenConsumed and applicantShareTokenFailed.
3. You can now pass a sourceKey parameter at the exact moment an applicant is created via Copy applicant or Reusable KYC API methods.

SDK

Mobile SDK update

1.43 version has been released. Changelog:

• iOS
• Android

Dashboard

Product tour

Now on the Applicant page, you can see a product tour guiding you through the new flow of resetting Proof of Identity.

User Verification

New mode names in Data comparison

We are introducing new terminology for the name and address comparison settings to streamline and clarify labels across the platform.

What’s new:

• Fuzzy and Weak containment → Flexible.
• AI mode → AI-assisted.

New permission: Manage fixed info

A new permission has been added: Manage fixed info. It allows users to modify an applicant’s (provided) personal information (Applicant Data).

Field shift for Columbian ID card

The Additional number field for Colombia ID_CARD has been moved from Extra fields to Default fields, which means the Additional number field is now free and OCRed by default.

Business Verification

New business verification source for MENA region

We have integrated a new UAE data source, resulting in a significant increase in the match rate for the country. Besides the United Arab Emirates, the package also supports 19 additional countries:

• Morocco
• Algeria
• Tunisia
• Libya
• Egypt
• Sudan
• Israel
• Lebanon
• Palestine
• Jordan
• Syria
• Iraq
• Kuwait
• Iran
• Qatar
• Bahrain
• Saudi Arabia
• Yemen
• Oman

See the Regional drop-down list in the documentation for more details.

Company Search & Selection API methods

Two new API methods have been introduced within Business Verification to enable company search and selection by name:

• Search companies for applicant
• Get company details by search item ID

Since different data sources may have specific search capabilities, refer to the documentation for the list of supported company search parameters, structured by region, country, and data source.

Entity types/Legal forms customization

Global Settings → Business Verification has received a second tab: Entity types.

It allows you to specify which entity types are available to be collected on the Company Information screen in the Entity Type and Legal Form fields.

New country in the Local pack: Poland

We have implemented a new integration with Polish business registries. This integration fetches data directly from KRS and CEIDG, providing information on both companies and sole proprietors.

See the Local drop-down list in the documentation for more details.

Merge options for individuals in companies

We now offer different options for merging verified individuals:

• Link if the previous verification covers all steps in the new level — default option. If the verified applicant has completed all the required steps, we will link the existing applicant instead of creating a new KYC applicant.
• Link if the previous verification matches the new level — a stricter option. Linking occurs only if the passed level is identical. This helps prevent cases where level step settings differ.
• Always link and move to the new verification level — an option that completely avoids duplicates by requiring the KYC applicant to complete the new verification steps. This will change the previously verified applicant’s status to Documents requested.

SDK

MobileSDK update

Version 1.44 has been released:

• iOS
• Android
• React Native
• Flutter (1.44.1)

Main updates:

• Updated consent flow — now displayed as a bottom sheet instead of a separate screen. The Steps screen is no longer skippable, aligning the behavior with WebSDK.
• Custom consents are now configured the same way as in WebSDK:
  • Verification level → Advanced settings → Custom consent for data processing.
  • The same translation key is used for both MobileSDK and WebSDK — custom.defaultDescription.

Dashboard

New service in Self Purchase: Reusable KYC

One more service is now available for Self Purchase: Reusable KYC.

Single-column layout for Reports

The Applicant Summary and AML reports have been redesigned from a two-column layout to a single-column view. The new layout ensures that you always see complete information without horizontal scrolling.

What’s new:

• Both reports now display all sections in a single, full-width column.
• No content is cut off or wrapped awkwardly regardless of screen size.
• Visual hierarchy is cleaner — section headers and data entries are easier to scan.

Fraud prevention

Identity Enrichment: new name and expanded data

Identity Enrichment is a service that takes the email and/or phone number provided by an applicant and returns linked personal data (name, date of birth, addresses). It is used in two ways:

• Cross-checking the linked data against the information provided by the applicant. A matching name and date of birth increase trust, while mismatches may indicate potential identity takeover, money mule activity, or synthetic identity fraud.
• Consistency checks on the linked data itself. Too many different personas may indicate the same potential risks as above.

What’s new:

• The service has been renamed to Digital Footprint Check in the Dashboard UI. This aligns with industry-standard naming for products that assess the reputation and history of contact details (email, phone number).
  Expanded data in the check. Digital Footprint Check now returns possible personas — names, addresses, and DoBs — along with timestamps.

Transaction Monitoring

BYOK for MerkleScience

We have enabled the BYOK functionality for our MerkleScience integration. You can use your own API keys in the Sumsub system for this provider across multiple products, including crypto transaction monitoring and wallet screening via payment methods/applicant actions.

User Verification

Lite mode OCR updates

We have improved our Lite mode OCR quality to bring Lite mode’s data extraction accuracy in line with Standard mode. The updates include:

• Cleaner field data. Automation is now much more accurate in how it fills information.

• Stability in metrics. While we have boosted data quality, approval rate and rejections due to Data not readable remain stable.

New API methods

You can now approve and reject applicant actions via following API methods:

• Approve applicant action
• Reject applicant action

New workflow expressions for BIN lookup data

New expressions for payment check results are now officially available in the Workflow Builder. The metadata can be used directly within conditional blocks inside the Workflow Builder to interact with payment check data from the last BIN lookup.

This allows you to dynamically route and review data including:

• Card brand
• Commercial flag (business/corporate cards)
• Country of issue
• Issuer bank
• Prepaid status
• Card type
• Virtual card flag

New API parameter

Previously, when using the Get ID verification results API method, the endpoint returned only the most recent image(s) per idDocType + country pair and filtered out any images marked as deleted.

Now, a new optional query parameter withDeletedImages (boolean, default false) is available. When set to true, the response includes deactivated documents and returns all matching image IDs per idDocType + country, sorted by addedDate descending.

New permission logic

The new permission logic has been enabled. Key changes include the following:

1. No more hidden roles. You will now always see all roles that overlap with your access by source keys/client group keys. If you have permission to edit roles, you will always be able to edit the permissions you have yourself, even if the role contains additional permissions that you do not have.
2. Clearer access boundaries for source keys/client group keys. Access to roles and members now strictly depends on overlapping access scopes. You will only see members and their roles that include source keys / client group keys you have access to. If there is no overlap in access, those members and roles will be completely hidden.
3. Restrictions on security actions for more privileged accounts. If you have permission to edit members, you will still be able to:
   • Update basic account information.
   • Block users.
   • Reset 2FA.

However, security-sensitive actions will be restricted for accounts with higher privileges. For example:

• Disabling Google Authenticator.
• Deleting a member.

Case Management

New features release

We have released several new features to improve your experience with Case Management:

1. Case analytics — a dashboard with aggregated case data over any selected period. Use it to:

   • Spot suspicious patterns (like transaction spikes) before they escalate.
   • Group cases by severity, impact, or exposure.
   • Review team impact over time.

2. Majestic overview for managers. Three tabs in one view:

   • General for daily ops (Awaiting Decision, SLA at Risk, FIU/SAR tracking).
   • Blueprints for workload balancing.
   • Team for live presence, top resolvers, and false-positive % per operator.

   Managers get instant visibility into capacity, workload, and risks — so decisions happen on time, before fines or fraud do.

3. Case prioritization in every case — filter and sort across the case list.

4. Case deadlines — set due dates when creating a case.

5. Smart escalation — one-button escalation to a more experienced team or another Blueprint.

6. 4eye control — after the case is resolved, the senior reviewer must approve before the decision becomes final. Use it to eliminate internal fraud risk, catch human errors, and meet regulatory expectations.

Automation

SumScript: Conditional scoring

Conditional scoring is now supported in SumScript via the addScoreIf function.

What’s new:

• addScoreIf(BOOL, INT) — adds a score when the condition is true.

• EOR — like OR, but evaluates all branches. Every matching condition adds its score.

• EAND — like AND, but evaluates both sides always. All matching effects apply.