KYC/KYB Hooks
Active portfolio classification — 2026-07-25 [D]. KYC/KYB Hooks is a
pre-launch onboarding-integration capability inside Skyzai Work, not an
independent SKU, package, identity verifier, or authority source. Product,
pricing, commercial-page, and standalone-launch language below is preserved
design history; linked routes are compatibility coordinates, not deployment
or regulated-provider proof.
Status: pre-launch. This page describes target design; this document does not establish a deployed service.
Scope: proposed onboarding-integration capability in the Skyzai Work package; any Personal use needs separately scoped acceptance. Personal and Work are two app/commercial packages for seven product owners, not two owners themselves. This is not a standalone SKU. See The Product Family.
Surface: kyc.skyzai.com (declarative)
Catalog route: skyzai.com/products/kyc-kyb-hooks/
Status: SPEC
Evidence tier: [D] — schema + hook events specified; first external integration is the proof gate (re-tiered [B]→[D] 2026-07-03 per TIER_MERGE_GATE: a spec/draft is not an observed run; [B] requires a dated reproducible receipt)
Source canon: (private, unpublished)
What KYC/KYB Hooks Are
KYC/KYB Hooks are an integration layer — not a regulated identity provider. They:
- Capture structured onboarding evidence from entities and individuals
- Route checks to verified third-party KYC/KYB providers
- Emit structured evidence packets with provider receipts
- Export compliance-ready audit trails
Critical boundary: Skyzai does not claim to be a regulated KYC/KYB provider unless counsel explicitly ratifies that path. This service is plumbing, not the pipe.
Architecture
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Onboarding │────▶│ Evidence │────▶│ Provider │────▶│ Provider │
│ Intake │ │ Capture │ │ Router │ │ (3rd party)│
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
│ │ │ │
│ ▼ ▼ ▼
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ │ EvoNet │ │ Provider │ │ Provider │
│ │ SHOULD NOT │ │ Receipt │ │ Response │
│ └─────────────┘ └─────────────┘ └─────────────┘
│ │ │ │
│ ▼ ▼ ▼
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
└─────────────▶│ Sovereign │ │ Evidence │ │ OFN │
│ Gate (PRISM)│ │ Packet │ │ Receipt │
└─────────────┘ └─────────────┘ └─────────────┘
The Sovereign Gate routes public-DAV high-risk checks through a complete valid bound PRISM decision receipt from the signer(s) required by applicable law, the entity's governing instrument, or a valid competent mandate binding the exact consequence. PRISM records and verifies only; AI/caste seats remain unsigned. Any Legal Person check still requires lawful external authority and the executors required by jurisdiction, with counsel conditional.
Evidence Capture Schema
Individual (KYC)
{
"check_type": "kyc_individual",
"subject": {
"full_name": "...",
"date_of_birth": "...",
"nationality": "...",
"residential_address": "..."
},
"documents": {
"id_document": {"type": "passport", "hash": "..."},
"proof_of_address": {"type": "utility_bill", "hash": "..."}
},
"self_attestation": {
"timestamp": "...",
"declaration": "I confirm the above is true..."
}
}
Entity (KYB)
{
"check_type": "kyb_entity",
"entity": {
"legal_name": "...",
"incorporation_jurisdiction": "...",
"registration_number": "...",
"business_address": "..."
},
"ubo": [
{"name": "...", "ownership_percentage": "25%", "verification_status": "..."}
],
"directors": [...],
"documents": {
"certificate_of_incorporation": {"hash": "..."},
"articles_of_association": {"hash": "..."}
}
}
Provider Routing
Supported Providers
| Provider | Capabilities | Regions | Status |
|---|---|---|---|
| Onfido | Document verify, biometric | Global | Planned |
| Jumio | KYC, KYB, AML | Global | Planned |
| Trulioo | Global identity verify | 195+ countries | Planned |
| Shufti Pro | KYC, KYB, video KYC | Global | Planned |
Routing Logic
def route_check(evidence: dict) -> Provider:
# Jurisdiction-based routing
if evidence["jurisdiction"] in EU:
return Provider.GDPR_COMPLIANT
# Risk-based routing
if evidence["risk_score"] > 0.7:
return Provider.ENHANCED_DUE_DILIGENCE
# Default routing
return Provider.STANDARD
API Specification
POST /v1/kyc/checks
Submit individual KYC check.
Request:
{
"check_type": "kyc_individual",
"subject": {...},
"documents": {...},
"provider_preference": "onfido"
}
Response:
{
"check_id": "kyc_2026_abc123",
"status": "pending",
"provider": "onfido",
"estimated_completion": "2026-05-09T14:00:00Z",
"webhook_url": "https://..."
}
POST /v1/kyb/checks
Submit entity KYB check.
GET /v1/checks/{id}
Retrieve check status and results.
GET /v1/checks/{id}/export
Export compliance-ready evidence packet.
Evidence Tiers
| Evidence description | What would support it |
|---|---|
| Design/specification [D] | Defined schema and hook events; scaffolds are not observed integrations |
| Local test evidence | Dated reproducible sandbox-provider test receipt; not live adoption |
| Observed run [B] | Dated reproducible integration/run receipt within its declared scope |
| Independent verification [E] | Authorized external use plus independent provider/outcome evidence |
Current documented status: design/specification [D]. A fixture or scaffold is not a provider-integration receipt. Counsel correspondence is not automatically a structural/algebraic [A] result.
What This Service Is NOT
- Not a regulated KYC/KYB provider
- Not a financial institution
- Not a legal identity verifier
- Not an AML/CFT compliance officer
- Not a screening guarantee or compliance attestation
- No legal-compliance guarantee for the buyer's jurisdiction
What This Service IS
- An integration layer between your onboarding flow and verified providers
- An evidence capture and routing system
- An audit trail generator
- A pass-through cost handler (provider fees pass through without markup)
η = 0 Compliance
| Chargeable | Not Chargeable |
|---|---|
| Integration setup | Provider check fees (pass-through) |
| Evidence routing | Identity verification itself |
| Controls and monitoring | Regulatory attestation |
| Support | Compliance guarantee |
Cross-links
- Product page:
/products/kyc-kyb-hooks/ - Buyer deck:
/products/kyc-kyb-hooks/deck/ - Resource room:
/products/kyc-kyb-hooks/resources/ - Access form:
/products/kyc-kyb-hooks/access/ - Adjacent canon: API Pay (P0), API contracts (35), Wallet Boundaries (P3)
- Source markdown: (private, unpublished)
- Validator code: (private, unpublished)
Historical predecessor wording — retained on 2026-09-27, not active rules
The displaced passages are preserved verbatim for lineage. This retention date is not their original authorship date.
Predecessor passage 1
| Tier | Claim | Required Evidence |
|---|---|---|
| [I] | KYC/KYB Hooks architecture is defined | Design document, API spec |
| [B] | Provider routing works in test | Integration tests with sandbox providers |
| [E] | External customer uses KYC/KYB Hooks | Customer integration proof, provider receipts |
| [A] | KYC/KYB Hooks used in regulated context | Counsel opinion, regulatory correspondence |
Current status: [B] — schema + hook events specified; reference adapter scaffolds exist; first external integration is the proof gate.