“I want to open a PSPPSP means Payment Service Provider. A PSP helps an operator accept deposits, process payments, settle funds, manage refund logic, chargebacks and reserves and, in some models, handle payout flows.” can mean very different projects: accepting payments for online shops, transferring money internationally, issuing a wallet balance, making payouts or selling technical connections to providers. They need different permissions, budgets and capabilities. Buying the cheapest “payment licence” does not solve the problem until the business itself is defined.
Payment service provider (PSP) is a general term, not one company category alongside banks. A bank can provide payment services; a non-bank provider may operate as a payment institutionA company authorised for specified payment services. PI status alone is not a banking licence or permission to issue electronic money., electronic moneyMonetary value issued electronically in exchange for funds and used for payments under the relevant regime. It is not synonymous with a bank deposit or crypto-asset. issuer or under another national model. A company with an attractive payment interface may sell technology alone.
This is a map of the system: who does what, which permissions exist and how to select a route for the product. It then becomes possible to assess complexity, capital, team, timing and expense meaningfully.
How the market works: banks, payment companies and technology
Banks: deposits, lending and settlement infrastructure
A bank is not simply a bigger PSP. Deposit-taking is a fundamental part of the banking model; banking authorisation operates differently from payment-company permission. Banco de España, for example, expressly identifies deposit-taking as credit-institution activity.[1] A bank’s actual operations depend on its authorisation and country.
For a payment founder, a bank may be an infrastructure partner rather than a competitor: accounts, settlementSettlement is the transfer of funds from a PSP, acquirer, EMI or payment processor to the operator’s settlement account. and the specified arrangement for customer funds may depend on it. A transfer or payment-acceptance service does not necessarily need to become a bank. Decide which functions you want to perform yourself.
Payment institutions: making payments without becoming a bank
A Payment Institution (PI) is authorised for specified payment services. These may include remittance, payment-account transactions, acquiring and other functions within its permission. The Bank of Italy describes the European PI model.[2]
Consider a service helping companies pay suppliers. A customer provides money for an operation, and the service arranges transfer and settlement with the recipient. That is a payment task, distinct from a bank deposit and issuing a wallet with electronic money. A payment account alone does not turn a PI into a bank or EMIEMI means Electronic Money Institution. An EMI may open accounts, issue electronic money and provide payment services within the scope of its authorisation..
Electronic money: a balance used for payments
An Electronic Money Institution (EMI) issues electronic money: monetary value in electronic form. An illustrative customer funds a wallet, receives a balance and uses or redeems it under applicable rules. E-money is not a separate currency or another name for crypto. EMI rules include specific issuance and funds-protection requirements; the Central Bank of Cyprus describes a European route.[3]
An EMI app can look like banking: a balance, transfers and a card. Appearance does not determine status. Card issuance, account details and access to settlement systems may involve several partners. Customer balances are not unrestricted company money for marketing or lending.
Acquirers, payment networks and gateways: three further roles
An acquirerAn acquirer is the bank or payment institution that enables a merchant to accept card payments. serves a merchantA business or entrepreneur accepting payment for its goods or services.’s acceptance of card payments. The issuing bankIn a card transaction, the bank that issued and services the buyer’s card. serves the buyer’s card. Visa and Mastercard provide their network rules and infrastructure; a technical gatewayTechnology that carries payment requests and connects providers. The gateway label alone does not determine the company’s regulated functions. carries payment messages and connects the shop’s interface to payment infrastructure. A group may combine these roles or different participants may perform them.
In a simplified card purchase, the buyer enters details at checkout; a request travels through technical infrastructure and the acquirer to the network and issuer. Approval is followed separately by settlement and payment to the merchant. “Approved” and actual money receipt are different events. A single PSP interface does not make one company a bank, acquirer, network and holder of every settlement account.
Practical takeaway Map two journeys: the payment instruction and the movement of fundsPayment flow is the map of how funds move: who accepts the deposit, where funds are held, who performs settlement, and how withdrawals, refunds, chargebacks, crypto conversion and reconciliation are handled.. Identify the company, function and customer obligation at each stage. This is more useful than choosing a country by an advertised licence price.
Payment permissions that exist in different countries
The world is not organised around one licence with different prices. Some countries authorise payment institutions; others regulate transfers, stored value and e-money separately. Financial-monitoring registration may coexist with payment licensing and supervision.
This is a route map, not a “best licence” ranking. Canadian registration and a European EMI are not interchangeable purchases: they answer different questions. Define services and customers first, then assess which route supports the required model.
Do not buy “an international PSP licence for every country”, “MSB equivalent to a bank” or “Visa registration instead of state authorisation” as a complete answer. A document may be genuine while the promised capabilities are not. FinCEN specifically warns against presenting MSB registration as a licence or government endorsement.[5]
Which permission fits the business model
Accepting payments for shops, platforms and other merchants
Distinguish acquiring, technical integration and the Payment FacilitatorA provider arranging merchant service through a sponsoring acquirer. It is an infrastructure role, not a universal state authorisation. (PayFac) model. A facilitator arranges merchant service through a sponsoring acquirer; a gateway may only transmit messages. State payment permission and contractual status in card infrastructure serve different purposes.
Onboarding merchants, participating in settlement and assuming payout responsibility requires more than a payment module. Establish who contracts with and checks merchants, receives funds and bears refunds and disputed-transaction losses. PayFac alone does not define the company’s entire state licensing status; check network and sponsor requirements separately.[11]
International transfers and bulk payouts
These projects depend on transfer permissions, sender and recipient countries, currencies and corridor partners. One company may cover part of the chain while a locally licensed partner pays the recipient. “We handle dollars” does not mean “we may serve every US customer”: currency and territorial permission are different parameters.
Check not only money receipt but delivery to the beneficiary: available systems, banks, timing, conversion cost and failed-transfer handling. Permission on the sending side does not automatically create a payout network.
Wallets, balances and neobank-like products
Where customers hold value for future payments, e-money or the relevant national stored-value regime may be involved. A European project may need EMI; Hong Kong has a distinct SVF model. A “wallet” interface does not classify the business: contracts, customer rights and actual balance operation matter.[3][10]
Cards and account details are additional architectural elements that may come through partners. If the aim is banking deposits used in a banking model, an ordinary payment or EMI licence does not replace banking permission.
Technical gateways and software
If you sell integration, message routing and reporting while authorised partners retain funds and payment obligations, your own financial licence may not be required. Check the actual function, not merely “we are an IT company”. Payment initiation, for example, is a separately regulated European service even without holding the money.[2]
A technical model still has obligations: contracts, information security, data protection and applicable card-data standards. Handing the financial function to a partner must be real, not just a product description.
Licence limitations and their practical effect
Permitted functions and territory
The service list matters, not just the institution’s title. Transfer rights do not confer e-money issuance; one market’s permission does not freely open every country. EU institutions have a cross-border mechanism, but it is a regulated procedure within a defined system, not a “global passport”.[3]
Scale limits also exist. MASSingapore’s monetary and financial regulator, including for the relevant payment institutions. distinguishes Standard and Major Payment Institutions through service and volume thresholds.[8] Growth or product changes may outgrow the original category. This affects real operations, not only a register description.
Banks, acquirers and networks
Suitable state permission does not oblige a bank to open every account or an acquirer to accept every industry. Partners assess the business, owners, customer countries, risk and their willingness to serve it. Check contractual connection terms alongside the licence.
This is particularly visible in high-risk sectors. A provider may be authorised for a service but lack an agreed infrastructure route for a customer category. “The service is legally possible” is not “we have functioning infrastructure and a contract for it”.
Customer funds and the company’s own money
Customer funds do not become a PSP’s operating budget. The FCA, for example, requires relevant-fund safeguardingMeasures required under the applicable regime to protect relevant customer money. This is separate from institutional capital and operating expenses. by authorised PIs and EMIs and separately explains small-category boundaries. Voluntary treatment for certain small payment services cannot be extended to every small EMI balance.[12]
Keep a separate financial model for salary/development money, company capital, customer funds, settlement balances and contractual reserves. The system must explain who owns each amount and when it may be used.
Analytical conclusion Three limitations exist: you may not perform a function; a partner will not support it; your team or technology cannot yet deliver it. The licence addresses only the first within its scope. Launch requires answers to all three.
Is your own licence compulsory?
No. A product may use a licensed partner’s infrastructure as a technical supplier, an agent under a permitted arrangement or a brand using another institution’s services. Contracts must explain who provides the regulated service and owes obligations to customers. Partnership does not mean simply “renting” permission to operate beyond its scope.
This can reduce the founder’s own licensing burden for an initial product test. Infrastructure brings dependence on customer categories, countries, prices, integrations and termination terms. If the partner will not accept the audience, a ready interface does not solve that.
Your own licence becomes a concrete option when independence provides commercial value: a direct customer agreement, control of product and settlement, scale or less dependence on one supplier. Control brings governance, verification, security, reporting and ongoing institution costs.
| Question | Partner model | Your own institution |
|---|---|---|
| Who provides the regulated service? | The licensed partner within the agreed structure | Your company within its permission |
| Main challenge | Finding a suitable partner and allocating functions correctly | Building and maintaining a regulated organisation |
| Dependencies | Partner pricing, markets, customer categories and decisions | Regulatory obligations plus infrastructure dependencies |
| When it makes sense | Testing a product within a model the partner supports | Proven economics and a substantiated need for control |
Requirements for a payment licence
A clear business model and financial plan
The applicant must explain the service, customers, countries and revenue model. Transfers need corridors and settlement chains; a wallet needs issuance, use and redemption; merchant services need customer categories, acceptance and payout. Regulators assess the actual business, so standard policies do not replace a working-model description.
Link volumes, pricing, expenses and capital in the financial plan. Test a weaker scenario: fewer customers, a more expensive bank or connection delays. If the business only works with immediately high turnover, licensing will depend on overly optimistic assumptions.
Owners, management and real governance
Owners, funding and management competence are checked. You need people who genuinely run the institution, not names in a questionnaire. Local substanceLocal substance means genuine presence in the jurisdiction: an office, local director, local management, employees, records, governance or another level of operational connection with the place of licensing. and functional allocation depend on the regime. FCA PI/EMI conditions, for example, include governance, responsible persons’ experience, risk controlsRisk controls are the rules, limits, checks, blocks, monitoring arrangements and procedures used to reduce operational, payment, AML, sanctions, fraud and reputational risk. and ownership transparency.[4]
Recruit before the licensing process ends. Buying documents from an adviser does not replace a manager able to explain settlement, incident response or customer verification.
Transaction controls, technology and protection of funds
Organise customer checks, anti-money laundering and counter-terrorist financing (AML/CFTAML/CFT means Anti-Money Laundering and Combating the Financing of Terrorism.), transaction monitoring, incidents and complaints. Technology must support records, security and recovery. The requirements differ for a technical gateway and a wallet holding customer balances.
Safeguarding and settlement infrastructure is a separate task. Before application or at the relevant stage, establish required bank and supplier arrangements. The merchant profile and business evidence explain how to describe the company to partners; an institution’s particular package will be broader and function-dependent.
Costs: capital, application fees and operating budget
“Licence cost” often combines three different items: required capital, regulator fees and preparation services. Add technology, team, infrastructure and post-launch expense. Compare separate lines, not a single “turnkeyA turnkey solution is a ready-made technical and operational package for launching a casino, including the platform, games, back office, payments, KYC, CRM, affiliate tools, support tools and sometimes licensing support.” price.
| Item | Particular regime example | How to interpret it |
|---|---|---|
| PI initial capital | The Bank of Italy states at least €20 000 for money remittance alone and €125 000 for points 1–5 of the relevant service list | The level depends on function; it is not a universal PI price or total budget.[2] |
| EMI initial capital | Bank of Italy: at least €350 000 | Institution capital; expenses and ongoing own-funds requirements remain separate.[2] |
| FCA APIAn authorised payment institution in UK FCA terminology. Here API denotes institutional status, not a software interface. application fee | Category 4: £2 820 for services (f)–(h); category 5: £5 640 for (a)–(e) | An assessment fee, not purchase of permission or guaranteed approval.[13] |
| FCA AEMIAn authorised electronic money institution in UK FCA terminology. application fee | Category 5: £5 640 | Excludes capital, team, infrastructure and support.[13] |
Fees follow the FCA table updated on 13 July 2026. Italy illustrates the European model’s basic capital levels, not a calculation for every country and service. Small categories, specialised services and other national regimes need separate treatment.
Capital is not “a fee the regulator takes”. Nor is it entirely free to spend: the institution must maintain required own funds. Safeguarded customer money does not fund the team either.
Practical takeaway Request five budget sections: capital; fees; preparation and implementation; monthly operations; infrastructure reserves and liquidity. Specify adviser scope: model, application, regulator responses, banking work and support. Without that breakdown, a universal total project price has no meaningful comparator.
Timing and complexity: registration is not launch
An independent PI or EMI is a months-long project, not simply company registration. Prepare the model and team, submit, address regulatory questions and complete infrastructure. A simpler registration route may have a lighter entry burden but does not confer a broader authorisation’s powers.
FCA publishes standard PI/EMI times of three months from a complete application and up to twelve months for an incomplete one. That is the regulatory process, not a promise to open three months after the first adviser conversation.[14] Include preparation, gap correction, banking arrangements and product testing separately.
| Stage | Required outcome | Main source of delay |
|---|---|---|
| Functions and market | Clear product and suitable permission model | Trying to cover incompatible tasks with one registration |
| Team, capital and documents | Applicant able to explain and operate its model | Unsubstantiated funding, nominal team and standard documents |
| Regulatory process | Decision on the particular application | Incompleteness, questions and model changes during review |
| Infrastructure | Accounts, contracts, settlement, integrations and end-to-end testing | Bank/sponsor rejection or integration development |
Assess complexity by function. Technical integration without an independent regulated service, agency and your own EMI are different projects, not three prices for one permission. Funding paperwork but not the team and ongoing operations means selecting the route prematurely.
Where intermediation ends and risky arrangements begin
An extra intermediary does not necessarily mean a breach. Technical suppliers, agents and servicing partners may have normal contractual roles. What matters is identifying the actual provider, basis of operation, funds flow and responsibility for return.
It is different if the money recipient is undisclosed, one business is presented as another or the payout basis cannot be explained. A registry number for one participant does not establish the entire model. Compare the contract with actual activity and settlement.
Red flag “No licence is needed because the money goes through another company” is not a model explanation. A partner should clarify functions and responsibility, not conceal the actual provider or customer. Before paying for connection, identify who owes you money and how settlement is evidenced.
The same applies to crypto-assets: settling in a stablecoinA stablecoin is a cryptoasset whose price is generally linked to a fiat currency or another asset. does not automatically answer custody, exchange and client-transfer questions. Check those functions separately from ordinary payments. The founder needs to understand their role, not find a new label for the same service.
Getting started: from product idea to licensing route
Describe the product simply: your customer, their problem, who receives their money, how long it remains in the system and who must return or transfer it. Specify countries, currencies, volumes, customer categories and proposed partners. If all you have is an interface idea, start with functions rather than buying a registered company.
Then compare two routes: suitable partner infrastructure and your own permission. Each needs available functions, limitations, team requirements, budget and timeline. Country selection becomes meaningful once the required rights and infrastructure are clear.
HRL can help analyse the model, identify the necessary permissions and prepare the licensing project. Send the product, customers and markets, funds-flow description and existing arrangements. The outcome should be a route for your business, not simply the cheapest “PSP licence”.
Frequently asked questions about payment licensing
Is there one international PSP licence?
No single permission covers every function and country. Services and markets matter. Even an EU cross-border mechanism is not a worldwide operating right.
How do PI, EMI and a bank differ?
A PI provides permitted payment services. An EMI issues electronic money and may provide specified payment services. A bank operates under banking rules, including relevant deposit-taking rights. Similar apps do not make their statuses interchangeable.
Do I need a licence for a gateway alone?
A purely technical model may not require its own financial permission. Check actual functions: money never reaching your account does not alone exclude regulation. Security, data and contractual infrastructure requirements remain.
Can I launch through a partner?
Yes, where the model and agreements clearly allocate services and responsibilities. It may be a sensible first stage, but you depend on accepted customers, countries and terms. “Licence rental” without that arrangement does not explain permission to operate.
Why does cheaper or simpler MSB registration not replace EMI?
The regimes differ. US FinCEN registration does not replace applicable state licences; Canadian FINTRAC registration is not a licence. Compare permitted activity and additional requirements, not only the cost of obtaining a number.
Does a licence guarantee banking and Visa or Mastercard access?
No. Accounts, sponsorship, participation and servicing particular industries need their own arrangements. Check infrastructure feasibility for your model before investing in licensing.
What does an independent licence cost and how long does it take?
Separate capital, fees, preparation, technology and ongoing expenditure. PI/EMI is a months-long project; complete-application review does not include all preparation and launch. The examples above show the scale of requirements, not a ready-project price.
What should be defined before choosing a country?
Product functions, customer countries, money movement, balances, customer categories, volume and partner roles. Compare independence with partnership afterwards. Starting with the cheapest registration can buy a status that does not solve the problem.
This material is informational and explains principal payment-business models. PI, EMI, MSB, PayFac and other labels do not confer identical rights across countries. Check services, cross-border operation, safeguarding, capital and partner requirements for the product. The stated figures and times concern the specified regimes, not a complete budget or guarantee of permission or infrastructure connection.
Sources
- Banco de España — institutions accepting deposits. Banking function illustrated by the European system.
- Bank of Italy — payment and electronic money institutions. Services, applicant conditions and basic capital examples; not a complete calculation for every special category.
- Central Bank of Cyprus — electronic money institutions. EMIs and the EU cross-border mechanism.
- FCA — payment/e-money applications. British categories and conditions: a separate national route.
- FinCEN — warning on misrepresenting MSB registration. MSB section, page 6: registration is not licensing; applicable state requirements remain separate.
- FINTRAC — MSB registry. Registration is not licensing or endorsement.
- Bank of Canada — retail payment supervision. RPAA registration, operational risks and funds protection.
- MAS — payment service provider licensing. SPI/MPI categories and thresholds.
- Hong Kong Customs — Money Service Operators. Remittance and currency exchange.
- HKMA — stored value and retail payments. Separate SVF regime, including wallets and prepaid cards.
- Visa — payment facilitator and marketplace risk guide. Roles in the PayFac model, not state authorisation.
- FCA — safeguarding for payment/e-money institutions. Relevant-fund protection, including small-category distinctions.
- FCA — application fees. Categories 4 and 5, table updated 13 July 2026; not total institution cost.
- FCA — standard payment/e-money application times. Three months for a complete application and twelve for an incomplete one, separate from preparation and launch.
