Skip to main content
This page is for the engineer choosing an investorType. After reading it you will know what a profile controls, and where a custom profile stops mattering.
Verification profiles are in beta. The API surface is read-only - create and edit profiles in the Issuer Platform.
A verification profile bundles a KYC requirement set: which documents an investor must provide, which Sumsub level applies, and which on-chain investor type a completed verification maps to. Every instance ships three presets - RETAIL, PROFESSIONAL, and ELIGIBLE_COUNTERPARTY - and can define custom profiles. Profile keys are valid investorType values wherever the SDK accepts one: customer records, ID links, and identity verification.

List profiles

Presets are listed first. Each profile:
key is what you pass as investorType. onChainInvestorType is the numeric classification: 1 Retail, 2 Professional, 3 Eligible Counterparty. requiredFields describes the document sets requested during a linked KYC flow, e.g. { idDocSetType: 'IDENTITY', types: ['PASSPORT', 'ID_CARD'], required: true, label: 'Government ID' }.

Use a custom profile

The profile key works anywhere an investorType is accepted.
On-chain, a custom profile resolves to its onChainInvestorType - the IdentityRegistry only distinguishes the three MiFID II classifications.