eSIM company setup Turkey is not a single licence application. “eSIM” is a technology and delivery method; the regulatory question is what electronic communications service the business will actually provide. A travel-connectivity reseller, software/platform provider, Sanal Mobil Şebeke Hizmeti (SMŞH/MVNO) operator, internet service provider and infrastructure operator can fall into different BTK categories.
For a 2026 launch, use this sequence: define the service → decide whether BTK authorisation is required → select the exact authorisation type → design the Turkish company and articles around that authorisation → secure any host-operator/access arrangements → build the technical and subscriber-compliance stack → notify/apply to BTK before starting the regulated service.
Last reviewed: 17 September 2026. BTK’s current authorisation, CEVHER application and paid-in-capital requirements were rechecked against the Authority’s live guidance.
Quick Answer: Is There an “eSIM Licence” in Turkey?
No. BTK authorises electronic communications services, networks and infrastructure under the Electronic Communications Law. The licence/authorisation owner is the underlying service—not the fact that a customer receives a SIM profile digitally.
| Business model |
First regulatory question |
Potential route |
| Branded mobile service without own radio spectrum |
Are you offering mobile electronic communications to subscribers over a host operator’s network? |
SMŞH / Sanal Mobil Şebeke Hizmeti may be the relevant BTK category. |
| Internet access provider |
Are you providing internet access as an electronic communications service? |
Internet Service Provider authorisation may apply. |
| Telecom infrastructure |
Will you build/operate infrastructure for electronic communications? |
Infrastructure authorisation / relevant usage rights may apply. |
| eSIM software / profile-management technology |
Are you only supplying technology to authorised operators, or directly providing communications to end users? |
Technology-vendor role may differ from operator authorisation; analyse the actual service. |
| International/travel connectivity resale |
Who is the authorised operator, whose IMSI/network is used, and does the model amount to a service offered in Turkey? |
Do not assume an overseas eSIM model can be copied into Turkey without BTK analysis. |
BTK’s current authorisation categories and definitions are published in its Electronic Communications Services, Networks and Infrastructure definitions.
1. Start With BTK Classification Before Company Formation
One of the most expensive mistakes is registering a broad “technology/telecom/e-commerce” company first and only later discovering that BTK requires a specialised corporate purpose for the intended authorisation.
BTK’s current application instructions require a company seeking notification or notification-plus-usage-right authorisation to:
- be established as a limited company (Ltd. Şti.) or joint-stock company (A.Ş.);
- be established to conduct only the activities subject to the requested electronic-communications authorisation and activities necessary to perform that service;
- include the relevant electronic communications / telecom service or network/infrastructure activity in its registered articles;
- avoid unrelated business objects in the purpose/scope section when applying under this route.
This is stricter than an ordinary multi-purpose company-formation brief. Build the articles around the intended BTK authorisation before filing MERSIS.
See BTK’s current authorisation application steps.
BTK authorisation can affect the company purpose and structure, so the telecom model should be defined before incorporation.
2. Ltd. vs A.Ş.: BTK Does Not Make A.Ş. the Universal Answer
The old idea that every serious eSIM/MVNO project “must be an A.Ş.” is too broad. BTK’s general notification / usage-right application guidance permits a qualifying Ltd. or A.Ş. applicant, subject to the selected authorisation conditions. Important exception: where the project requires a usage right whose number is limited, BTK’s current application conditions require the applicant to be established as an A.Ş.. Company type therefore has to be checked against the exact authorisation/resource route before incorporation rather than decided from the word “eSIM” or “MVNO” alone.
Choose between them using:
- investor/fundraising plans;
- share-transfer and governance needs;
- public-debt and management-liability considerations;
- capital planning;
- BTK-specific financial/technical requirements for the selected authorisation;
- host-operator and vendor contracting requirements.
Current statutory minimum capital under general company law is TRY 50,000 for an LLC and TRY 250,000 for a standard JSC. Do not reuse the old TRY 10,000 / TRY 50,000 figures.
Separate BTK paid-in capital gate: BTK’s current authorisation application page, citing Board Decision No. 2026/DK-YED/71, states that the applicant company’s paid-in capital must be at least the amount set by the Authority: currently TRY 2,500,000 for OKTH authorisation and TRY 10,000,000 for other authorisations. This is a sector-authorisation threshold and should not be confused with the lower statutory minimum capital required merely to incorporate an LLC or standard JSC. Confirm the selected authorisation category and current BTK amount immediately before incorporation/funding.
For the corporate comparison, see LLC vs Joint Stock Company in Turkey: 2026 Decision Guide.
3. How BTK Authorisation Works
Under Turkey’s electronic communications authorisation regime, companies that want to provide an electronic communications service and/or establish and operate a network or infrastructure must act before beginning the regulated activity.
BTK’s framework distinguishes:
- notification-based authorisation where no specific scarce resource allocation is required; and
- notification plus usage-right authorisation where resources such as numbers, frequencies or satellite positions are required under the relevant regime.
The exact route depends on the selected service and required resources. Do not describe every telecom project as a classic discretionary “operator licence” with one standard application file and one universal approval timeline.
4. What Is Sanal Mobil Şebeke Hizmeti (SMŞH / MVNO)?
BTK currently defines Sanal Mobil Şebeke Hizmeti as mobile electronic communications offered under the operator’s own brand, without a frequency band allocated to that operator, using the infrastructure of a host mobile operator authorised under the relevant mobile regime.
Important points in the current definition:
- the SMŞH operator does not establish its own radio access network;
- it can obtain or build other network elements needed for its service subject to the rules;
- commercial terms for use of the host operator’s infrastructure are negotiated with the host operator;
- if MNC or mobile-number resources are needed, the current framework includes specific host-operator/BTK notification mechanics.
This is why “get an eSIM licence and then choose Turkcell/Vodafone/Türk Telekom” is the wrong sequence. The intended service architecture and host-network relationship are part of the regulatory model.
5. Host-Operator Access Is a Commercial and Regulatory Dependency
An SMŞH business needs a workable relationship with an authorised host mobile operator. BTK’s framework allows the SMŞH operator and host operator to negotiate the terms and conditions of service delivery, subject to electronic-communications law and BTK regulation.
Before spending heavily on the platform, validate:
- host-operator willingness and wholesale model;
- subscriber ownership and onboarding responsibilities;
- numbering/MNC architecture;
- billing and settlement;
- customer support responsibilities;
- network/security interfaces;
- data, traffic and regulatory reporting responsibilities;
- exit/migration and continuity arrangements.
A company registration does not force a host operator to sign a wholesale agreement.
6. eSIM Technical Stack: Do Not Turn Vendor Standards Into Legal Guarantees
An eSIM service may use GSMA-standard subscription-management components such as SM-DP+ depending on the architecture. But the presence of a GSMA-certified platform does not itself create BTK authorisation or prove that the Turkish service model is compliant.
Technical due diligence should cover:
- profile lifecycle and provisioning;
- host-operator integration;
- subscriber identity/activation workflows;
- billing and charging;
- fraud controls;
- network and information security;
- business continuity;
- regulatory reporting and record retention;
- vendor location and data/traffic architecture.
Technical architecture should be designed around the authorised service and host-operator model.
7. International eSIM and Permanent Roaming Need Separate Analysis
Turkey has specific rules concerning electronic identity/IMEI registration and international permanent data roaming. Older commentary sometimes turns these rules into an unsupported statement that “international eSIMs are banned” or that a fixed number of foreign eSIM brands has been permanently prohibited.
Do not build a business plan on that simplified narrative. Instead determine:
- whose IMSI is used;
- whether the user is roaming or receiving a Turkish domestic service;
- how long the device/service will operate in Turkey;
- whether IMEI/permanent-roaming rules apply to the device/use case;
- whether the business is itself offering a regulated electronic communications service in Turkey.
IoT and machine-to-machine models can require a different analysis from short-stay consumer travel connectivity.
8. Subscriber and Consumer Compliance Is Part of the Product
If the company is an authorised operator with subscribers, the compliance stack extends beyond the BTK application. Depending on the service, obligations can include:
- subscriber-contract and identity/onboarding rules;
- tariff/campaign and consumer-information obligations;
- usage notifications;
- complaint/customer-service processes;
- numbering and portability rules where applicable;
- emergency-services obligations where applicable;
- regulatory reporting;
- retention and lawful-request processes.
Do not promise that an app-only onboarding flow is sufficient until it has been mapped to the rules applying to the chosen operator type.
9. Network Security and Personal Data Are Different Compliance Layers
BTK’s network/information-security framework and Turkey’s personal-data rules should not be collapsed into a generic “GDPR-style consent” checklist.
For an operator, map at least:
- BTK network/information-security duties applicable to the authorisation type and scale;
- electronic-communications confidentiality and traffic/location-data rules;
- KVKK legal bases, notices, security and data-subject rights;
- cross-border transfers and vendor access where applicable;
- VERBİS status based on the current exemption/registration rules;
- incident-response and regulatory notification duties.
Explicit consent is not the universal legal basis for every telecom data-processing operation.
10. Foreign Ownership: Separate Investment Law From BTK Authorisation
Do not use “100% foreign ownership is always allowed” as a substitute for a BTK authorisation analysis. The applicant for the relevant BTK route must be a Turkish Ltd. or A.Ş. satisfying the BTK corporate-purpose and authorisation conditions.
Foreign investors can participate in Turkish companies under the foreign-investment/company-law framework, but the shareholder structure, directors, funding, security requirements and any sector-specific restrictions should be checked for the chosen authorisation and transaction.
A Turkish citizen shareholder should not be invented as a universal requirement where the current BTK route does not state one.
11. A Practical Pre-Incorporation Decision Tree
- Write one sentence describing the actual customer service.
- Identify who carries the subscriber contract and who provides connectivity.
- Map the service to BTK’s current authorisation definitions.
- Decide whether notification alone or usage rights/resources are involved.
- Choose Ltd. vs A.Ş. using funding/governance needs and the selected BTK route.
- Draft the articles narrowly enough for BTK authorisation.
- Validate host-operator / wholesale feasibility before committing to launch spend.
- Map numbering, MNC, subscriber, billing and technical responsibilities.
- Build security, consumer and data compliance into the architecture.
- Submit the correct BTK notification/application before beginning the regulated service.
For a regulated telecom project, the company articles should be designed after the BTK service category is identified.
12. What Workon Can Coordinate
Workon can coordinate the Turkish company-formation workstream, foreign shareholder documents, registered-address/workspace setup, bank-account application support and the operational handoff to telecom/regulatory specialists. BTK authorisation, legal opinions, network design, spectrum/number-resource decisions, host-operator negotiations and regulated telecom compliance remain with the competent authority and appropriately qualified telecom/legal/technical professionals.
Key Takeaways
- There is no standalone universal “eSIM licence” in Turkey; the underlying electronic communications service determines the BTK route.
- SMŞH/MVNO is a defined BTK service: mobile service under the operator’s own brand without its own allocated radio frequency, using a host mobile operator’s infrastructure.
- BTK’s general application route can accept qualifying Ltd. or A.Ş. companies, but a limited-number usage-right route can require an A.Ş.; company type must follow the exact authorisation/resource model.
- The articles of association for a BTK-authorised operator must be aligned narrowly with the authorised electronic communications activity.
- Authorisation can be notification-based or include usage rights depending on the service/resources.
- Host-operator access, MNC/numbering and technical architecture are business-critical dependencies for an SMŞH model.
- GSMA/eSIM technology compliance does not replace BTK authorisation.
- Permanent-roaming/IMEI rules should be analysed from the actual IMSI/device/use case, not reduced to “all foreign eSIMs are banned.”
- Subscriber, consumer, security and personal-data compliance continue after authorisation.
No. eSIM is a technology and delivery method; the regulatory route depends on the electronic communications service the business actually provides. An MVNO\/SMŞH operator, internet service provider, infrastructure operator, technology vendor and travel-connectivity reseller can fall under different BTK analyses.
BTK’s current application framework permits a qualifying Turkish limited company or joint-stock company, subject to the selected authorisation conditions. A.Ş. is not a universal requirement, but the company purpose must be aligned with the authorised electronic-communications activity.
Do not confuse ordinary company-law minimum capital with BTK’s sector-authorisation financial threshold. The article states that BTK’s current paid-in-capital requirement is TRY 2.5 million for OKTH authorisation and TRY 10 million for other authorisations under the cited 2026 Board Decision, subject to verification for the exact route before filing.
BTK defines Sanal Mobil Şebeke Hizmeti as mobile electronic communications offered under the operator’s own brand without its own allocated radio frequency, using the infrastructure of an authorised host mobile operator. The host relationship, subscriber model, numbering and technical architecture are therefore part of the regulatory design.
No. Technical standards do not create regulatory authority. The company still needs to classify the underlying service, follow any required BTK notification or usage-right route and satisfy subscriber, consumer, security, data and reporting obligations applicable to the chosen model.
Foreign investors can generally participate in Turkish companies, but the selected BTK route can impose corporate-purpose, capital, shareholder, governance, security and other sector conditions. A Turkish shareholder should not be assumed mandatory unless the current authorisation rules require it.
Current-rule note — 17 September 2026: BTK authorisation type, company-form and corporate-purpose conditions, paid-in-capital thresholds, numbering/resources, host-operator arrangements and technical obligations depend on the actual service model and current BTK rules. Workon can coordinate the Turkish company setup and operational-readiness workstream and, where the project requires regulated telecom, legal, cybersecurity or technical work, coordinate the relevant handoff with appropriately qualified professionals. BTK remains the competent authority for authorisation and resource decisions, and Workon does not issue BTK authorisations or operate telecommunications networks.
