Skip to content

Stablecoin · checked 9 November 2026

Agent payment safety checks for USDC

USDC is Circle's stablecoin, issued natively on dozens of networks and moved between them by CCTP burn and mint, with Circle able to block addresses.

What your agent needs to know about USDC

When it counts as settled
A USDC payment is as final as the chain it settles on. For cross-chain moves with CCTP, Circle says Fast Transfer takes about 8 to 20 seconds. Standard Transfer time depends on the source chain: about 15 to 19 minutes from Ethereum and most OP Stack chains, but about 2 to 4 hours from Starknet and 6 to 32 hours from Linea. Fast Transfer is a property of the source chain: Circle marks it N/A for Sui and Aptos because their Standard attestation already takes about 0.5 seconds. Treat a cross-chain payment as settled when the mint on the destination chain is confirmed, not when the burn is seen.[1],[2],[6]
Fees
Gas is paid in each chain's own token, so an agent needs native gas on every chain it pays on. For CCTP USDC transfers, the CCTP page says the fee comes out of the transferred amount, so the received amount can be lower than the amount burned.[2]
Stablecoins
Circle's page lists the networks where USDC is natively supported, including Solana, Aptos, Sui, Base, Ethereum and Arbitrum. Tron is not on the list. Other versions are bridged USDC, and Circle's terms say it has no obligation to support copies or wrappers, and is not responsible for value lost because of that. Circle can block addresses and freeze USDC for Circle-custodied addresses, and may be ordered by authorities to freeze. Sending USDC to a blocked address can lead to freezing and loss of redemption rights.[3],[4],[5]
Issuer-published contract addresses. Compare all of it, not the first and last characters.
TokenAddressSource
USDC on Solana (mint)EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v[5]
USDC on Sui (coin type)0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC[5]
USDC on Aptos0xbae207659db88bea0cbead6da0ed00aac12edcdda169e591cd41c94180b46f3b[5]

How agent payments go wrong on USDC

  1. 1. Bridged or wrapped USDC treated as native

    A token called USDC on a chain Circle does not list, or issued by a third-party bridge, is not Circle's token. Circle's terms say it does not support copies or wrappers. Allowlist the contract address from Circle's page per chain.[3],[5]

  2. 2. Paying a blocked address

    Circle can block addresses linked to illegal activity, and funds moving to or from them may be frozen. An agent that pays an unknown counterparty can have funds stuck. Screen counterparties before paying.[4]

  3. 3. Settling on the burn, not the mint

    CCTP burns USDC on the source chain and mints on the destination after attestation. Between those steps the funds are in neither place. Wait for the destination mint before fulfilling.[1]

  4. 4. One timeout for every CCTP route

    Attestation time depends on the source chain and transfer type. Per Circle's table, Standard from Ethereum and most OP Stack chains (Base, OP Mainnet, Unichain, World Chain) and Arbitrum takes about 15 to 19 minutes, but from Ink about 30 minutes, Morph 20 to 30 minutes, Starknet 2 to 4 hours and Linea 6 to 32 hours, while Standard from Sui or Aptos takes about 0.5 seconds. An agent with one fixed timeout will misreport a normal transfer as failed, for example a 20 minute timeout on a Linea transfer, and may burn again. Set the timeout per source chain from Circle's table.[2],[6]

  5. 5. Wrong-chain send

    The same address string can exist on several EVM chains, but a transfer on the wrong chain lands in a different state. Circle's terms say USDC sent to an address that does not support USDC is lost for Circle Mint users. Bind each payment to a chain ID and token address.[4]

Pre-flight checklist for a USDC agent

  • Allowlist the USDC contract or mint per chain from Circle's address page.
  • Reject chains not on Circle's native list unless the policy allows bridged USDC.
  • Screen counterparty addresses before paying.
  • For CCTP, wait for the destination mint and use route-specific timeouts.
  • Account for the CCTP fee deducted from the amount.
  • Keep native gas on every chain the agent pays on.

Run the checks now, free

The free tools run in your browser: nothing you type leaves your browser, and wallet reads go only to a public RPC.

  • The Wrong-Money Test

    Write down what happens when your agent pays the wrong amount, the wrong address or the wrong token on USDC, and see whether the answer holds up.

  • Agent Spend-Cap Stress Test

    Work out how much your agents can really move in one window once retries, parallel runs and per-key limits stack up.

  • Agent Money Trace

    Joins on-chain transfers on Base, Ethereum, Arbitrum, OP Mainnet or Polygon to your run log, so every payment maps to a decision.

Want a second pair of eyes on how your agent pays on USDC? Book the free 48-hour integration review (opens Cal.com in a new tab).

Sources

  1. [1] CCTP overview, Circle
  2. [2] CCTP supported chains and domains, Circle
  3. [3] Multi-chain USDC, Circle
  4. [4] USDC Terms, Circle
  5. [5] USDC Contract Addresses, Circle
  6. [6] CCTP finality and block confirmations, Circle

Checked against these sources on 9 November 2026. Networks change: confirm against the live docs before you rely on a number. This page is a checklist from public documentation. It is not a security audit, legal, compliance or investment advice.