Skip to main content
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: The market admin installs and changes the gates with Set Identity Gates. 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, then Create ID Link. 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 until your wallet signs it onto your identity register. To run the same check inside your own app, Onboarding 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 puts one wallet on your identity register with its kycHash, and Batch Verify 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 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 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 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. 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 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 queues one by hand. The profile’s instance signs the admission with Build Admission. An approved sealed record admits a wallet to whitelists only, never to an eligibility register.

Which path fits which gate

Check a wallet before it acts

Get Identity Gates names the gates a market reads, and each vault record names its depositor gate. Identity Status shows a wallet on the identity register, and Get Wallet Eligibility on every eligibility register of your instance. A refusal names the gate that stopped the wallet. Open Loan answers IDENTITY_NOT_VERIFIED with the register, and the profile or whitelist behind it. A vault Deposit 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 and For banks put these steps in order.