Do You Need a Telecom Licence to Sell eSIMs?

Navy card titled Do You Need a Telecom Licence to Sell eSIMs, contrasting a reseller relying on the provider licence with an MVNO holding authorisations directly.

This is one of the first questions anyone asks before starting an eSIM business, and the general answer is reassuring: reselling connectivity supplied by a licensed operator usually does not require you to hold a telecoms licence yourself, because the licensed party in the chain is your wholesale partner.

The word doing the work in that sentence is “usually”. Regulation is jurisdiction-specific and licensing is only one of several questions. This sets out what actually determines the answer, and which obligations people most often miss.

This article is general information, not legal advice. Telecommunications regulation is jurisdiction-specific, varies considerably between countries, and changes. Nothing here establishes your position in any particular market. What it can do is tell you which questions determine the answer, so that a short conversation with someone qualified is productive rather than exploratory.

The general position, and its limits

  • Reselling a licensed operator's connectivity usually does not require you to hold a licence yourself.
  • That is because the licensed party in the chain is your wholesale partner, not you.
  • "Usually" is doing real work in that sentence. Rules vary by country and change.
  • Licensing is only one of four regulatory questions, and often not the one that bites.
  • This article sets out the questions. It cannot answer them for your situation.

Why resellers are generally outside the licensing regime

The structural reason is straightforward. A licence exists to authorise the provision of communications services, and in a reseller arrangement that provision is being made by an operator who already holds the necessary authorisations. You are packaging and selling their service under your own brand.

Time to launch by business model

ResellerAPI integrationFull MVNO 2-6 weeks4-12 weeks9-24 months Bars drawn to scale in weeks

The timeline gap largely reflects regulatory process. An MVNO carries operator-level obligations; a reseller generally does not.

1licensed party is usually enough in the chain, and it is normally your wholesale partner
0carrier agreements a reseller negotiates directly
2-6weeks to launch as a reseller, against 9 to 24 months for an MVNO

This is also why the timelines differ so dramatically between business models. An MVNO negotiates its own carrier agreements, operates or licenses a core platform and carries operator-level regulatory obligations, which is most of why launch takes nine to twenty-four months. A reseller inherits the licensed position of its partner and launches in weeks.

Four questions, not one

Licensing is the question people ask. It is frequently not the one that creates obligations.

QuestionWhat it coversTypical position for a reseller
Do you need a licence or authorisation?Permission to provide communications servicesUsually not, where you resell a licensed party's service
Must you register or notify?Some regimes require notification rather than a licenceVaries; a general authorisation model may still involve notifying
Are there identity verification rules?Requirements to verify who is using connectivityApplies in a number of markets; often the real obligation
What are your consumer and tax duties?Refunds, terms, advertising claims, consumption taxAlmost always yours, regardless of licensing

Licensing is the question people ask. The last two rows are more often where obligations actually arise.

Identity verification is the obligation people miss. Businesses ask about licensing, get a reassuring answer, and conclude they have no regulatory exposure. In practice, requirements to verify who is using connectivity apply in a number of markets and are a separate question from whether you need a licence. Ask about it explicitly rather than assuming a clear licensing answer covers it.

The fourth row deserves emphasis because it is unaffected by any licensing answer. Consumer protection duties, refund terms appropriate to a digital product consumed on activation, the accuracy of your advertising claims, and consumption tax on cross-border digital sales are all yours as the seller of record, regardless of who holds the telecoms authorisation.

What shifts the answer

These are the factors that determine whether the general position applies to you.

FactorPoints towards no licence neededPoints towards checking carefully
What you provideData-only plans supplied by a licensed operatorVoice, SMS or your own numbering
Your roleReseller of another party's serviceOperating your own core or holding carrier agreements
Where customers areSelling to travellers from your own marketEstablishing local presence or targeting a regulated market directly
Where the service is usedAbroad, on a host operator's networkDomestically, where local SIM rules may apply
Who the customer isConsumers buying a travel planCases where subscriber identity must be recorded
Contractual positionYour agreement states the provider is the licensed partyYour agreement is silent on it

The first row is the most consequential. Data-only resale sits comfortably within the general position in most places. Adding voice, SMS or your own numbering changes the analysis materially and is one of the few genuine reasons a travel connectivity business would need to look seriously at an MVNO structure.

The distinction between where your customers are and where the service is used also matters more than people expect. Selling a Japan plan to a British traveller involves at least two jurisdictions with potentially different rules, and the answer for one tells you little about the other.

Reasonable diligence

