ECB Pushes to Extend MiCA Stablecoin Yield Ban to Lending and Staking

The European Central Bank and the EU's national central banks have formally called on the European Commission to close what they see as a significant gap in the Markets in Crypto-Assets regulation: indirect yield on stablecoins. In a 57-page submission to the Commission's MiCA review consultation, the European System of Central Banks argued that crypto-asset service providers should be barred from offering any product, including lending, borrowing, and staking, that generates a return on stablecoin holdings, even where that return flows indirectly rather than as an explicit interest payment. The submission also proposed a structural overhaul of stablecoin reserve requirements, shifting the focus from where reserves are held to how quickly they can be liquidated. For accounting firms, CFOs, and auditors with EU-regulated clients, both proposals carry direct practical consequences.

What the ESCB Actually Proposed

The ESCB's response to the European Commission's MiCA consultation sets out two distinct but related positions on stablecoins. The first concerns yield; the second concerns reserve liquidity. Understanding each separately matters before considering how they interact.

Extending the yield prohibition beyond direct remuneration

MiCA already prohibits stablecoin issuers from paying interest or other remuneration directly to holders of e-money tokens. The ESCB's position is that this prohibition is being outflanked. Stablecoins can, the central banks noted, be "transformed into yield-bearing arrangements through lending, staking or other layered structures," which potentially circumvents the spirit of the existing ban without technically violating it.

The ESCB's proposed fix is a categorical one: the prohibition should cover both direct and indirect forms of remuneration, and it should apply to activities that are currently unregulated under MiCA, not just those already within its scope. Crypto lending, borrowing, and staking are all named explicitly. The submission described making this prohibition watertight as "a clear legislative priority."

The policy rationale centres on competitive neutrality. Electronic money is designed as a payment instrument, the ESCB argued, not a savings vehicle. Allowing crypto platforms to engineer yield equivalents on stablecoins creates a functional substitute for a bank deposit while bypassing the prudential, deposit-insurance, and capital rules that apply to banks. From the central banks' perspective, that distorts competition across the EU financial system and blurs a regulatory boundary that MiCA was intended to preserve.

Replacing deposit minimums with liquidity maturity thresholds

The second proposal addresses how stablecoin issuers structure their reserves. Under current MiCA rules, issuers must hold a minimum share of reserves as deposits at credit institutions: at least 30% for standard stablecoins and at least 60% for those designated as significant. The ESCB wants those floors removed and replaced with maturity-based liquidity requirements.

The argument is that mandatory deposit holdings create a concentration risk in the banking system itself. If a large stablecoin issuer needs to redeem quickly during a market stress event, the issuer must withdraw from credit institutions rapidly, potentially destabilising those institutions at the worst possible moment. A liquidity-focused framework would spread that risk across asset classes and maturities instead of concentrating it in bank balance sheets.

As a starting point, the ESCB pointed to draft European Banking Authority standards that had already set out suggested thresholds. For significant stablecoins, those draft standards call for at least 40% of reserves in assets maturing within one business day and at least 60% in assets maturing within five business days. For non-significant stablecoins, the suggested thresholds are 20% and 30% respectively. The ESCB's submission endorsed this maturity-ladder approach as the model for any revised MiCA reserve regime.

Why This Echoes the US Stablecoin Debate

The ESCB's submission is not happening in a vacuum. The source article notes that the same underlying tension, whether stablecoins can be engineered to pay deposit-like returns that bypass bank regulation, was at the centre of the US Clarity Act debate. Several US senators raised concerns that the bill's stablecoin provisions would allow crypto platforms to offer interest-like returns that compete directly with insured bank deposits, and those concerns contributed to the bill's procedural difficulties in the Senate.

The parallel matters for multinationals and globally active CASPs. Two of the world's largest stablecoin markets are heading toward similar regulatory conclusions through different legislative mechanisms: indirect yield on stablecoins is coming under pressure on both sides of the Atlantic. Firms that structured EU-facing or US-facing products on the assumption that indirect yield structures would remain in a regulatory grey zone should treat the ESCB's submission as a strong signal that the window for those structures is narrowing, even before any formal legislative amendment to MiCA is enacted.

For context on the US legislative trajectory, see our earlier coverage of the Clarity Act Senate defeat and its implications for stablecoin accounting.

MiCA Compliance: Accounting and Reporting Implications

The ESCB's proposals are still at the consultation stage; no legislative amendment has been adopted. That said, accounting firms and CFOs advising clients who issue or use stablecoins in the EU need to begin assessing the exposure now, because the direction of travel is clear and product re-engineering takes time.

Classification of stablecoin arrangements under IFRS

Under current IFRS 9 and IAS 32 frameworks, the classification of a financial instrument turns substantially on its contractual terms and economic substance. A stablecoin held for payment purposes with no entitlement to return has a relatively clean classification profile. One that is deposited with a CASP in a structure designed to generate a lending or staking yield raises harder questions: is it a financial asset under IFRS 9? Does the arrangement create a liability on the CASP's balance sheet that must be recognised at amortised cost or fair value? If the ESCB's proposed prohibition is enacted, product terms will change, which will in turn affect the accounting treatment for both issuers and holders.

Auditors reviewing client disclosures for periods ending before any legislative amendment should document their assessment of whether current stablecoin arrangements involve indirect yield and whether that yield has been recognised consistently. If a client is receiving effective economic returns through a lending or staking structure that is not explicitly labelled as remuneration, the auditor needs to consider whether the substance-over-form principle requires a different classification than the contract's labelling suggests.

Reserve asset reclassification for issuers

