Skip to main content
Every platform that needs to verify a user’s identity runs its own KYC process and stores a copy of the result. AIR Kit lets you issue a KYC credential once that partners can verify using their Verification Programs. ZK proofs can confirm eligibility without revealing underlying values; additional disclosure requires user approval.

​
The Problem

Every platform that needs to verify a user’s identity runs its own KYC process, stores a copy of the result, and takes on the liability for protecting it. The user goes through the same friction — passport upload, liveness check, waiting period — at every new service they join.The industry has accepted this as the cost of compliance. It isn’t.

​
What Changes With AIR Kit

  • Your customer verifies once — KYC passed at your platform issues a portable credential. Every partner in the ecosystem accepts it without running KYC again
  • Control what verifiers receive — Programs can request ZK proofs of eligibility or specific claims with user approval
  • Your KYC provider doesn’t change — You keep Jumio, Onfido, Persona, or whoever you use. AIR Kit converts their pass result into a portable credential. The verification itself stays with your provider
  • Limit copies of identity data — Raw source documents remain with the issuer or its KYC provider. Encrypted credential payloads may be stored in DStorage, and users control decryption and disclosure. Verifiers remain responsible for protecting any data they receive

​
Use Cases

KYC Portability

Issue a KYC attestation on verification pass. Partner platforms accept it without re-running checks. One verification, ecosystem-wide acceptance.

Age Verification

Prove a user is 18+ or 21+ without revealing their birthdate. The verifier learns only the boolean result — the actual age stays private.

Accredited Investor

Issue an income or net worth attestation for financial products, DeFi access, or private token sales. The verifier never sees the underlying figures.

Professional Credentials

Verify licences, certifications, and professional qualifications. Portable across employers, platforms, and jurisdictions.

​
How It Works

1

User completes KYC with your provider

Your existing flow. Your existing KYC provider. Nothing changes for the user or your team at this step.
2

Your backend issues a KYC credential

The moment your KYC provider returns a pass result, your backend calls on-demand issuance. One call. The credential issues silently — no user action needed.
3

Credential lands in the user's AIR Account

The user can access an issuer-signed credential encrypted to their public key and stored in DStorage. The issuer retains the source documents, while the user controls decryption and disclosure of the credential.
4

Any partner verifies via ZK proof

At a partner service, the user approves the requested disclosure. The partner receives a compliance result and, on success, a Verifiable Presentation containing the approved claims and any required proof.

​
What the Verifier Actually Sees

The following example uses a program that requests KYC status and limited claims with user approval. Other programs can request different disclosures.Try it live: a marketplace learns only that the user passed an ID check.

​
What Compliance Will Ask

Is this GDPR Article 5(1)(c) compliant — data minimisation? Use the minimum claims needed for the check, such as KYC level and isOver18. These derived claims can still be personal data. Credential encryption and user-controlled disclosure support minimisation, but compliance depends on your implementation.How do we handle data subject deletion requests? Revoke the credential to stop future successful checks once its revoked status is available. Handle deletion of source records, encrypted payloads, metadata, and disclosed copies separately. See the Compliance FAQ.Who has access to the underlying identity documents? Raw source documents remain with the issuer or its KYC provider. AIR may store encrypted credential payloads in DStorage.What if a user disputes their KYC result? The dispute process stays entirely with your KYC provider, as it does today. You revoke or re-issue the AIR Kit credential once the dispute resolves.Does AIR Kit have access to our users’ data? Your backend signs the credential and encrypts it to the holder before storage. AIR stores and routes ciphertext and metadata, not plaintext issuer data. The user controls decryption and disclosure; encrypted claims and metadata may still be personal data.

​
Integration at a Glance

​
Next Steps

Full Compliance FAQ

GDPR, CCPA, data residency, and breach liability answers.

Architecture & Data Flow

ZK proof flow explained end-to-end.

Talk to our team

Start a partnership conversation.