A USDC blacklist entry is Circle exercising the blocking rights set out in its USDC Terms, which reserve the right to block certain USDC addresses and, where those addresses are Circle-custodied, to freeze the associated USDC temporarily or permanently. The terms also reserve the right to block transfers of USDC to and from an address on chain under the blocklisting policy. As with any issuer control, it acts at the token level rather than at an exchange, so it reaches self-custodial holdings too.
Circle's USDC Terms, at Section 13 ("Blocked Addresses & Forfeited Funds" / "Blocklisting"), state that "Circle reserves the right to 'block' certain USDC addresses and, if such addresses are Circle custodied addresses, freeze associated USDC (temporarily or permanently)", and that it "reserves the right to block the transfer of USDC to and from an address on chain as permitted under the blocklisting policy."
Two things are worth reading closely there. Blocking an address and freezing custodied USDC are described as separate powers, and the on-chain transfer block is framed as applying to transfers both to and from an address.
| USDC (Circle) | USDT (Tether) | |
|---|---|---|
| Source of the power | USDC Terms, Section 13 | Terms of Service, Sections 2, 6 and 8 |
| Wording used | "block" an address; freeze custodied USDC | freeze tokens; "blacklist Digital Token Addresses" |
| Direction described | Transfers to and from an address | Freezing tokens held by a user |
| Additional reserved power | Forfeiture of funds under the terms | Confiscation and reporting to authorities on suspected prohibited use |
Both issuers publish the authority; neither publishes advance notice to holders. The workable conclusion for a business is the same in each case: the token you accept carries an issuer, and the issuer's terms are part of what you are accepting.
Because USDC is the settlement asset of choice for a lot of business flow — invoices, payroll, treasury movement — and a blocked counterparty address turns a routine payment into an incident. The check answers it before the transfer instead of after, in seconds.
The same applies to receiving. Value arriving directly from a blocked address is a question your bank will ask in its own time. Screen first: three free checks a day in the Telegram bot, or run it directly on a USDC address.
The result reports issuer freeze or block status as a plain fact next to the verdict — CLEAN, LOW, MEDIUM, HIGH or CRITICAL — with a recommendation of Proceed, Caution, Review or Reject and the decision drivers named. It is one of the few findings with no interpretive component at all: the status is either attached to the address or it is not.
Desks screening stablecoin deposit flow run this in the workspace and through the API, with each result exportable as a signed report for the payment file. Plans are on the pricing page.
Circle's terms describe blocking addresses and blocking on-chain transfers to and from an address, with freezing described for Circle-custodied addresses. The blocking power is written as applying at the address level rather than only inside Circle's own custody.
They are similar in effect and differently worded. Circle's terms speak of blocking addresses and blocking transfers to and from them; Tether's speak of freezing tokens and blacklisting digital token addresses, with confiscation and reporting reserved on suspected prohibited use.
A check names issuer block or freeze status in the result. Discovering it by attempting a transfer is the alternative, and it happens mid-payment rather than before it.
Also available in: · · ·
Circle's blocking policy is written around USDC addresses rather than a single network. For any specific address, checking it is faster than reasoning about which deployment it sits on.
Send any wallet to the Telegram bot and get a verdict in seconds. Three checks a day, free, no signup. Desks that screen every deposit run it on plans from $199/mo.