eSIM for online travel agencies and booking platforms
Add trip-matched eSIM plans to the booking flow. Keep the OTA checkout and give the guest data before departure.
Short answer: Your confirmation page already knows the destination and the dates. Add a data plan that fits the trip, without sending the guest to another store. The guest pays in your checkout and gets the QR before departure.
- At booking confirmation
- eSIM in your own checkout
- You set the retail price
The booking is confirmed. The data offer comes next.
Four places to put the offer. Pick one to see it in your flow.
Confirmation add-on
Show one to three plans for the booked trip on the confirmation page and email. The guest pays in the OTA checkout.
- Trigger
- Booking paid
- Measure
- Attach rate and revenue per booking
Pre-trip reminder
Send one email or app message before departure. The link opens a checkout with the trip already filled in.
- Trigger
- Departure near and no eSIM
- Measure
- Conversion per send and support contacts per 100 orders
Multi-country bundle
Offer one regional plan when the itinerary crosses borders. The guest installs once and keeps the same plan.
- Trigger
- Itinerary covers two or more countries
- Measure
- Multi-country attach rate and refund rate
Member data perk
Let members redeem points for data or add it to a member rate. The code arrives in the account.
- Trigger
- Member opens the rewards page
- Measure
- Redemption rate and repeat rate
A focused offer for this buyer.
Your confirmation page already knows the destination and the dates. Add a data plan that fits the trip, without sending the guest to another store. The guest pays in your checkout and gets the QR before departure.
Trip-matched plan card for the confirmation page and pre-trip email.
API for catalogue, order, and webhook events. Hosted checkout as a fallback.
Order, attach-rate, destination-mix, and install-status view.
Three numbers to review in a pilot.
- Attach rate on eligible bookings
- Ancillary revenue per booking
- Install completion 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 →- Buyer
- VP or Head of Ancillary Revenue
- Runs it
- Product manager for checkout and post-booking
Keep the OTA checkout. Do not add a full store inside the booking path.
Where this works.
Each deep-dive shows the same solution in one buyer moment.
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.
Map
Map destination, dates, order reference, locale, and currency.
Pilot
Pilot one market with three plans on the confirmation page.
Extend
Add pre-trip email and multi-country bundles. Review attach and support.
Before you choose
Short answers to the common questions. The partner agreement sets the final terms.
Can we show only plans for the booked trip?
Yes. Pass the destination, dates, and order reference, and show one to three plans that fit.
Can we keep our checkout and payment?
Yes. The API returns the plans and order status. The guest stays in your checkout.
Who handles install support and refunds?
Define the first-line owner and the refund window before launch. The API supports order lookup.
Can we start with one market?
Yes. Pilot one market with three plans and review attach rate and support contacts.