Skip to main content
Eligibility Notice This feature is available exclusively to Fintech platform clients that conduct KYC/KYB verification through Sumsub. To enable Sumsub token sharing for your account, please reach out to your Customer Success Manager (CSM)

​
The Core Concept

Tazapay supports reusable KYC/KYB, allowing platforms to share pre-verified applicant data via API. If your platform already conducts KYC/KYB verification through Sumsub, this enables Tazapay to reuse that data — removing the need for end-users to re-verify or re-upload documents.

​
Understanding the Two Tokens

​
How the Live Flow Works

Once the one-time setup is complete and your integration is live, each applicant flows through these steps:
  1. Your platform (the ‘Donor’) generates a shareToken for a verified Sumsub applicant.
  2. The token is passed to Tazapay (the ‘Recipient’) in the onboarding_package_url field of the Create Entity API.
  3. Tazapay retrieves the applicant’s documents and information from Sumsub and runs its own verification checks.
  4. The entity state management is based on what was retrieved:
    • If all required information and documents are available (from the Sumsub profile plus what you passed in the Entity API call), the entity is updated with all mandatory and other relevant information and moved to the submitted or approved state — both states can transact.
    • If required information is missing, the entity remains in the in_draft state. Provide the missing information or documents via the dashboard or API and submit the entity to complete onboarding.

​
Section A: Ops/Admin Setup (4 Steps)

  1. Enable Reusable KYC on Sumsub — Contact your Sumsub CSM to get your account enabled as a “Donor.” Sumsub requires a signed sharing agreement.
  2. Contact Tazapay CSM — Request enablement of Sumsub Reusable KYC. Tazapay will: accept your platform as a Donor, give you a one-time partner token, and share their Sumsub forClientId.
  3. Add Tazapay as a Recipient on your Sumsub dashboard — Go to Reusable Identity → Partners → Recipients, click ”+ Add recipient,” paste Tazapay’s partner token, and click Done.
  4. Verify the partnership — Confirm the partnership is active on both sides: Tazapay shows up as a Recipient on your dashboard, and your platform shows up as a Donor on Tazapay’s. You also need the forClientId in hand.

​
Section B: Developer Integration (2 API Steps)

Step 1 — Generate a Share Token (Sumsub API) Call POST https://api.sumsub.com/resources/accessTokens/shareToken with:
  • applicantId: the Sumsub ID of the verified user on your platform
  • forClientId: Tazapay’s Sumsub Client ID
The response gives you a JWT-style token — this is the shareToken.
Recommended: Set ttlInSecs to 86400 (1 day) when generating the share token. This gives Tazapay sufficient time to consume the token without it expiring prematurely.
Step 2 — Pass the Share Token to Tazapay (Entity API) Send the token in the onboarding_package_url field when calling the Create Entity API — POST /v3/entity. Works for both individual and business entity types.
Sandbox support: Reusable KYC/KYB is also available in the sandbox environment, so you can test the full token-sharing flow end-to-end before going live.

​
Required Data Points for Automatic Submission

For an entity to be moved to a submitted or approved state automatically, Tazapay must be able to assemble the following data points — either from your Create Entity API call or from the shared Sumsub profile. A few fields must always be passed directly in the Entity API call — they are platform-specific context that a Sumsub profile does not carry. All other data points can come from either source.
Data priority: If the same data point is available from both sources, the data passed directly to Tazapay in the Entity API call takes priority over the data retrieved from Sumsub.

​
Individual Entities

​
Business Entities

Business representatives: If the Sumsub company profile has representatives (e.g. directors, UBOs) linked to it, Tazapay can also pull their information and documents from Sumsub without needing a separate Share Token.
If any required data point cannot be retrieved from either source, the entity remains in the in_draft state until it is provided.

​
Possible Outcomes After Passing the Token

  • Submitted / Approved — All required data points are available. The entity is updated with all mandatory and relevant information, and moved to the submitted or approved state — both states can transact.
  • In Draft — All required data points were not available in the Sumsub profile. The entity remains in in_draft until the missing data is provided.