sumsub-integrate-websdk — Claude Code skill: Sumsub KYC via WebSDK

What sumsub-integrate-websdk does

The skill drives the whole loop. Stage one is a levelName that already lives in your workspace; if you don't have one, the agent talks through what the check should contain and hands the job to the sibling skill sumsub-create-level. It won't invent a questionnaire on its own.

Stage two is your backend. A route signs the request with HMAC and asks Sumsub for a short-lived access token scoped to one (userId, levelName) pair. The userId you pass becomes externalUserId, so keep it stable and opaque — a UUID or a database row id, never an email. Pick it badly and you get duplicate applicants, tickets about verifications stuck in submitted, and no way to resume a check the user abandoned.

On the client the skill loads sns-websdk-builder.js from the CDN, then initialises snsWebSdk and launches the widget. Here is the part teams usually get wrong: browser callbacks such as onApplicantStatusChanged are for the interface only. Gate access on the applicantReviewed webhook plus a server-side applicant read. You also need a sandbox App Token and secret pair, because a production token spins up sessions against real applicants.