Third-party Verification-Sumsub
Last updated
Last updated
Using Sumsub verification, user information will be submitted to the third party, which will perform KYC/AML checks and feedback the verification results to the exchange. The exchange can only get the verification results. The administrator needs to check the user information submitted on the Sumsub platform. If manual processing is required, it also needs to be done on the Sumsub platform.
Please ensure that all parameter configuration and application of Sumsub are in the production environment and do not use the test environment to apply. Green represents the production environment and yellow represents the sandbox (test) environment.
You need to create the APP Token and Secret Key in the Sumsub backend and configure it to the exchange backend.
a. Visit the following URL (https://cockpit.sumsub.com/checkus#/devSpace/appTokens) to enter the creation page:
b. Click the "Generate app token" button to enter the creation page:
You can define an application name and a whitelist address (after configuration, only the whitelist can access the corresponding interface. If not configured, there will be no restriction). All permission selections can be kept as default and do not change.
After clicking "Generate app token", the Token and Secret Key will be automatically generated. Remember, you need to save the Token and Secret Key. After clicking the confirmation button, the Secret Key cannot be viewed again.
Token and Secret Key will be configured in the spot backend, as shown in the figure below:
You need to create a verification level in the Sumsub backend and define the verification conditions for this level. When adding a verification level on the exchange later, it needs to be associated with the Sumsub verification level.
a. Visit the following URL (https://cockpit.sumsub.com/checkus#/sdkIntegrations/levels/individual) to enter the verification level page, and click the "Create Level" button, as shown in the figure below:
b. You can customize the level name and set verification requirements. As for the SDK settings, you need to create the SDK before making associated settings.
Note: The level name of Sumsub cannot contain spaces (wrong format "level 1", correct format: "level1", "level-1", "level_1").
You need to create Web SDK and APP SDK in the Sumsub backend, and define the KYC interface style and interaction at Web/APP. When users initiate a KYC application, they will see the page style you configured.
a. Visit the following URL (https://cockpit.sumsub.com/checkus#/sdkIntegrations/customizations/appearances) to enter the creation page, click the "Create customization" button, and select "Old customization", as shown in the figure below:
b. You can customize the name and type of the SDK. Note that a verification level requires creating Web SDK and APP SDK separately.
c. You can view the SDK you just created in the list
d. When setting the verification level, you need to select the corresponding SDK. In this way, when users perform Sumsub KYC verification, the system will display the verification requirements corresponding to that level and enter the corresponding verification process.
You need to create a Webhook in the Sumsub backend. Without configuration, the exchange cannot obtain the user's verification status.
a. Visit the following URL (https://cockpit.sumsub.com/checkus#/devSpace/webhooks/webhookManager) to enter the creation page and click the "Create webhook" button, as shown in the figure below:
b. Fill in the corresponding content as needed, and click the "Create webhook" button after completing the filling.
Name: customized by the administrator;
Webhook receiver: Select HTTP address, the configuration content is: https://www.xxx.com/fe-ex-api/sumsub/webhook_info, where www.xxx.com is the domain name of the exchange.
Webhook types: Select “Applicant Received”;
If the user's identity information has completed Sumsub KYC verification, Sumsub does not support repeated verification by default. If the administrator has enabled the multi-site function or requires repeated verification, additional settings are required.
To ensure that the function can be used normally after switching to Sumsub KYC, the system restriction must first add a Sumsub type verification level. Click the [Add] button, as shown below:
You can set the verification requirements and rights for the level, as shown in the figure below:
Field description:
Level name: the level name displayed on the client, supports multiple languages;
Verification type: Currently only supports Sumsub;
Sumsub Level Name: The name of the verification level set by the administrator in the Sumsub backend. The setting here is the relationship between the exchange verification level and the Sumsub verification level. The Level name cannot be added repeatedly;
Requirements: The administrator selects the verification information that the user needs to prepare in the background, which is only used for display on the client KYC verification page. In fact, the information actually needed for user verification is determined by the Sumsub background configuration;
Benefits: There are currently four types of benefits
Withdrawals, including:
Limit: Users are prompted to undergo identity verification when withdrawing money, and the withdrawal function is prohibited.
Unlimit: Users can withdraw normally (original logic),
Amount that can be withdrawn: the cumulative withdrawal amount by a single user in the last 24 hours. If the user makes a withdrawal within 24 hours, the exchange rate of USDT in that token needs to be converted according to the withdrawal initiation time, and deducted from the total amount. The total amount includes Normal Withdraw (on-chain) + Internal Transfer. If the withdrawal time exceeds 24 hours, the corresponding amount will be restored. This amount will be displayed on the user's withdrawal page.
Deposit, including:
Limit: The deposit coin and address are not displayed when the user deposits, prompting that identity verification is required, and the deposit function is prohibited.
Unlimit: Users can deposit normally (original logic)
P2P Trading, including:
Limit: When the user clicks the [Buy/Sell] button on the P2P trading page, the system prompts that identity verification is required and the P2P trading function is prohibited.
Unlimit: Users can use P2P trading normally (original logic)
Sort: This sorting will affect the verification level display on the user page and the management background at the same time. The smaller serial number is displayed in the front; among them, [Unverified] is fixedly displayed in the first row, and [Verified] is fixedly displayed in the second row. Sorting It is only valid for the remaining newly added verification levels.
Click the [Setup] button to switch to "Sumsub Verification", where you fill in the APP Token and Secret Key created on the Sumsub platform, as shown in the figure below:
Note: After switching the verification type, the verified user needs to re-use the new verification method for verification. After switching back, the user can restore the original verification level;
You can view the KYC application records submitted by users and view the audit results returned by Sumsub. If you want to see specific information, you need to jump to the Sumsub platform to view it.
Users can view the benefits and requirements of each level in the personal center and complete identity verification, as shown in the figure below:
If there is no deposit or withdrawal permission, the page will guide the user to identity verification, as shown in the figure below:
Users can view the benefits and requirements of each level in the personal center and complete identity verification. If there is no deposit or withdrawal permission, the page will guide the user to identity verification, as shown in the figure below: