Which Route Fits Your Product in Czechia?
First, the key point: who’s “in charge” in Czechia
In Czechia, licensing and supervision of payment services and electronic money are handled by the ČNB (Czech National Bank). Applications are submitted electronically only, via datová schránka (data box).
Legal framework: Act No. 370/2017 Coll. (Payment System Act / Zákon o platebním styku).
Four routes, no mysticism
1) Partnering with a licensed EMI (or PI)
In plain English: you build the product (UI, marketing, sales), while the licensed partner legally “holds” the regulated payment part: accounts/wallets, issuance of e-money (if needed), and compliance obligations toward the regulator.
When this makes sense:
- you need to enter the market fast;
- you are testing a hypothesis;
- you don’t have a compliance team or budget for licensing;
- you don’t want ČNB to supervise you “like an adult” right now.
Downsides people conveniently “forget”:
- dependency on the partner (pricing, de-risking/offboarding risk, product limitations);
- their KYC/AML and policies become your reality, even if you hate them;
- the partner may restrict certain geographies, verticals, or product features.
Best fit most often: marketplaces, SaaS with payments “inside”, pre-seed/seed startups, MVPs.
2) Agent model (Agent of a payment service provider)
Simply: you do not become a licensed provider. You become an agent of an already licensed PI/EMI and act “on its behalf” under a contract.
Important: In Czechia, ČNB maintains public registers/lists of payment institutions, EMIs, and related parties.
When this makes sense:
- you focus on sales/distribution and client acquisition;
- you build a partner network and local front-end;
- you’re fine operating under the rules of the licensed principal.
Typical constraints:
- branding and communications often must meet the principal’s requirements;
- you cannot “pretend to be a bank/EMI” if you are an agent;
- the principal will monitor you regularly (controls, reporting, audits), because their licence is on the line.
3) PI (Payment Institution) licence
Plain: a PI can provide payment services, but cannot issue electronic money (e-money).
If your product is about transfers/acquiring/payment execution without issuing e-money, a PI is often more logical than an EMI.
When PI fits better than EMI:
- you do not offer a wallet that stores e-money as a “money substitute”;
- you are not building customer “balances” as e-money;
- payments matter more than issuance.
4) EMI (Electronic Money Institution) licence
Plain: EMI = you can issue electronic money and provide payment services. This usually matters if you build:
- a wallet with a stored balance;
- an “account” in the sense of a user balance;
- a payment infrastructure where you hold customer value as e-money (not just “processed a payment and moved on”).
Who truly needs EMI:
- wallet products;
- super-apps with balances;
- paytech with mass payouts plus stored balances;
- card programmes tied to an e-money wallet.
Timelines (the detail everyone “loses”): formal statutory timelines look nice on paper, but in practice everything depends on how complete and accurate the submission is. If documents are incomplete or inconsistent, the process pauses until fixes are delivered. This is also reflected in official procedure descriptions.
A small but useful Czech workaround: “small-scale”
Czechia has “small-scale” regimes for certain providers (simpler entry in principle, but with strict caps and limits). For an MVP this can sometimes work, but it rarely fits if you plan EU scaling or a “serious” product.
How to choose: a super-simple checklist
Choose partnering with a licensed EMI/PI if:
- you need to launch quickly and validate demand;
- you don’t want to invest in compliance/licensing right now;
- you can live with partner constraints.
Choose the agent model if:
- you’re strong at sales/marketing/distribution;
- you don’t want to be licensed but want to monetise acquisition/service;
- you’re fine working under a PI/EMI’s umbrella.
Choose PI if:
- you provide payment services but do not issue e-money;
- you don’t need a wallet as electronic money;
- you want more control than pure partnering, but a narrower, simpler scope than EMI.
Choose EMI if:
- your product is fundamentally wallets/balances/e-money;
- you are building the core payment infrastructure (not just a widget);
- you want independence from partners and control over unit economics.
3 typical “wrong choices” (and why it hurts)
- Building a wallet but trying to live like a PI
Then you realise the product is essentially e-money, and you end up rebuilding architecture. - Entering a partnership and assuming “everything is ours”
It isn’t. The partner has the licence, so they set the rules. Regulators love accountability. Weird, I know. - Choosing EMI “because it sounds solid”
EMI isn’t a badge. It’s an operating machine: compliance, reporting, outsourcing control, and IT resilience. If you’re not ready, you’re just buying an expensive headache.
GET A ČNB-READY GAP CHECK AND A CLEAR FIX LIST
START EMI PRE-CHECK
FAQ:
Can I launch in Czechia without a licence if I’m “just an IT platform”?
Sometimes yes, if you do not touch funds and you are not effectively providing/arranging a payment service. But once you become part of the payment chain (accepting, holding, transferring, wallet, issuing value), it quickly becomes regulated activity. In Czechia, that’s ČNB territory.
Is it true that ČNB accepts applications only via datová schránka?
Applications are submitted electronically via datová schránka. ČNB also describes the document submission process and provides the relevant contact/data box details.
What’s faster: partnering or getting your own licence?
Partnering is usually faster because you skip the full licensing process. A licence can only run “on schedule” if the application is extremely well-prepared. Otherwise timelines stretch due to corrections and follow-up questions.
Is the agent model a “safe loophole”?
It’s a legitimate model, not magic. You still operate under the principal’s rules, and they will control you because they are responsible for the licence. Your communications must also be accurate: you’re an agent, not “we are an EMI”.
