A Level defines the verification requirements for a given compliance scenario. Configure it once, apply it across all your users.

Creating a Level

Navigate to Dashboard → Levels → Create Level. Choose a system template that best fits your use case:

Template	Included Steps	Use case
KYC Basic	ID Document	Simple onboarding with ID only
KYC Standard	ID Document + Liveness	Standard KYC with identity liveness check
KYC Enhanced	ID Document + Liveness + AML	Enhanced due diligence
AML Only	AML Screening	AML for existing users
KYB Basic	Company Data + UBO KYC	Basic business verification

💡 Levels are created as a copy of a template — changes to system templates never affect your existing Levels.

Level configuration fields

Field	Description
`levelId`	Your unique identifier for this Level (max 20 chars, letters/numbers/-/_). Cannot be changed after creation.
`name`	Human-readable name shown in the Dashboard (e.g. "Enhanced KYC – EU")
`steps`	The ordered list of collection Steps. Order determines the user's onboarding flow.
`configs`	Per-Step configuration settings (e.g. AML data sources, expiration policy). See Step-specific config guides.

Level versioning

Every time you save a configuration change, the Level's levelVersion is incremented. In-progress Applications are always pinned to the Level version they were created with — your changes only affect new Applications.

⚠️ Breaking change risk: If you change a Level's Steps and a user has an in-progress Application on that Level, their session is unaffected. However, new Applications will use the new Steps. Test your changes in Sandbox before applying to production.

Via API

POST/v2/levels

{
  "levelId": "enhanced-kyc-eu",
  "name": "Enhanced KYC – EU",
  "templateId": "tpl_kyc_enhanced"
}