EU passporting from a Czech payment institution: how far it reaches

Passporting under the EU payment services framework is a home-state procedure. The Czech institution files its notification with the Czech National Bank, identifying the host state, the payment services concerned and the delivery mode - freedom to provide services, a branch, or agents. The CNB transmits the notification to the host authority within one month; the host state registers the inbound institution but does not re-authorise it.

The result appears in two public places: the CNB's record for the institution and the European Banking Authority's central register, which aggregates passport notifications across the EEA. When a counterparty - or a buyer of the institution - wants to know the real footprint, those records are the answer. The theoretical maximum is 29 host states; the notification schedule in force shows the institution's current commercial footprint.

The freedom-to-provide-services route is the lightest: no local establishment, the Czech entity contracts cross-border. It fits payouts, collections and remittance corridors where clients are onboarded remotely. A branch is a physical establishment under home-state prudential supervision with host-state conduct overlays - heavier, and chosen when local presence is commercially necessary.

Agent networks deserve their own acquisition workstream. Each agent providing payment services in a host state must be notified and registered, and the institution answers for its agents' conduct. An inherited agent network is therefore both an asset - live distribution in host markets - and a diligence surface: every agent entry should reconcile to the register, a contract and a monitoring file.

Delivery modes also interact with AML obligations. A services-passported institution generally reports to its home financial intelligence unit, while establishments and agent networks can trigger host-state AML registration and central contact point duties. The operating model, not the passport label, determines the compliance build.

A corridor launch is a project with regulatory, banking and operational tracks that only partly overlap. The regulatory track starts with the CNB notification for the target state, service and mode; the framework's one-month transmission window is the floor, and establishment routes add host-side registration of branches or agents on top. Filing early keeps those steps aligned with the intended launch date.

The operational track runs in parallel: local payment rails or partner arrangements, currency and settlement design, customer terms in the host market's consumer-law shadow, and the AML overlay - which for establishments and agent networks can mean host-state registration duties and a central contact point. None of that is exotic; all of it belongs on the same timeline as the notification, not after it.

A practical pattern is corridor batching: notify the next two or three target states while the current ones are in build, so the regulatory lead time is absorbed by the operational one and the footprint develops in commercial-priority order.

A seller may describe the institution as able to serve 30 EEA countries. The authorisation creates that potential; the live CNB and EBA notification schedule shows the markets, services and delivery modes already in place. Agent registrations can continue with the institution, while each commercial relationship remains governed by its contract and should be reconciled to the relevant host register.

Passport notifications belong to the institution and continue through a share sale. If the buyer plans new corridors or a different service mix in the first hundred days, that expansion plan should be included in the qualifying-holding file and sequenced with the ownership process.