# Why a stablecoin can be frozen and what that means for a recipient

Stablecoin issuers can freeze funds at the smart-contract level — and recipients, not just senders, carry the risk. Here is how the mechanics work and what professionals need to know.

---


When a settlement agent, closing attorney, or OTC desk receives a stablecoin payment, the transaction looks final the moment the block is confirmed. The number appears in the wallet. The deal is done. Except, sometimes, it is not — because the tokens sitting in that wallet can be made unspendable by someone the recipient has never met and never dealt with: the issuer of the stablecoin itself.

This is not a theoretical edge case. It is a documented, growing, and legally codified feature of every major fiat-backed stablecoin in circulation. Understanding how it works — and what it means operationally for anyone who receives stablecoins as part of a deal — is now a basic professional competency, no different from understanding how a wire recall works or why title insurance exists.

This article explains the mechanics plainly: what the freeze function is, who controls it, what triggers it, what happens to the recipient, and how professionals running multi-party settlements can think about the problem structurally.

<figure class="keyfacts">
<div class="keyfacts-grid">
<div><b>$3.29 billion</b><span>frozen by Tether across Ethereum and TRON, 2023 to 2025</span></div>
<div><b>$109 million</b><span>frozen by Circle across 372 addresses over the same period</span></div>
<div><b>$698 million</b><span>of frozen USDT destroyed in 2025, roughly 55.6% of $1.26 billion</span></div>
</div>
<p class="fig-src">Issuer freeze figures as cited in the sections below; destruction applies to USDT only.</p>
</figure>

## The freeze function is not a bug — it is engineered into the contract

A stablecoin blacklist — also called a freeze function — is a mechanism built into a stablecoin's smart contract that gives the issuer the power to block specific addresses from transacting. This is not a policy that sits in a PDF somewhere. It is executable code baked into the token itself.

When an address is blacklisted, it cannot send, receive, or redeem the stablecoin: the tokens in that wallet are effectively frozen in place. The balance still appears on the blockchain explorer. The private key still exists and still controls the wallet. But any attempted transfer will be rejected.

Both USDT and USDC implement blacklist functionality directly in their ERC-20 token contracts. USDC's contract carries an admin-controlled blacklist operated by Circle. Tether's USDT contract does the same on Ethereum and Tron. In Tether's contract, these actions appear on-chain as `AddedBlackList` and `DestroyedBlackFunds` events, verifiable by anyone via Tronscan or Etherscan.

<aside class="callout">
<span class="callout-label">The key architectural point</span>
<h4>Self-custody does not protect against a freeze</h4>
<p>Even if you control the private keys, the token's contract can still enforce compliance rules. The issuer's authority operates at the token contract level, not the wallet level.</p>
</aside>

## USDT and USDC freeze differently — and that distinction matters

The two dominant stablecoins are not identical in how they exercise this power, and the differences have material consequences for anyone holding them.

### Tether's approach: proactive, and with a nuclear option

Between 2023 and 2025, Tether froze roughly $3.3 billion using a proactive "freeze, burn, and reissue" approach. Tether blacklisted addresses holding a combined $3.29 billion in frozen assets across Ethereum (ERC-20) and TRON (TRC-20), while Circle froze $109 million across 372 addresses — a roughly 30-times difference in both address count and value.

Tether's enforcement model has a second stage that USDC does not share. Tether can set a blacklisted address's balance to zero and reduce the total token supply accordingly — this is the nuclear option. When `destroyBlackFunds` executes, the tokens are permanently burned and cannot be recovered, even by Tether.

In practice, freezing and destruction are separate steps: Tether first calls `addBlackList` to immobilize the funds, then later calls `destroyBlackFunds` when a court order authorizes seizure. In 2025, roughly 55.6% — approximately $698 million — of the $1.26 billion in frozen USDT was subsequently destroyed.

Tether collaborates actively with law enforcement. Tether's model involves collaboration with over 275 law enforcement agencies across 59 jurisdictions. More than 2,800 freeze actions were carried out in coordination with U.S. law enforcement, targeting funds linked to scams and other criminal activity.

### Circle's approach: judicially anchored, but still unilateral

Circle acts in response to formal judicial orders or regulatory requirements. This more restrained posture means fewer and smaller freezes, but it does not mean no freezes. Circle has been explicit about its ability and willingness to freeze funds to satisfy regulatory obligations or prevent misuse.

