An OTA can introduce a travel eSIM during checkout, after booking or through manage-my-booking. The right starting point depends on what the customer is receiving: a paid benefit package, an included perk or an offer they can redeem later.
For an included benefit, confirmation email and manage-my-booking are practical places to test first. Both keep the offer connected to a confirmed trip and provide space for compatibility and installation guidance.
For a paid package, checkout may be appropriate. The offer needs to explain its value clearly enough for the customer to make another purchase decision.
Start with the model Stoa currently supports
Stoa’s current Distribution API issues eSIMs by redeeming entries from prepaid packages.
A partner can browse the eSIM catalog, select a plan that fits the package’s limits and request issuance. Successful issuance returns installation artifacts and queues a confirmation email.
Package purchase and eSIM issuance are separate events. Purchasing the package allocates benefits; the eSIM is issued when an entry is redeemed.
The current partner API does not provide standalone, individually priced eSIM ordering. Build the offer around the available package plans and agreed commercial configuration.
That gives an OTA several possible product approaches:
- Sell a prepaid travel-benefit package alongside the trip.
- Include a package benefit in a selected holiday offer.
- Allocate a benefit to an eligible customer for later redemption.
The OTA still owns the customer-facing offer and the decision about where to present it.
Compare the three placements
| Placement | Customer task | Design consideration |
|---|---|---|
| Checkout | Complete the trip purchase | Explain the package’s value without making the main booking harder to finish |
| Confirmation email | Review a confirmed trip | Distinguish an allocated benefit from an already issued eSIM |
| Manage-my-booking | Prepare for travel | Keep redemption, installation instructions and support accessible |
At checkout, use a concise offer with the included benefits and price. Link to the details needed to make an informed decision.
In the confirmation email, explain what the traveller has received and what they need to do next. A package redemption link should be described as a way to claim the benefit.
Manage-my-booking can provide a persistent place to return to the offer, check its status and find instructions. Confirm how your integration will retrieve and display that information.
There is a published example of the post-booking approach. Airalo describes Thomas Cook distributing free eSIM vouchers after holiday bookings. Its case study also acknowledges that directly attributing booking gains to the vouchers was difficult. Thomas Cook case study.
Use that example to inform a test. Measure the results of your own offer.
Help travellers choose a plan they can use
Before redemption, explain the destination coverage, data allowance, validity and device requirements.
Stoa’s eSIM catalog distinguishes local, regional and global plans. Prepaid packages can impose limits on data allowance and validity, so the customer’s available choices must fit the package they hold.
Keep two deadlines clear: the deadline for redeeming the package benefit and the issued data plan’s validity period. They describe different parts of the journey.
For an unlimited plan, confirm how any fair-use restrictions will be communicated. Customers need to understand the usable service, including conditions that affect speed or data use.
Device compatibility also belongs before issuance. Airalo’s guidance requires a compatible, network-unlocked device and notes that regional device variants can differ. Device compatibility guidance.
A familiar phone model name alone is insufficient evidence of compatibility.
Treat delivery and installation as part of the product
After successful issuance, Stoa can supply the original installation QR image, manual setup details and available installation instructions. It also provides a hosted eSIM pass page.
Your integration should preserve the supplied installation information and the booking reference. Those details help both the traveller and the support team.
Explain the distinction between issuance, installation and activation:
| Event | Meaning |
|---|---|
| Issued | The eSIM order has been fulfilled and installation details are available |
| Installed | The traveller has added the eSIM to their device |
| Activated | The plan’s activation condition has been met |
Successful issuance does not establish that the traveller has installed the eSIM or started using data.
Activation rules vary. Airalo explains that many plans activate when they connect to a supported network at the destination, while some activate on installation. Use the selected plan’s policy when telling customers when to install it. Activation guidance.
For Stoa’s current partner API, issued eSIMs are non-refundable. Make the relevant terms clear before the customer requests issuance.
Calculate the economics using the actual package cost
For a paid offer, start with the agreed package purchase cost and the customer-facing selling price.
The following example is illustrative. These figures are not Stoa rates.
| Item | Per package | For 200 purchases |
|---|---|---|
| Customer selling price | €12.00 | €2,400 |
| Package purchase cost | €8.00 | €1,600 |
| Assumed payment cost | €0.40 | €80 |
| Assumed support cost | €0.60 | €120 |
| Contribution before other costs | €3.00 | €600 |
This calculation excludes taxes, refunds and other operating costs.
For an included perk, record the cost of allocating or purchasing the benefit under the agreed model. Do not assume an unused benefit creates an automatic refund.
Stoa’s public commercial options include net rates and revenue share. Confirm the applicable package prices, funding arrangements and settlement terms when planning your offer. Stoa pricing.
Measure the placement and the fulfilment separately
Your OTA should record where the offer appeared and how many eligible customers saw it. That information provides the denominator for a meaningful purchase or redemption rate.
Match the resulting package and booking references to your trip records.
Track package purchases, benefit redemptions, successful issuance, unresolved orders and support contacts. Compare the results by placement.
The current Stoa Distribution API does not expose point-in-time eSIM data usage. Do not report issuance as installation or usage.
When an issuance outcome is unresolved, retain the original request reference and reconcile it before creating another order. A replacement request can issue another eSIM and consume another entry.
Common questions
Can an OTA sell a single eSIM directly through Stoa’s current partner API?
The current supported issuance path is redemption of a prepaid package entry. Standalone priced eSIM ordering is not available on Distribution API v1.
When should travellers install their eSIM?
Follow the selected plan’s activation policy and installation instructions. Some plans begin validity on installation; others activate on a supported destination network.
Can travellers buy a top-up from the hosted pass?
The pass provides an assisted top-up request. Eligible top-ups can be purchased through the partner portal. It is not a traveller self-service checkout.
Explore Stoa’s benefits for travel platforms.
Discuss an eSIM offer with Stoa. Share your intended placement, destinations and package model so the offer can be scoped around the supported fulfilment journey.


