Indirect exposure under MiCA: What treasury teams need to know about stablecoins

When MiCA's transitional period ended on July 1, 2026, the immediate impact was visible across the European crypto market. The European Securities and Markets Authority (ESMA) said unauthorized crypto-asset service providers should stop onboarding new EU clients and limit activity to wind-down actions, including asset transfers, reallocations and position closures.

For USDT, that transition had already started. Tether chose not to pursue MiCA authorization for USDT in Europe, with Paolo Ardoino arguing that MiCA's reserve rules would require large stablecoin issuers to hold 60% of reserves as cash deposits in European banks. For a global issuer built around US Treasury bills, repos and money market funds, that requirement would change the reserve model Tether believes protects its broader global user base.

Tether's strategy has moved in another direction. The company has invested in regulated issuers such as StablR in Malta and Quantoz in the Netherlands, both of which issue MiCA-compliant stablecoins while using Tether's Hadron platform for tokenization, compliance, KYC, AML, risk management and related infrastructure.

platforms adjusted accordingly. Coinbase had already moved to restrict USDT access for European users, and Revolut has now told its users they will no longer be able to buy USDT from July 6, 2026, with full delisting scheduled for August 31, 2026.

For regulated businesses operating in Europe, those platform decisions are the visible part of the transition. The operational issue, however, lies deeper within the treasury, settlement and payment infrastructure.

A company can hold no USDT on its balance sheet and still rely on workflows that touch USDT liquidity. Stablecoins, DeFi protocols, cross-chain routes, payment flows and tokenized products often retain exposure to the assets that make them liquid, even after direct holdings disappear.

What MiCA's USDT restrictions actually changed for regulated businesses

MiCA did not prohibit every company from holding USDT. It did not make USDT disappear from DeFi. The restriction falls on regulated service providers operating under MiCA, including exchanges and custodians serving EU clients.

That distinction matters because platform access changes the rails on which an asset runs. A token can remain in circulation while regulated firms lose the ability to access, custody, trade or route through it on the venues they use for business operations.

A finance team can move balances from USDT into MiCA-compliant alternatives such as USDC or EURC. A compliance team can update approved-asset lists. A custody team can adjust exchange relationships. Those steps reduce direct exposure.

The remaining exposure is harder to capture because it comes from the products and partners around the asset. Settlement providers may source liquidity from multiple stablecoins. DeFi products may route through pools that include USDT. Synthetic dollars can include USDT reserves. Cross-chain payments can complete one leg via USDT liquidity before delivering the other asset to the end user.

Those dependencies appear in execution paths, liquidity sources and counterparty workflows rather than in a wallet balance.

The exposure that does not appear on a balance sheet

Most treasury and compliance reviews start with the same question: which assets do we hold?

That is a sensible starting point, but it stops too early. Wallet balances show owned assets. They do not show which stablecoins support the products, counterparties and settlement routes the business uses every day.

Modern stablecoin infrastructure is composable. Treasury platforms, exchanges, custodians, liquidity venues, payment processors, DeFi protocols and tokenized asset products are increasingly built on top of one another. Each layer can introduce exposure that the end company does not directly hold.

A balance-sheet review can miss several common dependencies:

• A synthetic dollar partially backed by USDT reserves.
• A yield strategy that allocates capital to liquidity pools containing USDT.
• A cross-chain settlement flow sourcing USDT liquidity to complete part of a transaction.
• A payment processor that no longer exposes USDT to the customer but still depends on USDT pairs or liquidity venues behind the scenes.
• A counterparty that receives a compliant stablecoin from your business, then routes through USDT infrastructure to complete its own settlement leg.

From an accounting perspective, none of these may appear to be USDT exposure. From an operational perspective, they matter. They affect execution, settlement timing, counterparty risk, liquidity availability and the evidence a regulated firm can produce if an auditor or regulator asks how a transaction moved.

That is the gap MiCA exposes. It is not enough to know what the business owns. Finance and compliance teams need to know what the business depends on.

What USDT exposes about the next stablecoin transition

USDT dominates the current conversation because it is the largest stablecoin affected by the MiCA transition. The broader challenge is not unique to Tether.

Stablecoin competition is moving beyond issuer selection. Open Standard, a consortium including Visa, Mastercard, Coinbase and more than 140 businesses, announced Open USD on June 30, 2026. The stablecoin is expected to go live later this year, with no-cost minting and redemption, no artificial volume limits and reserve earnings shared among participating partners after a management fee.

That launch points to a more crowded operating environment. Stablecoins are increasingly designed around specific networks, business models, geographies, regulatory regimes and distribution incentives. Finance teams will need to understand where each token is used, which partners depend on it, what liquidity supports it and how it appears inside payment or treasury workflows.

Circle's response to Open USD made the network-effect argument from the issuer side. Jeremy Allaire argued that stablecoin markets are shaped by liquidity, integrations, regulatory infrastructure and network effects built over long periods. His point was competitive, but the operational implication is broader. Stablecoins are networks with different access points, liquidity surfaces, regulatory coverage and infrastructure dependencies.

Every new stablecoin, tokenized treasury product, synthetic asset or settlement protocol adds another layer between the asset recorded on the balance sheet and the infrastructure supporting treasury operations.

Building visibility beyond direct holdings

For companies operating under MiCA, stablecoin reviews need to cover direct holdings, counterparties, protocols and settlement infrastructure together.

That requires three layers of visibility.

First, finance teams need a real-time view of direct holdings across wallets, custodians, exchanges and bank accounts. Without that foundation, every dependency review starts from incomplete data.

Second, compliance teams need to understand counterparties across both stablecoin and fiat rails. A wallet address, exchange account or bank account is not enough on its own. Teams need to know which legal entity sits behind each endpoint, what relationship that entity has to the business and whether the transaction fits approved policy.

Third, both teams need pre-execution context. Post-settlement review is too late for stablecoin flows that cannot be recalled. The control must fire before the transaction executes, with enough information to block, approve or escalate based on the business's own risk policy.

Range is the platform for companies operating across stablecoins and fiat. We help finance, treasury and compliance teams build that operational view by unifying wallets, custodians, exchanges and bank accounts into a single real-time ledger. Transaction Screening applies sanctions, fraud and operational risk checks before transactions execute, while Counterparty Management links wallets, exchange accounts and bank accounts to the underlying legal entity. Our Asset Intelligence views give your treasury and compliance teams an in-depth look at both regulatory and monetary risks associated with digital assets in your treasury.

That gives teams a consistent view of who they are transacting with, which infrastructure supports each workflow and where indirect stablecoin exposure may exist across stablecoins and fiat.

If you're evaluating how MiCA affects your treasury operations or want to understand where indirect stablecoin exposure exists across your payment flows, get in touch with our team. We'll walk through your current infrastructure and help identify the operational dependencies that matter most.