← Regulations / Hungary / travel-rule
Grade B AI-Researched

Hungary -- Travel Rule Implementation Regulatory Overview

Published: 2026-04-26 Updated: 2026-04-18 Author: Perplexity Sonar Version 1 Sources cited in: English (1), Hungarian (2)
Note: This article cites primary sources in languages other than English. Cited links open the original-language text; machine translation (via browser) may help readers verify claims. See the badge next to each source for its language.

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

60%

**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)**:

60%

**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.

60%

**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).

60%

**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**.

60%

**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.

60%

**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.

60%

**Below €1,000:** Below this threshold, simplified due diligence may apply, but VASPs are still expected to implement risk-based controls.

60%

**Implement policies and procedures** to ensure the transmission and receipt of required originator and beneficiary information with crypto-asset transfers.

60%

**Detect missing or incomplete information** and have procedures for handling such cases (e.g., rejecting or suspending transfers, reporting to authorities).

60%

**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.

60%

**Withdrawal or Suspension of Authorization/License:** For severe or repeated breaches, the MNB can revoke or suspend a VASP's operating license.

6 fact(s) collected but awaiting source verification. View in explorer →

Sources & Attribution

This article was generated by Perplexity Sonar .

Based on reporting by

[2] https://net.jogtar.hu/jogszabaly?docid=A1700053.TV — https://net.jogtar.hu/jogszabaly?docid=A1700053.TV hu
[3] https://www.mnb.hu/en/financial-supervision — https://www.mnb.hu/en/financial-supervision hu

Edit History

2026-04-26 — fix-grade-d-pipeline: upgraded — Auto-upgraded from D to B using topicFacts sources

Related Content

Fact IDs: hu.travel-rule.threshold-aligns-with-the-fatf-recommended, hu.travel-rule.vasps-covered-applies-to-virtual, hu.travel-rule.technical-requirements-vasps-must-ensure

This article is maintained by AI research workers and reviewed by human editors. Learn about our methodology →