Verify your users.
Skip the KYC build.

Reap API's Compliance module is the identity verification layer for platforms building on Reap. It covers both KYC for individual users and KYB for businesses, through the same API, webhooks and statuses as the rest of the platform. Your users complete full checks — ID, documents and a liveness selfie — run by Reap rather than your team. If you already verify your users elsewhere, you can bring those results across instead of starting again.

Three. Managed KYC, where Reap runs the checks through a Sumsub SDK in your app. Sumsub Token Sharing, where you import verifications from your own Sumsub account. And Universal KYC, where you send results from any provider for Reap to review. You pick one per project during onboarding.

Both let you keep your own provider, and Reap makes the final call in both. Token Sharing only works with Sumsub: you share a token, Reap checks the verification meets its standards, and nothing is collected twice. Universal KYC works with any provider: you send the data and documents, and Reap reviews them. Token Sharing is faster per user. Universal KYC works with anyone.

Not if you haven't built one. Reap runs on Sumsub today and manages that relationship. If you already work with a provider, Token Sharing for Sumsub or Universal KYC for anyone else lets you keep it.

Only if their checks meet Reap's standards. If a user was verified to a lighter standard, they'll need to complete the missing steps in your KYC flow first.

No. The method is set once per project, and every user in that project uses it.

Yes. The same Compliance module handles KYB: business registration, ownership structure, and officer and UBO identification, each with its own KYC session. Once everyone is verified, the company is active and employees can start getting cards. No second vendor needed.

You are, whatever setup you choose. Reap helps you meet those obligations. It doesn't take them over.