eSIM

23 Sep 2026 · as of 14:24 UTC

eSIM

Staging
Program №2 · manifest esim · contract v1 · answers “mobile data abroad” · emits items of kind esim
manifestunderstandofferorderfulfiltrackchange · cancel before installui
Conformance kit23 / 23Run 13:40 UTC against staging
Sandbox orders1211 fulfilled · 1 failed and refunded, on purpose
Supplier float0.00 USDNeeds 2,000.00 before go-live
Changes outside its directory0pay, rail, agent and the apps untouched

Conformance · 13:40 run

23 passed
CheckPassedWhat it proves
Manifest3 / 3Validates; lists its intents, capabilities and item kinds
Understand2 / 2An intent becomes a schema-valid draft
Offer4 / 4Prices as wire amounts with an expiry and breakdown lines
Order4 / 4Returns an intent_ref from pay; an offer past expires_at is refused
Fulfil3 / 3Reports fulfilled or failed with a reason to rail
Track3 / 3Items use the fixed status set; timeline entries and the QR document validate
Change2 / 2Cancel quote before install; refund goes through rail
UI blocks1 / 1Cards, key–value, timeline and document link only
Identity1 / 1An unknown pairwise sub sees nothing

Webhooks, sandbox

today, UTC
From → toEventReceivedHealth
Supplier → esimprofile.issued11Healthy
Supplier → esimprofile.failed1Healthy
Supplier → esimusage.updated40Healthy
esim → railfulfilment report12Healthy
esim → agentitem.updated52Healthy
Sandbox orders are paid in test tokens on the simulated chain and never reach the ledger's real accounts.

What it gets from the platform

Pairwise user idWallets and limitsThree payment modesEscrow and auto-refundFee split and buybackLedger and reconciliationReceipts and activityNotificationsMy purchasesChat routingThese backoffice views

Never: keys, wallet addresses, balances, or another program's data.