Businesses integrating multiple partners that require KYC verifications can enhance their user experience with Sumsub ID Connect. This solution enables these businesses to link user accounts to Sumsub ID, which facilitates seamless, fast KYC processes across all their partners — without repeated document uploads. Users of the integrating business can do a quick, one-time connection between their service account and Sumsub ID, and from then on will get radically improved verification experience with the service’s partner platforms.

How Sumsub ID Connect works

To enable this streamlined experience, Sumsub ID Connect relies on secure token exchanges that facilitate safe and efficient data sharing between services and their partners.

Authorization code. A short-lived code that is received on the frontend after user authorization and follows standard OAUTH protocol.
Sumsub ID Connect token. A long-lived token that can be used at any point for generating a Sumsub ID share token. This token is obtained by exchanging the authorization code.
Sumsub ID share token. A short-lived token that can be used to trigger the fast KYC flow for partners. This token includes various security mechanisms like a shorter TTL (time-to-live), is one-time use only, and is partner-bound.
Access token. Using the Sumsub SDK always requires an access token. This access token can be easily enriched with a Sumsub ID Share Token at the point it is generated by the partner, which will then trigger the Sumsub ID enabled fast KYC flow.

With Sumsub ID Connect, the process includes two main stages:

Establishing the connection.
Performing fast KYC with partners.

Connection

The service embeds a Sumsub ID Connect button natively, which launches a simple flow for the user to link their service account with a Sumsub ID account. This connection is a one-time action. Once the user grants permission, the service stores an anonymized, persistent reference to the user’s Sumsub ID account, known as the Sumsub ID Connect token.

The Connection flow includes the following steps for the end-user:

After clicking the Connect Sumsub ID button, the user is prompted to enter their email address.
To continue, the user has to enter the verification code that is sent to the provided email address.
To complete the process, the user has to give permission to connect the service account (Service A) to the Sumsub ID account by clicking Allow connection.

If the user does not yet have a Sumsub ID account, the flow includes an additional step where the user can create an account:

After entering an email address and a verification code, the user will see the account creation screen.
The user clicks Create account to proceed to the permission step.

Fast KYC with partners

When a user navigates to a partner platform that requires KYC, the service sends a Sumsub ID share token to the partner. The partner includes this token when initializing the Sumsub SDK. This automatically launches an optimized KYC process that leverages the user’s connected Sumsub ID, enabling faster and more seamless verification.

Once verification process begins, the user flow includes the following steps:

Select the documents to share from the previously stored ones in the connected Sumsub ID account (no authentication required).
To share the selected documents, users will have to pass a Liveness check for security purposes.
Documents shared will be automatically submitted for relevant checks. No uploads are required.

Sumsub ID Connect setup

To start using Sumsub ID Connect, you will need to have a client key (client ID) enabled for this integration. Please contact us to enable this for your key. Once enabled, follow the technical documentation available here to complete your integration.

The integration process consists of two stages.

The first stage involves establishing the connection, which consists of the following steps:

Service A integrates the default or custom Sumsub ID Connect button into your service.
Service A captures the authorization code and exchanges it for a Sumsub ID Connect token.
Service A stores the Sumsub ID Connect token securely for each user account.

At the second stage, fast KYC with partners is performed. This stage consists of the following steps:

Service A converts the Sumsub ID Connect token into a Sumsub ID share token.
Service A passes the Sumsub ID share token to the partner platform.
The partner service includes the Sumsub ID share token when generating an access token for the Sumsub SDK, enabling the fast KYC flow.