The flow (recommended)
2) Show packages and help the user pick
Packages differ by:
- data allowance (capped vs unlimited)
- validity period (days)
- price
4) Show installation instructions
Retrieve eSIM details, generate a QR code from the LPA string, and show clear steps the user can follow.
The most important “success moment” is installation. Make the QR code easy to scan and keep the instructions short and device-friendly.
What to show in your UI
Coverage browsing
Let the user browse coverage by:- country
- region (multi-country plans)
Package selection
When listing packages, show:- price and currency
- validity (how long it lasts)
- data allowance (capped vs unlimited)
- whether it includes voice/SMS (many plans are data-only)
Package selection tips (for your UI)
Unlimited vs capped plans
Unlimited vs capped plans
If a plan is unlimited, the data quantity may be shown as 0 and the
unlimited flag will be true. Make that obvious in your UI to avoid confusion.Validity is time-based
Validity is time-based
Users expect validity to start at installation or first use. Communicate the exact rule your product uses based on what the API returns.
What to collect and store
After purchase, store:- the eSIM ID (your primary handle for support and “show details” screens)
- package name/summary (so the user recognizes what they bought)
- price and currency
What to show after purchase
Your “eSIM details” screen should show:- installation QR code (generated from the installation string)
- a short “How to install” checklist (device settings path)
- current status
- remaining data (if available)

