KYB Onboarding

The KYB Onboarding process is an Entitlement workflow used to onboard a Corporate to the platform, satisfying all required regulatory checks.

Like KYC Onboarding, the process exists in two variants, fixed by your entitlement configuration:

Reliance flow - available today. The platform relies on the identity verification you have already performed on the corporate's individuals.
Standard flow - in development. The platform will verify the Business Contact's identity itself, as in the standard KYC flow.

Entitlement Summary

Field	Value	Description
Name	`onboarding`	The system name used to identify and trigger this Entitlement.
Applies To	`Corporate`	Triggered for a Corporate entity.
Prerequisites	1. Corporate Creation: The target `Corporate` entity must exist. 2. Individuals: All relevant individuals are created and linked with valid roles.
Outcome	Upon completion, the Corporate's account is either `approved` or `rejected`, communicated via the final completion webhook and the entitlement trigger status.

Finding the right entitlement

Entitlement names are shared across owner types, but each owner type has its own entitlement UUID. Fetch the corporate variant via:

GET /entitlements?owner_type=corporate

Reliance Flow (Partner IDV)

Reliance - no IDV step

In the reliance flow, the platform relies on the identity verification you have already performed on the corporate's individuals as part of your own KYC/KYB procedures.

Unlike the standard KYC Onboarding of a Person:

No requirementsIDV webhook is sent and no Fourthline session is created - do not integrate the IDV flow or the Fourthline SDK for corporate onboarding.
Instead, you submit the results of your own identity verification of the Business Contact, and ID documents for the other linked individuals, through questionnaires.
The platform still performs its own compliance screening (PEP, sanctions, criminal, adverse media) of the corporate and every linked individual, followed by a risk assessment.

The process follows the standard Entitlement Trigger Flow outlined in the main Entitlements guide. All requirements are delivered as questionnaires - for the corporate itself and for its linked individuals.

Required Questionnaires

Questionnaire	Answered for	Purpose
Corporate onboarding questionnaire	The Corporate	Business profile, AML & risk information, expected account usage, and the required corporate documents.
Corporate obligated party questionnaire	The Corporate	Additional AML questions - required only if the corporate declares itself an obligated party (see below).
Corporate identity Verification	The Business Contact (Individual)	The results of the identity verification you performed on the Business Contact (method, status, personal data, ID document data).
Corporate ID document verification	Every other linked Individual	ID document type and a copy of the document for each representative/UBO.
Country-specific questionnaires	The Corporate	Additional questions may be required depending on the corporate's country.

The exact set is delivered via requirementsQuestionnaire webhooks and can also be listed at any time via GET /corporates/{corporate_id}/questionnaires and GET /individuals/{individual_id}/questionnaires.

The obligated party branch

The corporate onboarding questionnaire asks whether the company is itself an obligated party under anti-money-laundering law (obligatedParty). Answering true adds one more required questionnaire - the Corporate obligated party questionnaire - delivered as an additional requirementsQuestionnaire webhook after the main questionnaire is submitted.

Required Documents

The corporate onboarding questionnaire contains document questions for the following document categories, all uploaded via POST /corporates/{corporate_id}/documents:

organizational_chart
commercial_register_extract
article_of_association
financial_statement
transparency_register_extract

ID documents for individuals are uploaded via POST /individuals/{individual_id}/documents. When answering a document question, the uploaded document's category must match the question's value - see Document.

Flow Specifics

Creation: Create the entities and their links:
- POST /corporates, POST /individuals (or /individuals/bulk), POST /corporates/{corporate_id}/individual_links (or /bulk)
- See Corporate & Individuals for required fields and the role rules.
Trigger: Initiate the Entitlement workflow:
- POST /corporates/{corporate_id}/entitlement_triggers
- Body: {"entitlement_id": "..."} (the UUID fetched with owner_type=corporate).
- The role structure is validated immediately - an invalid structure fails the onboarding at this point.
Requirements: The system issues requirementsQuestionnaire webhooks covering the corporate questionnaires and the individual-level questionnaires. Submit answers via:
- POST /corporates/{corporate_id}/questionnaires/{questionnaire_id}/response
- POST /individuals/{individual_id}/questionnaires/{questionnaire_id}/response
Screening & Risk Assessment: Once requirements are met, the platform screens the corporate and every linked individual (PEP, sanctions, criminal, adverse media) and performs an automated risk assessment. If additional information is needed, a further requirementsQuestionnaire webhook with reason onboarding_edd is issued.
Account Setup: On a positive assessment, the account setup completes. Where the custody integration applies to your setup, this includes creating the custody account for the corporate and its individuals.
Completion: The workflow concludes with an entitlementCompleted or entitlementFailed webhook.

Submitting data before triggering

You can upload documents and submit questionnaire responses before triggering the entitlement. Pre-existing answers are picked up automatically, which shortens the overall processing time.

Standard Flow (Platform IDV) - In Development

A standard KYB variant is in development: the platform will verify the Business Contact's identity itself, as it does for Persons in the standard KYC flow. The integration contract - endpoints, webhooks, and questionnaire changes - will be published here when the variant becomes available.

Until then, all corporate onboarding uses the reliance flow described above.

Monitoring Progress

Corporate onboarding involves screening of multiple individuals and takes noticeably longer than a personal KYC onboarding - expect several minutes rather than seconds. In addition to the webhooks, you can poll the entitlement trigger at any time:

GET /corporates/{corporate_id}/entitlement_triggers

Field	Values
`status`	`pending`, `ongoing`, `terminated`, `canceled`, `blocked`, `failed`, `finished`
`result`	`success`, `failure`, `tangany_rejected`

A run is successful when status is finished and result is success. Where the custody integration applies to your setup, the result tangany_rejected indicates the account setup was rejected by the custody provider.

Failure Reasons

On failure, the entitlementFailed webhook's details describe the cause - either as an error code with a description (for failed compliance data checks, see the Error Codes Reference) or as a plain-text reason:

Failure	Delivered as	Meaning
Invalid role structure	`reason`	The linked individuals violate one of the role requirements (e.g., no Business Contact, or both a real and a fictitious UBO).
Compliance checks failed	`code` + `description`	One or more automated compliance checks on the submitted data/documents did not pass - see the Error Codes Reference.
Corporate screening hit	`reason`	The corporate matched sanctions/PEP/criminal/adverse-media screening.
Individual screening hit	`reason`	A linked individual matched screening; the reason identifies which individual.
Risk assessment failed	`reason`	The automated risk assessment could not approve the profile.
Custody setup rejected	trigger `result`	Surfaced via the trigger `result` value `tangany_rejected` (see above).

Entitlement Summary​

Reliance Flow (Partner IDV)​

Required Questionnaires​

Required Documents​

Flow Specifics​

Standard Flow (Platform IDV) - In Development​

Monitoring Progress​

Failure Reasons​