KYC ensures that all individuals tied to a business are properly identified and validated. The process may include:

Method	Endpoint	Description
`POST`	`/entity/{entityId}/kyc`	Generate an SDK token for identity verification
`GET`	`/entity/{entityId}/signed-payload`	Retrieve a signed payload for client-side verification
`POST`	`/entity/verify-signed-payload`	Verify a signed KYC payload server-side

If you're using a provider like SumSub:

Use POST /entity/{entityId}/kyc to generate a secure sdkToken
Pass the token to your web or mobile client to launch the provider’s verification flow
Let the provider handle liveness detection, photo uploads, and document checks

{
  "provider": "sumsub",
  "sdkToken": "_act-sbx-jwt-..."
}

If you're handling KYC form data yourself, you can:

Get a signed payload using GET /entity/{entityId}/signed-payload
Submit the payload and signature via POST /entity/verify-signed-payload
Reap will verify the payload hasn’t been tampered with and respond with { valid: true | false }

This is useful for clients implementing custom onboarding forms or integrating biometric verification from another provider.

Ensure your users complete KYC before granting access to features.
Use webhook notifications to listen for status changes (see the Notifications section).

After KYC is completed, continue with:

👉 See Notifications to track verification events in real time.