> For the complete documentation index, see [llms.txt](https://docs.agant.io/Y83ivqmfOiUspagNyFg6/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agant.io/Y83ivqmfOiUspagNyFg6/overview/onboarding.md).

# Onboarding

### Overview

To complete onboarding with Agant, you will need to provide company details, whitelist a bank account, verify the business and verify the identities of company directors and Ultimate Beneficial Owners (UBOs).

Onboarding is completed through a guided wizard, available once an Agant account has been reviewed and approved by the Agant team.

There are four steps to onboarding with Agant:

1. Company details
2. Team invitations *(optional)*
3. Bank account
4. KYB/KYC verification

{% hint style="info" %}
In the Sandbox environment dummy information can be used in Step 4 of the onboarding process.
{% endhint %}

### What You'll Need

Before starting, make sure you have the following to hand:

**Company details**

* Trading name and registered legal name
* Companies House registration number
* [Legal Entity Identifier (LEI)](https://search.gleif.org/#/search/) - a 20-character alphanumeric code

**Bank account**

* IBAN for a UK bank account to whitelist

**KYB verification**

* Details for company directors and UBOs - e.g. name, email address, addresses, and date of birth
* Company legal documents (Persona will guide you through what is required)

**Two-factor authentication (2FA)** must be configured on the Agant user account before the wizard can be accessed.

***

### Step 1: Company Details

**Required**

You will need to provide legal and regulatory details about the company. These must match official registration records.

| Field                           | Description                                                        |
| ------------------------------- | ------------------------------------------------------------------ |
| **Trading Name**                | The name the business operates under (e.g. `Acme Corp`)            |
| **Registered Legal Name**       | The full legal name as registered (e.g. `Acme Corporation Ltd`)    |
| **Company Registration Number** | Companies House or equivalent registration number                  |
| **Country of Registration**     | Country of incorporation — currently **United Kingdom** only       |
| **LEI Code**                    | 20-character Legal Entity Identifier (e.g. `5493001KJTIIGC8Y1R12`) |

{% hint style="info" %}
The **LEI (Legal Entity Identifier)** is a globally recognised identifier for legal entities participating in financial markets. If the company does not yet have one, it can be obtained through an accredited issuer. Search for an existing LEI at [search.gleif.org](https://search.gleif.org/#/search/).
{% endhint %}

***

### Step 2: Invite Team

**Optional — can be skipped**

Team members can be invited to the Agant account during setup. This step can be skipped and managed later from the company settings.

To invite a team member, provide their name, email address, and role. An invitation will be sent to their inbox. Pending invitations can be cancelled at any time.

| Role       | Description                                                                |
| ---------- | -------------------------------------------------------------------------- |
| **Member** | Can view and interact with Rails, Transactions, Wallets, and Bank Accounts |
| **Admin**  | Full access including company settings and team management                 |

{% hint style="info" %}
Only the **user who registered the Agant account** can initiate KYB verification in Step 4.
{% endhint %}

***

### Step 3: Bank Account

**Required**

You will need to whitelist a UK bank account with Agant. Whitelisted accounts are the only accounts from which Agant will accept and send fiat payments.

| Field            | Description                                                |
| ---------------- | ---------------------------------------------------------- |
| **Account Name** | A label to identify the account (e.g. `Operating Account`) |
| **IBAN**         | UK bank account IBAN (e.g. `GB29NWBK60161331926819`)       |

{% hint style="info" %}
Additional bank accounts can be whitelisted from the **Bank Accounts** section of the Dashboard after onboarding is complete.
{% endhint %}

***

### Step 4: KYB Verification

**Required - account registrant only**

Agant uses Persona to complete **Know Your Business (KYB)** verification. This step must be initiated by the user who registered the Agant account - other team members will see a prompt to ask them to complete it.

You will need to provide:

* Details for company directors and UBOs - name, email address, and date of birth (further KYC checks are run on these individuals)
* Company legal documents (Persona will guide you through what is required)

Verification runs in a guided popup window and typically takes **20 minutes** to complete.

Once the verification popup is completed, click **Complete Setup** to finish. You will receive an email once your account ha been verified.

{% hint style="info" %}
In the Sandbox environment, you can complete the KYB verification with dummy information.
{% endhint %}

***

### After Onboarding

Once all steps are complete, yand the account has been approved, you can then proceed onto the platform and whitelist additional Wallets and Bank Accounts, create new Rails, generate API Tokens, and begin utilising Agant's stablecoin infrastructure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.agant.io/Y83ivqmfOiUspagNyFg6/overview/onboarding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.