Handling Travel SIM Purchases and Connectivity Lifecycle

This page describes the operational phase of Customer X’s travel connectivity service, after the service has gone live.

At this stage:

Customer X has completed the backend configuration
Customer X has integrated its backend systems with the SFT platform using APIs
Customer X operates its own customer-facing portal, which is used to sell and manage eSIM-based connectivity add-ons

The portal is fully owned and operated by Customer X and acts as the single point of interaction for travelers.

Business Context

Customer X is now actively selling travel eSIM connectivity services.

Travelers:

Visit Customer X’s portal
Authenticate and manage their account (handled entirely by Customer X)
Purchase an eSIM with a specific connectivity add-on
Receive a QR code to install the eSIM on their device
Use the connectivity while traveling
Revisit the portal to:
- View remaining balance
- Check add-on validity
- Purchase additional add-ons

Customer X is responsible for handling all backend operations required to support this experience, including:

All interactions with SFT are performed via APIs.

Customer X is responsible for:

Triggering eSIM allocation and activation
Retrieving the eSIM installation data (e.g. QR code or activation details)
Securely delivering the QR code to the traveler through its portal or communication channels

SFT provides the backend connectivity and lifecycle management, while Customer X controls the end-user delivery and experience.