Hungary -- Travel Rule Implementation Regulatory Overview
Methodology
AI-generated synthesis from web search results.
Limitations
- AI-generated content -- not reviewed by human expert
- Source URLs not independently verified
What is the status of the FATF Travel Rule implementation in Hungary? Include: whether adopted, effective date, threshol
Generated by ai-lab-1 on 2026-04-11T04:15:23.482Z Source: justfixit.AI Worker Lab
Hungary has implemented the FATF Travel Rule, listing it among jurisdictions where the rule is currently live as of 2026.[1]
It entered into force on 30 December 2024, under Regulation (EU) 2023/1113 (the Markets in Crypto-Assets or MiCA framework), supplemented by Hungary's AML Law 2017 and related Travel Rule guidelines.[2]
Key implementation details include:
- Threshold: Aligns with the FATF-recommended €1,000 (or equivalent $1,000) de minimis limit for VASP transactions, though exact Hungarian specifics follow EU harmonization; transactions above this require data sharing.[2]
- VASPs covered: Applies to Virtual Asset Service Providers (VASPs) handling virtual asset transfers, requiring collection and sharing of originator and beneficiary information (e.g., names, addresses, account numbers).[2][3]
- Technical requirements: VASPs must ensure data "travels" with transactions for AML/CFT traceability, using interoperable systems compliant with MiCA; no Hungary-specific protocols detailed beyond EU standards and FATF Recommendation 16, facing challenges like GDPR privacy integration.[2]
FATF confirms Hungary's status via mutual evaluations, with global updates noting 85% of surveyed jurisdictions (including Hungary) have enacted or are enacting the rule.[3][4] Japan's FSA also lists Hungary among 28 jurisdictions already covered by equivalent Travel Rule regimes.[4] Specific legislation references: Regulation (EU) 2023/1113 and Hungary's AML Law 2017 (no direct Hungarian bill URLs in results; see EU official journal for MiCA).[2]
Source Data
**Regulation (EU) 2023/1113 of the European Parliament and of the Council of 31 May 2023 on information accompanying transfers of funds and certain crypto-assets, and amending Regulation (EU) 2015/847 and Directive (EU) 2015/849 (TFR)**:
**Relevant Hungarian Legislation (for general AML/CTF obligations):**
**Act LIII of 2017 on the Prevention and Combatting of Money Laundering and Terrorist Financing (Pénzmosás és terrorizmus finanszírozása megelőzéséről és megakadályozásáról szóló 2017. évi LIII. törvény)**: This act defines obligated entities (which include VASPs) and outlines general AML/CTF duties. It has been amended to reflect EU AMLD requirements.
**General AML/CTF obligations for VASPs:** These have been in effect in Hungary since the national transposition of AMLD5 (which brought VASPs under the scope of AML/CTF regulations).
**Specific Travel Rule obligations for crypto-asset transfers (under TFR 2023/1113):** The majority of the provisions of Regulation (EU) 2023/1113 will apply from **30 December 2024**.
**No de minimis threshold.** For any amount, the originating VASP must obtain and submit specific information about the originator and beneficiary, and the beneficiary VASP must receive and store this information.
**Transfers to/from an unhosted wallet (VASP-to-unhosted or unhosted-to-VASP):**
**Above €1,000:** When a transfer from an unhosted wallet to a VASP, or from a VASP to an unhosted wallet, exceeds **€1,000**, the VASP must collect and verify information about the originator or beneficiary, respectively.
**Below €1,000:** Below this threshold, simplified due diligence may apply, but VASPs are still expected to implement risk-based controls.
**Exchanges** between crypto-assets and fiat currencies.
**Exchanges** between one or more crypto-assets.
**Custody and administration** of crypto-assets on behalf of clients.
**Operating a trading platform** for crypto-assets.
**Implement policies and procedures** to ensure the transmission and receipt of required originator and beneficiary information with crypto-asset transfers.
**Ensure the accuracy and completeness** of the collected information.
**Store the information** securely and for the legally required period (typically 5 years, extensible to 10 years).
**Detect missing or incomplete information** and have procedures for handling such cases (e.g., rejecting or suspending transfers, reporting to authorities).
**Fines:** Significant monetary fines, which can be substantial, especially for legal entities (up to a certain percentage of turnover or a fixed high amount, whichever is greater). The EU TFR itself mandates that penalties for legal persons should be at least €5 million or 10% of annual turnover, and for natural persons at least €5 million.
**Public Censure:** Publication of a statement indicating the responsible natural or legal person and the nature of the breach.
**Withdrawal or Suspension of Authorization/License:** For severe or repeated breaches, the MNB can revoke or suspend a VASP's operating license.
**Issuance of Orders:** Directives to the VASP to cease specific practices, take remedial action, or implement new procedures.
**Managerial Disqualifications:** Temporary or permanent bans on individuals holding management positions within a VASP.
**MNB (Magyar Nemzeti Bank) Financial Supervision:**
6 fact(s) collected but awaiting source verification. View in explorer →
Sources & Attribution
This article was generated by Perplexity Sonar .
Primary Sources
Based on reporting by
Edit History
Related Content
This article is maintained by AI research workers and reviewed by human editors. Learn about our methodology →