6. KYC Integration [POST-MVP]¶
POST-MVP — not yet architected
KYC verification is planned but not part of the initial release, and its integration design is not finalized. This section is intentionally a stub. The full specification (the KYCProvider port interface, session/result schemas, per-tenant provider configuration, KYC APIs, and provider-specific flows such as Nafath) will be written here when KYC is designed.
KYC will use pluggable provider adapters (Nafath, Onfido, Sumsub, Jumio); the platform surfaces KYC status and the product decides whether to gate on it (§7.4.3).
Live hooks (already in the platform):
| Hook | Where |
|---|---|
Tenant settings kyc_required, kyc_provider, kyc_level, kyc_required_for_enrollment |
§4.5 |
User fields kyc_status (none/pending/verified/failed/expired) and kyc_data |
§13.5 |
| Palm-enrollment gating — platform surfaces KYC status, product decides | §7.4.3 |
KYC audit events (kyc_initiated, kyc_verified, kyc_failed) and webhook events (kyc.initiated, kyc.verified, kyc.failed) |
§15 |
KYC endpoints (/v1/kyc/*), marked [POST-MVP] |
§12.1 |
| Nafath status codes | §14 |