If you strip away all the “digital SIM” hype, eSIM is still a SIM. The difference is where it lives and how it gets there.

With a physical SIM, your mobile network operator (MNO) hands you a tiny plastic card that already contains your subscription “profile” (your identity on the network, plus security credentials). With eSIM, that profile is downloaded into an embedded chip in your phone called an eUICC. The operator still issues the subscription. The operator still authenticates you. The operator still decides what services you get. eSIM just changes the delivery mechanism.

That is why eSIM adoption is not only a phone story. It is an operating system story.

What actually gets downloaded

When you “add an eSIM,” you are not downloading “data.” You are downloading an operator profile: a packaged set of credentials that lets your device prove, cryptographically, that it is allowed on that operator’s network. That profile behaves like a SIM card, just stored digitally.

Your phone can store multiple profiles (how many depends on the device), but only one is active per SIM slot at a time (many phones support dual SIM with one physical plus one eSIM, or dual eSIM). The practical result: you can keep your “home” operator active while adding a second operator for travel, business, or backup coverage.

The invisible plumbing: RSP in plain English

The GSMA calls this whole download-and-manage process Remote SIM Provisioning (RSP). In the consumer world, the main reference is the GSMA consumer RSP architecture (the SGP.22 family).

Here’s the easiest way to picture the moving parts:

• Your phone has an eSIM chip (eUICC) plus software that manages profiles.
• Your operator (or a provider acting like one) has a secure server that can deliver profiles to devices.
• There is a discovery mechanism so your phone can find the right server and securely request the right profile.

In GSMA terms, you will often see SM-DP+ (Subscription Manager Data Preparation+) and sometimes SM-DS (Subscription Manager Discovery Service). Those names look scary, but the job is simple: SM-DP+ prepares and securely delivers the profile; SM-DS helps devices discover where to fetch it from (when used).

If you have ever typed an “SM-DP+ address” with an activation code, that is, you touched the plumbing directly, even if you did not realize it.

So why do operators care so much?

Because eSIM forces operators to modernize the part of their business that used to be “hand someone a SIM card and register it.”

Once eSIM becomes normal, operators need:

• Digital onboarding flows (in-store, online, app-based)
• Real-time provisioning and entitlement checks
• Fraud controls (since activation can be remote)
• Better customer support tooling (since “my QR code does not work” is the new “my SIM does not fit”)

And yes, it also creates a strategic problem: switching operators becomes easier. That is good for customers, but it means operators have to compete more on experience, coverage, and reliability, not just contracts.

How activation works on real phones

Most people meet an operator eSIM in one of three ways:

QR code activation

The operator gives you a QR code. You scan it, your phone downloads the profile, and you confirm. Apple documents this as a standard path on iPhone, including setup during initial phone onboarding.

In-app or “carrier activation”

Some operators let you activate directly in their app, or via a carrier prompt built into the phone setup. This is basically “QR code, but hidden behind a nicer button.”

Transfer from another device

This is where operators (and OS makers) are trying to remove friction. Apple supports eSIM transfer flows (including cross-device scenarios) depending on carrier support.
On Android, Google’s platform documentation explains how the OS provides eSIM management APIs (and notes eSIM support built into Android starting from Android 9).

The important detail most people miss: these flows still depend on operator readiness. When transfers fail, it is often not because “eSIM is bad,” but because the operator has not fully integrated the process end-to-end.

Who owns the eSIM experience: operator vs OS vs “travel eSIM brands”

Now the market splits into three very different realities that look the same to travelers:

Operator-issued eSIM (your home MNO)

This is your normal phone number and plan, delivered digitally. Best for continuity and services tied to your identity (banking SMS, WhatsApp number stability, iMessage registration, corporate device management).

Travel eSIM providers (often MVNO or reseller models)

These feel like “operators” in the app store, but behind the scenes, they are usually aggregating operator agreements or reselling profiles from partner networks. Their superpower is distribution and UX, not owning radio networks.

eSIM infrastructure and enablers

Companies like Kigen and others build parts of the provisioning stack, best-practice guides, and tooling that operators or IoT players rely on. If you wonder “how can 200 operators support eSIM,” this layer is a big part of the answer.

So when a traveler says “I bought an eSIM,” you have to ask: from whom? A national MNO, a travel eSIM brand, or a business platform. The user experience might look identical. The operational responsibility is not.

Consumer eSIM vs IoT eSIM: the market is quietly splitting

Most people talk about eSIM like it is one thing. It is not.

Consumer phones largely follow consumer RSP architecture (SGP.22 family). IoT and “constrained devices” are moving toward newer frameworks like SGP.32 for eSIM IoT, designed for devices that cannot rely on a human scanning QR codes and tapping “confirm.”

This matters because operators increasingly think in two tracks:

• Consumer: onboarding, churn, multi-SIM convenience
• IoT: massive scale, remote fleet changes, lifecycle management

If you are building travel tech, corporate mobility, or any embedded connectivity product, you are going to feel that split.

Trends operators can’t ignore

A few signals are getting louder:

• OS makers keep pushing eSIM as default. Android’s platform continues to standardize eSIM access and management at the framework level.
• Device makers are comfortable shipping eSIM-forward (and in some markets, eSIM-only) models, which forces operator readiness and better transfer flows.
• The “activation UX” is becoming competitive. Apple’s documentation shows how mainstream QR and transfer workflows are now, and that normalizes the expectation that setup should be fast and boring.

This is the bigger story: eSIM is turning connectivity into software onboarding. That changes how operators win.

Conclusion

The most interesting shift is not that eSIM removes plastic. It is that it exposes which operators have modern, software-grade provisioning and which ones are still built around retail rituals.

In the short term, that creates a weird paradox: travelers often trust “travel eSIM brands” more than traditional operators for the simple reason that the UX is smoother. But the long-term gravity still sits with mobile network operators, because they control the licensed spectrum networks, the core authentication relationship, and the phone-number identity layer that consumers and businesses depend on.

What I think happens next is not “operators lose.” It is “operators that treat provisioning like a product win.” The winners will be the MNOs that make eSIM activation as reliable as a contactless payment, and the partners and enablers that help them scale that globally. GSMA’s consumer and IoT specifications show the industry is standardizing the pipes. Apple and Android show the user expectation is simple, fast setup. The remaining gap is operator execution.