Reasonable steps to take

  • Get your provider to confirm in writing who is the licensed party
  • List the markets you will actually sell into, not aspire to
  • Ask specifically about identity verification requirements
  • Keep evidence of where customers are located
  • Take local advice for any market that looks material

Positions that get people into trouble

  • Assuming one country's answer applies everywhere
  • Relying on a forum post or an article like this one
  • Treating voice and SMS as an easy add-on
  • Ignoring identity rules because licensing was clear
  • Not asking the provider to state their position in writing

A practical sequence

  1. Establish who holds the licence

    Ask your wholesale partner to confirm, in writing, that they or their upstream operator hold the relevant authorisations, and that your reselling of their service is contemplated by the agreement. This is a reasonable request and a provider who resists it is telling you something.

  2. Name your actual markets

    Regulatory questions are per-jurisdiction and unanswerable in the abstract. Write down where your customers will be and where the connectivity will be used. Those are two different lists and both matter.

  3. Ask about identity verification separately

    This is where obligations most often arise in practice, and it is a distinct question from licensing. Several markets require verification of who is using connectivity, and the requirement can apply to the retail seller rather than the operator.

  4. Keep location evidence from day one

    Whatever your eventual position, being able to show which sales were made to customers in which markets converts a difficult retrospective exercise into a manageable one. This costs nothing to start and is painful to reconstruct.

  5. Get advice for material markets

    Not for every country you might theoretically sell to, but for any market that represents a meaningful share of your business or that you are actively targeting. The cost of a short professional conversation is small against the cost of being wrong.

  6. Revisit when you change what you sell

    Adding voice, SMS, your own numbering, or a local presence in a market changes the analysis materially. So does moving from reselling to operating your own infrastructure.

Step one is the highest-value action on this list and takes a single email. A wholesale partner should be able to state clearly that they or their upstream operator hold the relevant authorisations and that your resale of their service is contemplated by your agreement. If a provider becomes vague at that question, treat it as information about the provider rather than about the regulation.

Frequently asked questions

Generally no, where you are reselling connectivity supplied by a licensed operator under a reseller or white-label agreement, because the licensed party in the chain is your wholesale partner rather than you. Requirements vary by country and by what exactly you provide, so confirm your position for the markets you actually sell into rather than assuming a general answer applies.
Because an MVNO is providing the service itself: negotiating its own carrier agreements, operating or licensing a core platform, and often holding numbering. A reseller packages and sells a service that a licensed operator is providing. That difference is also most of why an MVNO takes nine to twenty-four months to launch and a reseller takes two to six weeks.
Some regimes require an individual licence before providing communications services. Others operate a general authorisation approach where providers may operate subject to conditions, sometimes with a notification requirement rather than an application. Which model applies, and whether a reseller falls within it, depends on the jurisdiction.
In some markets, yes, and this is a separate question from licensing that people frequently miss. Requirements to verify who is using connectivity apply in a number of countries and can fall on the retail seller. Ask your provider about it explicitly rather than assuming a clear licensing answer covers it.
Materially, yes. Data-only resale sits comfortably within the general position in most places. Providing voice, SMS or your own numbering brings a different set of obligations and is one of the few genuine reasons a travel connectivity business would need to consider an MVNO structure rather than reselling.
Potentially both, plus the country where the connectivity is used. Selling a Japan plan to a British traveller involves several jurisdictions, and an answer for one tells you little about the others. Write down where your customers are and where the service is used, because they are different lists.
Ask them to confirm in writing that they or their upstream operator hold the relevant authorisations, that your resale of their service is contemplated by your agreement, and what identity verification requirements apply in your target markets. All three are reasonable requests, and reluctance to answer is informative.
Yes, and they are unaffected by the licensing answer. Refund terms suitable for a digital product consumed on activation, the accuracy of your advertising and savings claims, and consumption tax on cross-border digital sales are all your responsibility as the seller of record.
For understanding which questions matter, yes. For establishing your actual position, no. Telecommunications regulation is jurisdiction-specific and changes, and the cost of a short conversation with someone qualified is small against the cost of an incorrect assumption. Use general guidance to make that conversation efficient rather than to replace it.
Whenever you change what you sell or where. Adding voice or SMS, taking on your own numbering, establishing a local presence in a market, moving from reselling to operating infrastructure, or entering a market that becomes a material share of your business all change the analysis.

Ask us the licensing question directly

eSIM Island can confirm in writing who holds the relevant authorisations in the supply chain and what applies in your target markets. Tell us where you plan to sell and we will set out the position alongside wholesale pricing.

Book a Free Demo

Or explore the Reseller Program, API Integration and Business Roaming.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>