eKYC Module

The eKYC (electronic Know Your Customer) module collects identity verification data through a configurable form — name, address, phone, email, SSN/tax ID, date of birth, ID numbers, etc. — and submits it to Incode's KYC verification engine. The displayed fields and their data sources (manual entry, document OCR, prior phone/email modules) are dashboard-driven.

Follows a form-based pattern variant — dashboard-driven dynamic field schema with optional pre-fill from earlier modules. See the patterns page for the shared lifecycle.

Tag

<incode-ekyc> is a standard Web Component. Importing the UI subpath registers the custom element; importing the CSS applies the module's styles.

import '@incodetech/web/ekyc';
import '@incodetech/web/ekyc/styles.css';

Properties

Configuration

type EkycConfig = {
  flowId?: string;
  verificationFields?: EkycVerificationFields;
  source?: string;
  fieldsCountry?: string;
  enablePhoneRisk?: boolean;
};

The full list of EkycVerificationFields keys: name, address, phone, email, SSN, taxId, nationality, 'date of birth', dlNumber, dlState, dlExpireAt, last4SSN, idNum, idNum1, gender, panNumber. Each field can be sourced from manual entry, OCR'd ID data, POA document data, or a prior phone/email module.

Dashboard field configuration

EkycConfig above is what you set in application code. The dashboard sends its own shape, EkycModuleConfig, which the orchestrator resolves into the rendered form. You do not set it yourself, but it is exported from @incodetech/core/ekyc so you can type a response you inspect.

It configures each verifiable field with a pair of properties:

• check<Field> (boolean) — whether to verify that field at all.
• <field>Source (string) — where its value comes from, using the same source names as verificationFields.

For example, checkName plus nameSource, and checkDob plus dobSource. The pairs cover Name, Email, Address, Phone, Ssn, Dob, Nationality, DlNumber, DlState, DlExpireAt, Last4SSN, IdNum, IdNum1, Gender, and PanNumber. A top-level source sets the default for fields with no explicit source, and riskAddons and enablePhoneRisk carry the risk configuration.

To change which fields a flow verifies, edit the eKYC module in your dashboard rather than passing config in code.

Risk addons

The dashboard-driven module config exposes a riskAddons array (RiskAddon: 'phoneCheck' | 'advancedPhoneCheck' | 'emailCheck'). A matching addon renders the corresponding input even when its checkPhone / checkEmail flag is off:

• phoneCheck or advancedPhoneCheck renders the phone input.
• emailCheck renders the email input.

A module source of RISK_ADDONS_ONLY runs the eKYC form purely to collect the inputs the configured risk addons need, without a full identity-data check. These values come from the dashboard flow configuration, so most callers pass them through unmodified.

State machine

EkycState is a discriminated union over status:

See also

• Module: eKYB: equivalent for businesses
• Module Patterns → form-based
• Module Patterns → composite
• Individual Modules