> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reap.global/llms.txt
> Use this file to discover all available pages before exploring further.

# Sumsub Token Sharing

> Reuse identity verifications you have already completed in your own Sumsub account, instead of asking your users to re-verify on Reap.

## Overview

If you already operate your own Sumsub account and have a verified user base, you do not have to put those users through KYC again when you onboard them to Reap.

Sumsub's Token Sharing feature lets you hand Reap a per-user share token from your Sumsub account. Reap imports the existing verification and the user becomes `APPROVED` on Reap without going through the Sumsub SDK a second time.

This is offered alongside [Managed KYC](/compliance/kyc/managed-kyc), where Reap runs the verification. Use this guide if your product runs Sumsub KYC under your own account by design and you want Reap to consume those verifications.

<Note>
  Token Sharing is a data import, not a re-verification. Reap does not re-screen the user. There is no `IN_REVIEW` step. A successful import moves the user straight to `APPROVED`.
</Note>

***

## Prerequisites

Before you can share tokens with Reap, two one-time steps need to be in place. Your Reap account manager will guide you through both.

<Steps>
  <Step title="Sign Sumsub's Reusable KYC Agreement">
    This authorises your company as a donor of KYC data and Reap as the recipient.
  </Step>

  <Step title="Add Reap as a recipient inside your Sumsub account">
    Use the setup token your Reap account manager will provide. Sumsub's [partner setup guide](https://docs.sumsub.com/docs/manage-sharing-partners) covers the exact steps.
  </Step>
</Steps>

Until both are done, token imports will fail regardless of how the request is made.

***

## How it works

You mint a fresh share token in your Sumsub immediately before the call, then hand it to Reap by [advancing the user's application](/api-reference/users/advance-the-user-application) with the `SUMSUB_TOKEN_SHARING` method and the share token. You get an immediate success or failure response.

```mermaid theme={null}
sequenceDiagram
    participant BE as Your backend
    participant Sumsub as Your Sumsub account
    participant Reap as Reap API

    BE->>Reap: Create user
    Reap-->>BE: userId
    BE->>Sumsub: Mint share token for this applicant
    Sumsub-->>BE: shareToken
    BE->>Reap: Import share token (userId + shareToken)
    Reap-->>BE: Success
    Reap-->>BE: USER_APPLICATION_STATUS_UPDATED (status: APPROVED)
```

A failed import (for example, an expired token) leaves the user at `NOT_STARTED` and returns an error you can act on. You can retry by minting a fresh token and calling again.

***

## How statuses update

The contract is the same as [Managed KYC](/compliance/kyc/managed-kyc):

* A successful import transitions the user to `APPROVED`.
* Reap emits a `USER_APPLICATION_STATUS_UPDATED` event for that user.
* Your existing webhook handler picks it up. No new event type and no new payload to integrate.

See [Application statuses](/compliance/kyc/overview#application-statuses) for the full status model.

***

## Constraints

A few things are worth knowing up front because they affect how you build around the feature.

* **Share tokens are valid for 20 minutes.** Mint the token immediately before the import call.
* **Rate limited.** Reap accepts up to 3 imports per second per business. If you create users faster than that, you'll get rate limit errors.
* **Each import targets one Reap user.** You pass the Reap `userId` with the share token, and Reap attaches the imported verification to that user. Mint the share token for the Sumsub applicant that corresponds to that user.
* **Token Sharing assumes the user is already approved in your Sumsub.** Only share tokens for users who have completed KYC successfully on your side. Sharing tokens for in-review or rejected users is not supported.

<Warning>
  The Reusable KYC Agreement and partner setup with Sumsub are hard prerequisites. Token imports will fail until both are in place.
</Warning>

***

## Get started

Sumsub Token Sharing is enabled per program. Talk to your Reap account manager to:

<Steps>
  <Step title="Walk through the Sumsub agreement and partner setup" />

  <Step title="Get access enabled on your account" />
</Steps>

Once enabled, the integration follows the flow above.