Licensing paths to launch a payment business: EMI, PI, and agent models

Launching a payment business usually starts with a question: what payment business license do we need?

I've seen many founders come to a demo with a product vision already formed. They know the vertical, the target merchants, the geography, and sometimes even the acquiring partners they want to approach. But the licensing path is still unclear. Should they apply for an EMI license? Is a payment institution license enough? Can they start faster with a payment agent model? Or should they postpone licensing and test the business first?

This article breaks down the main routes to launch a payment service provider (PSP) or payment business: Electronic Money Institution (EMI), Payment Institution (PI), and agent models. My goal is not to replace legal advice, but to help founders and payment entrepreneurs ask better questions before they spend months and serious money on the wrong structure.

Why payment licensing strategy should come before the tech stack

The payment market is still expanding, but launching a payment business now takes more than demand and a strong product idea. In the euro area, non-cash payments reached 77.7⁠ billion transactions in the first half of 2025, up 7.7% year on year, with cards making up 57% of transaction volume. E-money is growing too, reaching 4.7 billion transactions, up 10.7% year on year. BIS data show that cashless payments keep rising⁠, led by cards, credit transfers, and fast payments. For PSP founders, this creates a clear opening and a higher operating bar. Licensing, safeguarding, compliance, and infrastructure shape how fast you can launch, who will partner with you, and how far the business can scale.

That growth creates space for new PSPs, PayFacs⁠, payment platforms, and vertical payment businesses. But it also means regulators pay close attention to safeguarding, anti-money-laundering controls, governance, resilience, and customer funds protection.

In my experience, the licensing question is often treated as a legal checkbox. But it should also be treated as a business architecture decision, because it affects:

• what services you can legally provide
• whether you can hold or safeguard client funds
• which partners will work with you
• how much capital you need
• how long it takes to go live
• how much compliance capability you need from day one
• how much control you have over merchants, pricing, and payment flows

A strong PSP business is built on three layers: licence, banking/acquiring relationships, and technology. If a single layer is weak or misaligned, the whole model becomes harder to scale.

Three main licensing paths at a glance

This is the core trade-off: the more control you want, the more regulatory weight you carry.

Path 1: Payment agent model

The payment agent model is often the fastest practical route for entrepreneurs who want to enter the payment market without immediately applying for their own licence.

In this model, your company operates as an agent of an authorised payment institution or electronic money institution. The principal owns the regulatory permission. You may perform certain services on its behalf, depending on the agreement and the rules in the relevant jurisdiction.

In the UK, for example, the FCA states⁠ that agents must be registered before providing payment services on behalf of their principal. If the principal is an EMI, it is responsible for applying for the agent's registration.

When the agent model makes sense

In my experience, the agent route works best when the founder wants to validate the commercial model before taking on full licensing responsibility.

It may suit you if you:

• are still testing your merchant niche;
• need to launch quickly;
• do not yet have a full compliance team;
• want to prove transaction volume before applying for your own licence;
• are comfortable operating under another company's policies and risk appetite.

This path can be useful for PSP startups, independent sales organisations⁠, merchant service providers, and vertical payment platforms that want a faster entry point.

What you give up

The agent model is faster, but it is not the same as owning the business end-to-end.

You may have less control over:

• onboarding rules;
• prohibited merchant categories;
• pricing flexibility;
• settlement terms;
• risk policies;
• compliance decisions;
• available payment methods or geographies;
• final relationship with acquirers or banks.

The principal will usually have the final say because the regulatory liability sits with them.

Path 2: Payment Institution license

A payment institution license is often the middle route. It gives a company its own regulated status to provide payment services without going so far as to issue electronic money.

Under the EU's Payment Services Directive⁠ 2 (PSD2), payment institutions can provide services such as payment account operations, execution of payment transactions, card-based payments, credit transfers, direct debits, money remittance, payment initiation, and account information services, depending on their authorised scope. PSD2 also sets initial capital requirements according to the services provided.