USDC can freeze and unfreeze tokens, but Circle cannot unilaterally destroy them. This matters: a USDC freeze is potentially reversible, as demonstrated when Circle unfroze five of sixteen frozen wallets after review in a March 2026 incident, including one wallet holding 130,966 USDC that was unfrozen within three days after backlash. A USDT freeze that escalates to a `destroyBlackFunds` call, by contrast, is irreversible.

Tether's approach is proactive and has historically been less transparent about freezing decisions and policies compared to Circle. Circle acts quickly when government agencies or compliance teams flag addresses — because USDC is viewed as a more tightly regulated stablecoin under U.S. law, it may be frozen faster or more consistently in response to compliance directives.

## What triggers a freeze

Freeze decisions stem from three core scenarios: law enforcement or judicial requests, which are the primary trigger; OFAC sanctions screening, where a match with an address on the U.S. Treasury's Specially Designated Nationals list leads to near-automatic freezing; and proactive risk prevention, which involves preventive blacklisting of suspicious addresses identified through blockchain intelligence tools like Chainalysis.

To illustrate the scale of real events: in one of the largest single freeze events, Tether froze $344 million in USDT across two addresses linked to Iran's Central Bank and the IRGC-Qods Force — wallets that had received approximately $370 million across roughly 1,000 transactions since 2021. In July 2024 alone, USDT freezes exceeded $130 million, including $29.6 million frozen on the TRON network linked to the Huione Group in Cambodia.

Critically, the decision to freeze a stablecoin is executed by the issuing company's compliance team before any court is involved. Technically, the entity pressing the button is a centralised private company.

<aside class="callout">
<span class="callout-label">Order of events</span>
<h4>The freeze happens first, any recourse comes later</h4>
<p>The sequence is: compliance team decision → on-chain execution → legal process (if any) afterward.</p>
</aside>

## The contagion risk: innocent recipients at the center of someone else's problem

Here is the scenario that deserves the most attention from professionals handling large multi-party payments.

Imagine a closing table — a commercial real estate deal worth $4 million USD (~$6.1 million AUD). The buyer sends USDT directly to the receiving wallet. The funds land. The settlement agent distributes to the seller, two brokers, and the title company. Three days later, the seller's wallet is flagged because the funds that originated the payment had, two hops upstream, passed through an address linked to a fraud investigation that only came to light after the deal closed.

The most insidious risk is not theft but contagion. Even a user who has committed no crime may face a freeze if the USDT reaching them previously passed through a suspicious address or became linked to a chain later blacklisted.

Criminals often attempt to launder tainted funds by selling them for fair market value to unsuspecting innocent owners who have no reason to suspect the funds are tainted or connected to any crime. The recipient did nothing wrong. They simply received tokens that carried a history.

Crypto users can lose access to legitimate funds when stablecoin issuers and institutions freeze assets because enforcement measures are not always precise enough to distinguish illicit funds from lawful holdings — legitimate users can sometimes be caught up in actions intended to target criminal activity.

Stablecoin freezes may occur without warning, leaving users to seek relief through the courts. That process is slow, expensive, and uncertain — particularly for a closing attorney or settlement agent whose fiduciary obligation to their client cannot wait for a federal administrative review.

The "clean coin" problem compounds further in multi-recipient scenarios. In P2P transactions in particular, the counterparty's history of suspicious transactions can put the recipient's account at risk. When one inbound payment fans out to six parties simultaneously, any taint on the originating funds is delivered to all six destinations at once. A single contaminated wire-in creates simultaneous exposure across every recipient wallet.

## What the regulatory environment is adding to this picture

The GENIUS Act, signed into law in July 2025, is the first comprehensive federal framework for payment stablecoins in the United States, and it has made the freeze function more — not less — formally embedded in the regulatory landscape.

Under the GENIUS Act, issuers will need to have the technological capability to comply with all lawful orders to seize, freeze, burn, or prevent the transfer of outstanding stablecoins. This is no longer optional or discretionary infrastructure for issuers — it is a compliance requirement.

Payment stablecoin issuers are treated as financial institutions under the Bank Secrecy Act and all federal laws relating to economic sanctions and the prevention of money laundering. Issuers must maintain effective AML and sanctions compliance programs, as well as customer identification programs that include Know Your Customer verification procedures and appropriate enhanced due diligence.

