Skip to main content
Privy verifies an individual user with Bridge. Privy creates the Bridge customer on the first request and links it to the Privy user, so your app only ever references the Privy user ID. Before creating a KYC link, see hosted terms of service or, if Bridge has approved your app, terms of service reliance for how to collect the user’s acceptance. The user then submits their identity information through a hosted verification flow. To collect that data in your own interface instead, see headless KYC. Before verifying users, register a Bridge API key with Privy.
Use the initiateLinks method from the kyc resource on users().
Pass kyc.link to your app’s frontend so the user can complete verification. The request is idempotent: calling it again for the same user returns the existing link.

Track KYC status

Verification is asynchronous. Bridge reviews the submission after the user completes the hosted flow, and can revoke an endorsement later. See track KYC status to poll a user’s status or subscribe to webhooks.

Next steps

Track KYC status

Poll a user’s verification status or subscribe to webhooks

Headless KYC

Submit a user’s verification data from your server

KYB

Verify an organization

Handling webhook events

Configure an endpoint to receive Privy webhook events