Plenty of businesses know about eSIMs. These digital cards install on your phone, work nearly instantly, save money on roaming, and provide extensive coverage. And although these are well-established facts, not everyone looks at them from a technical perspective or researches how they work.

In reality, eSIMs are a bit more complex than they may seem. There’s a lot more going on in the background, and it’s important to understand the technical underbelly, especially for becoming an eSIM reseller or a white-label MVNO. This is also nearly a requirement for providing proper support or committing to an API integration.

In this guide, we’re going to break down everything tech-related behind eSIMs: SM-DP+, SM-DS, eSIM profiles, how they are created and delivered, and explain why the tech behind eSIMs matters for business.

What Is an eSIM, Technically?

Let’s start from the beginning. Every eSIM is made of two parts: a chip and a profile, plus an ID number that ties them together. 

• eUICC. The hardware: a chip that securely manages downloaded software, or the eSIM profile. It can be a separate component or built into the device's main processor. 
• EID. A unique number assigned to each eUICC. Support teams use it to confirm a device supports eSIM and to see which device a profile was issued to. Providers use it to lock each profile to one specific chip. 
• eSIM profile. The profile holds what a SIM card used to carry: the operator's data, the credentials to access its network, and the apps that connect the device. Each profile has its own ID (ICCID), and one eUICC can store several profiles. 

When you or your customer installs an eSIM, the provider sends the profile over the internet fully encrypted, so that only the chip with a particular EID can open it. Once it's installed and switched on, the device can connect to the operator's network, usually without any extra setup. 

The eSIM Ecosystem: Who Does What 

As the last paragraph made clear, an eSIM doesn’t appear on the device by itself. In fact, several parties are involved, all according to GSMA specs. They perform the following roles: 

Because GSMA sets telecom standards, they’re also an important part of the ecosystem. This organization represents the interests of 1,000+ mobile operators. It writes the industry rules and performs security checks. Although not strictly compulsory, their guidelines and policies regulate quality and indicate a stable, reliable telecom product if accredited and tested by the organization. 

But ultimately, only the last row really matters for resellers or white-label MVNOs. You don’t operate this chain, and all of the components sit outside your direct oversight or responsibilities. Yet, this can help properly troubleshoot future issues. 

What is an SM-DP+?

Subscription Manager - Data Preparation+ (SM-DP+) is the server that turns the operator’s plan into an eSIM profile and delivers it to the device. It generates, manages, and protects all profiles requested by the operator. It's run by the operator or by a specialist provider on its behalf. 

When an order comes in, the SM-DP+ packages and encrypts the profile, then locks it to one chip using that chip's EID. The customer then gets an activation code, usually a QR code, containing the SM-DP+ address and a reference to their order. If the QR code won't scan, phones like the iPhone let users type the details in by hand. That's why "SM-DP+ address" is such a common support question. 

Some profiles won’t even need the code at all, and that’s where Subscription Manager - Discovery Service (SM-DS) comes into play. It works like a notice board: the SM-DP+ posts a note saying a profile is waiting for a specific EID and where to collect it. If it finds one, it goes straight to that SM-DP+ to download the profile, and the user still has to confirm before anything installs. 

There’s one central Root SM-DS, managed by GSMA. Operators can also run their own SM-DS, which passes the notes to the root. The catch is that the operator has to know the device's EID in advance. That's why this route is typically used when a device is sold together with its plan. 

LPA and How It Helps with eSIM Installation

The Local Profile Assistant (LPA) is the eSIM software that connects the phone to the rest of the eSIM system. Each device maker builds it themselves, and that’s why adding an eSIM looks slightly different on an iPhone than on a Samsung or Pixel. It runs either on the eUICC chip or the phone’s operating system.

The LPA has three jobs:

• Downloading. When a customer scans a QR code, the LPA reads the SM-DP+ address from the activation code and connects to that server over a secure link. First, it downloads the whole locked profile in one go, then it feeds it into the chip in segments. It's only a courier, though. The SM-DP+ and the eUICC talk through their own end-to-end encrypted channel and allow the profile to open on a particular device.
• Discovering. When no QR code is involved, the LPA checks the SM-DS for a waiting profile. It can also use a default SM-DP+ address that's pre-set on the chip.
• Managing. It gives the user the screens to list, nickname, enable, disable, and delete profiles.

