Skip to main content
Custom fields are used in form_fill steps to collect structured data from users. Fields can be simple inputs or semantic fields that integrate with automation rules for automatic validation.

Field Categories

Basic Fields

Standard inputs: text, number, date, boolean, select, file

Contact Fields

Email, phone, URL with validation options

Semantic Fields

Country, name, wallet, domain with automatic rule integration

Complex Fields

Address, entity arrays, sub-merchants, nested objects

Common Field Properties

All field types share these base properties:
Use field_key for portable integrations: The field_id is auto-generated and different between staging and production. Define a field_key (e.g., full_name, date_of_birth, is_pep) to get a consistent identifier in webhooks that works across all environments.

Basic Fields

Text Field

Simple text input.

Number Field

Numeric input with optional range validation.

Date Field

Date picker with optional range constraints.

Boolean Field

Checkbox/toggle input.

Select Field

Dropdown selection with predefined options.

Multi-Select Field

Multiple selection dropdown.

File Field

File upload input.

Contact Fields

Email Field

Email input with optional verification.
Email verification can be used with EmailVerificationRule in automation rules to auto-deny invalid emails or flag disposable domains.

Phone Field

Phone number input with validation options.

URL Field

URL/website input.

Semantic Fields

Semantic fields have special meaning and integrate with automation rules for automatic validation.

Country Field

Country selection with semantic type for automation rules.

Country Types

Country fields with a country_type will automatically trigger matching CountryRule automation rules. For example, if you have a rule for nationality from KP, it will only apply to fields with country_type: "nationality".

Name Field

Name input with automatic sanctions/adverse media validation.
Enabling validate_lists or validate_adverse_media on name fields will trigger list checks during session processing and can trigger ListMatchRule automation rules.
Use entity_role to automatically tag names for watchlist auto-add. For example, set entity_role: "ubo" on a name field for beneficial owners, and when the session is processed with watchlist_auto_add enabled, these names will be tagged as ubo in the watchlist.

Wallet Field

Cryptocurrency wallet address input.

Document ID Field

Document identification number with format validation.

Domain Field

Domain/URL with optional web validation.

Financial Fields

Currency Field

Monetary amount input.

Percentage Field

Percentage input (0-100).

Volume Field

Transaction volume input with automation rule support.
Volume fields with apply_volume_rules: true will trigger matching VolumeRule automation rules during session processing.

Complex Fields

Address Field

Complete address input with optional country-based automation.

Entity Array Field

Array of related entities (directors, shareholders, beneficial owners).
Entity array fields support ListMatchRule with entity_scope: "related_parties" to apply different actions for list matches on directors/shareholders vs the primary subject.

Sub-Merchant Field

Sub-merchant information for payment facilitator onboarding.

Array Field

Generic array input.

Nested Object Field

Nested object with multiple sub-fields.

Conditional Logic

Fields can be shown/hidden based on other field values.

Conditional Operators


Field Types Reference