April, 2026

In April 2026, we expanded our Transaction Monitoring solution with a new, Pix Fraud Monitoring bundle and improved duplicates detection logic with new settings. Sumsub Dashboard has been updated as well to display more accurate maps reflecting the actual confidence range of the IP geolocation data.

Find more updates below, and stay tuned.

April 6 -> April 10

SDK

Expanded document subtype names

From now on, in the WebSDK we display specific document subtype names or groups of subtypes instead of the generic default ID document types.

MobileSDK update

New MobileSDK plugin versions have been released – 1.42.

Change log:

Transaction Monitoring

New bundle – Pix Fraud Monitoring

The Pix Fraud Monitoring Bundle is now available for deployment – a purpose-built set of 39 transaction monitoring rules for Brazilian PIX instant payments.

What it covers:

  • Monitoring of PIX transfer transactions

  • Real-time anti-fraud monitoring for incoming and outgoing PIX flows

  • Rule-based detection logic combining transaction indicators, DICT-related information, and customer profile context to identify anomalous or profile-inconsistent transactions

  • Behavioral analysis (atypical frequency, volume, amount)
  • Complex typologies: structuring, viral mass scams, and money mule dispersion tracking
Discover more ready-to-use rule bundles ->

Dashboard

Smart mode: Enhanced POI document upload

We have released a new Smart Mode setting for Supported ID documents.

Select Smart mode if you want the system to automatically decide how many sides of a document need to be requested based on the configuration of a specific document.

IP geolocation on maps

We have improved the maps in Location widget with the following:

  • IP geolocation points across all maps now appear as radius circles rather than precise pins — reflecting the actual confidence range of the data.

  • We now filter out VPNs, proxies, and hosting providers.
Learn how Sumsub uses IP geolocation ->

User Verification

Restriction for creating actions with duplicate ID

We have implemented a restriction for creating applicant actions with duplicate externalActionId.

Now, if an action with an already existing externalActionId is created, you will see an error: Action with externalActionId 'NonUniqueld' already exists.

Duplicates detection logic update

From now on, we are using applicant.tin (TIN, PAN, or any other tax number) field for duplicate search.

If TIN and country match between two applicants on the same key, we will count the latest applicant as duplicate.

New duplicates detection logic setting

We have released a new Ignore not completed duplicates setting that allows you to exclude duplicate applicants whose verification has not been completed from duplicate detection.

To learn how to manage account duplicates, see this article.

New user verification webhook

We have added a new webhook to provide better visibility into Applicant Actions workflows: applicantActionLevelChanged.

This webhook allows you to track when a specific Applicant Action moves to a different verification level.

See the full list of user verification webhooks ->