Founders and product owners
Use this page to decide whether your product is really an EMI, PI / PSP, open banking, or Canada MSB case before you spend time on the wrong jurisdiction.
FINANCIAL LICENSE CHOICE HUB
EMI, PSP or PI license: which financial license does your business need?
Entrepreneurs often start with the phrase PSP license, but that label is not specific enough to make the right regulatory decision. The practical question is whether your business will issue electronic money, hold stored customer value, only execute payment services, or operate under a narrower open banking or Canada MSB model. This page helps you separate those routes, understand where the terms overlap, and move to the right next-step page.
EUR 350,000
minimum initial capital for an authorised EMI under Directive 2009/110/EC EUR 20,000 / 50,000 / 125,000
PSD2 PI initial capital tiers depending on service category UK EMRs 2011 + PSRs 2017
core UK framework for electronic money and payment services firms FINTRAC registration
required before operating an MSB in Canada
Disclaimer
Start with the differences between EMI, PSP and PI, then move to the right route page
Last legally reviewed: 22 April 2026. This page is an editorial decision guide, not legal advice. The correct route depends on the exact service flow, customer-funds model, and target market.
How founders should think about EMI, PSP and PI licensing
The first decision is not country. The first decision is regulatory scope. If your product creates stored customer value or electronic money, you are usually testing an EMI route. If your product only executes payment services without issuing e-money, you are usually testing a PI route. If someone says PSP license, they often mean a commercial payment-firm label rather than a precise legal category. In some cases, the right answer is neither EMI nor a full PI: open banking models may fit AISP or PISP, while a Canada-focused money-services model belongs in the separate MSB regime.
Regulatory risks
- Using the phrase PSP license without mapping the actual service flow can hide whether the business really needs EMI, PI, AISP or PISP status.
- If customers hold stored value inside your platform, a PI analysis may be too narrow and can create perimeter risk.
- A UK EMI or PI route does not create EEA passporting rights.
- Canada MSB registration is a separate regime and should not be treated as an EU or UK licensing substitute.
- Choosing a wider route than the product needs can increase capital, compliance and launch burden without adding business value.
Who this guide is for
COO and compliance teams
Use this guide to align the business model with the right regulatory perimeter, prudential burden, and operating build.
Expansion teams
Use the linked route pages once you know the license family and need to compare Europe-wide, UK, or Canada-specific options.
Product, Risk & Operations teams
Use this page to translate EMI / PSP requirements into practical execution: onboarding flows, safeguarding setup, payment operations, fraud controls, and reporting.
Choose EMI when
The business needs wallets, stored balances, prepaid value, account-like payment features, or redeemable electronic money held within the platform.
Choose PI when
The business needs payment execution, remittance, payout flows, merchant services, or transaction processing without issuing electronic money or maintaining stored balances as e-money.
Treat PSP as a starting term
In business language, PSP can point to an EMI, a PI, or a narrower open banking permission. It is useful commercially, but not specific enough for a filing strategy on its own.
Check alternatives early
If the product only accesses account data, initiates payments, or serves the Canadian MSB perimeter, a different route may fit better than a full EMI or PI build.
If the platform holds redeemable customer value, start with EMI.
If the platform only moves money, test PI before assuming EMI.
PSP is often a commercial label, not the legal end answer.
AISP, PISP and Canada MSB can be the right route when EMI or PI would be too broad.
Start with the perimeter first, then choose EMI, PI, AISP/PISP or MSB.
Key terms founders mix up most often
EMI license
EU/EEA and UK usageAn EMI license usually refers to authorisation as an electronic money institution. In the EU, the legal framework is built around Directive 2009/110/EC and the relevant payment-services framework. In the UK, the core regime sits under the Electronic Money Regulations 2011 and the Payment Services Regulations 2017.
PI license
EU/EEA and UK usageA payment institution license authorises payment services without the issuance of electronic money. It is usually the cleaner route where the product executes payments but does not create stored-value liabilities as e-money.
PSP license
Commercial market languageA PSP license is usually a business label, not one formal legal category. Depending on the service model and jurisdiction, it may point to PI, EMI, AISP, or PISP status.
AISP
Open banking permissionAn account information service provider permission is relevant when the product accesses and aggregates payment-account data with customer consent but does not hold customer funds.
PISP
Open banking permissionA payment initiation service provider permission is relevant when the product initiates payments from an existing bank account but does not itself hold customer funds or issue electronic money.
Passporting
EEA internal market conceptPassporting allows an authorised institution in one EEA state to provide services in another EEA state through notification procedures. It depends on the institution type, authorised scope, and current EEA framework.
Canada MSB registration
Canadian AML registration regimeA Canadian money services business route is based on registration with FINTRAC. It is a separate regime and should not be described as the same thing as an EU EMI or PI authorisation.
Which route fits your business model?
EMI license
Choose an EMI license when the product needs to issue electronic money, maintain customer balances, run wallets, or support stored-value payment functionality. This is usually the right route when the customer holds redeemable value inside your system rather than using the platform only as a payment-execution layer.
Typical services
Wallets, stored balances, prepaid products, cards linked to e-money, account-like payment features, merchant settlement models with redeemable value, and broader e-money-enabled payment functionality.
PSP license
Use PSP license as a commercial starting label, not as the final legal answer. In practice, businesses that ask for a PSP license may actually need a PI, an EMI, or a narrower AISP / PISP permission depending on whether they issue e-money, hold funds, or only interact with payment accounts through open banking rails.
Typical services
Commercial shorthand for payment-firm activity, including payment execution, merchant flows, remittance, wallet-like products, open banking tools, or mixed payment models that still need legal scoping.
PI license
Choose a PI license when the business provides payment services without issuing electronic money. This route is often a better fit than EMI where the product executes payments, remittance, merchant services, or payouts but does not create stored-value liabilities for customers.
Typical services
Payment execution, remittance, merchant payment flows, payout services, acquiring-related support, and transaction processing without e-money issuance.
Common jurisdictions
Related alternatives
Sometimes the right route is narrower or outside the EU / UK EMI-PI comparison. If the product only accesses account information, only initiates bank payments, or serves a Canada-focused money-services model, an AISP, PISP, or Canada MSB route may fit better than a full EMI or PI build.
Typical services
Account aggregation, pay-by-bank tools, payment initiation, consent-based banking data access, and Canadian money-services business activity under the local registration regime.
Common jurisdictions
Documents founders usually need once the route is chosen
The right file is evidence-driven. Regulators do not authorise labels such as EMI or PSP in the abstract; they assess whether the documents, controls, and operating model actually match the business flow described in the application or registration package.
Compliance documents
1
Product and service-flow description
This should explain the customer journey, counterparties, jurisdictions, where funds move, whether e-money is issued, and why the model fits EMI, PI, AISP, PISP, or Canada MSB rather than another route.
2
AML and customer-risk framework
The compliance file should match the product, transaction flows, customer types, and geographic exposure instead of relying on a generic policy pack.
Technical and control documents
1
Safeguarding, IT and outsourcing pack
Where the chosen route involves safeguarding or technology dependencies, the file should show reconciliation logic, bank and partner structure, incident handling, access control, outsourcing oversight, and operational resilience.
Financial evidence
1
Business plan and financial projections
The financial model should be consistent with the proposed licence family, realistic customer volumes, and the prudential and operating burden of the route being chosen.
Corporate documents
1
Governance and management file
Founders should be ready to document controllers, management roles, fit-and-proper evidence, decision-making lines, and who will actually own the regulated activity inside the business.
What changes in practice when you move from EMI to PI or narrower routes
The key difference is not branding but regulated scope. A strong founder-level comparison looks at capital, safeguarding, governance, AML, and operational controls needed for the chosen model rather than assuming every payment business needs the same build.
01
Scope mapping comes before the filing strategy
The business should first determine whether it issues electronic money, only executes payment services, only accesses account data, only initiates payments, or belongs in the Canada MSB perimeter. That scope decision drives the rest of the compliance build.
02
Capital and prudential planning differ by route
EMI carries a different prudential profile from PI, and both differ from narrower open banking permissions. A founder should budget for the route that matches the product instead of using a generic payment-firm assumption.
03
Safeguarding matters where customer funds are in scope
Where the model holds relevant customer funds, the firm needs a credible safeguarding approach, reconciliation logic, and operational ownership rather than a superficial statement about segregated accounts.
04
Governance and AML must match the actual product
Regulators expect founders to show who controls the business, how AML and sanctions risk is managed, and whether management really understands the model being licensed or registered.
05
Technology and resilience are part of readiness
Payment and e-money businesses depend on secure systems, operational resilience, vendor oversight, and workable reporting and incident processes. Even a narrower route still requires a control environment that matches the service provided.
Official sources that anchor the core route comparison
This page should be read as an editorial decision guide backed by primary sources. The references below anchor the main distinctions between EMI, PI, PSP-as-market-language, open banking permissions, UK rules, and the Canadian MSB regime.
Regulator
EUR-Lex: Directive 2009/110/EC
Directive 2009/110/EC is the core EU legal instrument for electronic money institutions. It anchors the concept of electronic money and the initial capital framework for authorised EMIs.
Key takeaway: Use EMD2 when testing whether the model really involves electronic money issuance and therefore belongs in the EMI perimeter.
Official source Regulator
EUR-Lex: Directive (EU) 2015/2366
Directive (EU) 2015/2366 is the main EU payment-services framework. It anchors PI categories, payment-service taxonomy, and the open banking permissions used for AISP and PISP models.
Key takeaway: Use PSD2 to map whether the model belongs in PI, AISP, or PISP rather than assuming every payment business is an EMI.
Official source Regulator
European Banking Authority
The EBA is a central EU source for payment and e-money interpretation through guidelines, technical standards, and supervisory materials used across national competent authorities.
Key takeaway: Use the EBA as a cross-jurisdiction reference point when comparing how EU supervisors apply common payment and e-money rules.
Official source Regulator
Financial Conduct Authority
The FCA supervises UK payment institutions and electronic money institutions under the Payment Services Regulations 2017 and the Electronic Money Regulations 2011, supported by its current approach materials.
Key takeaway: Use FCA materials when the route is UK-focused. A UK EMI or PI route is a UK domestic regulatory strategy, not an EEA passporting answer.
Official source Regulator
FINTRAC
FINTRAC is the Canadian authority responsible for the money services business registration regime and related AML supervision materials for MSBs and foreign MSBs.
Key takeaway: Use FINTRAC materials when the business model belongs in the Canadian MSB perimeter. Registration is required before operating and is not the same as an EU or UK EMI / PI authorisation.
Official source Regulator
FINTRAC MSB Registry
The official MSB registry is the primary source for checking the current registration status of Canadian money services businesses and foreign money services businesses.
Key takeaway: The registry is useful for verification, but it does not convert the Canadian regime into an EMI or PI equivalent.
Official source Operational readiness still matters after you pick the right route
Choosing the right licence family is only the start. Founders should also think about the banking, payment-rail, partner, and operating dependencies that make the chosen route workable in practice.
1
Safeguarding and banking relationships must match the model
If the chosen route brings customer-funds obligations into scope, the business needs a realistic safeguarding and banking path rather than assuming that a licence label alone will solve operational access.
2
Payment infrastructure is separate from the licence label
Card schemes, processors, settlement partners, bank APIs, and treasury workflows are separate workstreams. Founders should compare routes with those dependencies in mind.
3
UK, EU and Canada lead to different operating setups
A UK route, an EEA route, and a Canada MSB route each sit in different market-access and counterparty environments. The business should choose the route that matches where it really plans to operate.
4
A narrower route can reduce unnecessary build
If the product only needs account-information access or payment initiation, a narrower route may avoid overbuilding controls for functions the business does not actually perform.
How founders choose and implement the right route
A strong licensing project starts with product scoping, not with a country headline. The practical sequence is to map the business model to the correct permission family, then choose the right route page, then build the legal and operational file that matches the real service flow.
1
Map the customer journey and money flow
Identify where funds enter, whether the platform creates stored value, whether the business only executes payments, and whether the model is really an open banking or Canada MSB case instead of a full EMI or PI route.
2
Choose the correct licence family first
Decide whether the business should be analysed as EMI, PI, PSP-in-commercial-language, AISP, PISP, or Canada MSB. This step prevents founders from comparing jurisdictions before they know what they are actually trying to obtain.
3
Move to the right route page and market
Once the permission family is clear, compare the relevant Europe-wide, UK, EU-country, or Canada route page based on target market, access model, operating footprint, and practical launch priorities.
4
Prepare the authorisation or registration file
Build the operating model, programme of operations, governance, AML framework, safeguarding design where relevant, IT controls, and supporting documents that fit the real business rather than a generic template.
5
Launch with the right controls in place
Authorisation or registration is only one milestone. The business still needs operational readiness, counterparties, reporting, internal ownership of risk, and ongoing compliance processes that match the chosen route.
About Our Company
Why Regulated United Europe?
Regulated United Europe OÜ (RUE) is a European legal consulting firm specializing in financial licensing, company formation, and regulatory compliance. Since 2016, we have helped hundreds of businesses obtain crypto, gambling, forex, and EMI/PSP licenses across 35+ jurisdictions.
With offices in four EU countries and a team of experienced lawyers, we provide end-to-end support — from initial consultation and company registration to license acquisition and ongoing compliance management.
500+
Clients Served
35+
Jurisdictions
Since 2016
Years in Business
4
EU Offices
Licensed Legal Practice
Fully registered and regulated EU company with partnerships across major financial centers.
Multilingual Team
Our experts speak English, German, Russian, Chinese, and 12+ other languages for global client support.
Turnkey Solutions
From company registration to license acquisition and compliance — we handle the entire process end-to-end.
Dedicated Support
Personal consultant assigned to each client. Direct communication channels, no call centers.
🇪🇪 Tallinn, Estonia
🇱🇹 Vilnius, Lithuania
🇨🇿 Prague, Czech Rep.
🇵🇱 Warsaw, Poland
Accounting, tax and substance still depend on the chosen route
Tax is not the legal perimeter, but it affects the viability of the structure. Once founders know whether the business fits EMI, PI, open banking, or Canada MSB, they should make sure the accounting model, entity structure, and local substance match the regulated operating reality.
Substance note
Local substance is not only a tax question. In regulated payments, weak substance can also undermine governance credibility, outsourcing oversight, and day-to-day supervision.
The accounting model must reflect the licence family
The accounting model must reflect the licence family
Customer liabilities, safeguarded balances where relevant, revenue assumptions, and internal reporting should match the actual regulated service flow.
Group structures need clear control mapping
Group structures need clear control mapping
If technology, compliance, support, or finance functions sit across multiple entities, the business should document who owns each critical function and how outsourcing boundaries are controlled.
Local maintenance is part of the operating model
Local maintenance is part of the operating model
Founders should plan for accounting, audit coordination, payroll, legal maintenance, and ongoing reporting in the jurisdiction of the chosen route, not only for the initial filing stage.
Related route pages
Use these pages after you identify the right license family. The goal of this hub is to help you choose the correct route first, then move to the jurisdiction or service-specific page that fits your business model.
EMI routes
- Electronic Money License in Europe – for businesses that need e-money issuance, wallets, stored balances, or broader account-like payment functionality.
- EMI License in the UK – for UK domestic e-money and payment services business models.
- EMI License in Lithuania – a common EU route for passporting-oriented fintech structures.
- EMI License in Cyprus – an EU route often reviewed for international operating structures.
- EMI License in Poland – relevant for businesses that want an EU base with a large domestic market context.
- EMI License in the Netherlands – useful when founders prioritise a mature Western European market and infrastructure base.
PI / PSP routes
- Payment Institution License in Europe – for payment execution models that do not issue electronic money.
- PI License in the UK – for UK payment services businesses that do not need e-money issuance.
Open banking routes
- PISP License in Europe – for pay-by-bank and payment initiation models.
- AISP License in Europe – for account information and aggregation products that do not handle customer funds.
Canada route
- MSB in Canada – a separate Canadian registration route that should not be treated as a substitute for EU or UK EMI / PI authorisation.
Answers
Frequently Asked Questions
Open the key issues founders, compliance teams and legal leads usually need to confirm before launch.
What is an EMI license? +
An EMI license usually means authorisation as an electronic money institution. It is the route to test where the business issues electronic money or holds redeemable stored value for customers.
What is a PI license? +
A PI license means a payment institution route for payment services without electronic money issuance. It is often the right answer for payment execution models that do not maintain stored-value balances as e-money.
Is a PSP license the same as a PI license? +
Not always. PSP license is often used as commercial language, while PI is a specific legal category. In some conversations PSP means PI, but in others it may also point toward EMI, AISP, or PISP depending on the model.
When does a business need EMI instead of PI or PSP? +
A business usually starts with EMI analysis when customers hold stored value inside the platform, the firm issues electronic money, or the product relies on wallet-like balances rather than payment execution alone.
When is PI enough? +
PI is often enough where the business provides payment services without issuing e-money, such as payment execution, remittance, merchant flows, or payout products that do not create stored-value liabilities for customers.
Can PSP mean EMI as well as PI? +
Yes. In business usage, PSP can be a broad label covering different types of payment firms. That is why founders should always map the actual service flow to the exact legal permission rather than stopping at the term PSP.
When are AISP or PISP better than EMI or PI? +
A narrower open banking route can fit better when the product only accesses payment-account data or only initiates payments from bank accounts and does not hold customer funds or issue electronic money.
Does a UK EMI or PI licence give EEA passporting? +
No. A UK EMI or PI route is a UK domestic regulatory route and does not create EEA passporting rights.
Is Canada MSB the same as EMI or PI? +
No. A Canada MSB route belongs to a separate Canadian regime based on registration with FINTRAC. It is not the same legal product as an EU or UK EMI or PI authorisation.
What should founders decide before comparing countries? +
Founders should first decide what the product actually does: issue e-money, hold stored value, execute payments only, use open banking permissions, or operate in the Canadian MSB perimeter. Only then does country comparison become efficient.
Choose the right license before you choose the jurisdiction
The most expensive mistake is to compare countries before you know the correct permission family. Start with the real business model, decide whether the route is EMI, PI / PSP, open banking, or Canada MSB, and then move to the right route page.
Free Consultation
Get Expert Guidance on Your License
Our specialists will analyze your specific case, recommend the optimal jurisdiction and license type, and provide a detailed roadmap with timeline and costs.
Confidential - No obligation - Response within 24 hours
Main Services
Terms of Cooperation
Regulated United Europe