In April 2026, FinCEN and OFAC issued a joint proposed rule to implement the Act's AML and sanctions compliance program requirements; the public comment period closed in June 2026. The final rules are not yet in force, but the direction is clear: stablecoin issuers serving the U.S. will need bank-grade compliance operations with on-chain execution capacity.

What this means practically: the pace and breadth of freezes is likely to increase, not decrease, as the regulatory toolkit becomes more formal and issuers are legally required to demonstrate active enforcement capability. Professionals accepting stablecoin payments for deals cannot treat the freeze function as a rare edge case — it is a systemic feature of the rails they are operating on.

## The false-positive problem: freezes that are wrong, not just inconvenient

Not every freeze targets genuinely illicit funds. Freezing decisions can stem from false positives, regulatory overreach, or address re-use issues — not all cases involve illegal activity.

Legitimate funds may also be frozen because compliance systems can misread unusual but lawful activity. Some institutions depend on flawed heuristics to identify potentially illicit behavior, increasing the likelihood that innocent users are flagged incorrectly.

For a settlement agent holding funds in trust on behalf of multiple parties, a false positive freeze is operationally catastrophic even if it is eventually resolved. The breach of timeline, the inability to disburse, the downstream liability — none of those are fixed by a subsequent unfreeze. The harm occurs at the moment of the failed disbursement.

In forfeiture defense cases, there are instances where there is no nexus between the criminal activity and the tokens being frozen. Federal agencies sometimes make bad assumptions about clusters or trace funds too far. In other cases, owners can show they are innocent parties who purchased the tokens for value without knowing the funds were tainted. The innocent owner defense exists — but it requires legal proceedings, time, and cost that professionals in a closing workflow cannot absorb.

## What professionals should actually do about this

The risk is real, documented, and growing. But it is also manageable with the right operational habits and the right settlement architecture.

### Screen before you receive, not after

Checking USDT and USDC addresses for freezes and blacklist status is no longer an exotic extra step but a key part of basic hygiene when working with stablecoins. Tools exist to run this check in real time. Live, independent records of stablecoin blacklisting allow verification of whether any wallet is frozen across USDT, USDC, and other issuers across 40-plus chains.

Screen the sending address before accepting funds — not just for blacklist status today, but for risk scoring based on transaction history. Controls should extend across the full transaction lifecycle, including customer onboarding, transaction execution, and settlement. Key elements of the control stack include address screening, transaction monitoring, sanctions compliance, and clearly defined alert and investigation workflows.

### Separate receiving wallets reduce contagion exposure

Segregated accounts are strongly recommended for pay-ins. Unlike omnibus structures, pay-in flows benefit from the clean attribution that segregation provides — every incoming transaction maps to a specific counterparty, which simplifies compliance screening, reconciliation, and reporting.

If a single omnibus wallet receives all incoming payments from all counterparties across all deals, one tainted inbound payment potentially contaminates the entire pool. Purpose-specific receiving addresses for each transaction limit the blast radius of any individual freeze event.

### Understand that finality cuts both ways

Stablecoin payments settle with immediate finality on the blockchain — once the transaction is confirmed, it cannot be reversed by either party, and there is no payment processor in the middle who can issue a recall. This finality is one of the principal reasons professionals choose stablecoin rails for large-value settlement: the payment is received, it stays received, and the deal closes without a three-to-five day wire-clear window.

But finality also means that if tainted tokens land in a recipient's wallet, they landed with finality too. The recipient cannot send them back to the sender in a way that "undoes" the contamination. The funds are effectively in limbo until the blacklist is lifted or, in USDT's case, until Tether destroys them. Finality is what makes screening before the transaction so important — after confirmation, the options narrow sharply.

### Know the difference between stablecoins you are accepting

Not all stablecoins carry the same freeze risk profile. USDT, USDC, and Frax retain issuer-level freeze capability by design, while LUSD and RAI, thanks to immutable, admin-less contracts, are the clearest cases of stablecoins that cannot be frozen at the smart-contract level. The tradeoff is liquidity: only a small number of stablecoins are truly unfreezable at the smart-contract level. The stablecoins with the deepest liquidity and broadest acceptance are, almost by definition, the ones with issuer-level freeze capability. Professionals accepting stablecoins for high-value deals need to make an informed choice about which token and which risk profile they are accepting, not simply default to the most liquid option without reading the contract terms.

