- For business
- For developers
The Problem
Carriers spend on KYC at activation, then that verified status expires at the edge of their network. A prepaid subscriber who passed full identity verification at your MVNO is unknown to your roaming partner. Carrier partnerships that could unlock subscriber benefits require bilateral API agreements that take months to negotiate and are rarely worth the integration cost.What Changes With AIR Kit
- KYC travels with the subscriber — Pass once at activation, accept everywhere in the ecosystem. Roaming partners verify the credential without calling your API or receiving subscriber data
- Loyalty tiers become cross-carrier benefits — Issue a Silver or Gold subscriber credential. Partner MVNOs, device retailers, and service providers accept it to unlock benefits — no direct agreement required
- Age-restricted services gated properly — Prove
isOver18at point of service without transmitting or storing a subscriber’s date of birth - Churn intervention without data sharing — Issue a “5-year subscriber” tenure credential. Retention partners can verify loyalty without accessing your customer database
How It Works
1
Subscriber activates and passes KYC
Your existing activation flow. Your existing identity verification. Nothing changes at this step.
2
AIR Kit issues a subscriber credential
At activation success, your backend fires one API call. A credential encoding KYC level, plan type, and age verification lands in the subscriber’s AIR Account. Invisible to the subscriber.
3
Subscriber accesses a partner service
At a roaming partner, MVNO, or retail service, the subscriber authenticates with their AIR Account — the same login they use with you.
4
Partner verifies the requested claims
The partner calls one SDK method. A successful result includes a Verifiable Presentation with user-approved claims and any required proof. Configure the program to request KYC status without subscriber identifiers or documents when those are unnecessary.
What Crosses the Network — and What Doesn’t
This example requests limited claims with user approval. The Verification Program determines which claims are disclosed and whether a ZK proof is required.What Compliance Will Ask
Does this satisfy roaming KYC obligations? The credential attests to the level of KYC completed at your platform. Roaming partners accepting it are verifying that fact — the underlying compliance obligation remains with the issuing carrier.Is subscriber PII transmitted to roaming partners? A ZK proof can confirm KYC status without disclosing MSISDN or subscriber documents. Verification Programs may also request claims with user approval. Limit disclosures to what the roaming partner needs.GDPR: where is subscriber data stored? Raw source documents remain with the issuer. Encrypted credential payloads may be stored in DStorage, while users control decryption and disclosure. Subscriber claims and metadata can still be personal data; assess storage-provider locations and retention as part of your GDPR review.Integration at a Glance
Compliance FAQ
Full GDPR and regulatory answers.
Partner Economics
Revenue model, fee structure, and reward.