CoverageBrandTalk to sales
Home/Use cases/eSIM on the e-ticket
Rail and coach operators

eSIM on the e-ticket, from the checkout to the border

Match the line to one plan, sell it in your ticket checkout, and put the install step in the e-ticket.

Short answer: A ticket already knows the line, the date, and the countries on the route. The eSIM API turns that into one plan in your checkout, an order when the payment clears, and an install step in the e-ticket.

  • One plan for the line
  • Paid with the ticket
  • Installed before departure
The flow

The line sets the plan. The e-ticket carries the install.

How the eSIM API runs in a ticket checkout: the line, the checkout, the e-ticket, and the trip. Pick a step to see it.

01 / Step

Match the line to a plan

The line holds the countries in route order. One regional plan covers a line across a border, and a local plan covers one country.

Trigger
Passenger picks a line
Measure
Cross-border tickets with a matched plan
Playbook

How to run it.

01Set up

  • List the lines that cross a border or end at an airport.
  • Map the line, the countries, and the dates to the order.
  • Connect the order API in the sandbox with a test key.

02In the ticket checkout

  • Show one plan for the countries on the line, next to the seat and the bag.
  • Charge it in your checkout, at your price.
  • Create the order when the payment clears.

03Before departure

  • Put the install step in the e-ticket email and the app.
  • Tell the passenger to install on Wi-Fi before departure.
  • Send one reminder the day before departure if the eSIM is not installed.

04Support

  • Choose the support split for failed installs and refunds.
  • Keep SIM packs at the ticket desk for walk-up passengers.
Measure

Three numbers to review in a pilot.

  1. Plans shown per 100 cross-border tickets
  2. Orders per 100 plans shown
  3. Installs before departure
Behind it

The products behind it.

What to pass
LineCountries on the routeTravel datesBooking reference
Good to know
  • On a line inside the EU roaming area, offer the plan to visitors from outside the EU.
  • The signal can drop at the border and in tunnels, so the passenger installs before departure.
  • Ticket platforms that resell your seats join through the OTA setup.
The solution

Rail and coach

Add a data plan to the e-ticket for lines that cross a border or end at an airport. Keep SIM packs at the ticket desk for passengers who buy on the day.

See the solution →
Commercial model

You set the retail price.

Buy at partner rates, keep the customer relationship, and agree the support split privately. One catalogue, three commercial shapes.

01
Partner rates

Wholesale pricing before your retail price.

02
Your retail price

You decide what the customer pays.

03
Private terms

Support, refunds, and volume in the agreement.

Pilot

From first step to first order.

Start with a short pilot. Review it, then add the next desk, route, or market.

01

Sandbox

Connect the order API and run test orders.

02

Pilot

Pilot two cross-border lines in the ticket checkout.

03

Extend

Add the reminder and more lines. Review orders and installs each month.

Start a pilot
Answers

Before you choose

Short answers to the common questions. The partner agreement sets the final terms.

Last updated 28 October 2026 · Reviewed by Roamworks
What if the data stops at the border?

The passenger checks that data roaming is on for the eSIM line. The install steps in the e-ticket email show how.

Can we keep our checkout?

Yes. Show the plan in your checkout and create the order through the API. The passenger stays in your flow.

Can a ticket platform sell the same plan?

Ticket platforms that resell your seats join through the OTA setup.

What about passengers who buy at the station?

Keep SIM packs at the ticket desk for walk-up passengers. Staff check the phone first.