If your customer has already completed KYC with another Sumsub client, you don’t have to make them go through verification again. Dakota supports Sumsub’s Reusable KYC flow: the Sumsub client that originally verified the customer (the donor) generates a single-use share token, hands it to you, and you redeem it on Dakota to create a customer and individual application pre-filled with the customer’s identity data and documents. This page covers how the flow works and the one-time setup between the donor and Dakota. Once that’s in place, Importing Sumsub Tokens covers generating and redeeming tokens.

​

How It Works

The share token flow has three parties:

• Donor — the Sumsub client that originally verified the customer. They generate the share token, scoped to Dakota’s Sumsub clientId (dakota.xyz_158913).
• Dakota — the recipient. You redeem the token on Dakota’s side, which creates a fresh applicant on Dakota’s Sumsub account with the donor’s data copied over.
• Sumsub — handles the transfer of identity data and documents between the donor’s account and Dakota’s account.

Tokens are single-use and have a default TTL of 1200 seconds (20 minutes). Once redeemed, the token is consumed and cannot be reused.

​

Before You Start: Establish the Sharing Relationship

Three things must be in place before a share token can be generated. The first two are entirely on your side; the third is an exchange between you and Dakota, carried out in each party’s own Sumsub Dashboard.

​

1. Reusable KYC, enabled on the verification level

Reusable KYC is switched on per verification level, not once for the account. A level that doesn’t have it cannot produce a share token, even if the feature is enabled for your organization. Enable it on the level your applicant was verified at, then generate a token. Sumsub’s Reusable KYC Share documentation covers the dashboard configuration — follow it rather than us, since it stays current with their interface.

​

Your level doesn’t have to match ours

The levelName used at redemption is the recipient’s level — Dakota’s. You don’t configure it and it doesn’t have to match yours by name. What does matter is that the two levels share verification steps. Sumsub compares the steps your level collected against the steps ours requires: In practice, Dakota’s level expects an identity document and a proof of address. A donor level that captured only an identity document still imports successfully — the customer is simply asked for the proof of address before the application can be submitted. See Things to Know.

​

2. The “Share applicants data” permission

Sumsub’s share-token endpoint requires a specific dashboard permission:

“This method requires the Share applicants data dashboard permission. App tokens and team members must have a role that includes this permission; otherwise, the request fails with a permission error.” — Generate share token

If your token-generation call fails with a permission error, check the role attached to the app token you are signing the request with.

​

3. Add Dakota as a recipient using a partner token

Before any share token can be generated, you must add Dakota to your sharing partners in Sumsub. This requires a partner token, which is a different thing from the share tokens you will generate later — and it comes from Dakota, not from Sumsub. How the exchange works, per Sumsub’s Partner management documentation: On your side the steps are:

1. In the Sumsub Dashboard, open the Reusable identity section and go to the Partners page.
2. Select the Recipients tab and click Add recipient.
3. Paste the partner token Dakota gave you.
4. Confirm that you want to add Dakota as a recipient.

Once Dakota appears in your Recipients list, you can generate share tokens with forClientId: dakota.xyz_158913 as described in Importing Sumsub Tokens. Sumsub’s own references for this setup:

• Partner management — adding donors and recipients, and the partner token exchange
• Reusable KYC — overview of the feature and its prerequisites
• Reusable KYC Share — the donor-recipient relationship and the full token lifecycle

Once Sumsub confirms the relationship is active, continue to Importing Sumsub Tokens.

​

Next

Once the sharing relationship is in place, continue to Importing Sumsub Tokens — generating share tokens, redeeming them, and completing the application.