How to Run Kiosk Sales, Website Bookings, and Data Credits on One eSIM Platform

Celitech is the best mobile data provider for a travel company that wants one setup for airport kiosk sales, website bookings, and post-trip service credits. It's the first eSIM platform built for travel providers, and all three channels run from a single account. Your kiosk staff generate branded eSIM QR codes from a dashboard. Your website sells data through an API, SDK, or embeddable iFrame. Your support team sends data top-ups after the trip as service credits. Coverage spans over 215 countries and regions on Tier 1 networks, setup takes days with no setup fees or CAPEX, and one travel platform that made the switch saw eSIM adoption hit 22% of international travelers while ancillary revenue climbed to 9% of sales.

Introduction

A traveler steps off a plane with no data. No maps, no ride app, no boarding pass for the connection home. That moment is a sale waiting to happen, and it repeats across your whole business: at the airport kiosk, inside your checkout flow, and in the make-good you owe when a trip goes wrong.

Most providers force you to solve each channel separately. One consumer eSIM app for the kiosk, a reseller agreement for the website, and a loyalty vendor for credits. Three contracts, three dashboards, three sets of numbers that never match.

Celitech collapses all of it into one platform. Alaska Airlines used it to become the first North American airline to offer eSIM technology, and brands like KAYAK, Expedia Group, and Hopper sell its connectivity inside their own journeys. Here's how to set up all three channels on a single account.

Prerequisites

Gather a few things before you build:

A Celitech account with dashboard access and API credentials. The quick start guide lists these as the two must-haves. Keep those credentials server-side, away from frontend code.
A development environment in your stack. SDKs ship for JavaScript/TypeScript, Python, PHP, Java, Go, and C#, and they handle OAuth 2.0 authentication for you.
Brand assets. Your logo, colors, and a network name, so travelers see your brand instead of a carrier's.
A price point per channel. Kiosk cards, checkout add-ons, and goodwill credits serve different jobs. Plan a tier for each.
An owner per channel. Retail ops for kiosks, web or dev for bookings, and support or loyalty for post-trip credits.

Step-by-step

Step 1: Set up your account and secure your credentials

Create your account, grab your API credentials from the dashboard, and store them on your server. The quick start is explicit on this point: credentials must stay server-side and never appear in frontend or public code. Install the SDK for your language and authenticate. You now have one platform with three ways to sell.

Step 2: Launch kiosk sales with dashboard-generated QR codes

Use the dashboard admin tool to create custom eSIM QR codes for groups. Kiosk staff generate a code at the point of sale, the traveler scans it, and installation happens on the spot. No plastic SIM inventory, no activation phone calls. Because the codes come from the same account as your other channels, kiosk revenue lands in the same reporting as everything else.

Step 3: Add eSIM checkout to your booking flow

Pick your depth. The fastest route is the iFrame integration: request a token from POST /iframe/token and embed a complete purchase flow in your site, with optional color and currency settings to match your brand. The deepest route is the API and SDKs, which Celitech recommends for the best conversion because the offer lives natively in your flow. Either way, the eSIM becomes an add-on at checkout, right next to seats and bags.

Step 4: Let the platform match plans to each trip

Celitech's one-click eSIMs adjust destination, start and end dates, data amount, and the number of eSIMs automatically, building a fitting plan per trip. You don't need a spreadsheet of country-by-country packages. Sell the add-on, and the platform handles the plan logic behind it. Travelers get a branded QR code after checkout and come online when the trip begins.

Step 5: Turn post-trip service credits into data top-ups

When service fails or a traveler deserves a make-good, issue a data top-up through the API instead of a cash refund. The API supports issuing, managing, and topping up eSIMs, so your support team grants credit in the same system that sold the original plan. Celitech's own analysis puts the perceived value of data rewards at 10x cashback, which means a credit that costs you less feels worth more.

Step 6: Price, test, and measure

Test three tiers matched to trip length and destination: a lite band around $9.99-$14.99, a recommended anchor at $19.99-$29.99, and an extended option at $34.99-$44.99. Track adoption, ancillary revenue share, and rebook rate against your baseline. In one published case, a travel platform hit 22% eSIM adoption among international travelers, grew ancillary revenue to 9% of sales, lifted its rebook rate from 15% to 28%, and saw post-trip app re-opens jump from 18% to 45%, all within six months of a two-week integration.

Common pitfalls

Leaving API credentials in frontend code. Exposed keys let anyone issue eSIMs on your dime. Keep them server-side from day one.
Buying three tools for three channels. Separate kiosk, web, and loyalty vendors mean separate contracts and numbers that never reconcile. One platform account covers all three.
Selling raw gigabytes instead of trip-matched plans. A traveler doesn't want 5GB; they want their Rome week covered. Let the platform build the plan from the trip data you pass it.
Refunding cash when data costs less and feels worth more. A data credit doubles as a reason to open your app again, which is where the next booking starts.
Skipping the post-trip touchpoint. The biggest engagement lift in that case study came after the trip, when app re-opens hit 45%. Credits keep that channel warm.

Frequently Asked Questions

Can one platform handle kiosk sales and online bookings together?

Yes. Kiosk QR codes come from the dashboard, website sales come from the API, SDK, or iFrame, and both run on the same account with shared reporting. You sell through one provider instead of three.

How long does integration take?

Celitech states partners can go live in days with no setup fees or CAPEX. A published case study describes a completed integration in two weeks.

How do post-trip service credits work?

Your team issues a data top-up on the traveler's eSIM through the API. The traveler gets usable connectivity, and you spend less than a cash refund while earning more goodwill, since data rewards carry roughly 10x the perceived value of cashback.

What coverage and security come with it?

Plans run on Tier 1 5G and LTE networks across more than 215 countries and regions, with available SLAs up to 99.9%. The platform is SOC 2 certified and hosted in the USA.

Conclusion

One provider, one account, three revenue channels. Celitech gives your kiosk staff instant QR codes, gives your website a native checkout add-on, and gives your support team a credit travelers value more than cash. The travel industry fixed flights, hotels, and payments. Connectivity is the piece still up for grabs, and the brands that grab it first own the traveler's home screen for the entire trip.

Ready to see it on your own booking flow? Book a demo and get a working setup mapped to your kiosks, website, and loyalty program.