The FCA describes authorised payment institution applicants as firms that must meet conditions regarding initial capital, governance, internal controls, risk management, fit-and-proper owners, safeguarding, where applicable, business planning, and anti-money laundering compliance.

When a PI is enough

A PI can be the right choice when your business model is focused on payment processing and money movement, but does not require issuing stored value.

For example, a PI structure may work for:

• merchant payment processing;
• payment gateway or PSP services;
• money remittance;
• account-to-account payment services;
• payout services;
• payment initiation or account information services;
• certain PayFac-style models, depending on jurisdiction and structure.

In my experience, many PSP founders initially assume they need an EMI because it sounds more complete. Then, after mapping the actual product, a PI turns out to be enough.

That matters because applying for a broader licence than you need can increase costs, delay launch, and impose obligations that do not create additional commercial value.

Where PI becomes limiting

A payment institution licence is not the right route if your product depends on issuing e-money or maintaining stored-value balances for customers. If customers can load funds, keep those funds in an account-like environment, and use them later for payments, you may be moving into EMI territory. The exact perimeter depends on the jurisdiction and product design, so this is where legal analysis matters.

The practical question is: are you moving funds as part of a payment service, or are you creating stored value that customers can hold and reuse? That distinction sits at the heart of EMI vs payment institution decision-making.

Path 3: EMI license

An EMI license gives a company permission to issue electronic money and provide payment services. It's typically relevant for wallet products, stored-value accounts, prepaid card programmes, embedded finance models, and more complex payment platforms.

We already have a dedicated article on how to become an Electronic Money Institution⁠, so I'll keep this section focused on what matters for this decision. Strategically, EMI offers the highest level of control, but it also entails the heaviest regulatory and operational burden.

In the UK, the FCA says⁠ authorised electronic money institution applicants must meet conditions regarding initial capital, governance, safeguarding, anti-money laundering compliance, fit-and-proper management, and effective supervision.

When EMI is the right path

An EMI may be appropriate if your model includes:

• e-wallets;
• stored customer balances;
• prepaid cards;
• IBAN-like account functionality;
• issuing and redeeming e-money;
• multi-currency stored-value products;
• more direct control over customer funds and account structures.

In my experience, EMI makes sense when the product genuinely needs e-money functionality. It should not be selected as a status symbol.

A founder once told me during a demo: "We want EMI because investors will like it." Maybe. But regulators do not authorise slide decks. They authorise operating models, governance, risk controls, safeguarding arrangements, and people who can prove they understand the responsibility.

What makes EMI harder

EMI usually requires more work across:

• capital planning;
• safeguarding;
• compliance documentation;
• governance;
• internal controls;
• risk management;
• technical resilience;
• financial projections;
• banking relationships;
• audits and reporting.

Regulatory expectations are also moving upward. In the UK, the FCA's new safeguarding regime for payment and e-money firms⁠ took effect from 7 May 2026, with the aim of reducing shortfalls in client funds and improving customer fund return if a firm fails.

For anyone planning licensing to start a PSP, this matters. Safeguarding affects reconciliation, reporting, bank account structure, operational discipline, and finance workflows.

EMI vs PI vs agent model: how to choose

The decision should start with product reality, not ambition.

The cleanest decision comes from drawing the actual money flow.

• Who sends funds?
• Who receives funds?
• Where are funds held?
• For how long?
• Under whose name?
• Who has the contractual relationship with the merchant or end user?
• Who is responsible if something goes wrong?

Once you map that clearly, the licensing path becomes much easier to discuss with lawyers, regulators, banking partners, and infrastructure providers.

How to get a payment license: the practical sequence

Most serious applications follow a similar pattern, regardless of jurisdiction. The European Banking Authority (EBA) publishes guidelines⁠ on information required from PI and EMI applicants under PSD2 to support consistent authorisation across the EU, but the substance of what regulators actually scrutinise is more specific than the guidelines suggest.

Here is the practical sequence I recommend founders think through before they ask how to get a payment license.

