You can launch a fintech without its own EMI license by limiting its activities to those that do not require EMI authorization or by delivering services through a licensed partner. How to launch a fintech without an EMI license depends on who issues e-money, holds customer funds and executes regulated payments. A partnership does not automatically remove every licensing or compliance obligation. In the United States, there is no single federal fintech license: money transmitter licensing is state-based.
Avoiding a direct license can reduce the regulatory burden of entering a market. The right route depends on what your fintech does, where it operates and which company performs each regulated activity.
This guide explains when payment or e-money activities require authorization, how jurisdiction and EEA passporting shape your options, and what a banking-as-a-service partnership changes. It also outlines the main cost drivers for direct licensing and partner-led models, helping you weigh the trade-offs before choosing how to build.
Key Takeaways
Map what your fintech will do: issuing e-money, executing payments, and providing other regulated services can trigger different authorization requirements.- Compare jurisdictions by permitted activities, capital requirements, and market access, not by headline licensing costs alone.
- EEA passporting can support expansion across member states for eligible EU licenses, while a UK license does not provide EU passporting after Brexit.
- A banking-as-a-service partnership can offer an alternative to direct licensing, but due-diligence and integration obligations may still apply.
- Compare the capital, timeline, and operational demands of an EMI license, banking charter, and partner-led model before choosing your route.
Table of Contents
- Payment and money-transmission activities that require authorization
- What Is a Fintech License and Why Do You Need One?
- Jurisdiction-specific licensing and EEA passporting
- Banking-as-a-service partnerships as an alternative to direct licensing
- Comparing EMI, banking charter, and BaaS costs
- Gemba: Fast time to market embedded banking
Payment and money-transmission activities that require authorization
In the United States, payment services and customer funds can trigger federal and state requirements. There is no single federal fintech license: businesses generally register with FinCEN as Money Services Businesses under the Bank Secrecy Act and obtain money transmitter licenses in operating states. The U.S. Government Publishing Office states that transmitting money without a license is a federal felony. State licensing can take 3 to 12 months per state, and some fintechs need licenses in 40 or more states.
The activity matters more than the app’s branding. Map each step in the flow of funds: who receives the money, holds it, moves it and owes it to customers. In the United States, this helps determine whether a business needs state money transmitter licenses or other registration. Customer funds are not automatically outside regulation just because a partner handles the payment infrastructure.
In Europe, a Payment Institution and an Electronic Money Institution have different permissions. A Payment Institution may provide payment transactions and payment accounts, but cannot issue electronic money itself. An EU EMI can issue e-money and provide related accounts and cards. Initial capital requirements for a European Payment Institution can vary with the services it provides. An EMI using Method D must hold ongoing own funds equal to 2% of average e-money outstanding, according to the European Parliament and Council.
These distinctions shape product design. For example, a fintech that only arranges payment transactions may consider a Payment Institution model, while issuing stored monetary value points toward EMI permissions. Deciding how to launch a fintech without an EMI license starts with identifying which entity performs each regulated activity. A bank’s permissions are different: partnering with a bank does not make the fintech a bank. Define who contracts with users, safeguards funds, executes payments and carries each customer obligation.
Partnerships can change how a service reaches market, but they do not erase every responsibility. A partner-bank or agent arrangement may let a fintech launch in weeks by relying on another company’s license. In the United States, a banking-as-a-service relationship can provide market access without direct licenses in every state. The fintech may still have due-diligence and integration obligations, so the contract and operating model must align.
Payment rails and card programs require more than a technical connection. Access to Visa and Mastercard programs in many jurisdictions depends on compliance and regulatory approval. If you’re considering how to launch a fintech without an EMI license, identify the required payment permissions, the regulated partner’s role and the approvals needed in each market. This clarifies whether the fintech can operate through partners or needs its own authorization.
What Is a Fintech License and Why Do You Need One?
A fintech license authorizes specific financial activities; it is not a universal permission covering every product. Requirements depend on your services, customers, flow of funds and operating jurisdictions.
Fintech License Types and Regulated Activities
License types define which regulated activities a business may perform and under what conditions. A Payment Institution can provide payment services, while an Electronic Money Institution can issue electronic money. A bank operates under different authorization. Product labels cannot replace an assessment of what the business actually does, including whether it holds customer funds, executes payments or provides crypto-asset services.
Before launch, describe each customer journey and identify the legal entity performing every financial step. A business plan should include financial forecasts for the next 3 years. The UK FCA authorization process for an EMI or Payment Institution typically takes 3 to 12 months. Treat authorization scope, capital planning, and launch sequencing as connected decisions, not separate workstreams.
Regulatory Checks and Compliance Obligations
Regulatory checks examine whether a firm can operate responsibly, protect customers, and manage its risks. Capital requirements depend on the authorization and services; AML and KYC controls address customer identification and suspicious activity. Data protection also matters: GDPR fines for lower-tier infringements can reach €10 million or 2% of global annual turnover, whichever is greater.
A sponsor bank does not take on every responsibility. Your fintech remains accountable for its own operations, customer communications, technology controls and the obligations assigned to it in the partnership. Define who collects customer information, conducts KYC checks, investigates alerts, handles complaints and reports incidents. Document responsibilities before integration, then test the handoffs against real customer journeys.
Outsourcing compliance tasks can support delivery, but oversight remains necessary. Set clear service responsibilities, escalation paths, access controls and reporting routines with each provider. UK financial-services advertising is also subject to FCA rules. Google and LinkedIn require license confirmation for UK financial-services advertising, so align campaign claims and account permissions with the firm’s regulatory position.
Risks and Penalties of Operating Without Licenses
Operating without a required money transmitter license can expose a business to enforcement and criminal consequences. The U.S. Government Publishing Office states that transmitting money without a license is a federal felony. It also identifies license revocation as a possible consequence of noncompliance in extreme cases. These risks can disrupt customer access, partnerships and planned market entry.
Before launch, validate the model by mapping the flow of funds, identifying each service and listing every target jurisdiction. Ask qualified legal counsel to assess the activities, entity roles and partner arrangements against local rules. Record the resulting licensing decisions and compliance responsibilities. Alexander Legoshin is the author of this article.
Jurisdiction-specific licensing and EEA passporting
Choose your licensing jurisdiction based on your target customers and the financial activities your business will perform. For a global fintech, assess market access, regulatory scope, tax treatment and advertising rules together.
Selecting a Fintech Jurisdiction
Jurisdiction selection means matching your operating base and licensing plan to your customers, products and expansion goals. Incorporating in one country does not automatically authorize services elsewhere. Compare where customers will hold accounts, which payment functions you need and whether the license supports your planned expansion.
For an EU-focused model, an EU EMI license can be passported across the European Economic Area. A UK license does not provide EU passporting after Brexit, so UK-based fintechs need separate authorization for EU markets. Consider this early: a business targeting both regions must plan for separate regulatory pathways, rather than treating the UK and EEA as one licensing zone.
Corporate tax is another comparison point, not a substitute for licensing analysis. Listed corporate income tax rates include 15% in Lithuania, 0% in Estonia, and 25% in the United Kingdom. Singapore is listed at 17%, Switzerland at 11.9%, and the UAE at 0-9%. The United States is listed at 21% plus state tax, while Canada is 15% plus provincial tax.
Licensing Strategies by Jurisdiction
Licensing strategy means choosing the authorization route that matches the services and markets your fintech intends to serve. It matters because permissions, capital requirements, and expansion rights differ across countries. In Europe, an EMI license requires minimum initial capital of EUR 350,000, while a Payment Institution’s minimum ranges from EUR 20,000 to EUR 125,000, depending on services.
Compare the permission with the product’s core function. If your service issues electronic money, assess an EMI route; if it provides payment services without issuing e-money, assess a Payment Institution route. The UK FCA authorization process for an EMI or Payment Institution typically takes 3 to 12 months. The FCA Sandbox operates in the United Kingdom, offering a separate setting for firms testing financial innovations.
Marketing access also varies by jurisdiction. UK financial-services advertising is subject to FCA rules, and Google and LinkedIn require license confirmation for UK financial-services advertising. Build advertising approval into the launch plan so campaign timing reflects the firm’s regulatory position. A Canada-focused business may also consider that MSB registration with FINTRAC can help fintech companies verify advertising accounts faster.
For each target market, map the required registration, permitted accounts and payment functions, passporting position and advertising conditions. Compare these requirements with your rollout sequence. This shows whether one authorization supports the first launch or whether separate jurisdictions need distinct licensing strategies.
Banking-as-a-service partnerships as an alternative to direct licensing
A banking-as-a-service (BaaS) or EMI-as-a-Service partner can provide regulated infrastructure for a fintech launch. This can change who holds permissions and performs financial activities, but it does not exempt the business model from regulatory analysis.
BaaS and EMI-as-a-Service Benefits
BaaS connects a fintech’s customer-facing platform to services provided through a licensed bank or other regulated partner. EMI-as-a-Service can similarly support products that rely on an electronic money issuer. These models can be useful when you want to test a target market or launch branded accounts without first building a regulated institution.
Those figures don’t settle the commercial case: product scope, partner responsibilities, integration work and the fintech’s operating model all shape the commitment. Before designing the technology around the partnership, define which entity issues funds, processes transactions, serves customers and manages security incidents.
US Fintech Models Without an EMI License
In the United States, models that provide software, customer interfaces or payment orchestration through a licensed partner may operate without holding an EMI license. The structure matters: a fintech that transmits money itself or controls customer funds may face other US licensing requirements. “No EMI license” does not mean “no authorization obligations.”
For a partner-led model, document the customer journey and the movement of funds. Specify whether the licensed partner opens accounts, receives money, executes payments or handles customer balances. Align platform permissions, customer terms and operational responsibilities with those roles. This clarity helps distinguish a technology provider from a business performing regulated financial functions.
Offering Payments Without Fund Custody
A fintech can design payment or wallet features so that a licensed partner, rather than the fintech, receives and holds customer funds. For example, the platform can initiate payment instructions while the partner maintains the account and executes the transfer. Actual control over funds and payment activity can affect licensing analysis.
Map each step from customer instruction to settlement, identifying which entity can access, move or return funds. Clarify the platform’s role in contracts and customer disclosures, then test the flows against exceptions such as failed payments and refunds. A wallet interface alone does not determine whether the fintech acts as custodian.
Crypto services require a separate assessment. MiCA has applied since December 2024, and EU firms providing crypto-asset services have been subject to the MiCA CASP regime since 30 December 2024. A BaaS relationship does not replace the relevant crypto authorization analysis.
Multi-currency accounts and foreign exchange can be delivered through partner infrastructure, with the partner’s role and conversion flow defined in the product design. Trading fees need separate consideration: payment permissions do not automatically cover investment services or crypto trading. Before setting platform fees, identify whether the product only transfers funds or also executes trades, arranges investments or provides crypto-asset services. Those functions can change the regulatory model and partner requirements.
Comparing EMI, banking charter, and BaaS costs
Compare each route by initial capital, application work, launch timing, integration and ongoing compliance. The regulatory minimum is only part of the financial commitment: staffing, technology and operating controls also shape the total.
An EU Electronic Money Institution requires minimum initial capital of EUR 350,000. A typical total capital requirement for an own EMI license is estimated at 1 to 3 million EUR, reflecting a broader planning view than the initial regulatory threshold. These options differ in scope, so compare permissions alongside capital rather than treating the largest figure as a direct like-for-like cost.
Timing changes the cost profile. UK EMI licensing is estimated at 9 to 12 months, Lithuania at 6 to 9 months, and Ireland at 12 to 18 months. A full US or EU banking charter typically takes 12 to 36 months. During authorization and integration, founders must plan for staff, technology, legal preparation, and delayed transaction revenue. A longer process can increase operating needs even before customer activity begins.
Application support is a separate budget line from capital requirements and ongoing compliance expenses. The workload depends on the authorization scope, governance design, financial forecasts and documentation prepared for regulators. Include internal time for responding to questions and maintaining consistent records.
Compare this with the resources required to build and operate an authorized institution, while accounting for partner charges, technology integration and service responsibilities. A partner-led model may shift some infrastructure work, but the fintech still needs to oversee its own operations and customer obligations.
Give ongoing costs equal weight. An EMI must maintain capital and compliance processes, while a partner-led fintech must manage due diligence, integration, monitoring and contract oversight. Assess staffing against actual functions: customer onboarding, AML reviews, transaction monitoring, data protection and incident handling. The functions retained in-house and the systems supporting them are key cost drivers.
Build a comparison using the same assumptions for each route: target markets, projected transaction activity, product scope, and operating responsibilities. Then separate one-time costs, required capital, and recurring expenses. For a partner-led model, discuss your embedded banking model in relation to the services and integration your launch requires.
Gemba: Fast time to market embedded banking
Gemba helps businesses bring branded financial services to market through banking infrastructure, rather than building every capability in-house. Its fast time to market embedded banking offering includes a white-label banking interface, ultra fast bulk payments and global payroll. These services can help your team develop a customer-facing financial product connected to underlying banking services.
This route suits businesses that want branded financial services and are considering a partner-led operating model. Infrastructure supports delivery, but you still need to define which regulated activities your business performs and which permissions apply. Alexander Legoshin is the author of this article.
Visit ge.mba to discuss your embedded banking needs.
Make your operating model a deliberate choice
Choosing how to launch a fintech without an EMI license is more than a way to shorten the path to market. It is a design decision about which functions your company owns, which it delegates and how clearly customers understand the arrangement. Treat the operating model as part of the product, not paperwork to add after building the interface.
Turn the licensing analysis into a business decision: define the customer experience you want to create, identify the activities central to your differentiation and decide where a partner-led structure supports that ambition. Keep the model adaptable as your product, customer base and target markets evolve. Thoughtful architecture can help you focus resources on the capabilities that matter most, while making responsibilities clear across your business and its partners.
If you’re assessing the infrastructure behind your next financial product, discuss your plans with Gemba. Build forward with clarity, discipline, and confidence.
Frequently Asked Questions
What is an Electronic Money Institution?
An Electronic Money Institution (EMI) is an authorized business that issues electronic money and may provide related payment accounts and cards. For example, an EMI can issue stored monetary value for customers to use through an account or card. This differs from a bank’s role: an EMI provides e-money services. Identify the issuer and account provider when assessing how a product works.
Can a fintech launch through a bank sponsor or Banking-as-a-Service provider instead of obtaining licenses?
Yes, a fintech can use a licensed bank or BaaS provider for services covered by the partner’s permissions. For founders considering how to launch a fintech without an EMI license, this route can support branded services through a partner. The right approach depends on the model: identify which entity holds accounts, moves funds, handles exceptions and serves customers. Your own activities still matter.
What federal rules apply to fintechs, including FinCEN registration, BSA/AML, and sanctions screening?
In the United States, fintechs must register with FinCEN under the Bank Secrecy Act when applicable, alongside state money transmitter licenses where they operate. Build AML controls around customer identification and transaction monitoring, and include sanctions screening in the compliance design. For example, document how a potential match is reviewed, escalated and resolved. Map these controls to the firm’s role and its partner’s responsibilities.
Frequently Asked Questions
What is an Electronic Money Institution?
An Electronic Money Institution (EMI) is an authorized business that issues electronic money and may provide related payment accounts and cards. For example, an EMI can issue stored monetary value for customers to use through an account or card. This differs from a bank’s role: an EMI provides e-money services. Identify the issuer and account provider when assessing how a product works.
Can a fintech launch through a bank sponsor or Banking-as-a-Service provider instead of obtaining licenses?
Yes, a fintech can use a licensed bank or BaaS provider for services covered by the partner’s permissions. For founders considering how to launch a fintech without an EMI license, this route can support branded services through a partner. The right approach depends on the model: identify which entity holds accounts, moves funds, handles exceptions and serves customers. Your own activities still matter.
What federal rules apply to fintechs, including FinCEN registration, BSA/AML, and sanctions screening?
In the United States, fintechs must register with FinCEN under the Bank Secrecy Act when applicable, alongside state money transmitter licenses where they operate. Build AML controls around customer identification and transaction monitoring, and include sanctions screening in the compliance design. For example, document how a potential match is reviewed, escalated and resolved. Map these controls to the firm’s role and its partner’s responsibilities.
