KYC Know Your Customer

Who this is for: issuers and developers deciding whether and where to gate an application by individual identity. This is a concept page. For the integration steps, see /build/identity/on-chain-kyc-integration (developer lens) or /tokenize/kyc/on-chain-kyc-for-issuers (issuer lens).

What it verifies

KYC confirms the real-world identity of an individual: typically that a person is who they claim to be, and in some flows that they meet an eligibility bar (age, jurisdiction, accreditation status). It is a check on a person, distinct from KYB, which checks a business entity.

Where it applies on Lumia

Per Lumia's compliance model, KYC is enforced at the application layer, not the protocol layer. A contract (typically a token's transfer() function or a gated entry point) checks an on-chain attestation or credential produced by a KYC process, rather than the chain itself checking identity before including a transaction. Retail or individual token holders are the typical subject of a KYC check; institutional entities are usually checked under KYB instead.