Skip to main content
Privy verifies an organization with Bridge. Privy creates the Bridge business customer on the first request and links it to the Privy organization, so your app only ever references the Privy organization ID. Before creating a KYB link, see hosted terms of service or, if Bridge has approved your app, terms of service reliance for how to collect an authorized representative’s acceptance. The representative then submits the organization’s information through a hosted verification flow. To collect that data in your own interface instead, see headless KYB. Before verifying organizations, register a Bridge API key with Privy.
Bridge reviews business customers manually, so KYB usually takes longer than KYC for an individual. Bridge may also require the organization’s associated persons to complete their own verification.
Use the initiateLinks method from the kyb resource on organizations().
Pass kyb.link to your app’s frontend so the organization’s representative can complete verification. The request is idempotent: calling it again for the same organization returns the existing link.

Track KYB status

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

Next steps

Track KYB status

Poll an organization’s verification status or subscribe to webhooks

Headless KYB

Submit an organization’s verification data from your server

Organization wallets

Create wallets an organization’s members can operate together

Handling webhook events

Configure an endpoint to receive Privy webhook events