Cryptoassets Regulatory Intelligence cryptoassets.gi
HU v13.3.0
content: ai_generated legal review: never_reviewed (informational) publication gate: 1 failing15 sources retrieved model claude-sonnet-5 · 2026-08-05

Hungary

HU schema crypto-v2.0.0 trajectory: not yet assessedin transitionoverlaps: FIM, WPM

Last updated · 8 categories · 19 sourced findings · 20 sources in the cumulative register

8Categoriesbaseline.
19Findings.claims[]
10Tier-1 sourcesrun_metadata.t1_source_count
Confidence mix (sums to 8 rendered categories; click to filter)
No categories moved this cycle.

Jurisdiction lead brief

Lead Signal

Hungary's crypto-asset regulatory posture is liberalising this cycle. On 20 July 2026, Magyar Nemzeti Bank (MNB) granted Tiwala Solutions Kft, operating as CoinCash, Hungary's first domestic MiCA CASP authorisation, covering custody, crypto-to-fiat and crypto-to-crypto exchange, transfer, investment advice and portfolio management. The scope of CoinCash's authorisation is broad by CASP standards: it covers most of MiCA's core CASP service categories under a single licence rather than a narrow subset. This High-confidence finding anchors an amber traffic-light assessment for crypto licensing this cycle: the first domestic licence is a material development, but it arrives alongside a second, still-unconfirmed change to the same regime. The Hungarian Parliament has voted to repeal the mandatory third-party crypto-transaction validator requirement, which had previously required verification of asset origin, wallet ownership and customer identity ahead of certain crypto conversions and had made Hungary one of the European Union's stricter CASP jurisdictions, having shortened the MiCA transition period for CASPs to 1 July 2025, a year ahead of the EU's own 1 July 2026 maximum deadline. Taken together, the picture this cycle is one of a jurisdiction that initially over-implemented MiCA's stricter-end options and is now correcting toward closer EU-standard alignment while simultaneously operationalising its first domestic licence under the corrected regime. The repeal vote is High confidence but its regulatory stage is enacted-not-yet-effective, and the exact statutory citation, effective date, and the fate of any residual criminal-liability transition for now-discontinued validation offences were not confirmed against a primary Tier-1 source this cycle; both gaps are logged and should be treated as open.

8 of 8 categories
Signal
Density

Selections OR within a group, AND across groups. Press / to search.

#

Hungary applies the EU MiCA authorisation regime with Magyar Nemzeti Bank (MNB) designated as the sole national competent authority holding 'ALL' MiCA tasks (no split with a securities regulator, unlike most peer states). Overlaid on this, Hungary enacted a stricter national law (in force 1 July 2025) criminalising the use of unlicensed crypto exchanges and large unauthorised trades, with penalties far exceeding MiCA's own enforcement toolkit; licensing application procedures under that domestic regime were never published, leaving both domestic firms and global exchanges unable to comply. As of the July 2026 end of the MiCA transitional period, Hungary had zero CASP authorisations on ESMA's interim register. In June 2026 the government announced an intention to repeal the criminal penalties, calling them 'politically motivated,' but this has not yet been enacted.

Standing sub-brief485 words · last cycle 2026-08-21

Crypto Licensing

