Skip to main content
Share verified customer KYC data from partner platforms to streamline onboarding and eliminate duplicate verification processes.

Overview

Token sharing enables seamless customer onboarding by accepting pre-verified KYC data from partner platforms through Sumsub. When a customer is already verified on a partner platform, you can import their verification data instead of requiring them to complete KYC again. How it works:
  1. Customer completes KYC verification on partner platform
  2. Partner generates a Sumsub token containing the customer’s verified data
  3. Partner calls Busha’s token-share endpoint with the token
  4. Busha imports the verified KYC data
  5. Customer is instantly verified without re-uploading documents

Prerequisites

  • A Busha Business Account and Secret API Key (from the Quick Start Guide)
  • Active Sumsub account with verified applicant
  • Busha’s Client ID
  • Sumsub API credentials

Setup

Add Busha as Recipient

The Reusable KYC feature must be enabled on your Sumsub account before you can share tokens. Contact your Sumsub Customer Success Manager (CSM) to enable this feature if it is not already active.
Before sharing tokens, add Busha as a trusted recipient in your Sumsub dashboard:
  1. Contact Busha support at eng@busha.co to receive a recipient token
  2. Log into your Sumsub dashboard → Reusable Identity → Partners
  3. Add Busha using the recipient token

Generate Sumsub Token

Before sharing customer data with Busha, generate a share token from Sumsub. This token securely encapsulates the customer’s verified KYC data. Refer to Sumsub’s Generate Share Token documentation for complete details on token generation.

Request

Parameters:
Authentication: You’ll need your Sumsub API credentials (App Token and Secret Key). See Sumsub’s authentication guide for authentication requirements.Busha’s Client ID: Contact Busha support at eng@busha.co to receive Busha’s forClientId for token generation.

Response

Save the token value for the next step.
Token Expiry: Tokens expire based on ttlInSecs. Use the token immediately after generation.One-Time Use: Each share token can only be used once. Generate a new token for each customer share.Token Format: Treat the token as an opaque string. Do not parse or validate its contents, as the format may change.

Share Token with Busha

Once you have the Sumsub token, share it with Busha to import the customer’s verified data.

Create Customer in Busha

First, create a customer record in Busha:
Response:
Save the id for the next step.

Share the Token

Call Busha’s token-share endpoint with the Sumsub token:
Path Parameters: Body Parameters: Response:

Verify Import

Check that the customer’s verification status was updated:
The customer should now have updated status and level fields reflecting the imported KYC data.

Integration Example

What’s Next?

Now that you understand token sharing, you can explore related customer management topics: