What You Can Build
- KYC credentials — Issue a verified identity attestation the moment a user passes KYC; partner platforms accept it without re-running the check
- Income / accreditation proofs — Issue an “Accredited Investor” credential backed by income verification, provable via ZK proof
- Compliance gating — Gate DeFi pools, financial products, or high-value transactions behind credential checks
- Age verification — Prove a user is 18+ or 21+ without revealing their birthdate to the verifier
- Cross-border compliance — One credential, accepted at every partner service in the ecosystem
Architecture
Recommended Schema
KYC Attestation
Implementation
Step 1 — Issue KYC credential from your KYC webhook
Step 2 — Gate financial products with credential verification
Step 3 — Age verification gate (no birthdate exposed)
Privacy Guarantee
The ZK proof flow means the verifier receives only a boolean result. No raw KYC data, no PII, no liability for the verifier to store sensitive documents.Examples
KYC Passport — Issuer
KYC provider app: issues credentials once; user carries the proof to other platforms.
KYC Passport — Verifier
Lending platform app: verifies the credential and accepts the proof without re-running KYC.
ZK Age Verification — Issuer
Identity provider app: issues age credential; user proves 18+ without revealing date of birth.
ZK Age Verification — Verifier
iGaming platform app: verifies age-gate (e.g. 18+) via ZK proof; no PII received.
Next Steps
Direct Issuance — Concepts
Server-side issuance without user presence.
Architecture & Data Flow
ZK proof flow end-to-end.
Partner Authentication
JWT signing setup for your backend.
Verifying Credentials
SDK verification reference.