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.
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
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 aninvestorType is accepted.
onChainInvestorType - the IdentityRegistry only distinguishes the three MiFID II classifications.