Magyar Nemzeti Bank granted Hungary's first domestic MiCA crypto-asset service provider authorisation on 20 July 2026, to Tiwala Solutions Kft, operating as CoinCash. The authorisation is broad in scope, covering custody of crypto-assets, crypto-to-fiat and crypto-to-crypto exchange, crypto-asset transfer services, investment advice and portfolio management — most of MiCA's core CASP service categories under a single domestic licence. This is a High-confidence finding, though sourced this cycle to a single tier-three report, and the interpreter flags that a stronger Tier-1 anchor would improve confidence in the exact terms of the authorisation.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (4)
  1. T1 · ESMAESMA — Magyar Nemzeti Bank (MNB) is designated as Hungary's single competent authority under MiCA with 'ALL' tasks (authorisation and supervision), rather than splitting functions with a separate securities regulator as most Member States do.retrieved M5bindingin force
  2. T4 · The BlockThe Block — A Hungarian law passed 17 June 2025 and effective 1 July 2025 requires all crypto service providers operating in Hungary to obtain a licence from MNB, criminalising unlicensed-exchange use and unauthorised high-value trades (HUF 50m-500m) with prison terms up to 5 years for users and 8 years for service-provider operators.retrieved M5bindingin force
  3. T4 · The BlockThe Block — As of the MiCA transitional period's end (1 July 2026), Hungary had no Crypto-Asset Service Provider (CASP) authorisations listed on ESMA's interim MiCA register, unlike Germany, France and the Netherlands which led with dozens of authorisations each.retrieved M4non-binding
  4. T4 · The BlockThe Block — Hungary's Minister of Science and Technology announced in June 2026 that the government intends to scrap the criminal penalties for unlicensed crypto exchange use introduced in 2025, characterising the rules as politically motivated rather than necessary market safeguards.retrieved M4bindingproposed

#

Hungary follows the EU-wide MiCA taxonomy of asset-referenced tokens (ART), e-money tokens (EMT), and other crypto-assets (including utility tokens), with MNB implementing ESMA's guidelines on the qualification of crypto-assets as financial instruments through a domestic 'MNB Guidance,' bridging MiCA and MiFID II classification boundaries.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

no periodic updates on record for this sub-brief

Sources and findings (2)
  1. T1 · ESMAESMA — MNB has implemented ESMA's Guidelines on the conditions and criteria for the qualification of crypto-assets as financial instruments in the form of an 'MNB Guidance on the conditions and criteria for the qualification of crypto-assets as financial instruments.'retrieved M3bindingin force
  2. T1 · EUR-LexEUR-Lex — The MiCA classification distinguishing e-money tokens (EMTs), asset-referenced tokens (ARTs) and other crypto-assets applies directly and uniformly in Hungary as an EU Member State, with EMT/ART-specific rules (Titles III/IV) having applied since 30 June 2024.retrieved M4bindingin force

#

MiCA's CASP licensing regime (enforced in Hungary by MNB) covers custody, exchange, execution of orders, placing, portfolio management and transfer services, and MNB has adopted ESMA's transfer-services guidelines. However, MiCA does not itself regulate DeFi lending/borrowing, staking, mining, or validator/node operation as such (Recital 94); EU-level guidance (ESMA Q&A) only addresses disclosure expectations where a licensed CASP chooses to offer such unregulated services alongside regulated ones. No Hungary-specific bespoke regime for these activities was identified.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

no periodic updates on record for this sub-brief

Sources and findings (3)
  1. T1 · ESMAESMA — MNB has confirmed compliance with ESMA's Guidelines on transfer services for crypto-assets under MiCA, publishing an implementing MNB recommendation applicable to CASPs providing transfer services on behalf of clients.retrieved M3bindingin force
  2. T1 · ESMAESMA — MiCA does not address the lending and borrowing of crypto-assets (Recital 94); CASPs offering such unregulated services, including decentralised lending protocols, remain subject only to general MiCA conduct obligations (fair, clear, non-misleading communications) rather than a dedicated licensing regime, and no Hungary-specific supplementary regime was identified.retrieved M3non-bindinga fact about the regime
  3. T1 · ESMAESMA — No Hungary-specific licensing or registration regime for staking, mining, or validator/node operation activities (as distinct from MiCA CASP-intermediated services) was identified in research to date.retrieved M2non-bindingour coverage gap, expected to resolve on a re-run

#

Hungary applies MiCA Titles III and IV (ARTs and EMTs) directly, with MNB as competent authority for issuance authorisation, reserve, redemption-right and disclosure obligations since these titles took effect on 30 June 2024, ahead of the full CASP regime. Industry commentary (Ripple, cited in coverage of the July 2026 MiCA milestone) flags that multi-jurisdictional stablecoin issuance treatment remains unresolved across the EU generally, a gap not specific to Hungary but affecting HU-facing issuers.

Standing sub-brief190 words · last cycle 2026-08-21

Stablecoin Regime

