cReusable KYC Share lets you securely transfer and reuse applicant verification data from trusted partners. This helps you onboard users without asking them to upload documents or pass the same checks again.

After the client authorizes data sharing, the parties establish a donor-recipient relationship. Clients can configure multiple sharing partners in the Dashboard. Reusable KYC Share also supports bidirectional data sharing.

When the recipient reuses applicant's data, Sumsub runs fresh checks against the recipient’s level settings to make sure the reused data meets their compliance requirements.

How Reusable KYC Share works

Reusable KYC Share uses a share token to transfer verified applicant's data from the donor to the recipient.

The flow includes the following steps:

1. Donor generates a share token for a verified applicant and sends it to the recipient.
2. Recipient uses the share token to reuse applicant profile.
3. Sumsub maps verification requirements between the donor and recipient's profiles and transfers only the matching data intersection.
4. Sumsub runs fresh checks against the recipient’s level settings.
5. Sumsub assigns the applicant status on the recipient side based on the reuse result and request parameters.

For example, Sumsub can check whether the reused identity document:

• Has an accepted document type.
• Was issued by an accepted country.
• Meets age requirements.
• Has not expired.

These checks help the recipient treat the reused verification as a fresh KYC verification.

Step matching and data transfer

Sumsub transfers data only for verification steps that overlap between the donor and recipient levels.

For each matching step, Sumsub can transfer the following data:

If the donor and recipient levels do not have matching verification steps, Sumsub does not create an applicant profile on the recipient side and returns a reuse error.

Reuse outcomes

Depending on the donor data and the recipient level configuration, the reuse attempt can result in one of the following outcomes.

Request parameters

When the recipient uses this API method, they can control how Sumsub processes reused applicant data with the following request body parameters.

Share checks

After Sumsub transfers matching data, it generates a Reusable KYC Report with fresh verification timestamps.

The Report includes the results of fresh share checks and transferred data.

Use this API method to get the Reusable KYC Report. Request example:

curl -X GET \
     'https://api.sumsub.com/api/reusableIdentity/69ce35c7b776d140bb500000/reports?levelName=basic-kyc-level' \
     -H 'Authorization: Bearer token' \
     -H 'Content-Type: application/json' \
     -H 'X-App-Token: <your-app-token>' \
     -H 'X-App-Access-Sig: <your-signature>' \
     -H 'X-App-Access-Ts: <unix-timestamp>'

Reuse of specific level steps

In addition to documents and verification results, Sumsub can reuse specific applicant data objects from the donor profile. This includes face match and liveness, confirmed email and phone verification results, standard applicant profile fields, and questionnaire data.

Sumsub transfers these level steps to the recipient profile when the donor and recipient configurations support the same data structure or verification step. Some level steps, such as email and phone verification, can be reused without asking the applicant to complete the same check again.

Email and phone

If the donor applicant passed email or phone verification, Sumsub transfers these values and their confirmation results to the recipient profile.

The recipient applicant receives the confirmed email or phone status without passing OTP verification again.

Applicant data

Sumsub transfers text attributes and core profile data from the donor profile without running OCR again on the recipient side.

Questionnaires

Sumsub can transfer individual questionnaire answers to the recipient profile if the donor and recipient questionnaires have matching structure and response options.

For successful mapping, the following properties must match exactly:

• Question and section IDs. The question IDs must be identical in both questionnaire configurations.
• Response options. The applicant’s answer on the donor side must match one of the predefined options on the recipient side.

To align questionnaire structures, use the following export and import options in the Dashboard.

Export questionnaire on donor side

The following steps describe how to align the questionnaires on the donor side:

1. In the Dashboard, open Integrations and go to the Questionnaires section.
2. Find the questionnaire that you want to reuse.
3. Open the actions menu on the right and click Export.
4. Save the exported questionnaire data by clicking the Copy to clipboard button in the pop-up window.
5. Send the export to the recipient.

Import questionnaire on recipient side

The following steps describe how to align the questionnaires on the recipient side:

1. In the Dashboard open Integrations and go to the Questionnaires section.
2. Click Import questionnaire.
3. Paste the questionnaire data you received previously and click the Create questionnaire button.
4. Add the imported questionnaire to the relevant verification level. For more instructions, see this article.

Once these steps are completed, the donor and recipient questionnaires will contain the same data.

Workflow Builder

Reusable KYC Share supports multi-stage document and data reuse across custom levels configured in Workflow Builder.

