With Sumsub, you can streamline your compliance with a one-time integration, which you can customize through the “Integrations” section of your dashboard without any developer assistance. You build your flow by creating and customizing respective verification levels.
Verification levels let you choose the steps that an applicant has to pass in order to get verified. This should depend on the level of risk, which becomes apparent when considering details such as the user's verification purpose and their country of residence.
You can create several unique levels with different check sequences and set up triggers related to the applicant's actions.
For example, you can create a region-based level, requesting one set of documents in low-risk regions and a different set of documents in high-risk ones.
Customizations let you adjust what the applicant sees when passing verification. You’ll be able to customize colors and styles, while adding instructions and tips for each step of the verification process. Moreover, you can preview the resulting verification flow with just a few clicks.
You can also skip the customization step completely if you want or use it to A/B-test different interfaces for one or many verification levels.
Creating and Managing Verification Levels
To create a new verification level, go to the “Integrations” tab and click “Add new level”. Fill in all the required fields and select the necessary verification steps from the drop-down menus. Then press “Add" to have the level saved.
The Level name is the name of a particular verification level. Once you create a level, you cannot rename it.
- Description lets you add some detail related to this level.
- Supported ID documents turns on custom ID documents settings.
- Countries and territories lets you create a list of countries where your verification level applies. This allows you to create different verification levels for different countries.
Video indent lets you add a video identification module to a level.
The Required steps specify the steps, documents, and actions required. You can add new steps by clicking ‘Add new step’ and delete existing steps by clicking the ‘Trash’ icon.
Source key assigns this level to a specific source.
- Customer emails enables notifying the customer about verification statuses.
Web and Mobile SDK set up let you choose customizations (if you have any) for the specific level.
Please note that there are several settings that allow you to specify the supported countries and documents for a specific country.
Global Settings also lets you specify supported countries and documents. If certain documents are excluded in the Global Settings, they are automatically excluded in all other levels.
Example #1. You can use Global Settings to make country-specific exceptions for supported documents. For example, you may choose not to accept Residence Permits in the UK, while accepting Residence Permits everywhere else.
Alternatively, if you allow Passports, Driving Licences, and Residence Permits for the UK via the Global Settings, and then create a level that accepts only passports globally, no documents apart from Passports will be accepted from the UK.
Example #2. If you have a standard KYC procedure for all customers, you might expect one applicant level (you could name it: 'Basic KYC') which may consist of the following steps:
1. Providing personal information,
2. Uploading identity documents,
3. Passing the liveness check.
Example #3. If your verification procedures differ depending on, for instance, the purchasing limits of your customers, then you may have three levels. Your users will start at Level 1 and will have to complete extra verification steps if they want to move to the next level.
|Level 1.||Full Name||Email Address|
|Level 2.||Identity Document||Liveness check|
|Level 3.||Proof of Address||-|
All your existing levels can be accessed from the “Applicant Levels” tab of the “Integrations” section of your dashboard. You can edit, delete, and import/export levels (as a code from the clipboard), or run a specific level from a new tab to preview it together with the selected customization.
Creating and Managing Customizations
To create a new customization, go to the “Integrations” tab and press the “Add new customization” button. Fill in the required fields, specify the elements you need and their specifics by choosing from the drop-down menus, and press “Add” to have the customization saved.
Please note that to create customizations, you should have at least one applicant level.
The Customization name is the name of your customization. Once you create a flow, you cannot rename it.
The Integration type lets you choose your integration preference: WebSDK or MobileSDK. For example, you may wish to customize the WebSDK and the MobileSDK separately. As a level may contain a link to a WebSDK customization and a MobileSDK customization, multiple levels can also point to the same customization.
Type is the verification procedure that the customization refers to.
- The “Standard” type refers to initial customer verification and is normally used for onboarding new clients.
- The “Applicant Action” type refers to an extra check that you may request from an existing client (e.g. payment method verification or facial authentication).
- The “Module” type refers to a specific verification step for an existing client where extra data is required, e.g. in addition to the ID and Liveness checks that are included in the ‘Standard’ flow, Proof of Address may be requested too.
Action Type will be activated only if the “Applicant action” checkbox has been selected. There are two action types to choose from: ”Face Enrollment”, which requires a photo or video selfie and “Payment method check”, which requires one to provide settlement account details.
Navigation screens will be activated only if the ‘Applicant action’ or ‘Standard’ checkbox has been selected. In this section, you can choose the screens and devices for the customization by ticking/unticking the corresponding boxes.
Warning screen. The screen informs the user about the company that they are passing verification for to deter phishing attacks.
Welcome screen. You can use this screen to display the summary of the verification procedure to help your users prepare.
Agreements screen. You can use this screen to display all of the agreements you want your applicants to accept before they proceed to verification.
Review screen. You can use this screen to ask your applicants to review all of the information that they have entered for verification purposes.
Force mobile devices. If this box is checked, the flow will be passed on mobile devices only.
Disable mobile use. If this box is checked, the user won’t see the option to continue on his/her mobile.
- Required steps customization lists the screens of the flow that you can customize in terms of uploaded file format, CSS settings, screen titles, instructions or questions, etc. All the steps are added from the applicant level you assign the flow to.
The “Allow files of all formats” box, if checked, allows the uploading of all file formats on the front end.
1. Custom CSS. A path to your own CSS file that will override the default CSS.
2. Custom CSS string. CSS content that will override the default content.
Selectable languages. A drop-down menu lets you choose the language that will be displayed to the user.*
*Please note that the users will still be able to select their language during the verification procedure.
Require UBO/Shareholder info makes the specified fields obligatory. These can be filled either manually by the applicant or by the UBO/shareholder/representative via a link that has been sent by email.
UBOs/Shareholders/Representatives - required fields to be filled.
The Skip emails screen allows the applicant to mandate all the filling in of information to the UBOs/Shareholders/Representatives themselves.
Link lifetime (in sec.) - the period over which the link sent to a UBO/shareholder/representative is valid.
Allow editing of approved payment methods allows one to change the required payment method data.
Disable an option to add other payments leaves only one payment method to be verified at the specific level.
Hide payment method type selectors disables the selection of the payment method for the applicant.
Respect applicant level lets you initialize the flow within an existing or new applicant level.
On the right-hand side of the tab, you’ll be able to assign an applicant level for specific customization to see previews of the screens that you are customizing.
All your existing customizations can be accessed from the “Customizations” tab of the “Integrations” section of your dashboard. You can edit, delete, clone, and import/export customizations (as a code from the clipboard).
Please make sure that you don't delete any applicant levels or customizations that are currently in use as this will impact your entire integration.