eSIM next to the seat, from the PNR to the install
Map the itinerary to one plan, sell it next to the seat and the bag, and deliver the install step at check-in.
Short answer: The PNR already knows where the passenger goes and when. The eSIM API turns it into one plan next to the seat, an order when the payment clears, and an install step at check-in.
- One plan from the PNR
- Paid with the seat and the bag
- Installed before boarding
One plan from the PNR. Installed before boarding.
How the eSIM API runs in an airline booking: the PNR, the extras page, check-in, and landing. Pick a step to see it.
Map the PNR to one plan
The PNR holds the destination, the connection points, and the dates. One local or regional plan covers the trip.
- Trigger
- Booking created
- Measure
- Itineraries with a matched plan
Sell it on the extras page
The plan sits next to the seat and the bag, in the booking currency. The order goes to the API when the payment clears.
- Trigger
- Passenger opens the extras page
- Measure
- Orders per 100 plans shown
Install step at check-in
The check-in email and the app show the install step. The passenger installs on Wi-Fi before boarding.
- Trigger
- Check-in opens
- Measure
- Installs before boarding
Online on landing
When the plan is active, the app says so, with a help link for the install steps.
- Trigger
- Flight lands
- Measure
- Help requests per 100 orders
How to run it.
01Set up
- Pick one route group and one direct channel.
- Map the PNR fields to the order: the destination, the connection points, and the dates.
- Connect the order API in the sandbox with a test key.
02In the booking path
- Show one plan next to the seat and the bag, in the booking currency.
- Charge the plan in your own payment step.
- Create the order when the payment clears, and keep the order reference with the booking.
03Before departure
- Show the install step in the check-in email and the app.
- Tell the passenger to install on Wi-Fi before boarding.
- Listen for the order webhook to show the status in the app.
04Support
- Choose the support split for failed installs and refunds.
- RoamWorks handles provisioning and activation.
Three numbers to review in a pilot.
- Plans shown per 100 bookings
- Orders per 100 plans shown
- Installs before boarding
The product behind it.
- Data only. On a dual-SIM or eSIM phone, the passenger keeps the home number.
- Check the route list before the offer goes live.
- Onboard Wi-Fi is a separate service.
Airlines
Add arrival data to the direct booking, check-in, and loyalty journey. The passenger installs 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 order API and run test orders with a test key.
Pilot
Pilot one route group in one direct channel.
Extend
Add check-in and the app. Review orders and installs.
Before you choose
Short answers to the common questions. The partner agreement sets the final terms.
Can we start without a change to the reservation system?
Yes. Start in the booking engine: read the itinerary, show one plan, and create the order through the API.
Which plan fits a trip with a connection?
One plan covers the destination. A long stopover in another region can need a regional or global plan.
When does the passenger install?
Before boarding, on Wi-Fi. The check-in email and the app show the install step.
Who handles a failed install?
You choose the support split. Your team answers first, and RoamWorks handles provisioning and activation.