Multi-Jurisdiction Strategy Is Getting More Deliberate

This is the fifth of seven follow-ups, each taking one trend from our 2026 outlook and pushing past the headline into the part that changes how an operator actually runs. Trend #5 was that multi-jurisdiction strategy is getting more deliberate - geography turning from a reflex into a plan. The headline - "go multi-jurisdiction" - is true and almost useless on its own. The sharper version is a sequence of decisions, each one narrowing the next: where are your customers, what reaches them, where can you operate, and where does a second entity actually earn its keep? Walk them in order and the map draws itself.

Every deliberate map starts at the same place, and it is not a regulator's website. It is your own customer and revenue base. For most of the last decade the order ran backwards: you picked a home regulator on price and speed, secured an EMI or payment institution license, and assumed passporting would carry you across the rest of Europe. That worked when regulators were competing for fintech business and substance expectations were light.

Two things changed. Regulators across the EEA have raised their substance bar - they now expect real local management, staff and decision-making, not a brass plate - and the map itself fragmented when the UK left the single market. The cheap-and-fast home base is often the one that costs you most over the life of the license, because you cannot staff it credibly or because it carries a reputational discount with banking partners.

The deliberate version inverts the order. You begin from where your customers and revenue actually are, and let every later decision follow from that - price comes last, not first. The rest of this piece is the path that demand sets in motion: three forks, taken in order.

Passporting is still the single most valuable feature of an EEA license, and it is widely misunderstood in both directions. Under PSD2 - Directive (EU) 2015/2366 and EMD2 - Directive 2009/110/EC, an authorized payment or e-money institution can provide its services across the entire EEA on a single home-state authorization, notifying other regulators rather than re-applying in each one. That is genuinely powerful: license once, reach thirty markets.

The limit is that the passport is exactly as wide as the EEA and no wider. It does not reach the UK, Switzerland or any market outside the bloc, and it does not soften local conduct rules, language requirements or consumer-protection regimes you still have to meet market by market. A passport gives you the right to offer the service; it does not give you product-market fit or a local complaints process.

So the first fork is not "can I passport?" - almost always yes - but "does the passport cover the markets that matter to me, and what still has to be built locally even where it does?" If every market on your map sits inside the EEA, the path is short: one well-chosen license, passported, is the whole strategy. If any market sits outside it, you keep walking - the passport is the floor, not the ceiling.

If the license is going to passport anyway, the home jurisdiction is a fit decision, not a price one. The capital floor is set EU-wide, so countries do not really compete on the headline number - they compete on regulator speed and style, substance expectations, language and total cost to operate year after year. Our comparison of EU fintech jurisdictions sets out how those trade-offs actually fall.

The practical filters are consistent. Where can you realistically build substance - a local board, compliance staff, an office that satisfies the regulator? Which language can your team operate in for every renewal and supervisory exchange? How does the home regulator's reputation read to the banking partners and schemes you will need? A Lithuania EMI license, for instance, is shortlisted by firms that want fast EEA access and a fintech-experienced supervisor, but the right answer for a group that needs a blue-chip regulator and a particular home market will be different.

The common mistake is optimizing for the application and ignoring the operation. A jurisdiction you cannot staff, or whose language you cannot work in, becomes a tax on every interaction with the regulator for the life of the license. Choose for where you can actually run the entity, then passport from there.

For some firms a single license genuinely is not enough, and the deliberate move is a second entity. The clearest case is the UK: since it left the single market, an EEA passport no longer reaches it, so serving UK customers means a separate UK authorization alongside your EEA license. The same logic applies to Switzerland and to any non-EEA market you want to serve directly rather than through a partner.

A second entity is a serious commitment - duplicated capital, governance, reporting and substance in each location - so the test is whether the market justifies it. A material customer base, a regulator that requires local presence, or a strategic need to be supervised in-market can all clear that bar. A vague sense that "more licenses look impressive" does not; it just multiplies your fixed costs and your audit surface.

This is also where regulatory arbitrage shows its limits. Picking a jurisdiction purely to exploit a lighter-touch regime is a fragile strategy: substance expectations are converging upward, supervisors share information, and a home base chosen to dodge scrutiny tends to attract exactly the scrutiny it was meant to avoid. The durable version of multi-entity structuring follows real demand and real obligations, not a loophole.

Most operators do not start at the same fork - where you enter the path depends on what you run.

For early-stage EMIs and payment institutions whose market is entirely within the EEA, the lesson is restraint: one license, chosen for operating fit rather than price, passported across the bloc. Resist adding entities until demand outside the EEA actually forces it.

For scale-ups with UK or Swiss customers, the map is the priority. Decide early whether those markets justify a second authorization or are better served through a partner, and budget for the duplicated substance before you commit.

For crypto businesses, MiCA now offers an EU-wide authorization that passports across the bloc, so the same "license once, reach the EEA" logic applies - but non-EEA crypto markets still need their own answer.

For founders generally, the trap is treating jurisdiction as a procurement decision made on cost. It is a strategic choice about where you can build substance and reach the customers you actually want. Draw the map first; buy the licenses it requires, not the ones that look cheapest.

The headline - go multi-jurisdiction - is true and, on its own, not much help. The operating consequence is that geography has become a path you walk on purpose rather than a word you say. Each fork narrows the next: start from your customers, test whether one passport reaches them, choose a home base you can actually operate, and add a second entity only where a real market and real obligations demand it. The single rule that holds the whole path together is this: draw the map before you buy anything. Map first, licenses second. Done in that order, expansion compounds. Said as one word on a slide, it just multiplies cost.

This is the fifth in a seven-part series expanding on our 2026 fintech trends. If you are weighing which jurisdictions your model actually needs, speak to our team - we have run jurisdiction selection across 100+ licensing processes.