EurofinancenewsMonday, June 29, 2026 · Practical guides to notiticias financeiras da europa
Fintech

The Lithuanian EMI License: A 2026 Regulatory Roadmap

A procedural breakdown of the authorization requirements for Electronic Money Institutions in Lithuania, detailing capital thresholds, governance structures, and the 2026 compliance expectations of the Bank of Lithuania.

Fernanda Monteiro
Fernanda MonteiroSenior Macroeconomic Correspondent8 min read
Editorial image illustrating The Lithuanian EMI License: A 2026 Regulatory Roadmap

Lithuania remains a premier gateway for fintechs entering the European Union, but the regulatory environment of 2026 bears little resemblance to the "fast-track" era of the late 2010s. The Bank of Lithuania (BoL) has systematically tightened its oversight, moving away from volume-based authorization toward a rigorous, quality-over-quantity approach. For a fintech targeting the EU single market, the Electronic Money Institution (EMI) license offers the critical ability to issue e-money and provide payment services across member states, provided the institution navigates the authorization phase with precision.

The following steps outline the procedural roadmap for obtaining an EMI license in Lithuania, strictly adhering to the current Rulebook on Activities of Electronic Money and Payment Institutions established by the central bank.

1. Establish the Legal Entity and Capital Structure

Before an application can even be drafted, the company must exist as a legal entity incorporated in Lithuania. The regulatory framework explicitly requires the firm to be a limited liability company (UAB). More critically, the capital requirements serve as the first filter for seriousness. As of 2026, an EMI must hold initial capital of at least €350,000. This is distinct from a Payment Institution, which may have lower capital tiers depending on the services rendered, but an EMI dealing with safeguarding client funds requires this full buffer.

The capital is not theoretical upon submission. The Bank of Lithuania requires proof that at least 50% of the initial capital is paid up prior to submitting the authorization application. The remaining 50% must be paid up within 12 months of authorization. This allocation must be demonstrated through bank statements or a confirmation from a credit institution holding the funds. Furthermore, the source of funds must be transparent. The BoL conducts thorough anti-money laundering (AML) checks on the shareholders themselves, particularly those with qualifying holdings (usually 10% or more). Any opacity in the ultimate beneficial ownership (UBO) structure at this stage will result in an immediate rejection.

2. Compose the Management Body

The competence of the management team is often the deciding factor in the approval process. The Bank of Lithuania requires a Management Body composed of at least two individuals. These individuals must be of "good repute" and possess "sufficient experience." The definition of sufficient experience has hardened over the years; a general background in business administration is no longer sufficient. The BoL seeks specific, verifiable experience in the payments or financial services sector, typically at least three years in a senior executive role relevant to the services the firm will offer.

The application must include detailed CVs, descriptions of responsibilities, and declarations of absence of criminal records for all management body members. The institution must also implement a fit-and-proper policy that will govern future hires. The regulator assesses whether the collective knowledge of the management covers all operational areas: finance, IT security, risk management, and legal compliance. A gap in expertise—such as a team comprised solely of tech founders without a dedicated compliance officer or financial director—will trigger a request for restructuring before the application proceeds. This governance rigor mirrors the scrutiny faced by major banking groups, reflecting the systemic importance payment infrastructure has gained. Comparing stability across different licensing models highlights how governance structures determine long-term viability in the EU market.

Photographic detail related to The Lithuanian EMI License: A 2026 Regulatory Roadmap

3. Develop the Business Plan and Policies

The core of the application is a comprehensive business plan covering a three-year horizon. This document cannot be a generic pitch deck used for venture capital. It must include a detailed breakdown of the target market, competition analysis, and revenue projections. The Bank of Lithuania specifically examines the viability of the business model to ensure the firm does not rely on unsustainable pricing models that could jeopardize consumer funds later.

Alongside the business plan, the firm must submit a suite of policies that form the operational backbone of the institution. These include:

  • AML/CFT Policy: Based on the risk-based approach required by the 5th AML Directive.
  • Safeguarding of Funds Policy: Detailing how client funds will be segregated from the institution's own funds, typically via a safeguarding account or an insurance policy.
  • IT Security and Business Continuity Policy: Outlining the protocols for data protection, incident response, and disaster recovery.
  • Outsourcing Policy: Identifying any third-party service providers and demonstrating that the firm retains full control and regulatory responsibility.

The quality of these policies is scrutinized for copy-pasting. The regulator expects policies that are tailored to the specific risks of the business model. A generic AML policy, for example, will be rejected if it does not address the specific risks associated with the EMI’s intended customer base or transaction types.

4. Conduct the IT Audit and Infrastructure Setup

