Hungary Repeals Crypto Validator Requirement as CoinCash Secures First MiCA License
Hungary has removed a contentious layer of domestic crypto oversight, repealing the mandatory third-party validator requirement for certain crypto conversions at the same moment that Budapest-based platform CoinCash became the first Hungarian company to receive a MiCA compliance authorization directly from the National Bank of Hungary. For accounting firms, auditors, and CFOs with clients operating in Central and Eastern Europe, this is a material regulatory shift that changes the due-diligence, transaction-record, and licensing landscape in one of the EU's more activist crypto jurisdictions.
What Hungary's Validator Requirement Was and Why It Failed
Hungary introduced its own crypto assets law in 2024, layering a domestic validation process on top of the EU-wide MiCA framework. Under that regime, which took effect on 1 July 2025, a licensed validator had to verify the origin of crypto assets, confirm wallet ownership, and collect customer information before issuing a compliance declaration. Only once that declaration was in place could certain conversions proceed.
The practical effect on the market
The requirement effectively created a double-gating structure: firms had to satisfy both the MiCA authorization process and a separate, Hungary-specific approval step at the transaction level. The operational cost and friction proved significant. Multiple service providers suspended activities in Hungary rather than build out a compliance stack that served a single national rule overlaid on a regulation already covering 30 EEA states. Finance Minister Kármán András acknowledged the impact directly, stating that the previous rules had been market-shaking and had caused many players to terminate their crypto-related services in the country.
Why the repeal matters beyond Hungary's borders
The episode illustrates a tension that compliance teams across the EU are navigating: MiCA sets a harmonized baseline, but member states retain room to impose additional national measures, at least until the regulation's passporting provisions are fully settled. Hungary's experience is a live case study in what happens when national gold-plating disrupts a market that MiCA was designed to integrate. Its reversal signals that political and commercial pressure can unwind domestic additions relatively quickly, which has implications for how firms model regulatory risk in each member state where they hold or plan to hold authorizations.
Hungary's Compressed MiCA Transition and Its Consequences
Separately from the validator rule, Hungary chose a shortened MiCA transition period. While the default EU-wide deadline for crypto asset service providers (CASPs) to obtain full authorization was 1 July 2026, Hungary required compliance by 1 July 2025, a full year earlier. That compressed timeline, combined with the validator requirement, created a regulatory environment tight enough to push some platforms out of the market entirely.
Compliance cost and market exit
CoinCash, one of Hungary's best-known retail crypto platforms, voluntarily paused all operations in December 2025 while working through the MiCA authorization process with the National Bank of Hungary (MNB). That is a significant commercial decision: voluntarily going dark for months rather than operating under uncertainty. It reflects the weight that MiCA compliance genuinely carries when a competent authority applies it strictly. Firms advising clients on MiCA timelines should note that some national competent authorities have enforced transition deadlines aggressively, and the consequence of non-compliance is not a fine alone but a potential operational halt.
CoinCash's MiCA Authorization: What the Record Shows
The MNB granted authorization to Tiwala Solutions, the operator behind CoinCash, on 20 July, according to a company announcement reviewed by Cointelegraph. CoinCash's co-founder described the firm as the first and only Hungarian company authorized directly by the National Bank under the EU framework, a claim consistent with the timing of Hungary's compressed transition period and the general pace of CASP authorizations across the bloc.
What comes next for CoinCash
CoinCash has indicated it will resume services gradually and intends to expand beyond spot trading into additional MiCA-regulated product categories. That expansion path matters for compliance teams because MiCA authorization is product-specific in scope: a CASP authorized to provide custody services is not automatically permitted to offer, say, portfolio management or advice on crypto assets without the relevant authorization class. Firms onboarding CoinCash as a counterparty or exchange will need to verify which specific services fall within the authorization granted by the MNB before transacting.
Accounting and Audit Implications
The repeal of the validator requirement and the grant of Hungary's first MiCA license have several concrete implications for accounting firms and their clients.
Transaction records and the removed validation layer
Under the old regime, the validator's compliance declaration was itself a document that auditors could reference when verifying the legitimacy of a crypto conversion. With that layer removed, the evidentiary chain for certain Hungarian crypto transactions now relies entirely on the CASP's own KYC and AML records plus the standard MiCA requirements around travel rule data. Audit teams should update their evidence-gathering checklists for Hungarian crypto transactions to reflect that no third-party validation declaration will exist for conversions executed after the repeal takes effect.
Counterparty due diligence for the post-repeal environment
Accounting firms conducting counterparty due diligence on Hungarian CASPs need to confirm MiCA authorization status directly with the MNB or via the ESMA MiCA register. The ESMA MiCA register reaches 309 CASPs as of the most recent update, and Hungary-authorized entities should appear there once passporting is processed. Cross-referencing the ESMA register against a client's list of active CASP relationships is now a standard step in any EU crypto audit engagement.
Balance sheet and revenue recognition considerations
For clients that suspended crypto operations in Hungary during the regulatory freeze, there are balance sheet questions to address. Crypto assets held but not actively traded during an operational pause may need to be assessed for impairment under IFRS or reclassified depending on the entity's accounting policy. Any costs incurred during the MiCA authorization process, legal fees, compliance consultancy, and technology build-out, should be reviewed under IAS 38 to determine whether they qualify for capitalization or must be expensed as incurred. Authorization itself does not create an intangible asset under current IFRS guidance, but the systems built to support ongoing compliance may.
MiCA compliance and digital asset accounting software
Firms building or upgrading their crypto accounting software stack for EU-regulated clients should factor in the data requirements that MiCA authorization imposes. Licensed CASPs must maintain detailed records of every transaction, including travel rule data, wallet ownership information, and AML screening results. Good digital asset accounting software must be able to ingest those fields, map them to the correct ledger entries, and produce audit trails that a competent authority can inspect. The Hungarian repeal does not reduce that underlying data burden; it simply removes one additional national approval step that sat on top of it. The CSSF's activation of MiCAR Title II white paper notification illustrates how each member state is building its own procedural layer on top of the core regulation, meaning that a single EU-wide data model in your accounting software must accommodate national variations in submission format and timing.
What CFOs and Compliance Teams Should Do Now
The situation in Hungary is still developing. The validator requirement has been voted out, but the implementing legislation and the exact effective date of the repeal should be confirmed against the official Hungarian parliamentary record before client advice is finalized. Similarly, CoinCash's gradual service resumption means that the range of MiCA-regulated services available in Hungary will expand over time, and counterparty agreements may need to be revisited as new authorization classes are added.
Immediate action points
First, review any existing compliance procedures that referenced the Hungarian validator declaration as a required document. Those procedures need to be updated to reflect the post-repeal reality. Second, confirm the MiCA authorization status of any Hungarian CASP relationships via the ESMA register and the MNB's own published list of authorized entities. Third, assess whether any clients held crypto assets in suspended accounts during CoinCash's operational pause and determine whether those positions require disclosure or reclassification in financial statements. Fourth, verify that your crypto bookkeeping software can correctly categorize transactions that occurred during a period when a CASP was not actively authorized, since the accounting treatment for trades executed under transitional permission may differ from those executed under full MiCA authorization.
Hungary's regulatory reversal is a reminder that MiCA compliance is not a one-time exercise. The framework is live, national competent authorities are actively applying it, and member states continue to adjust their domestic implementation. Firms that treat MiCA as a filed-and-forgotten project will find themselves behind the curve as these adjustments accumulate.
Frequently Asked Questions
What was Hungary's crypto validator requirement?
It was a domestic rule introduced via Hungary's 2024 crypto assets law requiring a licensed third-party validator to verify transaction details, including wallet ownership, asset origin, and customer information, before certain crypto conversions could proceed. A compliance declaration from the validator was a prerequisite for those transactions. The Hungarian Parliament has now voted to repeal this requirement.
Does removing the validator requirement mean Hungary has relaxed its AML rules?
No. The validator requirement was an additional national layer on top of MiCA. MiCA's own AML, KYC, and travel rule obligations remain fully in force for all authorized CASPs operating in Hungary. The repeal removes the extra domestic approval step, not the underlying EU-level compliance framework.
What does CoinCash's MiCA authorization mean for counterparty due diligence?
It means Tiwala Solutions, trading as CoinCash, is a fully authorized CASP under MiCA as granted by the MNB. Firms transacting with CoinCash should verify the specific authorization classes granted, since MiCA authorization is service-specific, and should check the ESMA CASP register to confirm the entry is current before onboarding or transacting.
How should auditors handle transactions from the period when the validator requirement was active?
Auditors reviewing Hungarian crypto transactions from 1 July 2025 through the repeal date should check whether a validator compliance declaration was obtained, as required under the rules then in force. Absence of that declaration for a transaction executed during the active period could represent a compliance gap that warrants disclosure or qualification depending on materiality.
What is the broader lesson from Hungary's experience for EU MiCA compliance planning?
Member states can impose national measures that are stricter than the MiCA baseline, and some have done so, including shorter transition periods and additional procedural requirements. Firms operating across multiple EU jurisdictions need jurisdiction-specific compliance mapping, not just a single EU-wide MiCA checklist. Hungary's rapid reversal also shows that national gold-plating can be unwound, so compliance frameworks should be reviewed whenever a member state amends its implementing legislation.
Source: Cointelegraph