Table of Contents
Send native Circle USDC to another wallet by transferring Circle's official contract on the same chain the destination address uses. A wallet send is one chain, one contract, one address.
Cross-chain movement is a different job. Circle's CCTP burns USDC on the source chain and mints native USDC on the destination; a wallet transfer does not do that.
Key Takeaways
- A wallet send moves native Circle USDC on one chain to an address that monitors that same chain.
- Confirm you hold Circle-issued USDC, not a bridged USDC.e wrapper.
- Match the token to Circle's published contract for that chain before you sign.
- The destination address must be for the chain you are sending on.
- The sending wallet needs the chain's native token for gas.
- On large tickets, send a small test first and wait for confirmation.
- Cross-chain is CCTP or a bridge, not a wallet send.
- Off-ramping after receive is a separate cash-out, not part of the transfer.
What a wallet send actually is
A wallet send is an on-chain transfer of the USDC you already hold to another address on the same blockchain. The recipient sees the same Circle-issued token you sent; no issuer mint or burn is involved.
Circle publishes native USDC on 37 networks as of June 2026. Ethereum's official contract is 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48; Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.
Those strings are not interchangeable. If the destination sits on a different chain, stop and use a cross-chain rail instead.
Checklist before you click send
Run every row. Skipping one item is how native USDC lands on a chain the recipient does not monitor, or how a wrapper leaves the wallet labeled as USDC.
| Check | Pass means | Fail mode |
|---|---|---|
| Native token | Balance is Circle-issued USDC, not USDC.e | Recipient cannot redeem or book the inbound as USDC |
| Official contract | Token address equals Circle's published string for that chain | Clone, old wrapper, or ticker-only match |
| Destination chain | Recipient address is for the same chain you send on | Tokens sit where the recipient is not looking |
| Gas | Sending wallet holds the native fee token | Transfer never broadcasts |
| Test send | Small confirmed credit on the explorer | Full ticket sent to a bad address |
1. Confirm native Circle USDC
The ticker is a label. Native USDC is the Circle-issued contract on that chain; a bridged USDC.e wrapper is not.
Use how to tell native USDC from bridged USDC before you treat the balance as sendable dollars. Circle states, on X Layer and by the same split elsewhere, that a separate bridged representation is not issued or backed by Circle.
2. Confirm the official contract on that chain
Match the token address character-for-character to Circle's USDC contract list. A wallet token list or a search result is not the source.
How to check the official USDC or USDT contract is the treasury method. Ethereum, Base, Solana, Arbitrum, and every other listed chain have different strings.
3. Confirm the destination is for that chain
The destination address must be the one the recipient monitors on the chain you will use. An Ethereum deposit is not a Base deposit, even when the 0x string looks identical on EVM wallets.
A confirmed send on the wrong network is not reversible by Circle. Recovery is a later, separate process: how to recover USDC sent to the wrong network.
On memo-based or tagged chains, the payment includes the memo. Omitting a required destination tag has the same result as the wrong chain.
4. Fund gas in the native token
USDC does not pay for blockspace on most networks. The sending wallet needs ETH on Ethereum, Base, and Arbitrum; SOL on Solana; and the equivalent native token on other chains.
Circle's own transfer quickstart lists the same two balances: USDC to send, and native tokens for gas. Why you need a second token to send stablecoins is the operational reason; without that second token the send never leaves the wallet.
5. Send a small test first
On any ticket large enough to matter, send a small amount to the same address on the same chain first. Wait until the explorer shows success and the recipient can see native USDC.
Then send the remainder from the same wallet, on the same chain, to the same address. Do not change the token, the network, or the destination between the test and the full amount.
6. Wait for confirmation, then verify
Broadcast is not received. Wait for the confirmations your policy already uses on that chain, then match token, amount, and destination on the explorer.
Ask the recipient to confirm the credit against Circle's published contract, not against a ticker. Store the transaction hash with the payable or the internal transfer record.
Cross-chain is not a wallet send
A wallet transfer cannot move Ethereum USDC onto Base. If the recipient needs USDC on another chain, use Circle's Cross-Chain Transfer Protocol, which burns native USDC on the source and mints native USDC on the destination.
That flow is how to transfer USDC between chains without a bridge. A lock-and-mint bridge that creates USDC.e is a third path, and it is not a wallet send either.
Circle's consumer USDC Bridge is an app built on CCTP. It is still a burn-and-mint, not a same-chain wallet transfer.
After the recipient has USDC
The transfer is done when native USDC is visible under Circle's official contract on the destination wallet. Booking a ticker is not enough.
If the recipient later needs dollars in a bank, that is a separate cash-out: how to off-ramp USDC to ACH or wire. Do not fold an ACH or a wire into the send.
What not to do
Do not send USDC to an address that arrived only by email or chat. Confirm the string out of band the same way you would confirm a new bank account.
Do not paste a contract a stranger labeled USDC. Approving or sending to a clone can drain the wallet.
Do not treat a pending mempool sighting as paid. Wait for the explorer success and the recipient's confirmed balance.
Do not share a seed phrase with anyone who offers to "complete" or "unstick" a transfer. A wallet send is a signed transaction; it is never a remote-control of your wallet.
Conclusion
Sending USDC to another wallet is a same-chain transfer of Circle's official contract. Confirm native USDC, match the destination network, fund gas, test, then verify the hash.
If the recipient needs the tokens on a different chain, stop and use CCTP. If they need dollars in a bank, stop and off-ramp after they already hold native USDC.
FAQ
1. Can I send Ethereum USDC to a Base wallet in one transaction?
No. A wallet send stays on one chain. Use CCTP or another cross-chain rail if the recipient monitors a different network.
2. How do I know I hold native Circle USDC?
Match the token contract to Circle's published address for that chain. If the address is a bridge or a USDC.e wrapper, you do not hold Circle-issued USDC.
3. Why did my send fail if I have USDC?
The wallet is missing the chain's native gas token, or the transaction reverted. Circle's transfer guidance requires both USDC and native tokens before you submit.
4. What if I already sent USDC to the wrong network?
Circle cannot reverse a confirmed transfer. Identify who controls the destination and follow how to recover USDC sent to the wrong network; do not send a second amount.
5. Is a confirmed USDC send reversible?
Not at the protocol level. A recall is a new inbound from the recipient to an address you control.
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.
){kind=link}