eSIM in the booking flow, from the plan card to the QR
Match plans to the booking through the eSIM API, charge them in your checkout, and send the QR before departure.
Short answer: The booking already knows the destination and the dates. The eSIM API turns that into one to three plans, an order when the payment clears, and a QR before departure, without a store in your booking path.
- Plans matched to the trip
- Paid in your checkout
- QR before departure
From the booking to the QR, in your own flow.
How the eSIM API runs in a booking flow: match, pay, deliver, and follow up. Pick a step to see it.
Match plans to the booking
The booking holds the destination and the dates. The catalogue returns the plans that cover every day of the trip, and you show one to three.
- Trigger
- Booking paid
- Measure
- Plans shown per 100 bookings
Charge it in your checkout
The plan is a line in your own payment step, at your price. The order goes to the API when the payment clears.
- Trigger
- Guest adds the plan
- Measure
- Orders per 100 plans shown
Deliver the QR
The order returns the QR and the install link. Show them on the confirmation page and in the booking email.
- Trigger
- Order fulfilled
- Measure
- QR delivered per order
Follow up on the install
The order status shows if the eSIM is installed. Two days before departure, send the install steps to the guests who have not started.
- Trigger
- Two days before departure
- Measure
- Installs before departure
How to run it.
01Set up
- Get a test key and call the catalogue in the sandbox.
- Map the destination, the dates, the order reference, the locale, and the currency.
- Pick one to three plans to show for each trip.
02In the booking flow
- Show one plan card on the confirmation page and in the email.
- Charge the plan in your own checkout, at your price.
- Create the order through the API when the payment clears.
03After payment
- Poll the order, or listen for the webhook, and show the QR when it is ready.
- Offer the install link on the same phone where it works.
- Send one install reminder before departure.
04Support
- Choose the support split: your team answers first, and RoamWorks handles provisioning and activation.
- Agree the refund rule for an eSIM that was never installed.
Three numbers to review in a pilot.
- Plans shown per 100 bookings
- Orders per 100 plans shown
- Installs before departure
The products behind it.
eSIM API
Add eSIM to your product with one API.
See eSIM API →
White-label eSIM
A co-branded eSIM store for large platforms.
See White-label eSIM →- Keep your checkout. Do not put a full store inside the booking path.
- Show the plans that fit the trip, not the whole catalogue.
- The QR comes after payment. Never print it.
Online travel agencies
Add trip-matched eSIM plans to the booking flow. Keep the OTA checkout and give the guest data before departure.
See the solution →You set the retail price.
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.
From first step to first order.
Start with a short pilot. Review it, then add the next desk, route, or market.
Sandbox
Connect the catalogue and run test orders with a test key.
Pilot
Pilot one market with three plans on the confirmation page.
Extend
Add the booking email and more markets. Review orders and installs.
Before you choose
Short answers to the common questions. The partner agreement sets the final terms.
Do we need to build a store?
No. Show one to three plans on the confirmation page, charge them in your checkout, and create the order through the API.
How does the guest get the eSIM?
After payment, the order returns the QR and the install link. Show them on the confirmation page and in the booking email.
Is there a sandbox?
Yes. Test keys and sample plans let you run orders end to end before you go live.
Can we offer a co-branded store instead?
Large platforms can use a co-branded store with their brand. Most start with plans in the booking flow.