Digital asset regulation and tokenization in Hungary

In Hungary, businesses must distinguish MiCA financial authorisation from former national conversion-validation rules. Those rules changed in August 2026. Relying on 2025 documents without checking the amendment can lead to requesting procedures that no longer apply.

The Magyar Nemzeti Bank, MNB, remains the reference for services within its supervision. This guide follows asset classification, electronic applications, holder rights and conduct duties that need to be reflected in the product.

What changed when additional validation was removed

MiCA determines requirements for crypto-asset issuance and services within its scope. Act VII of 2024 supports domestic implementation. Classification precedes licensing choices: tokenized financial instruments fall under securities rules, while electronic money and asset-referenced tokens have specific requirements. A commercial token label does not establish its legal category.

Act XXXVIII of 2026 removed additional conversion validation requirements. SZTFH confirms abolition of this obligation and associated specific criminal offences. The reform took effect on 7 August 2026. It does not deregulate financial services or remove authorisation, anti-money laundering and customer protection requirements.

What MNB authorises and which regime ended

The Magyar Nemzeti Bank, MNB, handles CASP authorisation and supervises financial activities within its remit. Its procedure distinguishes authorisation applications from notifications by institutions meeting MiCA Article 60 conditions. An institution's existing status does not automatically permit every new crypto-asset service.

The consolidated statute closes pending validation proceedings and extinguishes validator licences following the reform. That regime must be distinguished from MNB financial authorisation. Former SZTFH certification does not establish CASP entitlement and should not be presented as a current market access requirement.

How to apply and demonstrate capacity

MNB guidance provides for electronic filing through ERA, with information about the entity, responsible persons and operations. Prudential safeguards apply throughout the business: paying a specified amount at incorporation is insufficient. Applications must match actual services, risks and available resources.

Hungary required pre-existing providers to comply by 1 July 2025. The EU maximum transition date in July 2026 cannot automatically be applied to those firms. Cross-border provision requires the relevant communication under MiCA Article 65. Entitlement should be checked by legal entity and service, rather than commercial brand.

What tokenized securities arrangements require

The MNB explains the DLT pilot as a dedicated route for financial instrument infrastructure, with defined permissions and exemptions. This establishes the regulatory framework, not authorisation of any particular Hungarian platform. Its 2023 report is used to explain the regime rather than describe the current operator population.

The DLT Regulation does not make every token a security or independently confer ownership of underlying assets. Documentation must identify issuer, represented rights, transfer conditions and register functions. Where intermediaries participate, the structure should establish responsibility to holders and treatment of their positions in insolvency.

What clients must be told and operations must control

The MNB announced conduct expectations applying from 1 October 2026 on client assessment for advice and portfolio management, and transfer information. Firms should explain the process, maintain current information and communicate costs, timing and irreversibility. Operational procedures and understandable communications must support these expectations.

DORA requires entities within its scope to manage technology risk, including third parties and continuity. The Transfer of Funds Regulation requires originator and beneficiary information for affected transfers. Custody and execution architecture should support compliance while distinguishing technical confirmation, customer consent and legal settlement.

How to prepare under the current framework

Prepare services, corporate structure, resources and controls for submission to MNB through ERA. Review references to SZTFH validation in light of the amendment; its removal does not replace provider authorisation or controls.

Before operating, coordinate customer assessment, cost disclosures and transfer explanations with technical processes. Tokenized securities require separate issuance, register and rights documentation. Cross-border operations need the relevant communication and scope checks rather than treating a licence as covering every service or group company.

To understand how this framework applies to your project, discuss your case with our team.