Skip to main content

​
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 verifies that shared applicant data and returns the decision via the same USER_APPLICATION_STATUS_UPDATED webhook as Managed KYC. This is offered alongside 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.

​
Prerequisites

Before you can share tokens with Reap, one-time setup on both sides needs to be in place. Your Reap account manager will guide you through the Reap-side steps.
1

Sign Sumsub's Reusable KYC Agreement

This authorises your company as a donor of KYC data and Reap as the recipient.
2

Add Reap as a recipient inside your Sumsub account

Use the setup token your Reap account manager will provide. Sumsub’s partner setup guide covers the exact steps.
3

Align applicant levels in Sumsub

Import or configure the applicant levels Reap expects for your program so share tokens are minted at a compatible level. A level mismatch returns SUMSUB_TOKEN_LEVEL_MISMATCH on ingest.
Until this Sumsub-side configuration is complete, token imports will fail regardless of how the API 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 with the SUMSUB_TOKEN_SHARING method and the share token. A successful ingest returns IN_REVIEW; wait for the USER_APPLICATION_STATUS_UPDATED webhook for the final decision. A failed import (for example, an expired token) leaves the user at NOT_STARTED or RETRY_REQUIRED and returns an error you can act on. You can retry by minting a fresh token and calling again. An applicant that is approved in your Sumsub but missing identity fields returns SUMSUB_APPLICANT_INCOMPLETE. See Constraints for what is required. Complete those fields on the applicant. Then mint a new share token and import again.

​
How statuses update

The contract matches Managed KYC:
  • A successful submission transitions the user to IN_REVIEW.
  • Reap emits USER_APPLICATION_STATUS_UPDATED when the review completes (APPROVED, REJECTED, or RETRY_REQUIRED).
  • Your existing webhook handler picks it up. No new event type and no new payload to integrate.
See 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.
  • The applicant must include the identity fields Reap needs to issue a card. Required fields are name and date of birth, plus identity document type/number and a residential address (line1 and country). Missing any of those returns SUMSUB_APPLICANT_INCOMPLETE.
The Reusable KYC Agreement, Sumsub partner setup (including adding Reap as a recipient and aligning applicant levels), and Reap program enablement are hard prerequisites. Token imports will fail until all are in place.

​
Get started

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

Walk through the Sumsub agreement, donor setup, and applicant levels

Complete the Sumsub-side configuration: sign the Reusable KYC Agreement, add Reap as a sharing recipient, and import or align the applicant levels for your program.
2

Get Token Sharing enabled on your Reap account

Reap enables the method on your program once Sumsub configuration is confirmed.
Once enabled, the integration follows the flow above.