KYC

# KYC Self supports a KYC document type for identity verification. ## Overview KYC is represented in verification payloads as attestation ID `4`. ## User flow 1. User selects `kyc` as document type in the Self app. 2. The app starts the partner KYC flow. 3. After completion, verification is finalized asynchronously (websocket/push). 4. The app stores the resulting KYC attestation and can generate disclose proofs. ## What you receive When verification completes against a flow that allows KYC, the `verification.completed` webhook fires with `proof_attributes` describing the disclosed predicates exactly as it would for any other document type. There's no per-flow document picker: a KYC attestation is accepted whenever the flow's **Security level** is **Standard** (Hi-security flows require a chip-backed document). See [Supported documents](/docs/self-enterprise/flows/supported-documents/) for the capability matrix. ## Notes - KYC follows the same proof and verification path as other document types. - Standard disclosure fields and config checks (age, OFAC, country restrictions) apply.

Read https://docs.self.xyz/docs/self-enterprise/reference/document-specifications/kyc.md so I can ask questions about this Self documentation page.