In 2026, the technological resilience of a fintech is under the microscope as never before. The Bank of Lithuania requires an independent auditor's report confirming the institution's compliance with information security and business continuity requirements before a license is granted. This audit must verify that the IT systems are secure, resilient, and capable of protecting client data against breaches.

The firm must establish a physical presence in Lithuania. While remote work is common, the regulation requires a head office in Lithuania that is effectively managed and capable of hosting regulator inspections. The IT infrastructure, whether hosted on-premise or in the cloud, must meet specific availability standards. If the firm relies on cloud services, the outsourcing contract must guarantee the regulator's right to access data and audit the cloud provider.

The auditor's report is a distinct deliverable. It cannot be produced by the firm’s internal IT staff; it must come from an accredited external audit firm. This phase often causes delays, as rectifying identified security vulnerabilities can take months. The shadow of high-profile collapses in the fintech sector looms large here; authorities are unforgiving of weak internal controls. The regulatory lessons from past compliance failures serve as a stark reminder of why the Bank of Lithuania prioritizes this technical audit over theoretical business models.

5. Submission via the OCSS System

Once the legal entity is formed, capital is allocated, management is vetted, and policies are audited, the application is submitted electronically. The Bank of Lithuania utilizes the Online Company Search System (OCSS) for licensing procedures. The submission must include all documents listed in the "Description of the licensing procedure" published on the regulator’s website.

As of 2026, the licensing fee for a specialized bank (which includes EMIs) is €5,440 (subject to adjustment by the BoL). This fee is non-refundable. Upon submission, the clock starts ticking. The Law on Payments of the Republic of Lithuania states that the regulator must make a decision within three months of receiving a complete application. However, "complete" is the operative word. If the Bank of Lithuania identifies missing documents or requires clarification during the preliminary review, the statutory clock is paused until the deficiencies are remedied.

6. The Supervision and Interaction Phase

The three-month timeline is rarely a passive waiting period. The Licensing Division engages in active dialogue with the applicant. This phase involves written questions and, frequently, in-person meetings with the management team. Regulators will drill down into the logic of the financial projections. They may challenge the assumptions regarding customer acquisition costs or churn rates.

This interaction also extends to a review of the internal control framework. The firm must demonstrate it has an internal audit function independent of the operating units. The regulators will assess whether the Compliance Officer and the Money Laundering Reporting Officer (MLRO) have sufficient authority and direct access to the Management Body.

Applicants often underestimate the depth of this inquiry. It is not enough to have the right documents on file; the management team must demonstrate a command of the regulatory landscape during these interviews. If the team cannot articulate how they would handle a specific data breach or a complex AML suspicious activity report, the application is unlikely to succeed.

7. Authorization and Passporting

Upon a positive decision, the Bank of Lithuania issues an authorization to act as an Electronic Money Institution. The firm is then entered into the public list of electronic money and payment institutions. However, the license itself is only the beginning of the operational reality.

With the Lithuanian license, the EMI gains the right to passport its services to other EU member states. To do this, the institution must submit a notification to the Bank of Lithuania, detailing the member states it intends to operate in and the services it plans to offer. The BoL then communicates this to the relevant host country competent authorities. While the host authorities cannot prohibit the provision of services, they do have the right to take action if the firm acts in breach of the regulations in their jurisdiction. This mechanism is the cornerstone of the single market, allowing a firm licensed in Vilnius to service clients in Rome or Berlin seamlessly. The impact of this integration is particularly visible in markets where legacy banking is slow to adapt. Analysis of open banking adoption in Southern Europe shows how licensed entrants leverage these passporting rights to disrupt local incumbents.

The Post-Licensing Reality

Obtaining the license is a significant achievement, yet it marks a shift from the "project" phase to the "supervision" phase. The Bank of Lithuania maintains ongoing supervision through regular reporting requirements. EMIs must submit periodic financial reports, statistical reports on payment services, and annual financial statements audited by an approved auditor. The regulator also conducts on-site inspections to ensure the reality of operations matches the application.

Furthermore, the regulatory convergence between traditional e-money and crypto-assets is tightening. EMIs looking to expand into the issuance of e-money tokens under MiCA (Markets in Crypto-Assets Regulation) will find that the rigor applied to their initial EMI license serves as the foundation for future authorizations. The standards set by EUR stablecoin regulations are increasingly influencing the general governance expectations for all electronic money issuers, blurring the lines between fiat and crypto oversight.

The cost of compliance in 2026 is structural. It is not a one-time entry fee but a continuous operational expense. The Bank of Lithuania has made it clear that it prefers fewer, more stable institutions over a crowded field of undercapitalized players. For a well-capitalized, well-governed fintech, this creates a competitive moat: the barrier to entry is now high enough to deter low-quality competition, rewarding those who treat compliance as a core competency rather than a bureaucratic hurdle.

Sources

To dig deeper and verify the data, see:

Read next