Embedded connectivity has moved from a telecom pitch deck to a product roadmap.

Fintechs are adding travel data. Airlines are experimenting with eSIMs around booking and loyalty. Rewards platforms are putting connectivity inside their apps. Some consumer brands are going further and launching full mobile plans. The GSMA’s latest compliance work describes eSIM as increasingly foundational across consumer and IoT connectivity.

That creates a slightly awkward problem: just because a company can add connectivity does not mean it should.

A badly placed eSIM feature is not innovation. It is another tab in an already crowded app.

The rush to embed

Revolut was an early proof point. Its travel eSIM made sense because the product sat beside cards, foreign exchange, insurance, lounges and other things customers already use abroad. In 2026, Qonto applied a similar logic to business travel: customers can buy and manage eSIM data in the same app they use for company finances, while admins can assign connectivity to travelling employees.

READ MORE: Qonto Adds Travel eSIMs With Gigs — and Fintech Connectivity Gets More Serious

The market is now moving beyond travel data. Klarna launched a US mobile plan inside its app, and Cash App followed with a $40 unlimited 5G pilot aimed at users already managing recurring financial life through Cash App. These are not random brand extensions. In each case, there is a plausible link between the existing customer relationship and the connectivity problem.

That is the first rule of embedded eSIM: adjacency beats novelty.

The feature test

Before asking which eSIM platform to integrate, a business should answer a harder question: what job is connectivity doing inside the product?

1. Is there a natural moment?

The strongest use cases have an obvious trigger. A customer books a flight. Checks into a hotel. Starts an international business trip. Pays abroad. Receives a travel benefit through a premium account.

Connectivity appears exactly when the user is likely to need it.

Compare that with a grocery app, a general media app or a retailer whose customers travel no more than the population average. An eSIM marketplace may generate some incremental revenue there, but it is hard to call it product strategy. The feature exists because it can, not because the customer journey asked for it.

2. Does it improve the core product?

Good embedded connectivity makes the original service more useful.

For an airline, destination data can reduce the gap between landing and becoming digitally functional. For a business-banking platform, connectivity can sit beside cards, expenses and travel administration. For an OTA, it can extend the booking relationship into the trip itself.

The useful question is not “Could our customers buy an eSIM?” Of course they could. It is “Would having connectivity here make our main proposition meaningfully better?”

If the answer is weak, an affiliate link or travel-benefit partnership may be smarter than a native integration.

3. Will customers blame you when it fails?

This is where many enthusiastic business cases become less attractive.

Once connectivity carries your brand, the customer does not care which upstream operator had an outage, whether the handset was incompatible or whether an APN setting was wrong. They opened your app. They paid you. The problem is yours.

That means evaluating device checks, installation flows, network quality, refund rules, first-line support, escalation and visibility into usage—not merely wholesale data pricing.

The smoother the front end becomes, the easier it is to underestimate the operational mess hidden behind it.

4. Will they use it again?

A one-off travel extra and a genuine product layer are different businesses.

If users travel rarely, discover the feature late or buy only when heavily discounted, deep integration may never earn its keep. Repeat usage, renewal and attachment to a subscription or loyalty tier tell you far more than launch-week sales.

Choose the right depth

Embedded eSIM is not one product architecture.

Platforms such as 1GLOBAL, Gigs and eSIM Go now expose telecom through APIs, while lighter models also exist. Gigs offers hosted no-code flows; 1GLOBAL describes QR-code distribution as an alternative to app integration; eSIM Go supports branded travel-data experiences without requiring a business to build telecom infrastructure itself.

READ MORE: The Hidden Risk of eSIM APIs: Support, Refunds and Failed Activations

A company testing demand can start with a referral, benefit or hosted flow. A travel platform seeing strong conversion can move toward white-label distribution. A fintech or superapp with frequent travellers, strong authentication, payments and product resources may justify a deep API integration. Only a smaller group has a credible reason to turn connectivity into a recurring mobile proposition.

The mistake is jumping directly to the deepest integration because it looks more strategic.

Measure the friction

eSIM proposals are often sold with ARPU, ancillary revenue, and loyalty language. Those metrics matter, but they are incomplete.

A serious pilot should also measure discovery-to-purchase conversion, installation success, activation success on arrival, support contacts per activation, repeat purchase, refunds, and whether connectivity changes engagement with the core product.

READ MORE: eSIM White Label: Launch Your Own Telecom Product

One metric is particularly revealing: how many customers would notice if the feature disappeared tomorrow?

If almost nobody would, the business has added inventory, not capability.

The verdict

The embedded-connectivity market is becoming more credible precisely because companies such as Gigs, 1GLOBAL and eSIM Go are making telecom easier to package, while Revolut, Qonto, Klarna and Cash App are testing increasingly ambitious versions of the model.

But infrastructure availability is not product-market fit.

The winners will not be the apps with the longest list of adjacent services. They will be the ones where connectivity solves a problem that already belongs to the brand. A travel-heavy fintech may have a stronger case than a retailer with ten times the users; an airline may benefit from a simple pre-trip connectivity offer without needing to “become a telco.”

The next phase of embedded eSIM should therefore be less about asking who can launch it and more about who has earned the right to place it inside the customer journey.

For some businesses, connectivity can become a genuine product layer. For others, the smarter strategy is to keep it one click away.