> ## Documentation Index
> Fetch the complete documentation index at: https://docs.byzantine.fi/llms.txt
> Use this file to discover all available pages before exploring further.

# Individuals - KYC

In order to use the Byzantine Prime application, an individual user needs to go through a KYC process. This is a regulatory obligation for individuals.

<Info>
  Before creating the individual account, the user must accept the required terms. See [Terms and Conditions](/api-reference/terms-and-conditions).
</Info>

### 1. Create the individual account

The creation of the individual account is done by calling this API endpoint:

<Card icon="arrow-right" horizontal href="/api-reference/customer-management/create-individual-account" title="Create an individual account" />

An individual account is described by two distinct fields:

* **`userInfo`** — the person being verified. They are the KYC subject and the account's customer.
* **`rootUsers`** — the signer(s) who control the account. Each root user holds their own passkey and can sign transactions, exactly like the root users of an entity account. Every entry carries its own `firstName`, `lastName`, `email`, and `authenticators`.

For a standard, self-created account, the account holder is both the verified customer and the signer — include the **same person in both `userInfo` and `rootUsers`, using the same email**.

Only the following fields are required to create the account:

* `firstName`, `lastName`, `email` (in `userInfo`)
* one signer in `rootUsers` (`firstName`, `lastName`, `email`)
* `byzantineTermsSignedAt`

The account receives an `accountId`, and every person on it gets their own `userId`: one for the verified customer in `userInfo`, and one for each signer in `rootUsers`. In a standard self-created account, `userInfo` and the single root user are the same person, so there is just one `userId`.

<Warning>
  To register a passkey at account creation, provide the `authenticators` inside the corresponding `rootUsers` entry. If no passkey is added at creation, OTP authentication is automatically set up for that user — and OTP will then be required to add a passkey later through a dedicated endpoint.
</Warning>

<Note>
  An individual account can have **more than one signer**, and you can create an account **on behalf of a client** (for example as a wealth manager / CGP) by verifying one person in `userInfo` while a different person signs via `rootUsers`. See [Multi-users account](/api-reference/multi-users-account).
</Note>

### 2. Complete the application

Once the account is created, use the update endpoint to progressively provide the remaining information needed for KYC verification:

<Card icon="arrow-right" horizontal href="/api-reference/customer-management/update-an-individual-accounts-user-details" title="Update an individual account" />

The following information can be submitted via one or multiple update calls:

* Personal data (date of birth, nationality, address, phone number, etc.)
* ID documents (passport or national ID card). See the [list of accepted documents](/api-reference/accepted-documents)
* Proof of address. See the [list of accepted documents](/api-reference/accepted-documents)

<Info>
  The response of both the create and update endpoints will include a `missingDocuments` field listing any remaining required documents that have not yet been submitted.
</Info>

### 3. KYC verification

Byzantine and Bridge will verify the individual's identity and address. Both Bridge and Byzantine may ask for additional details during this process.

Throughout the KYC process, the user receives email notifications at every stage with updates on their status.

<Info>
  The KYC process usually takes only a few minutes.
</Info>