On 25 March 2026, Magyar Nemzeti Bank issued Recommendation No. 5/2026 (III.25), transposing European Securities and Markets Authority guidelines on crypto-asset transfer services. The recommendation addresses disclosure requirements, cut-off times, execution times, and risk-based transaction policies that crypto-asset service providers are expected to apply. This is a High-confidence finding sourced to a tier-two source, though the recommendation itself is explicitly non-binding: MNB expects CASPs to align with it as a matter of supervisory expectation rather than legal obligation. The interpreter accordingly rates this module green rather than amber, reflecting that the development is guidance-level EU-alignment rather than a new binding domestic obligation.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (2)
  1. T1 · EUR-LexEUR-Lex — MiCA's asset-referenced token (ART) and e-money token (EMT) issuance authorisation, reserve and disclosure requirements (Titles III and IV) have applied across the EU, including Hungary under MNB supervision, since 30 June 2024, ahead of the CASP regime's full application.retrieved M4bindingin force
  2. T4 · The BlockThe Block — Industry participants report that key elements, including the treatment of multi-jurisdictional stablecoin issuance and associated redemption rights, remain unclear in practice under MiCA as the framework moved to full application in July 2026, a gap affecting issuers serving Hungarian clients.retrieved M3non-binding

#

Hungary's domestic 2025 crypto law layered an additional consumer safeguard atop MiCA -- a mandatory 'conversion-validation certificate' for each trade -- on top of MiCA's own conduct-of-business and disclosure requirements. EU-level ESMA guidance requires CASPs offering unregulated ancillary services (e.g., crypto lending) to disclose associated risks fairly, clearly and non-misleadingly, and to safeguard client assets distinctly from own-account use. However, since MNB has not published licensing application procedures, the practical consumer-protection benefit of the domestic certificate regime remains unrealised for many providers.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

no periodic updates on record for this sub-brief

Sources and findings (3)
  1. T4 · The BlockThe Block — Hungary's 2025 crypto law adds a mandatory 'conversion-validation certificate' requirement for each crypto trade, presented by regulators as an extra consumer safeguard beyond MiCA's baseline requirements.retrieved M3bindingin force
  2. T1 · ESMAESMA — Under MiCA, CASPs holding client crypto-assets or means of access must safeguard ownership rights and not use those assets for their own account; where lending services are offered, client consent must be prior, express and specific, and revenues from lending should accrue to the client.retrieved M4bindingin force
  3. T4 · The BlockThe Block — Because MNB had not published application procedures for the domestic licensing overlay, some international platforms (e.g., Revolut, Bitstamp) suspended crypto services for Hungarian residents rather than risk non-compliance, directly affecting consumer access and choice.retrieved M4non-binding

#

No Hungary-specific primary-source confirmation of the current personal income tax rate, capital-gains treatment, or VAT/GST position for crypto-asset transactions was located in this research pass. At EU level, Hungary is bound by DAC8 (Council Directive (EU) 2023/2226), extending automatic exchange-of-information and reporting obligations to crypto-asset service providers on transactions involving EU residents, but Member State tax rates, thresholds and exemptions remain nationally determined and were not confirmed for Hungary specifically in this pass.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

no periodic updates on record for this sub-brief

Sources and findings (2)
  1. T1 · EUR-LexEUR-Lex — Hungary, as an EU Member State, is subject to DAC8 (Council Directive (EU) 2023/2226), which extends the Common Reporting Standard framework to crypto-asset service providers and requires automatic exchange of information on crypto-asset transactions involving EU tax residents.retrieved M3bindingin force
  2. T1 · ESMAESMA — No Hungary-specific confirmed source was located for the current personal income tax rate or capital-gains treatment applicable to individual crypto-asset disposals; this requires escalation to a primary Hungarian tax-authority (NAV) or Personal Income Tax Act source.retrieved M4non-bindingour coverage gap, expected to resolve on a re-run

#

