How the sim issuance flow works
Every step is managed by the SDK. Your application calls SDK methods and receives results — the device interactions happen inside the platform layer.
Plan selection
Customer selects prepaid or postpaid. Rate plan options fetched from carrier BSS. SDK manages the UI session state.
Identity verification
Biometric capture — fingerprint or facial scan. SDK sends to the identity verification backend and waits for clearance before proceeding.
SIM type selection
Customer chooses physical SIM or eSIM. SDK branches the session: physical path triggers SIM printer; eSIM path initiates carrier provisioning API call.
SIM print or eSIM provisioning
For physical SIM: SDK controls the SIM printer, deducts from inventory, and prints the card. For eSIM: SDK calls the carrier eSIM API and returns the activation QR code.
Activation and confirmation
SDK posts to the carrier activation endpoint, confirms successful SIM activation, and closes the session with a receipt or confirmation screen.
What the SDK handles
Hardware
- SIM printer / card issuance module
- Biometric scanner (fingerprint or facial)
- Receipt printer
- Card reader (for existing customer lookup)
Integrations
- Carrier BSS/OSS APIs
- eSIM provisioning APIs
- Identity verification backend
Deployed with
Production deployments running sim issuance flows in real environments.
du
SIM issuance, eSIM provisioning, and plan management across 200+ kiosks.
Rakuten Mobile
SIM issuance and plan management via self-service kiosks.
Asiacell
SIM issuance, plan purchases, and top-ups at self-service points.
Airtel
SIM issuance via self-service kiosks.
MTN
SIM registration and self-service mobile features at kiosks.
Digicel
SIM issuance and self-service at kiosks across Caribbean markets.