Skip to main content
Carriers run identity verification for every new subscriber, but that verified status stays locked inside each operator’s silo. A prepaid user who passes KYC at one carrier starts from zero at a roaming partner. AIR Kit lets you issue a subscriber credential at activation — so your KYC investment travels with the user across carriers, MVNOs, and partner services.

What You Can Build

  • Subscriber credentials — Issue a verified subscriber attestation the moment a user activates; roaming and partner carriers accept it without re-running identity checks
  • Plan tier credentials — Issue a “Premium” or “Business” tier badge that unlocks partner benefits automatically, with no bilateral API required
  • Device ownership proofs — Issue a verified device credential (IMEI-bound) for device insurance, warranty, and repair partner integrations
  • Churn intervention — Trigger a “Loyalty Reward” credential when a subscriber hits a retention milestone; partner services can verify and honour the benefit
  • Roaming partner verification — Let partner carriers verify a subscriber’s KYC status via ZK proof; no PII crosses operator boundaries
  • Age-gated service access — Gate adult content, gambling, or age-restricted add-ons behind an age credential without storing birthdates

Architecture

Subscriber Credential

Subscriber Loyalty Tier

Never include MSISDN (phone number), IMSI, full name, or address in credentialSubject. Store only attestations and derived factsisOver18, kycLevel, planType. ZK proofs let partner services confirm subscriber attributes without receiving any underlying data.

Implementation

Step 1 — Issue subscriber credential at activation

Your activation system already fires an event when a subscriber passes KYC and activates. Add one Direct Issuance call to that event handler.

Step 2 — Issue loyalty tier on tenure milestone

Step 3 — Verify subscriber KYC at a roaming partner

The roaming partner integrates AIR Kit as a verifier. They call one SDK method — they never receive subscriber PII, only a COMPLIANT/NON_COMPLIANT result plus the KYC level.

Step 4 — Gate age-restricted services

Key Patterns

Privacy Guarantee

The roaming partner or MVNO receives only a boolean result from the ZK proof. No MSISDN, no IMSI, no subscriber identity document data crosses operator boundaries.

Examples

The repo uses fintech and loyalty app names (KYC provider, lending platform, airline, hotel). The same code adapts to telco (carrier, roaming partner) via schema and branding — see each example’s schema.json and the README’s “Adapting to Your Vertical” section.

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.

VIP Status Portability — Issuer

Airline loyalty app: issues tier credential; user carries status to partner brands.

VIP Status Portability — Verifier

Hotel chain app: verifies tier and grants equivalent perks (e.g. room upgrade, lounge).

Next Steps

Direct Issuance — Concepts

Server-side issuance without user presence.

Direct Issuance — API

Full endpoint reference with error codes.

AIR for Fintech & Payments

KYC portability patterns used in financial services.

Architecture & Data Flow

ZK proof flow end-to-end.