One regulator, several instruments and a practical choice
The Czech National Bank is the single authorisation and supervision authority for the financial market: banks, payment institutions, e-money institutions, investment firms and, under MiCA, crypto-asset service providers. That concentration is a practical advantage - one filing office, one supervisory culture, one set of public registers - but it makes precise vocabulary essential, because every instrument carries different capital, governance and passporting consequences.
Act No. 370/2017 Coll., on Payment Systems governs the payments perimeter. Under it, a payment institution provides payment services from operating accounts and executing transfers to acquiring, issuing instruments, remittance and payment initiation. The electronic money institution regime adds e-money issuance with its own capital and safeguarding rules. Deposit-taking remains reserved to banks.
The Czech permission map, as of July 2026
| Instrument | What it covers | EEA passport |
|---|---|---|
| Instrument Payment institution authorisation | What it covers Payment services 1-7 of the PSD2 annex per the recorded schedule | EEA passport Yes, service by service via CNB notification |
| Instrument Electronic money institution authorisation | What it covers E-money issuance plus payment services | EEA passport Yes, including distribution arrangements |
| Instrument Small-scale payment service provider registration | What it covers Capped volumes, Czech market only | EEA passport No |
| Instrument Small-scale electronic money issuer registration | What it covers Capped e-money float, Czech market only | EEA passport No |
| Instrument MiCA crypto-asset service provider authorisation | What it covers Crypto-asset services under the EU MiCA regulation | EEA passport Yes, under MiCA's own notification rules |
| Instrument Banking licence | What it covers Deposit-taking and the full banking perimeter | EEA passport Yes, under CRD |
The decision logic most models reduce to
Start from the money flow. If your model holds client funds in accounts and moves them - payouts, collections, acquiring - you are in payment institution territory, with initial capital of EUR 125,000 for the full service set. If you issue stored value that customers redeem later, that is e-money issuance and the EMI regime. If you only initiate payments or aggregate account data, the lighter payment initiation and account information regimes apply, at EUR 50,000 and no initial capital tier respectively.
The small-scale registrations serve genuinely local, capped models. They combine a defined Czech-market scope with volume limits and a conversion project when the business outgrows them. Cross-border ambitions almost always justify filing for the full authorisation directly - or acquiring an entity that already holds it.
Crypto-asset services use MiCA authorisation through the Czech National Bank, with the applicable white-paper, prudential and conduct rules. A payments platform adding crypto rails maps the payments and MiCA perimeters together and plans the two permission workstreams around one operating model.
PI or EMI - the boundary that actually bites
The payment institution and e-money institution regimes overlap enough to confuse and differ enough to matter. Both can operate payment accounts and execute transfers. The boundary is stored value: the moment customers pre-fund balances that function as a means of payment against the issuer - wallets topped up today and spent next month - the model is issuing electronic money and maps to the EMI regime.
The difference cascades through the file. An EMI carries the e-money initial capital requirement, float-based own funds alongside the payments calculation, safeguarding sized to the outstanding e-money, and redemption obligations with their own conduct rules. Customer balances held beyond the payment-execution window can move the model from payment services into e-money issuance, so the product design and ledger treatment should be settled before filing.
Groups sometimes run both instruments deliberately - a PI for payouts and acquiring, an EMI for wallet products - or hold the EMI authorisation with payment services recorded inside it. Which structure wins is a product-roadmap question: if stored value is eighteen months away, filing the PI now and upgrading later costs two processes; filing the EMI once may cost more capital sooner but only one assessment.
The public registers support faster transaction verification
Every instrument on the map above resolves to a public record. The Czech National Bank maintains the lists of regulated and registered financial market entities - the JERRS system - where an entry shows the entity, its instrument and the services or activities recorded under it. Agents enter through the REGIS notification system; small-scale registrants appear with their limited status visible; MiCA authorisations join the same public architecture.
In a partnership or acquisition, SKY7 reconciles the entity name, recorded instrument and service schedule against the proposed operating model. A payment institution authorisation, small-scale registration, agent appointment and MiCA authorisation each support a different scope, and the public record gives the transaction team a clear basis for structuring and diligence.
Four questions that settle the instrument
-
Do you hold client funds in accounts you operate?
Yes points to the payment institution or EMI authorisation, with safeguarding from day one.
-
Do customers pre-fund stored value you redeem?
That is e-money issuance and points to the EMI regime.
-
Do you need more than the Czech market?
EEA reach points to full authorisation and its notification framework.
-
Are crypto-assets part of the product?
MiCA authorisation via the CNB runs in parallel; plan both perimeters together.
Where the Czech venue sits on the EU licensing map
Venue selection inside the EU is a trade between regulator familiarity with your model, process predictability and the operating cost of substance. The high-throughput hubs process more payment applications and carry the queues to match; the Czech National Bank runs a codified, decree-driven process with fewer applicants competing for attention, an integrated view across banking, payments and MiCA, and public registers that make every outcome verifiable.
The trade-offs are real rather than rhetorical: filings and formal interaction run in Czech, so local counsel and translation are part of the plan; the local fintech-talent pool is deep for engineering and solid for compliance, and Prague substance costs sit below the western-hub benchmark. For a group whose EEA strategy is corridors and passporting rather than a Czech consumer brand, those economics usually favour the venue. A Czech payment institution authorisation reaches Berlin through the same EU passporting framework as one granted in another member state.
FAQ
Frequently asked questions
01 How does the CNB assessment timetable work?
The instruments and assessment standards are set by Act 370/2017 and the EU frameworks behind it. A complete application enters the CNB's three-month decision framework, so preparation quality and a coherent evidence file are the practical levers available to an applicant.
02 Who supervises fintech companies in the Czech Republic?
The Czech National Bank authorises and supervises payment institutions, e-money institutions, small-scale registrants and MiCA crypto-asset service providers, and maintains the public lists where any counterparty can verify a permission.
03 Can a foreign group own a Czech payment institution?
Yes. Qualifying shareholders are assessed for soundness and transparency during authorisation, and any later acquisition of a qualifying holding goes through the CNB's assessment framework before closing.
Keep reading