## Where settlement architecture enters the picture

For professionals handling multi-party settlements — deals where the total consideration needs to reach a seller, one or more brokers, a title company, legal counsel, and perhaps a management fee — the stablecoin freeze problem compounds with each additional recipient address.

If the workflow routes a single inbound payment through a central holding wallet before distributing outward, that central wallet is the exposure point. Every party waits for a series of sequential outbound transactions. Each transaction is a separate event, a separate moment of exposure, and a separate point of failure if the inbound funds carry any taint.

The architectural answer is to collapse that exposure surface. A non-custodial onchain payment router — one that receives the total deal amount and routes it to every named recipient in a single atomic transaction, without ever holding the funds — removes the aggregation risk of a long-lived omnibus wallet and eliminates the sequential-disbursement window during which a freeze could interrupt an in-progress distribution.

shaka.deal is built for exactly this workflow. A deal is configured with the receiving addresses and preset percentage shares for each party. When the buyer sends the total payment, the router fans it out simultaneously to every party in one transaction. There is no intermediate holding step, no sequential series of outbound sends, and no point at which the router accumulates and retains the funds. The routing is instant, the shares are predetermined and auditable on-chain, and the settlement is final in a single block.

This does not eliminate the underlying freeze risk — that is a feature of the stablecoin contract itself, not of any routing layer. But it changes the risk profile in meaningful ways for settlement professionals. The window during which any one party's share is vulnerable to an intermediate-wallet freeze event is reduced to the duration of a single block confirmation. The distribution happens simultaneously to all parties. There is no moment at which the routing wallet holds material balances between receipt and disbursement. And the full transaction — every recipient, every share, every address — is verifiable on-chain in a single immutable record.

For a settlement agent or closing attorney who needs to demonstrate that all parties received their shares, and that the funds moved directly and immediately upon receipt of the buyer's payment, that on-chain record is the audit trail.

## The practical checklist

For any professional who accepts or distributes stablecoins as part of a commercial transaction, the following practices are not optional extras — they are the current baseline for responsible operation:

**Before any transaction:**
- Screen the sending address against current blacklist databases and risk scoring tools.
- Confirm which stablecoin is being sent and understand that issuer's freeze model (proactive vs. judicially anchored; reversible vs. destructive).
- Use segregated receiving addresses per deal or per counterparty rather than a single omnibus wallet.

**At deal setup:**
- Define recipient addresses and share percentages at the outset, not after receipt.
- Use an atomic distribution architecture where feasible — one inbound payment fans out to all parties in one transaction, with no holding step.
- Document the transaction structure so all parties understand what address they will receive from and when.

**After receipt:**
- Verify the on-chain record against the agreed distribution before closing the file.
- Monitor for any freeze notifications from the issuer on the receiving addresses in the days immediately following settlement — a post-receipt freeze on a recipient address, while rare, is an operational scenario to have a response protocol for.
- If a freeze has already happened, the only correct route is to work through the issuer's and/or service's official channels, with legal support where large amounts are involved.

## Conclusion

The freeze function in stablecoins like USDT and USDC is not a flaw — it is a deliberate design choice that reflects the reality that fiat-backed stablecoins are issued by regulated companies operating under national and international law. Freeze powers have been used to comply with OFAC sanctions, assist law enforcement investigations, and recover stolen funds. Those are legitimate and often beneficial uses of the capability.

But the existence of that capability creates real operational risk for any professional who receives stablecoins as part of a deal — risk that does not require any wrongdoing on the recipient's part. The regulatory environment, driven by the GENIUS Act and parallel frameworks, is making the freeze function more actively deployed, not less. The history of the stablecoin you receive can become your responsibility — when the music stops, the party holding the tainted coin may be the one bearing the loss, even if not guilty.

The answer is not to avoid stablecoins — they offer genuine advantages for large-value, multi-party settlement that no traditional rail matches for speed and certainty. The answer is to understand the mechanics, screen rigorously, architect the settlement correctly, and use tools like shaka.deal that are designed to minimize the exposure window between inbound receipt and outbound distribution. Settlement that is split precisely, distributed instantly, and recorded with finality in a single transaction is not just efficient. In the current stablecoin compliance environment, it is the professional standard.