There is a moment that catches many founders off guard. It usually comes after the celebration. The MiCA CASP approval lands, the board exhales, the product team starts moving again, and Cyprus begins to look exactly as it should look to an ambitious fintech: credible, European, operational, and close enough to both regulation and growth to make the equation worth it.
Then someone asks a question that changes the mood in the room: can we send and receive crypto to and from third parties in a way that feels like payments, not just crypto infrastructure?
Cyprus remains one of the most commercially interesting jurisdictions in Europe for founders looking at fintech, payments, MiCA, CIF and cross-border market access. It has regulatory density, service-provider depth, and a business environment that still understands what it means to build for Europe rather than only within one domestic market.
That is why EMI application in Cyprus, PI application in Cyprus, CIF licensing and CASP structuring often end up in the same conversation even when a business starts from only one of those boxes. A CASP thinks like a CASP until its product begins to behave like a payments business. A fintech thinks it needs a PI until it realises it wants wallet functionality and stored-value logic that may look closer to e-money. A group starts with crypto execution, then discovers that client flows, treasury design, settlement logic and third-party transfers raise questions that live under a different supervisor.
In Cyprus, that matters because payment institutions and electronic money institutions are authorised by the Central Bank of Cyprus, while MiCA in Cyprus sits within the CySEC perimeter except for electronic money tokens, which MiCA itself treats as a special category that resembles electronic money. That institutional split is not cosmetic. It is the beginning of the structuring problem.
On paper, founders often think the question is simple. We are a CASP. We move crypto. We are already regulated. Why should we need anything else?
Because regulation does not follow the pitch deck. It follows the activity.
In June 2025, the European Banking Authority advised national authorities under PSD2 to view the transfer of crypto-assets as a payment service where those transfers involve electronic money tokens and are carried out on behalf of clients. The same no-action letter also said custody and administration of EMTs can amount to a payment service, and that a custodial wallet can amount to a payment account where it is held in the name of one or more clients and allows users to send and receive EMTs to and from third parties.
That single clarification changed the boardroom conversation for many newly approved MiCA players. A founder may still describe the business as crypto. The law may already be looking at payments.
A PI application in Cyprus may become relevant where the business is effectively providing payment services, but does not need the broader electronic money perimeter. Under the Cyprus payment services framework, the initial capital requirement depends on the payment services sought: EUR 20,000 for money remittance only, EUR 50,000 for payment initiation only, and EUR 125,000 where the institution will provide payment services in points 1 to 5 of Annex I.
For a CASP that wants to facilitate the transfer of EMTs for clients, the key question is whether the model is still merely crypto execution or whether it has crossed into regulated payment activity. If the answer is the latter, the issue is no longer theoretical. It is about whether the business can continue offering the client journey it has already sold.
An EMI application in Cyprus becomes more relevant where the model includes the issuance or management of e-money-like value, wallet-based stored value functionality, or a broader architecture that looks less like a narrow payment-service overlay and more like a financial product with recurring balances and payment utility.
At EU level, the Electronic Money Directive requires an electronic money institution to hold initial capital of at least EUR 350,000 at the time of authorisation. In Cyprus, applicants must also satisfy the CBC on governance, safeguarding, internal controls and ongoing own-funds adequacy.
In practical terms, founders should not ask only which licence covers today’s feature list. They should ask which licence supports the business they expect to be operating twelve to twenty-four months from now. A PI may solve today’s overlap. An EMI may better fit tomorrow’s product roadmap.
This is usually the point where the legal discussion becomes a finance discussion.
Founders often assume that once they already meet MiCA prudential safeguards, the second licence is mainly a filing exercise. It is not. MiCA requires CASPs to maintain prudential safeguards equal to the higher of their permanent minimum capital requirement - ranging from EUR 50,000 to EUR 150,000 depending on services - or one quarter of fixed overheads. A Cyprus PI or EMI authorisation brings its own capital and own-funds logic on top.
For a PI, Cyprus law requires the applicant to hold initial capital at authorisation and to maintain own funds that do not fall below that initial capital and the amount calculated under the applicable method. The same law also empowers the CBC to prevent multiple use of own-funds elements when the payment institution belongs to a group with other regulated entities.
For EMI structures, the capital conversation is even more strategic. The EU initial-capital threshold is EUR 350,000, but that is only the beginning. EMIs are also subject to ongoing own-funds rules and safeguarding expectations, while the CBC's framework excludes certain same-group and participations-based items from own-funds calculations.
In plain English: if a newly approved CASP in Cyprus is now considering adding a PI or EMI layer, the share-capital and own-funds planning should be treated as a structuring workstream, not a clerical step. The founder has to decide whether the model belongs in one entity, in parallel entities, or in a group arrangement where capital cannot simply be counted twice.
More often than founders initially think. Cyprus is still a serious jurisdiction for CIF licensing, and CIF keeps appearing in conversations around MiCA, PI and EMI because some business models do not stay in one category. Some begin with crypto and move toward investment services. Others begin with execution or dealing features that can trigger a different analysis depending on the instrument, the client journey and the legal nature of the asset.
MiCA itself covers crypto-assets that are not already regulated under existing financial services legislation. That means founders who want to build in Cyprus cannot afford to think of CASP, EMI, PI and CIF as isolated silos. They are adjacent strategic routes that sometimes overlap around the same product.
They think the second authorisation is a burden. Sometimes it is the bridge.
A properly structured EMI or PI application in Cyprus can turn a fragile MiCA business into a more durable fintech architecture. It can clarify where client-money logic sits. It can force cleaner safeguarding analysis. It can improve the credibility of the operating model in front of banks, payment providers and institutional counterparties.
In other words, the additional regime is not always friction. Sometimes it is the moment the company stops being an approved idea and starts becoming a financial institution.
The real value of Cyprus is not only approval. It is optionality.
Cyprus can still be the right answer for a founder weighing an EMI application, PI application, CIF route or MiCA CASP structure. But the advantage does not come from forcing everything into a single label. It comes from understanding how the regimes interact before the product goes live, before counterparties ask harder questions, and before the growth team sells functionality the licence stack cannot safely carry.
That is the difference between using Cyprus as a flag and using Cyprus as a platform.
At Obtained, we see this tension more often than most founders expect. The business starts with one licence in mind. Then the model matures. Then the real shape of the company emerges. That is usually the point where licensing, payments, banking, counterparties and legal architecture need to be viewed together, not one filing at a time.
For the newly approved MiCA CASP in Cyprus, that is the real lesson. Approval is not the end of the structuring exercise. It is where the serious one begins.
|
Route |
Initial capital |
Editorial note |
|
MiCA CASP |
EUR 50k / 125k / 150k |
Permanent minimum capital depends on services; ongoing prudential safeguards are the higher of that threshold or one quarter of fixed overheads. |
|
PI |
EUR 20k / 50k / 125k |
Cyprus payment-institution capital depends on the Annex I services sought. Ongoing own funds and safeguarding rules also apply. |
|
EMI |
EUR 350k |
EMI capital is materially higher and should be considered together with ongoing own-funds and safeguarding requirements. |
No. A CASP authorisation under MiCA does not automatically solve payment-services questions where the business transacts EMTs in a way that falls within PSD2. That is exactly why founders must assess PI or EMI routes early.
A PI is authorised to provide payment services. An EMI can issue electronic money and provide payment services. For product teams building wallet-based or stored-value functionality, that difference becomes strategic very quickly.
It depends on the services: EUR 20,000 for money remittance only, EUR 50,000 for payment initiation only, and EUR 125,000 for payment services in points 1 to 5 of Annex I.
At EU level, the Electronic Money Directive sets initial capital at EUR 350,000. Cyprus applicants must also satisfy ongoing own-funds, governance and safeguarding requirements.
Not safely as a planning assumption. CBC and EMI own-funds rules include anti-double-use logic, so founders should model capital carefully at entity and group level before choosing the structure.
Further details are available upon request via strategic meeting.