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

# Onboarding and access

> The gates a market and a vault check, the five ways a wallet gets through them, and which way fits which gate.

A wallet can borrow or deposit only when it passes the gate the lender of record chose. Onboarding is getting a client's wallet through that gate. This page explains the gates once and maps every onboarding path onto them, for banks and fintechs alike.

## The gates

A market has two gates. The **borrower register** examines every loan and every further draw. The **provider register** is read by each vault that funds the market before it admits a depositor. A vault can also carry a register of its own, chosen at creation in the Issuer Portal. Without one, it adopts the provider register of the first market it funds and keeps it.

Every gate is one of three kinds:

| Gate | Admits | Who puts wallets on it |
| - | - | - |
| Identity register | Wallets verified on it. That is the Trusset ID Register, shared by every instance without a register of its own, or an instance's own Trusset or ERC-3643 register | The instance that verifies the wallet. Its own wallet signs, with `KYC_PROVIDER_ROLE` on a Trusset register or as agent of an ERC-3643 registry |
| Eligibility register | Exactly the wallets admitted under one [verification profile](https://docs.trusset.org/protocol/infrastructure/investor-profiles.md) | The profile's instance. Admissions are queued for it and its wallet signs them |
| [Whitelist](https://docs.trusset.org/endpoints/lending/list-access-lists.md) | Exactly the wallets its owner and managers listed. It examines no identity | The owner and managers of the list |

The market admin installs and changes the gates with [Set Identity Gates](https://docs.trusset.org/endpoints/lending/set-identity-gates.md). A change applies from the next loan, draw or deposit. Repaying, closing and redeeming are never gated.

Three rules limit the choice. A `MARKET`-priced market lends to professional clients only, so its borrower gate must be the eligibility register of a profile limited to professional clients, and never a whitelist. A whitelist becomes a provider gate only with the attestation that it lists identified wallets only. Eligibility registers run on Ethereum instances only, and deploying one needs the instance's own ERC-3643 register.

## The five onboarding paths

**1. Hosted ID link.** For a fintech without its own KYC process. [Create Customer](https://docs.trusset.org/endpoints/customers/create.md), then [Create ID Link](https://docs.trusset.org/endpoints/customers/create-id-link.md). The client opens the link on verify.trusset.org, signs in with the wallet and passes the identity check. The approval then waits in the [pending queue](https://docs.trusset.org/endpoints/customers/list-pending-verifications.md) until your wallet signs it onto your identity register. To run the same check inside your own app, [Onboarding](https://docs.trusset.org/endpoints/customers/onboarding.md) takes one customer from the start to the signed registration through a single endpoint group, and follows a sealed record from your KYC source (path 4) the same way.

**2. Direct verification.** For an institution that ran KYC itself. [Verify Identity](https://docs.trusset.org/endpoints/customers/verify-identity.md) puts one wallet on your identity register with its `kycHash`, and [Batch Verify](https://docs.trusset.org/endpoints/customers/batch-verify.md) does many in one transaction. Your wallet signs.

**3. KYC proofs.** For an institution that holds the KYC data and wants claims backed by zero-knowledge proofs. [KYC-STARKs](https://docs.trusset.org/tools/kyc-starks/overview.md) runs on your machine and turns each record into a Merkle root and one proof per field. The root goes on the register as the `kycHash`, and [Add Claims from Proof](https://docs.trusset.org/endpoints/customers/add-claims-from-proof.md) files the proven claims, such as residency or investor type. Trusset never sees the data.

**4. Sealed KYC record.** For a bank that wants the KYC file itself from a verifier it trusts. The bank adds the verifier as a KYC source bound to its whitelists. The verifier seals the client's file with [KYC Courier](https://docs.trusset.org/tools/kyc-courier/overview.md) so that only the bank can open it, and delivers it. The bank opens it on its own machine and approves it, and its wallet lists the client's wallet on those whitelists. See [Sealed KYC Records](https://docs.trusset.org/protocol/infrastructure/sealed-kyc-records.md).

**5. Direct whitelist listing.** For the owner or a manager of a whitelist that already knows the wallets, such as a bank's existing clients. [Set Whitelist Members](https://docs.trusset.org/endpoints/lending/set-access-list-members.md) lists or removes up to 200 wallets per transaction. On a list bound to a KYC source, each wallet first needs an approved, valid sealed record.

Every registration through paths 1 to 3 also queues the wallet's admission to the eligibility register of the profile it was verified under, when that profile has one. [Request Admission](https://docs.trusset.org/endpoints/customers/request-admission.md) queues one by hand. The profile's instance signs the admission with [Build Admission](https://docs.trusset.org/endpoints/customers/build-admission.md). An approved sealed record admits a wallet to whitelists only, never to an eligibility register.

## Which path fits which gate

| The gate is | A wallet gets through by |
| - | - |
| The Trusset ID Register | Paths 1, 2 or 3, run by any instance that writes to it. The register holds one identity per wallet, so a wallet verified there once passes every gate built on it |
| An instance's own identity register | Paths 1, 2 or 3, run by that instance |
| An eligibility register | An admission under its profile, queued by paths 1 to 3 and signed by the profile's instance |
| A whitelist | Path 4 or 5 |

## Check a wallet before it acts

[Get Identity Gates](https://docs.trusset.org/endpoints/lending/get-identity-gates.md) names the gates a market reads, and each vault record names its depositor gate. [Identity Status](https://docs.trusset.org/endpoints/customers/identity-status.md) shows a wallet on the identity register, and [Get Wallet Eligibility](https://docs.trusset.org/endpoints/customers/get-wallet-eligibility.md) on every eligibility register of your instance.

A refusal names the gate that stopped the wallet. [Open Loan](https://docs.trusset.org/endpoints/lending/open-loan.md) answers `IDENTITY_NOT_VERIFIED` with the register, and the profile or whitelist behind it. A vault [Deposit](https://docs.trusset.org/endpoints/vaults/deposit.md) answers `DEPOSITOR_NOT_VERIFIED` the same way.

## Who does what

A **fintech** usually onboards its clients through paths 1 to 3, and acts as the verifier in path 4 when a bank asks for the file. A **bank** chooses the gates, receives and approves sealed records, keeps its whitelists and signs the admissions to its own profiles' registers. [For fintechs](https://docs.trusset.org/protocol/fintechs.md) and [For banks](https://docs.trusset.org/protocol/banks.md) put these steps in order.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.