Implement Sumsub Reusable KYC via API to import a previously verified applicant from a partner instead of re-running full document and biometric checks

domain: sumsub.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Establish a data-sharing agreement with the partner Sumsub client whose verification data you want to reuse
  2. Use the Reusable KYC API to import the shared applicant record, referencing the partner's applicant identifier
  3. Configure which checks are satisfied by the imported data versus which must still be freshly performed (e.g., a new liveness check even if the ID document was already verified)
  4. Handle the applicant's resulting review status and confirm the reused data is scoped to your agreed level before treating the applicant as verified
  5. Distinguish this API-based import flow from the SDK-based share-token flow, which is intended for end-user-initiated reuse rather than partner-to-partner import

Known gotchas

Related routes

Configure Sumsub applicant levels to define per-use-case verification requirements and route new applicants to the correct level at creation time
sumsub.com · 5 steps · unrated
Create a Sumsub applicant, trigger verification, and handle status webhooks
docs.sumsub.com · 6 steps · unrated
Implement a prenote-to-instant verification migration strategy: fall back to prenotes when instant account verification is unavailable
moderntreasury.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans