One Passport, 27 Rulebooks: Hungary Didn't Actually Free Its Crypto Users

I keep a folder on my desktop called national add-ons. It's where every clause that a finance ministry in the EU bolted onto MiCA after the regulation passed goes to live. In September it got a new entry, and this one was a subtraction. Hungary dropped its extra crypto restrictions in August.

That should have been the end of a small, tedious story. Then I started asking people what actually changed on their phones.

The answer depended on the app. Bitvavo moved quickly and told Hungarian customers that spot trading and euro deposits were back. Others didn't. Some kept accounts in a read-only state. Some still refuse a Hungarian address at sign-up. Same country, same EU regulation, same week, different answers.

So the restriction lifted. The border stayed.

What Actually Got Removed

Start with the mechanics, because the headlines skipped them.

Hungary, like every member state, had to apply MiCA. Regulation (EU) 2023/1114 came into force in June 2023, stablecoin rules applied from 30 June 2024, and the CASP regime kicked in on 30 December 2024. On top of that, Budapest layered national conditions on the market. Extra registration steps, extra reporting, the kind of paperwork that makes a country of 9.6 million people expensive to serve relative to its revenue potential.

Scrapping those conditions in August was the right call. It was also the easy part.

Because MiCA doesn't give a crypto firm the right to serve Europe. It gives a firm the right to be authorised once in a home member state, then to notify other member states that it intends to operate there. That's the passport. It's a notification process, not an approval process. The host regulator gets told, it doesn't get to veto.

Bitvavo is licensed in the Netherlands and supervised by De Nederlandsche Bank. Once Hungary removed its national extras, Bitvavo could notify, flip the switch, and reopen deposits. It already had the licence, the capital, and the compliance team.

Smaller platforms didn't. Some are still running on old national registrations inside the transitional period, which runs for up to 18 months and expires on 1 July 2026. They can't passport anything yet, because they don't hold a MiCA authorisation. Others have the licence but no Hungarian-language support, no local payment partner, and no commercial reason to prioritise a market that might bring them a few thousand users.

Here's the part that gets glossed over. MiCA is 150 pages. The implementation guidance is 400 more. The devil lives in the delegated acts. And even the delegated acts can't force a company to find Hungary worth the effort.

The Border Isn't The Licence

This is where the story stops being about Hungary.

Every compliance officer I talk to in Brussels says the same thing, and they say it quietly. The licence was never the hard part of cross-border crypto in Europe. The banking rail is.

A MiCA authorisation lets you offer crypto services. It doesn't get you an IBAN. Euro deposits still run through payment providers and credit institutions, and those institutions have their own risk committees, their own appetite, and their own national supervisors looking over their shoulders. A Dutch exchange with a clean licence can still lose a euro deposit corridor because a bank in the corridor decides crypto isn't for it this quarter.

So yes, Bitvavo restored euro deposits for Hungarian users. That sentence contains two regulatory universes. One is MiCA. The other is a payments relationship most customers never see and never think about.

Harmonization sounds clean. The reality is 27 national interpretations, 27 competent authorities, 27 sets of marketing rules, and a transitional window that runs to 1 July 2026. Until that window closes, a customer in Hungary and a customer in the Netherlands can be holding the same asset on the same platform under two different sets of protections. That's not a detail. That's the whole ballgame for anyone who thinks passporting solved Europe.

And ask yourself this. If a licence is portable but the deposit rail isn't, what exactly did we harmonize?

What I'd Actually Check

My honest read is that the next 12 months will separate the exchanges that built real European infrastructure from the ones that bought a licence and a press release.

Brussels moves slowly. But when it moves, it moves everyone. The firms that spent 2024 and 2025 hiring compliance staff, opening local entities, and negotiating payment corridors are the ones who can turn a regulatory change into a product change within weeks. Bitvavo did it in days. That's not luck, that's a balance sheet decision made two years ago.

The firms that treated MiCA as a stamp will keep telling customers in Budapest and Bucharest and Zagreb that their market is "coming soon." It won't be a compliance problem by then. It'll be a prioritisation problem, which is harder to fix.

So if you're a user, don't read the press release. Open the ESMA register and search the entity that actually holds your account. Ask which legal entity your assets sit with, and which regulator authorised it. Then ask where the euro deposit lands, because that's the part that breaks first and gets explained last.

And if your app still says no while Bitvavo says yes, don't blame Brussels. Brussels already did its bit. The app made a choice.