The proposed shift from deposit-percentage floors to maturity-based liquidity thresholds is equally consequential for stablecoin issuers. Under MiCA as currently drafted, the 30% or 60% deposit requirement effectively mandates a specific asset category for a material share of reserves. That has straightforward accounting consequences: those deposits are typically classified as cash or short-term financial assets at amortised cost.

A maturity-ladder framework, by contrast, would allow a broader range of reserve assets, including short-dated government securities, money market instruments, and other near-cash equivalents, provided they meet the maturity thresholds. For issuers, this means the reserve portfolio could look quite different from its current composition. From an accounting standpoint, those instruments may carry different measurement bases, fair value hierarchies, and disclosure requirements under IFRS 7. Finance teams at stablecoin issuers should begin mapping their current reserve asset classifications against the EBA's draft maturity thresholds to understand what reclassification, if any, would be required under a revised regime.

Implications for CASP audit and compliance engagements

Accounting firms providing audit or agreed-upon procedures engagements to MiCA-authorised CASPs should note two near-term actions. First, any CASP currently offering or facilitating crypto lending, borrowing, or staking on stablecoin positions should be asked to document its legal analysis of whether those activities fall within or outside the existing MiCA remuneration prohibition. The ESCB's submission signals that national competent authorities and the European Commission may take a more expansive view of that prohibition during the review period, even before a formal legislative amendment. Second, the reserve asset composition of any e-money token issuer client should be stress-tested against the EBA draft thresholds to identify gaps between current holdings and the proposed liquidity requirements.

For firms tracking the ECB's broader involvement in the digital asset space, the Eurosystem's Pontes platform is also worth monitoring: our analysis of what Pontes means for digital asset accounting covers the settlement infrastructure context.

The Competitive Distortion Argument and What It Means for Clients

The ESCB's competitive neutrality argument deserves more attention than it typically receives in coverage of this issue. The central banks are not simply arguing that stablecoin yield is risky; they are arguing that it is structurally unfair to the banking sector under current EU rules.

Banks that accept deposits are subject to capital requirements, deposit guarantee scheme contributions, resolution planning obligations, and prudential supervision. A CASP that engineers an economically equivalent return for stablecoin holders through a lending or staking wrapper faces none of those costs. If the prohibition is extended as the ESCB proposes, the effect is to flatten that competitive asymmetry: stablecoins revert to pure payment instruments, and any yield-generating function migrates back into regulated deposit-taking or fund structures that carry the corresponding regulatory burden.

For corporate treasury teams and CFOs currently using stablecoin yield structures as a cash-management tool, the practical implication is straightforward: those products may cease to be available in their current form in the EU market. The timeline depends on how quickly the Commission acts on the ESCB's consultation response and what the legislative amendment process looks like. Given that MiCA only began taking full effect in June 2024, a formal amendment would follow the ordinary EU legislative procedure and is unlikely to be rapid. But product terms may change earlier if CASPs decide to pre-comply, or if national competent authorities begin interpreting the existing prohibition more broadly in response to the ESCB's position.

Frequently Asked Questions

Does the ESCB's proposal change anything about MiCA right now?

No. The ESCB's submission is a response to the European Commission's consultation on reviewing MiCA. It sets out what the central banks want the Commission to propose as legislative amendments. Until the Commission tables a formal proposal and it passes through the EU co-legislative process, the current MiCA text remains the applicable law. Firms should monitor the Commission's formal response to the consultation for the next concrete step.

Which stablecoins are affected by the proposed yield prohibition?

The ESCB's proposal targets e-money tokens specifically, which are the stablecoin category under MiCA pegged to a single fiat currency and intended as a means of payment. The prohibition on remuneration already applies to EMT issuers. The new element is the proposed extension to indirect yield delivered through CASPs offering lending, borrowing, or staking on EMT holdings, regardless of whether those CASPs are currently regulated under MiCA for those activities.

How would the maturity-based reserve rules affect stablecoin accounting for issuers under IFRS?

If the deposit percentage floors are replaced by maturity thresholds, issuers would have more flexibility in the types of assets they hold as reserves, but each asset class carries its own IFRS measurement and disclosure requirements. Short-dated government bonds classified as fair value through other comprehensive income, for example, would require mark-to-market accounting and IFRS 7 disclosures that a plain bank deposit does not. Finance teams at issuers should map current reserve compositions against the EBA draft thresholds and model the accounting impact of any required repositioning before a new regime takes effect.

Is the MiCA yield prohibition relevant to US GAAP filers with EU operations?

Yes, indirectly. A US parent with an EU subsidiary that is a MiCA-authorised CASP must consolidate that subsidiary's financial statements. If the subsidiary's product range is curtailed by an extended yield prohibition, the revenue and liability recognition implications will flow through the consolidated accounts. Under ASC 350-60, the US GAAP framework for crypto assets adopted in 2024, the measurement of digital assets at fair value is the default for most tokens, but the structuring of stablecoin products is a separate commercial and regulatory question that affects what assets and liabilities the subsidiary recognises in the first place.

What should accounting firms do now given this is still a proposal?

Three near-term actions are worth taking. First, identify which clients issue or facilitate products that generate indirect yield on EU stablecoins and document those arrangements thoroughly. Second, review whether any current audit or reporting engagement involves a stablecoin reserve portfolio that would be materially repositioned under the EBA draft liquidity thresholds. Third, set up a monitoring workflow for the Commission's formal legislative response to the ESCB consultation so that clients can be notified promptly when the proposal moves from consultation input to legislative text.

Source: CoinDesk Policy