Proposed experience / v0.01 / 23 September 2026
One connected experience for buying, installing and looking after an eSIM. The proposed flows, labels and recovery paths, drawn as simple wireframes.
Follow the links between screens. Try the installation choices and payment states. All data and interactions are illustrative; no payments or phone setup are launched.
Based on the flow audit, competitor findings and the accepted installation direction. These are design proposals, not implemented product features.
02 / Purchase
Choose plan + starting balance → pay with chosen method → automatic invoice → same private eSIM page
Starting credit is money for usage, not a fixed data allowance.
Method labels match actual availability. Illustrative amounts are not a price quote.
Invoice opens automatically. Keep the private page available while paying.
View payment wireframe →Your choices remain selected. We could not load availability.
Try loading plans againUpdate the selected credit and total visibly before the user commits. Explain the adjustment beside the method, without a hover-only tooltip.
Keep the existing one payment activation for a known plan and default balance. No compulsory cart, compatibility questionnaire or new confirmation page. No measured time saving is claimed.
03 / Payment + interrupted checkout
Payable → resume existing invoice / Paid → preparation / Ready → install / Unknown → check, without paying again
Order · DEMO-01
Bookmark this page. You will need this private link to return. Anyone with it may access your eSIM details; do not share it.
In the product: Copy link, with copied/failed feedback and selectable text when clipboard access is blocked.
Return automatically to the matching private page when the provider supports it.
Continue to your eSIM →Visible fallback when automatic return stalls. The destination must remain usable without redirect JavaScript.
Show “Payment received” separately from “eSIM ready”. Keep checking and offer an explicit status check and help, without an invented delivery estimate.
Recover authorised status from the order identity where supported. If it is unavailable, show the unknown-state path rather than an endless pending loop.
Backend/provider contract required for status recovery, partial/late payments and safe invoice replacement. Closed windows and delayed callbacks are not evidence of nonpayment. Sample controls only change this wireframe; they do not call payment services.
04 / Accepted installation direction
Ready eSIM → Add eSIM to this phone → native confirmation → data settings → connection help if needed
Preview the device
On an eligible iPhone, start setup here. Your phone will ask you to confirm installation.
Candidate route for iOS 17.4+; provider and device validation required.
Open the target phone’s add-eSIM scanner. Keep this private page on your other screen.
Selectable values + separate copy actions in the product. Show “Copied” or “Could not copy; select the text”. Full activation string remains available.
Native screen wording varies. This is a schematic, not a reproduction of system UI.
Return to your eSIM →Returning to the browser does not prove installation succeeded.
Try your system browser if you opened the page inside another app. QR and manual setup remain available.
Check whether the profile already appears in the phone’s SIM list. Follow plan-specific retry guidance or contact support. Do not delete it as a generic retry.
Check the chosen data line, destination coverage and plan-specific roaming/APN instructions. Installation and a working connection are separate states.
Lead with balance and connection help. Keep details available according to the plan’s reuse restrictions; do not encourage a second installation.
Both iOS and Android handoffs are included. Device detection suggests a route; users can change it. Desktop leads with QR. Android handler coverage, profile eligibility and installation-state meaning remain unverified. Device validation research →
05 / Return to the right eSIM
Saved private link → identifiable eSIM + balance → the relevant action, with that eSIM carried through
Open it from your bookmarks or the place you saved it. It leads directly to your eSIM.
Preview a saved-link visit →Check your browser history and saved checkout details. If you cannot find it, contact support with whatever non-secret reference you still have.
Help with a missing linkRecovery is not guaranteed. No invented account lookup or automatic saved-order history.
Data plan · ID ending 0123
$10.00
Available balance · illustrative
Only show number renewal for an eligible plan with a number.
Bookmark this page and keep the link private. Product copy controls need visible success/failure feedback.
Check the complete private link. If it still fails, get help; you can ask without an order reference.
Contact support →Keep the known eSIM identity visible. Say the balance cannot be loaded, rather than showing a misleading zero.
Try loading balance againAdd silent.link to your home screen to top up this eSIM or order another one next time.
Offer the platform’s available install action, or show the appropriate browser menu instructions. The exact iOS and Android instructions will be validated during implementation.
This installs the web app shortcut; it does not install the eSIM itself.
Not now — continue in the browser
Return to this eSIM’s private page, with authentication if enabled.
Implementation decisions: private-link/start destination, multiple eSIMs, TOTP access and safe caching. Offline should explain that current balance and payment need a connection; cached data must not imply a completed transaction.
Show the originating eSIM explicitly across tabs and payments. Do not select it from whichever order last wrote to local storage. Keep private links and activation details out of support URLs and analytics.
06 / Add credit
Top up balance → amount + payment → pending / credited receipt → same eSIM
Adds monetary credit, not a fixed data package.
Total + currency + any fee shown here
Pay with Lightning →Find this on your private order page. Validate the full ID and display the selected eSIM before enabling payment. Do not silently use another order’s ID.
$10 added · updated balance $20
Illustrative confirmed receipt
Automatic contextual return may show this receipt in the originating private page.
Invalid ID → explain the format.
Lookup unavailable → retry lookup.
Payment outcome unknown → check the existing transaction.
Do not clear the form on a Processing event or ask for another payment before status is known.
Top-up help →Target: two activations plus amount entry when automatic return is supported, versus three including reopening the order. A manual return link still costs three but removes searching. Transaction persistence and confirmed credit need provider/backend support.
07 / Keep your phone number
Prefilled number + current expiry → one-year extension + price → confirmed before/after dates
Current expiry: 23 Sep 2026
Extension: one year
Price: confirmed lookup amount + currency
This extends the number lease. It does not add data balance.
Pay with Bitcoin →Look up eligibility, expiry and price before payment.
Number · ending 4567
Example dates. Show this success state only after authoritative confirmation.
Back to your eSIM →Preserve the number and payment reference. Show pending status without claiming a new expiry.
Check existing payment →A service failure should say “Could not look up this number”, not “Invalid number”. Keep retry and help visible.
Renewal help →Existing number prefill stays. The receipt can complete the task without a mandatory return click. Interrupted transactions and renewal eligibility need confirmation; payment must not promise restoration of a disconnected or reassigned number.
08 / Specialist purchasing
Quantity + credit per eSIM → pay → readiness count → complete CSV, or deliberate partial export
Show plan, total price, currency and delivery format before payment.
Pay with Bitcoin →No new cart required. Payment opens automatically after this action.
Automatic checks continue while preparing.
Demo snapshot; no live provisioning.
This partial CSV excludes 8 profiles still being prepared. Make that choice explicit; keep the order link for the rest.
Export action is illustrative. No credential file is generated here.
If download fails: keep this order open and offer “Try download again”. Do not start a new purchase.
Bulk order help →CSV contains private activation information. Keep it private.
Retain two activations for a default complete order: pay and download. Keep manual status checks available. Progress reporting, readiness and partial export semantics need backend confirmation and bulk-user review.
09 / Coverage + answers in context
One destination choice → compare plan rates → retain choice when buying / task-specific help → return
Compare both plan families for Japan.
Rate placeholders only. Real coverage and prices must come from current product data.
Choose a plan →Retain the country. Offer retry and help; do not display missing rates as zero.
Device compatibility → direct/QR/manual setup → data-line and plan-specific connection instructions.
Back to installation →Check your saved link and payment reference. Unknown payments need a status check, not another purchase.
Back to payment →Explain credit versus a number lease. Show how to find the eSIM ID (IMSI).
Top up balance · Renew number[Verified support contact goes here.] Explain the issue; include a non-secret order/payment reference if available. A missing reference should not block asking for help.
Wireframe placeholder, not an active support channel. Do not send activation codes or private links automatically.
One country choice applies to both plan families and should survive the return to purchase. No forced help detour. Product help content and external destinations must be verified during implementation.
10 / Additional brief items
Concept wireframes for the remaining requested capabilities in the brief. These need endpoint and policy confirmation; the tracker stays open.
$4.20
Illustrative usage charges, distinct from top-up payments.
No charges in this period, or “Could not load spending” with retry. Never turn a load failure into a zero total.
Number ending 4567 · eligible plans only
[Full incoming message appears here, inside the private page.]
Optional phone delivery, if supported by the endpoint. Clearly explain what switching it changes; do not imply website messages stop.
Include no-messages, refresh failure and unavailable-for-this-plan states.
Authenticator verification before viewing protected order details.
Wrong code → retry.
Lost authenticator → agreed recovery process.
Recovery, setup confirmation and server-side enforcement must be defined before release. Hiding a page with front-end code is not access control.
The overall UX and visual refresh (04 / 07) run through these wireframes. Post-checkout continuity (01) is covered in Payment, and direct installation (08) in Install. This page proposes layouts, not backend implementation.
11 / Wording across the experience
| Current / location | Proposed wording | Why |
|---|---|---|
| Buy | Buy eSIM | Name the product. |
| Pricing | Coverage & rates | Country availability and usage cost. |
| Top up | Top up balance | Adds money, not a data bundle. |
| Renew | Renew number | Extends the number lease. |
| Bulk Order | Bulk orders | Clear, consistent sentence case. |
| FAQ | Help | Requires task guidance and a real support route. |
| No public management entry | Manage eSIM | Explain saved-link access and the missing-link path. |
| IMSI | eSIM ID (IMSI) | Explain where to find it; retain the precise identifier. |
| Payment icons / pay with | Pay with Bitcoin / Lightning / Monero | Readable, method-accurate actions. |
| Activation details / QR | Add eSIM to this iPhone / Android phone Show QR code · Enter details manually | Lead with setup; keep alternatives visible. |
| Private order link | Save your private eSIM link | Explain future access and privacy. |
| Check now | Check payment status | Use “Check preparation status” after payment. |
Review labels for comprehension and test all eight journeys with the same start/end points as the current flow. Check multiple eSIM tabs, unavailable storage, unknown payments, copy failure and native setup cancellation. Browser checks validate this document; actual payment and device behaviour still need separate validation.