Investor Profiles

This page is for the compliance lead or operator who decides who may onboard and invest through an instance. After reading it you will know what an investor profile controls, where it applies, and how it gates lending markets and vaults. 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

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.

​

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.

​

Set up a profile