Malta API for Sale
A Maltese authorised payment institution (API) can provide the payment services approved by the Malta Financial Services Authority (MFSA). For buyers interested in merchant acquiring or payment processing, an existing company may also bring customers, a working platform, staff, and provider arrangements.
The licence alone does not tell you which of those assets you are buying. Nor does it authorise electronic money issuance or guarantee that banks and payment partners will support your business model. Legasset helps buyers examine available payment institutions, assess the proposed transaction, and compare acquisition with a new MFSA application.
Malta Authorised Payment Institutions Currently Available
Malta Authorised Payment Institution With EUR 33M Monthly Turnover
An MFSA-regulated Maltese Authorised Payment Institution with an active customer base, established payment infrastructure, and profitable operations. The company serves both high-risk and low-risk merchant sectors and offers immediate access to a functioning payments business with existing transaction volume.
• MFSA-regulated Authorised Payment Institution in Malta
• Approximately 200 active customers across high-risk and low-risk sectors
• Monthly transaction volume of approximately EUR 33 million
• Merchant portfolio includes iGaming, crypto, adult, and traditional business sectors
• Core banking system, payment rails, and full operational infrastructure already in place
• Slightly profitable operation with no disclosed debts or liabilities
Licensed activities include merchant acquiring, payment processing, settlement services, and merchant servicing across multiple risk categories.
Full financials, regulatory information, and due diligence materials shared after NDA.
Key Takeaways for a Malta Authorised Payment Institution
- Permissions are service-specific. An API may provide the payment services covered by its MFSA authorisation. Check the target’s exact permission before relying on a sales description.
- Acquiring needs more than a licence. Merchant onboarding, processing, settlement, chargeback handling, safeguarding, and partner contracts must work together.
- Capital depends on services. MFSA rules distinguish payment-service categories with initial capital thresholds of €20,000, €50,000, or €125,000. Ongoing own funds can exceed the initial amount.
- EEA expansion requires the proper process. Authorisation can support cross-border activity through the applicable passport notification. It does not make every new market immediately operational.
- Ownership changes need planning. Changes to a qualifying holding or beneficial ownership structure require the MFSA’s prior approval.
- Sensitive merchant sectors require evidence. Experience with gaming or crypto-sector merchants does not mean every proposed customer or payment partner will be accepted.
- Legasset’s role. We help identify suitable entities, coordinate buy-side review, and plan the regulatory and operational work around acquisition or a new application.
Is a Malta API Licence Right for Your Payment Business?
Table of Contents
Start with what happens to the customer’s money. An API may be appropriate where the business provides authorised payment services, such as executing transactions, merchant acquiring, or money remittance.
The commercial terms “PSP” and “payment processing” do not answer the licensing question. Establish who contracts with the merchant, receives funds, executes the payment, bears chargeback risk, and settles the balance. Those functions may involve different entities and agreements.
Who Benefits from Buying an Existing Malta API?
An acquisition may suit a buyer who wants both the relevant permission and an operating business built around it. An existing API may have a team, merchant portfolio, processing history, and established relationships that would take work to develop from the beginning.
It is especially worth considering when:
- the target’s authorised services match the buyer’s product;
- its merchant sectors fit the buyer’s risk appetite;
- key staff and providers are willing to continue;
- the technology can be retained and supported;
- the buyer can fund ongoing capital and compliance needs.
An operating company is valuable only to the extent that these features can be verified and used after closing.
When a Malta Payment Institution Is the Wrong Fit
If the product requires issuing electronic money, assess an electronic money institution (EMI) instead. A payment institution does not gain that permission merely because it handles payment accounts or temporarily receives funds while executing transactions.
A target may also be unsuitable if its authorisation excludes a required service, its main partners will not support the buyer’s merchant sectors, or its technology needs extensive replacement. In those cases, the apparent advantage of an existing licence can be consumed by post-acquisition work.
- Product Fit: Map each step from merchant onboarding to final settlement. The target needs the correct permissions and a workable arrangement for every regulated function it performs.
What Services Can a Malta Payment Institution Provide?
Malta’s framework implements the EU payment-services regime through the Financial Institutions Act and MFSA rules. The services available to a particular API depend on its authorisation.
Merchant Acquiring, Processing and Settlement
An authorised institution may hold permissions relevant to executing payment transactions, acquiring payment transactions, issuing payment instruments, or money remittance. Payment initiation and account information services are separate categories that require the appropriate permission.
Do not assume every API has every payment-service permission. Compare its MFSA authorisation with the contracts and payment flows in operation.
This matters particularly for merchant acquiring. A listing might say that the company “processes payments,” but that does not establish whether it is the regulated acquirer, a processor acting for another firm, or a technical provider. Ask who signs the merchant agreement, receives and safeguards funds, manages chargebacks, and makes settlement decisions.
Where an EMI Licence Is Required Instead
A payment institution licence does not, by itself, permit electronic money issuance. If your product involves stored monetary value issued on receipt of funds and accepted by parties other than the issuer, the Malta EMI route needs separate assessment.
This is a product-design question. A payment account used to execute transactions and an e-money wallet may appear similar to a customer while creating different regulatory requirements for the provider.
Buying an Operating Malta API: What Creates Value?
Buyers often compare the asking price with the cost of a new licence application. That misses much of the commercial picture. An operating API may be valuable because of its merchant relationships, staff, technology, transaction history, and partner agreements.
The next question is which of these assets will remain useful under the new ownership.
Merchant Portfolio, Payment Partners and Technology
| Asset presented in a sale | The question that affects its value |
|---|---|
| Merchant portfolio | How many merchants are active, profitable, compliant, and contractually retainable? |
| Processing volume | What share is recurring, and how concentrated is it among merchants or sectors? |
| Payment partners | Which services are live, under whose agreements, and subject to what change provisions? |
| Core system | Who owns the code, data, integrations, documentation, and maintenance rights? |
| Team | Which employees and key function holders will remain after the transaction? |
| Regulatory record | Are there open findings, remediation commitments, reporting issues, or restrictions? |
How to Test Transaction Volume and Profitability
High volume deserves deeper review because it can coexist with thin margins or significant exposure. Ask for merchant-level data over several periods rather than relying on one headline month.
Examine volumes alongside:
- net revenue after bank, scheme, processor, and gateway fees;
- chargebacks, refunds, fraud losses, and merchant reserves;
- concentration in a few large merchants;
- seasonality and recent changes in the portfolio;
- settlement delays and working-capital needs;
- compliance and staffing costs required to support the activity.
A description such as “slightly profitable” should lead to an examination of normalised earnings and cash needs. It should not be treated as an assurance that the buyer will inherit the same result.
Malta API for Gaming, Crypto and Other Sensitive Merchants
Some payment institutions have experience serving merchants in sectors assessed closely by banks and payment schemes. That experience can be commercially useful when supported by appropriate controls, documented partner acceptance, and a well-understood merchant portfolio.
What a Payment Licence Does Not Authorise
An API licence covers the institution’s approved payment services. It does not grant a merchant a gaming licence, authorise crypto-asset services, or override requirements in the merchant’s operating markets.
A company’s experience with one gaming or crypto business does not establish that it can onboard every business in that category. The precise merchant activity, jurisdictions, transaction flows, and partner restrictions all matter.
Five Checks for a Specialist Merchant Portfolio
- Merchant legitimacy: required licences or registrations, ownership, operating countries, and products sold.
- Transaction behaviour: expected volumes, refunds, chargebacks, fraud alerts, and unusual flows.
- Partner acceptance: whether banks, schemes, and processing partners allow the specific activities.
- Contract terms: reserves, rolling holds, prohibited activities, termination rights, and liability allocation.
- Control capacity: the compliance team, monitoring rules, escalations, and evidence behind onboarding decisions.
- Portfolio Risk: A merchant category served by the current API may not fit the buyer’s future partners or risk appetite. Check the underlying agreements before assigning a premium to that portfolio.
Malta API Capital Requirements and Operating Costs
Capital is tied to the authorised payment services. The statutory starting figure is only one part of the financial commitment involved in running an API.
Initial Capital by Authorised Payment Service
| Payment-service category | Initial capital threshold |
|---|---|
| Money remittance | €20,000 |
| Payment initiation | €50,000 |
| Core services, including execution of payment transactions and acquiring | €125,000 |
Own Funds and the Real Cost of an Acquisition
A payment institution must maintain own funds under the applicable method. For a business processing substantial volumes, the calculated requirement may exceed its initial capital threshold. The MFSA may also assess the institution’s capital position in light of its risk and controls.
Model the acquisition using the target’s actual figures and agreements:
- capital and own funds against historic and projected volumes;
- safeguarding and settlement account costs;
- scheme, processor, gateway, and software fees;
- fraud losses, chargebacks, and merchant reserves;
- management, AML/CFT, reporting, audit, and ICT expenses;
- transaction costs and planned post-closing changes.
This work helps distinguish the purchase price from the money needed to operate the business after acquisition.
Safeguarding and Settlement for a Malta Payment Institution
A payment institution receiving relevant customer funds must protect them under the applicable safeguarding rules. In an acquiring business, the buyer needs to know what the institution owes each merchant and how those liabilities are recorded and protected.
Follow a Payment from Customer to Merchant
Select several transaction types and trace them from initiation to final settlement. Identify:
- who receives the funds at each stage;
- where they are held;
- when the merchant becomes entitled to settlement;
- how fees, refunds, reserves, and chargebacks are treated;
- who investigates a reconciliation break.
This exercise can reveal more than a general statement that “safeguarding is in place.” It tests whether the legal description, system records, account structure, and actual operating process agree.
Check Reconciliations and Supervisory History
Request the safeguarding policy alongside reconciliations, account confirmations, exception logs, and relevant audit findings. A named banking provider does not prove that all protected liabilities are included and correctly calculated.
The MFSA supervises financial institutions through regulatory returns, financial statements, and risk-based reviews. Examine correspondence and any outstanding actions before treating a company’s operating history as an advantage.
How to Buy a Malta API Company
The acquisition generally involves shares in an MFSA-authorised institution. The licence remains with the company; it is not removed and transferred separately to the buyer.
MFSA Approval for a Change of Ownership
Under the MFSA’s current application rule, a change in a qualifying holding or beneficial ownership structure requires prior MFSA approval. Proposed owners are assessed for fitness and propriety.
Plan this before agreeing the completion sequence. The buyer’s ownership documents, source of funds, group structure, and intended changes to the business may all affect the information required for review.
Regulatory and Commercial Due Diligence
Run two connected reviews:
- Regulatory: permissions, capital, safeguarding, management, compliance, reporting, MFSA correspondence, and outstanding remediation.
- Commercial: merchant quality, contract terms, revenue, reserves, partner concentration, technology rights, employees, liabilities, and working capital.
Neither review can replace the other. A clean financial statement does not establish good regulatory controls; an active licence does not establish a profitable business.
What the Transaction Documents Need to Address
The share purchase agreement should reflect what diligence reveals. Depending on the target, material issues may include MFSA approval, partner consents, continued access to technology, key-person retention, and the treatment of unsettled merchant funds.
Agree what evidence is needed before payment and completion. Regulatory approval, merchant retention, and partner continuity are different matters and should not be bundled into one vague promise of a “ready-to-operate” company.
- Deal Sequence: Record which permissions and relationships must be confirmed before closing, who obtains each confirmation, and what happens if one is unavailable.
Buy an Existing Malta API or Apply for a New Licence?
Acquisition can be the stronger route when the company’s permissions and operating business already resemble what you intend to build. A new application deserves consideration when you would replace most of the target’s customers, systems, people, or providers.
When an Existing Malta Payment Institution Makes Sense
An existing API may offer a working combination of authorisation, merchants, personnel, systems, and partner contracts. Those components can justify a purchase when diligence supports them and the buyer can continue the operation.
The decision should be based on the business you can operate after closing, including the cost of required changes. Do not value every historic merchant or integration as though it were guaranteed to remain.
When a New MFSA Application May Be Better
| Existing API | New application |
|---|---|
| Assess a company with a licence and operating history. | Design the institution around the proposed product. |
| Investigate historic liabilities and remediation. | Build systems and provider arrangements before launch. |
| Check retention of merchants, partners, and staff. | Select merchants and partners for the intended risk model. |
| Plan ownership approval and post-closing changes. | Complete MFSA review and licensing conditions. |
Malta API Passporting and Operational Readiness
A Maltese API may seek to provide its authorised services in other EEA states through the applicable passport notification process. The institution still needs systems, people, and partners capable of supporting the activity it plans to conduct.
Expanding Payment Services Across the EEA
Passporting concerns the regulated permission. It does not automatically supply a bank account, local merchant demand, scheme access, or compliance coverage for each new market.
Examine the proposed countries, distribution channels, agents or branches, customer communications, and partner reach. The institution must be able to supervise its activities beyond Malta while remaining within its authorised service scope.
Technology, Outsourcing and DORA
An API may rely on cloud hosting, payment gateways, fraud systems, and outsourced customer support. Buyers should understand who operates each critical function and what happens if a provider fails.
Review incident records, access to transaction data, recovery arrangements, outsourcing contracts, and the institution’s applicable Digital Operational Resilience Act (DORA) work. These matters can affect both transaction value and the resources needed after acquisition.
How Legasset Helps with a Malta API Acquisition or Application
We start with the payment services you intend to provide, the merchants you want to serve, and the countries in which you plan to operate. This tells us which permissions an existing Malta API must hold and whether an EMI or another jurisdiction would serve you better.
For an acquisition, we help source relevant institutions and organise the information needed for buy-side review. We coordinate work on MFSA ownership approval, merchant quality, safeguarding, partner contracts, capital, and post-closing operations with the parties and specialist advisers.
For a new application, we help define the service model and coordinate preparation of the regulatory materials. The aim is to select a route that supports the business you intend to operate.
Discuss Your Malta Payment Institution Plans
Tell us which services you need, where your merchants operate, and whether an existing customer portfolio matters to you. We can then compare available Malta APIs with a new application and identify the approvals, controls, and commercial arrangements each option requires.
FAQ About Malta API Licences and Acquisitions
Can I buy an authorised payment institution licence in Malta?
An acquisition generally concerns shares in the MFSA-authorised company. The buyer must assess the institution and proposed ownership change. A change in qualifying holding or beneficial ownership structure requires the MFSA’s prior approval.
Does a Malta API licence include merchant acquiring?
It can, if acquiring falls within that institution’s authorised services. Confirm its MFSA permission and operating contracts. Processing software or merchant relationships alone do not establish an acquiring permission.
Can a Malta API issue electronic money?
A payment institution licence does not, by itself, authorise electronic money issuance. If the planned product requires e-money, assess an EMI authorisation or a suitable existing EMI company.
How much capital does a Malta API require?
The initial threshold depends on its authorised services. MFSA rules specify €20,000, €50,000, or €125,000 for relevant categories. The institution must also maintain applicable own funds, which may exceed the initial threshold.
Can a Malta API work with gaming or crypto-sector merchants?
The sector label does not provide a universal answer. Assess each merchant’s activity, legal status, risks, and payment flows. The API’s banking, scheme, and processing partners must also support the relationship. An API licence does not authorise the merchant’s underlying regulated activity.
Does MFSA authorisation give immediate access to the EEA market?
Authorisation can support EEA activity within the approved service scope through the applicable notification process. Commercial launch still depends on operational arrangements, partner coverage, and controls for the proposed markets.