After a profile is enabled, disabled, or deleted, the LPA can notify the operator, so the provider's systems stay in step with the phone. 

For resellers, the practical point is to always give customers both a QR code and the manual details, because they work on every phone. App-based installs and one-tap activation depend on the platform and on carrier support. Apple's own troubleshooting asks for the device's IMEI or EID, so ask for them early in a support ticket too.

How an eSIM Profile Is Created and Delivered 

Now that we’ve discussed the important profile delivery elements, let’s recontextualize how the customers get them. There’re six distinct steps involved: 

1. The operator places an order. It sends the subscription details, including the network credentials that identify the user, to the SM-DP+ over a dedicated connection. 
2. The SM-DP+ builds a profile. The server builds a Protected Profile Package encrypted for later storage. 
3. The customer gets an activation code. Usually shown as a QR code that contains the SM-DP+ address and a reference to the order. For a code-free install, the SM-DP+ posts a notice to the SM-DS instead. 
4. The phone and server authenticate. The phone's eSIM software (the LPA) connects to the SM-DP+, and each side checks the other's GSMA-issued certificate. The customer confirms the download, and some providers also ask for a confirmation code. 
5. The profile locks onto the chip. The SM-DP+ turns the package into a Bound Profile Package linked to the eUICC as discussed previously.
6. The chip installs the profile. The eUICC checks that the package hasn't been tampered with, installs it in a disabled state, then enables it. Finally, the SM-DP+ receives confirmation that the installation succeeded. 

Why This All Matters for Businesses

Although you won’t run your own SM-DP+ or build an LPA as a partner, understanding how these things work lets you control three things: which provider you pick, how you integrate, and how you support your customers. 

Choosing the Provider

As you’ll be relying on someone else’s infrastructure, it’s only fair you ask about it. Inquire whether the provider’s SM-DP+ was accredited by GSMA. Ask about which operators they work with and to which networks their profiles connect. If you can’t confirm anything with the provider, it indicates poor service quality. 

Integrating 

If you’re going to use the API to build connectivity into an app or create a webstore, a few things will require your attention:

• Every order needs two delivery formats. Your checkout, confirmation email, and app should show the QR code and also the manual details (the SM-DP+ address and activation code). Both work on every phone.
• One eSIM means one device. A profile is locked to a single chip, so your order logic, refund rules, and FAQs need to reflect that. With esimba.ai, for example, refunds apply only to unused eSIMs.
• Profile creation isn't always instant. Build for waiting. For your reference, esimba.ai’s API returns a tracking ID for bundles that take longer to prepare, and it sends signed webhooks when an eSIM's status changes. These include a "running low" event you can use to offer a top-up.
• Code-free installs need the EID first. Sending a profile through the SM-DS only works if you capture the device's EID before the order.

Troubleshooting

The last step is support, and a lot can go wrong here. A common issue is when an LPA can’t read the activation code and customers can’t install the eSIM, but because you know about SM-DP+, you’ve already accounted for that during integration. If you encounter another error like “This code is no longer valid”, the eSIM was bound to the device, and you know you should issue a new one. 

If the customer can’t install an eSIM at all, you know that means the phone doesn’t support it or has no internet connection. You’ll ask for the EID and IMEI, and troubleshoot accordingly. The list goes on, but the main point is that you’ll be able to handle these issues quickly and leave customers satisfied with the quality of support. 

esimba.ai as a Reliable Partner for Newcomers

We are glad we could make things simpler and help you understand how eSIMs truly work without getting too technical. Content is only one way we share such information, and we’ve got plenty of training materials and guidance to offer for partners at esimba.ai. 

If you’re interested in making ancillary revenue through eSIMs or focusing your entire business around connectivity, we’re here to help. We vet all new partners, assign account managers, and ensure they’re fully informed before operations begin. If you need development services or want someone to help with support, our teams are always available. Plus, you’ll get even more content like this over the coming months. 

If you want a reliable partner with 15+ years of industry experience to guide you through the entire process, contact us today by clicking the button below.