Skip to main content
An investor profile turns your onboarding policy into configuration. It decides who may onboard, which documents they provide, which countries you refuse, and how each customer is classified. Every onboarding path of your instance applies the same profile. The result is recorded on-chain, where a token, a lending market or a vault checks it before anything moves.

What a profile controls

Investor classification

Retail, professional or eligible counterparty, applied to every customer the profile verifies

Who may onboard

Natural persons through KYC or legal entities through KYB, optionally professional clients only

Required documents

The identity, liveness, residence, questionnaire and company documents the check collects

Blocked countries

Countries refused on every onboarding path of the profile

Re-verification period

How long a verification stays valid, from 30 days to five years, or without a limit

Eligibility register

An on-chain register that holds exactly the wallets admitted under the profile
The identity check runs through Sumsub, on the level you name for each profile. On the Trusset ID Register the investor type is written on-chain with the identity. An ERC-3643 identity registry carries no investor type, so there it stays on the customer record.

Start from a preset

Every instance starts with three presets: The presets cannot be deleted, and their name, classification and professional-client rule are fixed. Their documents, level and blocked countries can be adjusted. When your policy differs, add a custom profile, for example a professional profile for one jurisdiction with its own blocked countries, or a KYB profile for corporate clients. A custom profile works everywhere a preset does.

Apply one policy everywhere

A profile is the policy for every path a customer can take into your instance:
  • ID links: a hosted verification link issued under a profile runs that profile’s check, with its documents and its applicant type. The link keeps the classification it was issued with.
  • Customer records: a customer created or updated under a profile is checked against its blocked countries.
  • On-chain verification: a wallet registered on your identity register under a profile receives its investor type and is checked against its blocked countries.
  • Pending approvals: an approved check waits until your wallet signs the registration, and the profile is applied again at that point.
Adding a country to a profile’s blocked list also queues the removal of every admitted wallet whose customer comes from that country. Nothing is written to a register until your wallet signs.

Take a verifier’s KYC under a profile

A profile can also be served by a KYC source: a verifier you designate that already verified the investor, for example the liability umbrella at the time of investment. The source is tied to one profile and delivers each investor’s KYC file as a sealed KYC record, encrypted to a key only your local tool holds. When you open a record, the wallet’s customer record is created under the source’s profile if none exists. Trusset cannot read a sealed file, so it applies none of the profile’s document or country rules to it. The review of the file is yours. An approved record admits the wallet to the whitelists bound to the source, with a transaction your wallet signs. It does not admit the wallet to the profile’s eligibility register.

Change a profile safely

A profile in use carries real customers, so changes to it are controlled:
  • Reclassification needs confirmation. Changing the classification, the professional-client rule or the applicant type of a profile in use must be confirmed before it applies. The change is written to the audit log with the customers it affects.
  • Disable instead of delete. A disabled profile takes no new links, customers or wallets, while customers already under it keep working. A profile in use cannot be deleted, and its key cannot change.
  • Every admission keeps its requirements. Each admission records a hash of the requirements it was made under. When the requirements change, admissions made under the earlier ones are flagged.

Gate lending and vaults on a profile

Give a profile an eligibility register and it becomes a gate. The register holds exactly the wallets admitted under the profile. A lending market gated on it lends only to that profile’s customers, and a vault takes deposits only from them. Admissions and removals are queued for you. A customer who passes an ID link review with a wallet is queued for admission. A revocation, a rejected review, a country added to the blocked list or an expired re-verification period queues a removal. On a register deployed for the profile, your wallet signs each change before it reaches the register. A lending market priced from a live market price lends to professional borrowers only. Its borrower gate must be the eligibility register of a profile limited to professional clients. See Professional borrowers. A register is deployed for a profile in the Issuer Platform, or an existing register is bound to it. Eligibility registers are available on Ethereum instances only. A deployed register extends the instance’s own ERC-3643 identity register, bound under Settings, Identity Register. An instance that verifies its customers into the Trusset ID Register cannot deploy one, because that register holds the customers of every instance: deploying is refused with ELIGIBILITY_REQUIRES_OWN_REGISTER. Such an instance can still bind an existing ERC-3643 register to a profile that is not limited to professional clients, and its admissions are then managed with that register’s own tools. A profile limited to professional clients needs a register whose admissions the instance signs, so it needs the instance’s own ERC-3643 register first. A profile without a register chosen as a gate is refused with ELIGIBILITY_REGISTER_NOT_SET. A lender of record on such an instance can still name the eligibility register of another instance’s professional profile by its address.

Set up a profile

1

Open the profiles

In the Issuer Platform, open Customers, then Configure. The three presets are already there.
2

Define the policy

Adjust a preset, or add a custom investor type. Set its on-chain type, who may onboard, the professional-client rule and the re-verification period. Then choose the Sumsub level, the required documents and the blocked countries.
3

Onboard customers

Issue ID links under the profile, or name its key when you verify a wallet through the API.
4

Gate markets and vaults

Deploy an eligibility register for the profile, then choose the profile as the gate of a lending market or vault. This needs your own ERC-3643 identity register bound under Settings, Identity Register first.
Investor profiles are in beta. They are created and edited in the Issuer Platform. The API reads them with List Verification Profiles, where they are called verification profiles.

Verification Profiles

Read every profile and its eligibility register through the API

Eligibility Registers

Admit and remove wallets on a profile’s register