Sumsub ID Connect – Partner sharing
Streamline multi-partner KYC with Sumsub ID Connect.
Sumsub ID Connect also supports multi-party verification flows with a partner sharing integration. In this model, the integrating partner (the intermediary) triggers instant verification for a downstream party (the final verifier) while the Intermediary does not process or store the applicant documents or biometric data.
How partner sharing with Sumsub ID Connect works
The partner sharing flow consists of three main steps:
- The Intermediary establishes a connection using Sumsub ID Connect and requests the
sharescope to obtain the applicant’s permission for sharing verified data. - After establishing the connection, the Intermediary service generates a Sumsub ID share token and sends it to the downstream partner.
- The downstream partner passes the Sumsub ID share token to the Sumsub SDK and runs a fast verification based on the applicant’s existing Sumsub ID data.
When an applicant needs to verify with a partner, they can reuse documents from their connected Sumsub ID and prove ownership with a quick selfie. This approach removes manual document uploads and still supports fully compliant KYC, as all checks run according to the partner’s configuration.
Note
For more details on Sumsub ID supported verification flows, see this article.
Establish connection
The business integrates Sumsub ID Connect as described here, so that users can link their service account to a Sumsub ID account.
During this integration, the business includes the share scope. This scope adds a specific permission to the authorization screen that allows the service to generate a Sumsub ID share token.
The authorisation screen will look like this:
Generate Sumsub ID share token
After the service obtains the share scope, it can generate a Sumsub ID Share Token. To do so, use this API method.
Request example:
curl -X POST \
'https://api.sumsub.com/resources/accessTokens/sumsubIdShareToken' \
-H 'content-type: application/json' \
-d '{
"sumsubIdConnectToken": "snd-id-con-a-WRT7FRBRfdejpsDR8a_cYeX9BU32QP_I_Hyc93saZcg5965PfGzrHGDEdrTRseop",
"forClientId": "CoolCompanyLtd",
"ttlInSecs": "1800"
}'
The service then sends this Sumsub ID share token to the partner, who uses it to run a faster verification.
Setup for partners
Partners have to complete the following one-time steps to start getting the improved verification flow:
- Get a client key (client ID) to use Sumsub services.
- Ask Sumsub support to enable Sumsub ID Connect for your client key.
- Add the integrating business to the Donors list. For more information on how to do so, see this article.
After that, when the partner receives the Sumsub share token, they can include it when generating an access token to initialize the WebSDK. It automatically triggers the Sumsub ID reuse flow.
Request example:
curl --request POST \
--url https://api.sumsub.com/resources/accessTokens/sdk \
--header 'content-type: application/json' \
--data '
{
"applicantIdentifiers": {
"email": "[email protected]",
"phone": "555-1111"
},
"ttlInSecs": 600,
"sumsubIdShareToken":"eyJhbGciOiJub25lIn0.eyJqdGkiOiJfYWN0LTZmODI2ZTU0LTE2MzctNDViMS05NzMyLWY1MjZiN2YxNWE3YyIsInVybCI6Imh0dHBzOi8vYXBpLnN1bXN1Yi5jb20ifQ",
"userId": "johndoeID",
"levelName": "basic-kyc-level"
}
'
Updated about 3 hours ago