Check if a USDC address is blacklisted — 2026 guide

Circle’s USDC contract on each settlement chain includes a blacklister role. To verify whether an address can move or redeem USDC, call the view function isBlacklisted(address) on Circle’s native USDC contract for the chain where settlement will occur. A true result causes transfers, approvals, mints and burns that touch that address to revert.

Begin by copying the native USDC contract address for the settlement chain from Circle’s official contract registry. Blacklist state is stored per contract, so using the wrong chain or a bridged wrapper will return a meaningless result. On EVM chains, open the chain’s block explorer, paste the native USDC contract address, use the Read as Proxy or Read Contract interface and call isBlacklisted with the counterparty address. The call returns false if the address is not blacklisted at that moment and true if the contract will block USDC movements for that address.

Run the check on the chain where you will settle. For automated systems, use an eth_call or a direct node query immediately before building transfer transactions rather than relying on a stale CSV or cached list. If an RPC read fails or an explorer returns an error, treat the result as a closed gate and do not proceed.

A true isBlacklisted response does not remove on-chain balances from view. Wallets may still display USDC, but the token contract will reject the transfer operations that issuer redemption or spending require. If a counterparty address returns true, stop settlement and escalate to compliance. If funds are already received and an address later appears on the blacklist, quarantine the receivable and suspend outgoing transfers from that address.

Do not conflate issuer blacklists with venue custody locks. An exchange can freeze a platform balance while the on-chain isBlacklisted check for a deposit address remains false. When a flow involves an exchange, run both the on-chain contract check and the venue’s custody verification. Also do not apply the EVM isBlacklisted check to non-EVM chains; Solana and other networks require their native token-account tools and queries against the Circle mint on those chains.

If the payable asset is USDT rather than USDC, query Tether’s contract on the settlement chain and use its view (typically spelled isBlackListed). The two booleans are independent: the same address can be clear for one issuer and frozen by the other. As of August 2026, issuer freezes totaled roughly $109 million across about 372 addresses for Circle and more than $4.2 billion across over 7,200 addresses for Tether. Historical data shows a small share of blacklisted addresses have been removed.

Operational practice should record each isBlacklisted query alongside the contract address, chain, block or timestamp, transaction hash and the operator who ran the check. Run the query for both sender and receiver before marking an inbound as paid and again before sending material outbound payments. Treat wrapped and bridged USDC as separate instruments until you confirm the native Circle contract for your settlement chain.

To check a USDC address: match the chain to Circle’s native contract, call isBlacklisted(address) on that contract, record the boolean with the timestamp and operator. A false result is a snapshot; a true result prevents on-chain USDC movement and should stop settlement.