As an EU Member State, Hungary participates in MiCA's passporting mechanism (a CASP authorised in one EEA Member State can operate across the EEA), and MNB has confirmed compliance with ESMA's Guidelines on the crypto-asset transfer 'travel rule' and on reverse solicitation (limiting third-country firms to services initiated at a client's own exclusive initiative). Because Hungary itself had no authorised CASPs as of July 2026, in-bound passporting from other Member States is the primary cross-border channel into the Hungarian market rather than outbound Hungarian-licensed passporting.

Standing sub-brief177 words · last cycle 2026-08-21

Cross-Border Transfer

Magyar Nemzeti Bank's March 2026 recommendation also addresses cross-border crypto-asset transfer execution policy, expecting crypto-asset service providers to adopt risk-based policies determining whether to execute, reject, suspend or return a given crypto-asset transfer transaction, in alignment with the EU Transfer of Funds Regulation (the Travel Rule). This is a High-confidence finding sourced to the same tier-two source underlying the stablecoin_regime module's finding, and it is explicitly alignment-only guidance: no new restriction on cross-border crypto-asset transfers was identified this cycle beyond confirming CASP alignment with the existing EU Travel Rule framework. The interpreter rates this module green accordingly.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (3)
  1. T1 · ESMAESMA — MNB complies with ESMA's Guidelines on transfer services for crypto-assets under MiCA (the crypto travel rule), publishing an implementing recommendation.retrieved M4bindingin force
  2. T4 · The BlockThe Block — Exchanges that secure MiCA CASP authorisation from any EEA competent authority can operate across the EU under a single regulatory regime and passport services into Hungary, even absent an HU-domiciled CASP.retrieved M4bindingin force
  3. T1 · ESMAESMA — Third-country firms may only provide crypto-asset services into Hungary (and the wider EU) under the MiCA 'reverse solicitation' exemption where the service is initiated at the client's own exclusive initiative; any marketing or solicitation in the EU voids the exemption, and NCAs including MNB are expected to detect and prevent circumvention per ESMA guidelines.retrieved M3bindingin force

#

Crypto AML/CFT obligations (KYC/CDD, travel rule, SAR/STR reporting, sanctions screening, record-keeping, risk assessment) for HU are researched and published under the FIM aml_ctf module per the crypto-consumer subscription model; this baseline does not duplicate those claims. For disambiguation only: MNB is the single Hungarian competent authority for MiCA-related AML/CFT-adjacent supervision of CASPs (no split with a separate FIU-style body for this purpose at the MiCA layer), and EU-wide travel-rule guidelines (Regulation (EU) 2023/1113) are implemented by MNB per its published guidance.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

no periodic updates on record for this sub-brief

No categories match.

Filters combine as OR inside a group and AND across groups.

Publication gate

Blocking. 1 failing check(s).

schema_validFAIL
min_quoted_text_presentwaived — floor 0%
egress_verifiedpass
every_practical_object_has_source_idn/a — no subject in this jurisdiction
source_tier_integrity_okpass
jurisdiction_source_floor_metpass
tier_a_b_national_primary_pct66.67
aggregator_only_jurisdiction_count0
manual_override

Editorial metadata

Provenance only. Nothing below gates publication or affects the render.

Editorial metadata for Hungary
FieldValue
trust.lawyer_review.statusnever_reviewed
trust.lawyer_review.reviewerno reviewer on record
trust.content_sourceai_generated

Provenance and declared absence

Disclosure model: module cards load OPEN; standing positions render in full; sub-briefs and jurisdiction briefs load as a clamped teaser with an explicit “read full” control carrying the true word count; earlier updates stay collapsed behind a counted summary. No text is hidden without disclosing how much of it there is.

Sentinel-fed modules receive no special rendering treatment. sentinel_feed is an attribution chip only: it does not suppress content, does not generate an absence reason code, and does not exclude the module from any count, filter, search index or export on this page.

Family taxonomy is renderer-level presentation config, not a JID field. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score; per-module RAG traffic light; derived_scores = {}.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-09-27. A year-precision row is never promoted into a tighter band.

Orphan deltas: 0 cycle_delta row(s) target non-module objects and are listed in the rail rather than attached to a card.

Envelope: baseline resolved at jurisdiction_json.baseline; 8 module(s), 19 finding(s), 20 source(s) in the cumulative register.

Think something on this page is wrong? Report an error.