May 2024

In this release, we have delivered a lot of updates for Workflow builder, Transaction Monitoring, and Travel Rule. Non-Doc Verification has been improved as well, and now supports SSN as an input for the USA Non-Doc verification product. See what's in the article to learn more.

Dashboard

Now it’s possible to download a CSV report with all AML Cases

Starting today, it’s possible to download a CSV report for AML cases on the All AML Cases page:

  • The filters used on the All AML Cases page will affect the data extracted, creating a precise report
  • The maximum number of rows within the CSV report is up to 10K
  • The CSV file will have more data compared to AML cases table (20 data points, including name/DOB/country of the entity in question, ongoing status, and more!)

Moreover, you can now perform a CSV export for applicant actions.

The limit is the same as for exporting applicants: 10K rows. Export with the following fields:

  • id
  • externalActionId
  • applicantId
  • type
  • creationDate
  • lastReviewDate
  • rejectType
  • rejectLabels
  • result
  • userComment

All your customizations in one place

Manage all your customization options within one table.

Features:

  • Added search functionality.
  • Filters by theme (light/dark) and type (web/mobile).
  • The Customization , Created , and Changed buttons can now be sorted (by date, alphabet, etc.)

Suspicious Applicant Name Check: Is that a real movie star signing up?

Navigate to the Applicant Insights section within the level settings to find a new checkbox called AI Suspicious Name Check, which can be turned on for specific levels. This way, customer names will be automatically sent to be reviewed by AI.

Some risk labels, like Famous Person or Strange name, can be added if the AI considers the case suspicious. You can set up a rule to receive an alert and send such cases to your team for manual review.

Team management settings update

Previously, if you wanted to allow a team member to authenticate via Google Sign-In, you had to create the team member, and then separately add their email to the Dev Space -> Google Sign-In list. Now you can manage all the settings in a single place.

What’s changed:

The separate Google Sign-In section no longer exists. Instead, each member in the Settings -> Team -> Members section now has a new property: Allow Sign-In with Google, which completely replaces the previously existing section.

All previously set values have been migrated to this property from the Dev. Space section and will not be lost.

WebSDK

Dutch and Georgian language support have been added to the WebSDK

Check out this article to see all the languages supported by our SDKs.

Non-Doc Verification

USA Non-Doc Verification: Now with an SSN input

The last 4 digits of SSN are now supported as an input for the USA Non-Doc verification product.

Previously, only phone number + date of birth could be used as an input.

The output will remain unchanged:

  • Full name
  • Date of birth
  • SSN
  • Phone number
  • Address
  • Email

Workflow Builder

Workflow Builder improvements: Now live

  • Use the Modal Window to search for existing nodes.
    If you have a lot of nodes, it can be a struggle to find the particular node you want to connect. Now, it’s much easier with the Connect to existing block option, which activates a search feature for previously created nodes within the workflow. The search can be based on both block names and level names.
    Bonus: If you hover over a node for several seconds, the interface will zoom in on this option.
  • The Copy to Test Workflow button
    Now, you can easily copy an active flow to a Test Workflow, allowing you to test changes without impacting the actual flow.

Proof of Address

Proof of address settings update

In some cases, a document with no expiration date cannot be accepted as a PoA—for example, the Hungarian Address Card. To help you solve this challenge, we added a new checkbox titled, Always consider document's issue date, on the POA preset page. If this checkbox is enabled, Sumsub will always consider POA document issue date and ignore "valid until".

Database Verification

One place to manage database access

Check out the new Active Services tab in the Dashboard. It lets you see all the databases you have enabled and check their uptime. This includes Non-Doc Verification options and Database Validation. Get more control and transparency over your database performance.

Transaction Monitoring

Case Management for Transaction Monitoring

Exciting news about Transaction Monitoring: Cases are live. What does this mean?

  • Save time by reviewing fewer cases. Consolidate multiple transactions, either manually or through rule-based automation. This means you can focus on just 20 cases representing potentially suspicious activity, instead of reviewing 100 individual alerts.
  • Single-window view. Get all the information you need for investigations (transactions, events, applicants, analytics, etc.) in one place. Plus, there’s now three ways to use cases:
    • Post-monitoring, which enables you to spot anomalies like limit breaches, transaction bursts, suspicious patterns, etc.
    • Real-time monitoring
    • Filling out reports such as SARs

Learn more ->

Chainalysis Insights in the Sumsub Dashboard

No need to go to the Chainalysis dashboard to check their risk rules. Simply navigate to the new Chainalysis Insights section in your Sumsub Dashboard.

These data points can be used via custom rules in addition to the existing Chainalysis Rule Bundle on our Transaction Monitoring solution.

External User ID within Сounterparty Data

Are your applicants transacting with each other? Managing this has gotten much easier. Now, transactions that occur between your clients will be clearly marked blue. This is done by matching external IDs within the counterparty data to existing applicants. You will also be able to go to the second user profile from the transaction using a link on the counterparty’s side within the transaction.

Travel Rule

Notifications for incoming Travel Rule transactions

Incoming Travel Rule transactions will be visible to all Transaction Monitoring customers.

When a Sumsub customer (originator) sends a Travel Rule transaction to any other Sumsub customer (beneficiary), the beneficiary will receive a notification in the dashboard about it.