Starts verification for an authorized user of a corporate. Once approved, the user becomes an authorized signatory who can act as a legal representative of the corporate.

The response contains a reference used to initialize the KYB UI Component, which presents the provider's verification flow to the user. Verification itself happens there, not through this API.

Prerequisites

Three things must already be true, and each has its own conflict code:

• The corporate itself must have completed KYB (KYB_IDENTITY_NOT_APPROVED). See Start KYB for a corporate.
• The user must have verified their email address (EMAIL_NOT_VERIFIED). See Verify email of the authorized user.
• The user must have verified their mobile number (MOBILE_NOT_VERIFIED).

Calling it more than once

The request fails with KYC_ALREADY_APPROVED if the user is already a verified signatory, KYC_PENDING_REVIEW while a submission is under review, and KYC_REJECTED if it was turned down. Treat these as "no action needed" rather than retrying.

Read Corporate due diligence and KYB for the verification requirements and integration flow.

{
  "reference": "123456789"
}