QR stands and screens
A stand or a screen at the site shows the QR code. It opens the RoamWorks checkout on the phone, never the eSIM itself.
A QR stand in an arrival hall, a station, or a port. The traveler joins the free Wi-Fi, scans, checks the phone, pays, and installs the eSIM on the spot. No staff and no stock.

A traveler lands after the desk closes, or waits an hour at a gate. A stand sells data with no one on duty. Pick a step to see it.
The traveler joins the free Wi-Fi of the site and scans the stand. The RoamWorks checkout opens in the phone browser.
Before payment, the checkout asks if the phone is unlocked and supports eSIM, and shows how to check. A phone that fails sees why before it pays.
The checkout shows the plans for the trip, and the traveler pays on the phone. The site earns a share of each sale through the stand link.
The install steps open on the same phone, over the site Wi-Fi. The receipt email keeps them for later.
A stand or a screen at the site shows the QR code. It opens the RoamWorks checkout on the phone, never the eSIM itself.
Before payment, the checkout shows how to check that the phone is unlocked and supports eSIM.
After payment, the install steps open on the phone that paid. The receipt email keeps them for later.
Each stand has its own link and QR code, so every sale counts for the site that hosts it.
RoamWorks runs the checkout, the install help, and support. The site hosts the stand.
The RoamWorks team sends the sales by stand, so you see which spots work.
Two checks decide the format. eSIM support varies by model and region; confirm it in the phone settings.
Choose both answers to see the right format.
Compare the formats →Each deep-dive shows it at work for one buyer.
On a long coach, train, or ferry trip, show the plan for the next country after the Wi-Fi login and on screens.
Explore →Use caseHang SIM packs for the top routes next to the till. Staff ask the destination, check the phone, and sell the pack before the gate. A QR stand covers the hours when the shop is closed.
Explore →Buy at partner rates, keep the customer relationship, and agree the support split privately. One catalogue, three commercial shapes.
Wholesale pricing before your retail price.
You decide what the customer pays.
Support, refunds, and volume in the agreement.
Start with one site and two stands, then add the next site.
Tell us your sites: where travelers arrive, where they wait, and where the Wi-Fi is free.
Pick the spots with Wi-Fi and a wait, and the line on each stand.
Each stand gets its own link and QR code. Travelers scan and buy on their phones.
After four weeks, review the sales by stand. Then add the next site.
What to know before the first order.
Yes, at a RoamWorks QR stand in the arrival hall. The traveler joins the free Wi-Fi and scans the stand QR, which opens the RoamWorks checkout, then checks the phone, pays, and installs the eSIM on the spot. For a SIM pack, the traveler goes to a staffed desk.
No. Place stands where the site has free Wi-Fi. The traveler joins it, scans, and installs the eSIM over the same Wi-Fi.
No. A stand sells eSIM only. SIM packs stay at a staffed desk, where staff check the phone and any ID that local rules ask for.
The checkout shows the steps before payment. On iPhone, Settings > General > About shows Carrier Lock. On most phones that support eSIM, dialing *#06# shows an EID.
No. The stand QR opens the checkout, not the eSIM. The traveler installs from the checkout on the same phone.
A share of each sale through the stand link. The partner agreement sets the share.

A sealed RoamWorks travel SIM card with one preloaded plan for one destination. Keep packs in stock, check the phone, and hand one over. The traveler is online on arrival.
Explore →
A one-time code for an eSIM plan, sent by email or placed in the customer account. The traveler redeems it, checks the phone, and installs the eSIM. You hold no stock and print nothing.
Explore →
Match plans to the trip, charge them in your checkout, and deliver the eSIM in your app or by email. One API for plans, orders, and status, with webhooks, a sandbox, and an SDK for in-app install.
Explore →