# V7.55.0 - Smarter Identity Controls & Flexible Onboarding

*<mark style="color:$info;">Learn about all the details of all our recent CRM updates here.</mark>*

**Released Date - 22 September 2025**

This release strengthens identity management and onboarding flexibility across the CRM. Brokers gain tighter control over KYC data quality, more configurable third-party verification options, and stronger withdrawal safeguards — alongside clearer client communication and expanded API support for custom onboarding integrations. These enhancements help reduce operational friction, reinforce compliance, and support more adaptable onboarding journeys without disrupting existing workflows.

### <mark style="color:red;">Key Function Highlights</mark>

1. [**KYC Duplicate Prevention**](#id-1-kyc-duplicate-prevention)**:** KYC forms can now be configured to prevent duplicate identity submissions. When enabled, the system blocks repeated values (e.g., ID numbers or phone details) that already exist in approved KYC records — helping brokers maintain cleaner client data and reduce identity-related risk.
2. [**More Flexible ShuftiPro Verification Controls**](#id-2-more-flexible-shuftipro-verification-controls)**:** Optional ShuftiPro verification add-ons can now be managed more precisely. Brokers can choose whether to enable additional paid checks (e.g., age verification or enhanced data retrieval), aligning verification depth with operational needs and cost considerations.
3. [**Enhanced Sumsub Verification for Withdrawals**](#id-3-enhanced-sumsub-verification-for-withdrawals)**:** Sumsub verification can now be applied beyond onboarding to support added checks during withdrawals. Brokers can configure withdrawal thresholds that trigger face or identity verification — requiring clients to complete verification before high-value withdrawal requests can be submitted. This adds protection for sensitive transactions while keeping standard withdrawal flows unchanged.
4. [**Multi-Step Registration Confirmation Emails**](#id-4-multi-step-registration-confirmation-emails)**:** Clients completing multi-step registration will now receive an automatic acknowledgement email. This improves onboarding transparency by confirming that registration details have been received and are under review.
5. [**New KYC Open APIs for Custom Onboarding Journeys**](#id-5-new-kyc-open-apis-for-custom-onboarding-journeys)**:** New KYC Open APIs are now available to support brokers building custom or integrated onboarding flows. Brokers can submit KYC data and documents via API, retrieve KYC status and records, and programmatically manage approvals or rejections — helping streamline compliance workflows and external registration integrations.

### <mark style="color:red;">1)   KYC Duplicate Prevention</mark>

KYC forms can now be configured to prevent duplicate identity submissions. When enabled, the system blocks repeated values (e.g., ID numbers or phone details) that already exist in approved KYC records — helping brokers maintain cleaner client data and reduce identity-related risk.

To configure KYC duplicate prevention, follow these steps:&#x20;

{% stepper %}
{% step %}

#### Go to KYC Dynamic Form&#x20;

1. Go to "**Settings**" > "**KYC**" > "**KYC Dynamic** **Form**".&#x20;
2. Choose the KYC form you wish to amend.<br>

   <figure><img src="/files/SNyvIhD8ith6rLAnjmbu" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

#### Edit KYC Field

1. Locate the relevant KYC field and click the "**Edit**" icon. <br>

   <figure><img src="/files/fh6nno5DCAndoJNrkAxB" alt=""><figcaption></figcaption></figure>
2. Note: Duplicate prevention is available only for the following field types:
   1. Text
   2. Numbers
   3. Phone Number
3. Select "**Block Duplicates**".&#x20;
4. Click "**Save**" to apply the configuration. <br>

   <figure><img src="/files/4RpconZ9u1Hlgov8vg0X" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

#### Application

1. Once duplicate prevention is enabled, if a client submits a KYC form containing information that already exists in approved KYC records, the system will display an error message indicating which field is duplicated and prevent the submission from being completed.<br>

   <figure><img src="/files/m6FmigrBX9PdSm8tj5xm" alt=""><figcaption></figcaption></figure>
2. For existing KYC requests that are pending review, if duplicate prevention is enabled and a duplicate is detected during approval, a pop-up notification will be displayed. The notification will indicate which field is duplicated and identify the existing client, allowing you to decide whether to proceed with approval or reject the request.<br>

   <figure><img src="/files/gjk5sNMFKuVIXLMcXgJI" alt=""><figcaption></figcaption></figure>

{% endstep %}
{% endstepper %}

### <mark style="color:red;">**2)   More Flexible ShuftiPro Verification Controls**</mark>

Optional ShuftiPro verification add-ons can now be managed more precisely. Brokers can choose whether to enable additional paid checks (e.g., age verification or enhanced data retrieval), aligning verification depth with operational needs and cost considerations.

To configure the additional paid checks, follow these steps:&#x20;

{% stepper %}
{% step %}

#### Go to ShuftiPro Settings

1. Navigate to "**Settings**" > "**KYC**" > "**ShuftiPro Settings**".&#x20;
2. Go to "**Offsite Verification**" > "**Document Verification**". <br>

   <figure><img src="/files/Pb2DnuGiMWtm647d7T3U" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

#### Enable Additional Verification

1. Click the "**Edit**" icon.<br>

   <figure><img src="/files/CyybJqOtLTd5UGp596Cg" alt=""><figcaption></figcaption></figure>
2. Select "**Age Verification**" and/or "**Fetch Enhanced Data**".&#x20;
3. Click the "**Save**" icon. <br>

   <figure><img src="/files/42P6RZ3EsENpABtUXx9r" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

#### Application

When clients submit their KYC request and upload documents, the ShuftiPro document verification process will also perform age verification and fetch enhanced data, if these options are enabled.
{% endstep %}
{% endstepper %}

### <mark style="color:red;">**3)   Enhanced Sumsub Verification for Withdrawals**</mark>

Sumsub verification can now be applied beyond onboarding to support added checks during withdrawals. Brokers can configure withdrawal thresholds that trigger face or identity verification — requiring clients to complete verification before high-value withdrawal requests can be submitted. This adds protection for sensitive transactions while keeping standard withdrawal flows unchanged.

To do so, follow these steps:&#x20;

{% stepper %}
{% step %}

#### Go to Sumsub Settings

1. Navigate to "**Settings**" > "**KYC**" > "**Sumsub Settings**".&#x20;
2. Under "**Embedded Verification**", click the "**Edit**" icon.<br>

   <figure><img src="/files/jQ337aJ6KTFXZKnnDZOD" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

#### Configure Applicant Actions Level

1. Click "**Enable Applicant Actions Level**".&#x20;
2. Once enabled, the **Verification Reminder Settings** will automatically be set to "**Mandatory Verification**", with "**Withdrawal**" enforced as the selected option. These settings cannot be changed while Applicant Actions Level is active.  <br>

   <figure><img src="/files/4wRtqnWeRYCrvfwnHrQY" alt=""><figcaption></figcaption></figure>
3. Select the "**Applicant Actions Level**" from the dropdown menu. The available options are automatically retrieved from the Applicant Actions Levels configured in your Sumsub account.
4. Select the **Actions Requiring Verification**. Currently, only "**Withdrawal**" is supported and will be selected by default.
5. Configure the trigger condition for each withdrawal currency. If the withdrawal amount exceeds the configured threshold, the client will be required to complete identity verification before the withdrawal request can be submitted.<br>

   <figure><img src="/files/jS3SPupoZhDknVh2Kjdh" alt=""><figcaption></figcaption></figure>
6. Click the "**Save**" icon. <br>

   <figure><img src="/files/aZXTY8GDD3U7yUJWFBCC" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

#### Application

1. When a client submits a withdrawal request that exceeds the configured trigger condition, the client will be prompted to complete identity verification.
2. A Sumsub verification pop-up will be displayed for the client to complete the required verification.<br>

   <figure><img src="/files/Zs2faLZ7likeR8tNBCkl" alt=""><figcaption></figcaption></figure>
3. Once verification is completed, the withdrawal request will be submitted and you will be redirected to the withdrawal transaction history to view its status.<br>

   <figure><img src="/files/WA55KKsWzeXKdoeqLMxP" alt=""><figcaption></figcaption></figure>
4. When reviewing a withdrawal request in the CRM Back Office portal, you can click "**Sumsub Verification Results**" to view the embedded verification outcome.\
   &#x20;

   <figure><img src="/files/eMrJAZR5WJcakIy4wgQI" alt=""><figcaption></figcaption></figure>
5. Selecting the verification code will redirect you to the Sumsub portal, where detailed verification information can be reviewed.<br>

   <figure><img src="/files/eVgZnlqueuSm0mT68jKt" alt=""><figcaption></figcaption></figure>
6. After reviewing the verification details, you can proceed to **Approve** or **Reject** the withdrawal request.
   {% endstep %}
   {% endstepper %}

### <mark style="color:red;">**4)   Multi-Step Registration Confirmation Emails**</mark>&#x20;

Clients completing multi-step registration will now receive an automatic acknowledgement email. This improves onboarding transparency by confirming that registration details have been received and are under review.

To configure the email, follow these steps:&#x20;

{% stepper %}
{% step %}

#### Edit the Email Template

1. Navigate to "**Settings**" > "**Notification Setting**" > "**Notification Templates**".
2. Under "**Email Templates**" > "**To Client**", locate the relevant multi-step registration email and click the "**Edit**" icon. This email notification is enabled by default.<br>

   <figure><img src="/files/4eRfUwZkCENhUHozUeeF" alt=""><figcaption></figcaption></figure>
3. Update the email content as required and click "**Save**".<br>

   <figure><img src="/files/rCAa4GAJswR15XpjTcLg" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

#### Application

Upon successful submission of a multi-step registration, the client will automatically receive the configured email notification.
{% endstep %}
{% endstepper %}

### <mark style="color:red;">**5)   New KYC Open APIs for Custom Onboarding Journeys**</mark>

New KYC Open APIs are now available to support brokers building custom or integrated onboarding flows. Brokers can submit KYC data and documents via API, retrieve KYC status and records, and programmatically manage approvals or rejections — helping streamline compliance workflows and external registration integrations.

To receive access to the KYC Open APIs, please contact your dedicated account manager.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://reference-guide.gitbook.io/crm-version-release-notes/v7.55.0-smarter-identity-controls-and-flexible-onboarding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.