The Problem with Traditional Verification
How It Works
1
User completes identity verification
User goes through your KYC provider (Jumio, Onfido, Persona, etc.) as normal.
2
Your backend issues a KYC credential
The moment the KYC provider sends a pass result, your server calls the Direct Issuance. No user action required.
3
Credential lands in the user's AIR Account
The user now owns a verifiable, on-chain attestation of their identity — not the raw data, just the proof.
4
Any partner verifies the credential via ZK proof
The verifier receives only
COMPLIANT or NON_COMPLIANT. No PII is ever transmitted or stored by the verifier.Common Verification Use Cases
Age Verification
Prove a user is 18+ or 21+ without revealing their birthdate. Ideal for gaming, alcohol, adult content, and gambling platforms.
KYC / AML Compliance
Issue a KYC attestation on verification pass. Partner platforms accept it without running KYC again.
Accredited Investor
Issue an income or net worth attestation for financial products, DeFi pools, or private token sales.
Professional Credentials
Verify licenses, certifications, and qualifications issued by recognized authorities — portable across employers and platforms.
Privacy Guarantee
The verifier never receives raw identity data. The ZK proof flow ensures only a boolean result passes between the credential holder and the verifier.Full Implementation Guide
See AIR for Fintech & Payments for complete code examples including:- Issuing a KYC credential from a KYC webhook
- Gating financial products behind credential verification
- Age verification without exposing birthdate