1. Define the regulated activity. Write down whether you touch funds, hold funds, or issue e-money and for whom. This step prevents over-licensing and under-licensing. Both mistakes are expensive to fix.
2. Choose the jurisdiction based on substance. Jurisdiction affects not only processing timelines but regulator expectations, local hiring, banking access, passporting, and credibility with partners. Lithuania is the fastest in the EU; Ireland and the Netherlands carry more reputational weight but take longer.
3. Build a business plan regulators can stress-test. Your plan needs to show how the company operates sustainably — volumes, pricing, capital, outsourcing, safeguarding, and compliance resources. A PSP is not only a technical product. It is a regulated operating company, and regulators review business plans to look for evidence that management understands that.
4. Prepare governance before you submit. Weak governance can slow an application. AML policies, KYC procedures, transaction monitoring, safeguarding arrangements, and evidence that senior management is competent need to exist and be internally consistent before the file goes in, not in response to regulator questions.
5. Show how payments will actually flow. The technical architecture matters as much as the compliance documents. Regulators want to see how payments are processed, routed, reconciled, and reported, and how your payment infrastructure⁠ handles multiple providers, markets, and settlement cycles. This is where a payment orchestration layer answers the 'how does it work in practice' question.
6. Respond to regulator questions precisely and quickly. Questions don't mean something is wrong. But slow, vague, or inconsistent answers create friction that extends timelines by months. The areas that attract the most questions are safeguarding architecture, financial projections, compliance staffing, and outsourcing arrangements.

How much does a payment licence cost?

The regulator's application fee is the smallest line item. In Lithuania, state levies run €898⁠ for a PI licence and €1,463 for a full EMI licence. The UK FCA charges £1,120⁠ for small PI or small EMI applications, rising to £2,790–£5,580 for authorised PI and authorised EMI depending on the services in scope. Ireland charges no application fee, though authorised firms pay an industry funding levy⁠ post-approval.

The real cost is everything behind the application: initial capital (€125k for a PI, €350k for an EMI), legal and advisory preparation (typically €20k–€40k), compliance infrastructure, safeguarding arrangements, governance setup, and runway until the business is profitable. Total committed capital to reach a live licensed operation is realistically €1–2 million; the application fee is a rounding error by comparison.

Common mistakes I see from payment entrepreneurs

• Choosing the broadest licence by default. An EMI licence may sound stronger, but more permission also means more responsibility. If your first product does not need e-money issuance, a PI or agent model may be more efficient.
• Treating licensing and infrastructure as separate projects. They are separate workstreams, but they must connect. Your transaction flows, reporting, safeguarding, and reconciliation logic should match the operating model you describe to partners and regulators.
• Underestimating banking and acquiring relationships. A licence does not automatically grant you access to bank accounts, safeguarding accounts, BIN sponsorship, acquiring access, or local payment methods. These relationships require their own due diligence.
• Building before proving the commercial model. Some teams spend a year building infrastructure before signing enough merchants to prove demand. The agent model or white-label infrastructure can help test the market faster.
• Ignoring post-licensing operations. Getting authorised is not the finish line. It is the starting point for reporting, audits, monitoring, safeguarding, risk reviews, policy updates, and partner management.

Final thoughts

When I speak with founders about licensing to start a PSP, I usually ask one question first: what do you need to control on day one, and what can wait?

That question changes the conversation.

Some businesses need their own EMI from the beginning. Others can launch faster as an agent, prove demand, and apply for their own permissions later. Some need a PI. Some need to rethink the product flow before choosing any licence at all.

In my experience, the winners are the teams that match regulation, infrastructure, and commercial strategy in the right order.

Corefy helps payment entrepreneurs launch and scale the infrastructure side of that equation: payment orchestration⁠, provider connectivity, routing, cascading, dashboards, reconciliation, and white-label PSP capabilities. If you are planning a payment business, the right licence matters. So does the system you build around it. Contact us⁠ — we're happy to talk through what makes sense for your model.