Sumsub KYC Sharing

Use this flow to migrate users you've already verified in your own SumSub account to Reap — without re-verifying them. You generate share tokens for each applicant, compile them into a CSV, and upload the batch to Reap.


1. Prerequisites

Before you begin, please complete the following one-time setup steps with Sumsub and Reap:

  1. Sign the Sumsub Reusable KYC Agreement

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

  2. Add Reap as a Recipient

    After signing the agreement, use the token provided by your Reap Account Manager to add us as an authorized recipient within your Sumsub account.

    (Refer to Sumsub’s documentation on how to set up Partners for exact steps.)


2. Prepare Your Applicant List

  1. In your Sumsub dashboard, filter and export the list of applicants you want to share with Reap.

  2. The CSV must include at least the following columns:

    externalId, applicantId
    

Note:

• Maximum 5,000 rows per file

• File size ≤ 10 MB

• Must be UTF-8 encoded and include a header row


3. Generate Share Tokens

We provide an open-source Python CLI tool to generate share tokens for each applicant.

kyc-share-token - Generates share tokens from Sumsub applicant IDs with automatic rate limiting, retry logic, and resume functionality. The output CSV is ready for batch upload.

See the repository documentation for installation and usage instructions.

  • Input: Your exported CSV from Sumsub

  • Output: A new CSV with the columns below:

    externalId, shareToken
    

The script automatically handles rate-limiting and retries.

Once generated, this final CSV is ready to share with Reap.

Note: Share tokens are single-use and expire after 1,200 seconds (20 minutes). Generate them shortly before uploading.


4. Batch upload the applicants and tokens data

Upload the generated CSV to the integration endpoint below

POST /entity/kyc/import/batch

Processing Time:

Uploads begin processing within ~10 minutes and typically complete in 2–10 minutes per 1,000 records.

Tip: The API supports idempotency — duplicate uploads with the same key are safely ignored, so you can retry failed uploads without creating duplicates.


5. Support

For any setup or upload issues, please contact your Reap Implementation Manager