As the applicant moves through the workflow, Sumsub does the following:

• Re-evaluates step matching at each stage and carries forward matching data.
• Generates Reusable KYC Share Report at each workflow level.

AML screening handling

Reusable KYC Share handles AML screening differently depending on the preserveVerificationStatus value.

Enable Reusable KYC Share

The following is a sequence of steps to be taken to turn on the data-sharing functionality.

Step 1: Generate share token

The donor generates a temporary share token for a verified applicant. To generate a share token, use this API method:

Request example:

curl --request POST \
     --url https://api.sumsub.com/resources/accessTokens/shareToken \
     --header 'content-type: application/json' \
     --data '{
        "applicantId": "63e092c51b7b4030f2e01154",
        "forClientId": "CoolCoinLtd",
        "ttlInSecs": 600
     }'

Request body parameters:

Response

A new share token is returned.

{
  "token": "eyJhbGciOiJub25lIn0.eyJqdGkiOiJfYWN0LTZmODI2ZTU0LTE2MzctNDViMS05NzMyLWY1MjZiN2YxNWE3YyIsInVybCI6Imh0dHA6Ly9hcGkuc3Vtc3ViLmNvbSJ9.",
  "forClientId": "CoolCoinLtd"
}

The donor must send a new share token to the recipient to proceed with the reuse flow.

Step 2: Reuse applicant data

The recipient sends the share token to Sumsub to create a reused applicant profile and run background checks using this API method.

Request example:

curl 'http://localhost:8080/resources/api/reusableIdentity/reuse?shareToken=_act-snsId-56e87868-e249-43eb-98ce-30fd116b196d&levelName=selfie-id-otps' \
--header 'Content-Type: application/json' \
--data '{
    "requireFreshSelfie": false,
    "preservedVerificationStatus": false
}'

Request parameters:

Response example:

{
  "id": "689223ed75b5d1bc2bb38gdg",
  "createdAt": "2026-07-08 21:28:40",
  "key": "UUBSGJZXJDFXXW",
  "clientId": "RecipientCompany",
  "status": "init"
}

Track share token consumption

Donors can track applicant share token processing by configuring the following webhooks in the Dashboard.

Test Reusable KYC Share

You can test Reusable KYC Share in Sandbox without a legal agreement. For testing purposes, the same Sandbox client key can act as both the donor and the recipient.

Step 1: Configure Sandbox verification preset

Create a verification preset and apply it to the required verification level:

1. Switch to the Sandbox in the Dashboard.
2. Navigate to the Sandbox mode for verification testing page.
3. Click on an existing preset or select Create new verification preset.
4. Adjust the preset settings:
   1. Select the Automated applicant review option.
   2. From the Face match drop-down list, select Always approve.
   3. Check the Enable Reusable KYC box.

      📘

      Note

      If you use a verification preset, you must enable Reusable KYC in the preset settings. Otherwise, Reusable KYC will not work for the level where this preset is applied.

      If no preset is applied, Reusable KYC can still work when you pass a valid share token. However, in this case, Face match returns RED by default. To avoid this during testing, use a preset with Face match set to Always approve.

5. Save the preset.
6. Apply the preset to the relevant verification level.

Step 2: Run reuse flow

1. Create an applicant in Sandbox using the selected verification level.
2. Make sure the applicant receives the Approved status.
3. Generate a share token for the applicant using one of the following options:
   1. Use this API method. Make sure to include an app token configured for the Sandbox environment in the request.
   2. In the Dashboard, go to the Applicants page and select the applicant of interest. In the drop-down menu on the top of the page, click Generate share token.
4. Use this API method and include an app token configured for the Sandbox environment in the request.
   
   Request example:
   cURL

    curl -X POST \
         'https://api.sumsub.com/resources/api/reusableIdentity/reuse?shareToken=_act-jwt-eyJhbGciOiJub25lIn0.eyJqdGkiOiJfYWN0LTE3YjM5YTljLWRhOWUtNGY2MS04Y2ZjLTYwNzViNWM2NDk5MSIsInVybCI6Imh0dHA6Ly9sb2NhbGhvc3Q6ODA5MCJ9.&levelName=liveness-id-poa' \
         -H 'X-App-Token: <your-app-token>' \
         -H 'X-App-Access-Sig: <your-signature>' \
         -H 'X-App-Access-Ts: <unix-timestamp>'

This triggers the Reusable KYC Share flow and creates a new reused applicant profile instantly.