Adding lounge and eSIM rewards to a loyalty program connects two processes. Your program authorizes the member’s points spend. The travel service allocates or issues the benefit they have selected.
Stoa supports lounge bookings, prepaid benefit packages and package-based eSIM issuance through its partner API. Your loyalty system remains responsible for its reward currency, member balances and points rules.
The integration must connect those records so the member understands what they have redeemed and how to use it.
Choose rewards that fit your members’ trips
Start with the travel patterns and needs of the members you intend to serve.
A lounge reward must fit an airport and journey the member can actually use. A travel-data reward needs suitable destination coverage, validity and device compatibility.
Consider when members discover the reward. Someone planning a trip has different needs from a member browsing the catalog without travel dates.
Practical rewards already exist in established loyalty programs. Finnair lists lounge access and travel extras among the ways members can use Avios. Finnair’s redemption options.
That example supports the usefulness of offering choices beyond award flights. The appropriate reward mix for your program should come from your own members’ needs and commercial arrangements.
Set the points price and explain what it buys
Your program decides the points price, any customer contribution and the funding behind the reward.
Make the redemption unit clear. A member needs to know whether their points buy a specific issued pass or a package containing benefits they will redeem later.
For example, an illustrative reward could exchange 2,000 points for a package containing one lounge entry. The points price is hypothetical. The package allocation and the eventual lounge-pass issuance are separate events.
Show the included benefit, restrictions and redemption deadline before the member confirms.
Stoa’s allowance and package balances count travel-benefit entries. Keep those counts separate from your member’s points balance.
Agree responsibility for each part of the journey
Use a responsibility table during integration planning.
| Responsibility | Owner to establish |
|---|---|
| Member identity, tier and eligibility | Your loyalty program |
| Points balance and conversion rules | Your loyalty program |
| Authorization and recording of points spend | Your loyalty program |
| Lounge catalog, booking and pass issuance | Stoa’s configured booking services |
| Package entries and eSIM issuance | Stoa’s configured package services |
| Display of points price and reward terms | Your customer-facing product |
| Points restoration after an eligible reversal | Your loyalty program’s integration |
| Traveller support and escalation | Agreed between your team and Stoa |
This table should become part of the launch scope.
It also helps support teams answer a common question: whether the problem concerns a points transaction, a travel booking or the delivery of the benefit.
Map the complete redemption journey
For a lounge reward, the journey could work as follows:
- The member selects a reward and sees its points price.
- Your program checks eligibility and authorizes the points transaction.
- Your integration requests the relevant package allocation or lounge booking.
- The customer sees a confirmation that describes what has been completed.
- An issued pass is delivered or made accessible when available.
- Your records connect the member’s points transaction with the travel reference.
The exact moment when points are reserved or deducted is a decision for your existing system and integration.
For package-based rewards, the first confirmation may mean the member now holds entries for later redemption. It should explain how to choose a lounge or request the included eSIM.
Stoa returns a hosted redemption link for a prepaid package. Partners can place that link in their app or email, allowing the traveller to select and redeem the included benefits.
Purchasing the package issues neither a lounge pass nor an eSIM immediately.
Handle pending outcomes without confusing the member
A booking request can remain unresolved while issuance is confirmed or reconciled.
Keep the member informed with a clear pending state. Retain the original points transaction, package and booking references so the teams can investigate the same attempt.
Your integration should also define what happens to the member’s points during that period. The customer should be able to see whether their spend is awaiting confirmation or has completed.
Use the original request identity when recovering an unresolved redemption. Starting another eSIM request can consume another entry and issue another SIM.
Write cancellation rules for each benefit
A single refund promise is unsuitable for benefits with different fulfilment rules.
| Benefit or event | Current behaviour to account for |
|---|---|
| Eligible unused lounge booking | Successful cancellation can restore its wallet funds, allowance or package entry |
| Used lounge pass | The booking is no longer cancellable through the normal unused-pass flow |
| Issued eSIM | Non-refundable through Stoa’s current partner API |
| Package approaching expiry | Its redemption deadline must be communicated clearly |
| Unresolved issuance | The original attempt needs confirmation or reconciliation |
A restored package entry is a travel-benefit adjustment. Your loyalty system must apply any corresponding points restoration under the program’s policy.
There is another important distinction for package rewards: the deadline for requesting a benefit and the validity of the issued benefit can differ. Explain both where they affect the member’s plans.
Pilot with a defined group and measure completed rewards
Start with a member group whose eligibility and travel needs are understood. Agree the reward catalog, funding and support responsibilities for that pilot.
Measure:
- Eligible members who see the offer.
- Members who allocate points to a reward.
- Packages allocated and entries redeemed.
- Lounge passes issued and visits recorded as redeemed.
- eSIMs successfully issued.
- Pending or failed redemptions.
- Support contacts and resolution outcomes.
Each measure describes a different stage.
A points transaction alone does not establish that the traveller received the benefit. An issued lounge pass does not establish that it was used. An issued eSIM does not establish installation or data consumption.
Compare those stages before expanding the program. Measure any effect on member engagement or retention using your own program data.
Common questions
Does the program need a new points system?
The integration should be scoped around your existing system’s ability to authorize spend, record transactions and handle reversals. Stoa supplies the travel-booking and benefit-fulfilment capabilities.
Are Stoa’s package entries the same as loyalty points?
They are separate. Package entries represent available travel benefits. Your loyalty program defines how its points convert into those benefits.
What happens if a redemption fails?
Identify whether the outcome is definitively failed or still unresolved. Reconcile the original travel request, then apply the appropriate points treatment in your program.
Explore Stoa’s travel rewards for loyalty programs.
Discuss travel rewards with Stoa. Bring your current points journey, proposed rewards and cancellation rules so responsibilities can be agreed before launch.


