Table of Contents
Receive native Circle USDC by sharing the wallet address that monitors the same chain the sender will use, then confirming the inbound under Circle's official contract on that chain. A receive is one chain, one contract, one address.
This is not a merchant checkout. A wallet receive is a same-chain credit of Circle-issued USDC at an address you control.
Key Takeaways
- A receive is native Circle USDC on one chain at one address.
- Share the address that monitors the chain the sender will use.
- The same 0x string on a different chain is a different receive.
- Import Circle's official contract so the inbound is visible.
- Confirm the explorer hash, token contract, amount, and destination.
- Exchange deposits need the memo or tag the venue published.
- A receive does not require a signature.
- Never share a seed phrase to complete a receive.
What a wallet receive actually is
A wallet receive is an on-chain credit of USDC at an address you control, on one blockchain. The sender transfers Circle's official contract on that chain; you do not mint, burn, or approve anything to take the inbound.
Circle's contract list names native USDC on 37 mainnet networks. Ethereum's official contract is 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48; Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.
Those strings are not interchangeable. If the sender uses a different chain than the one your wallet is watching, the credit sits where you are not looking.
The counterpart send is how to send USDC to another wallet. A receive is the same transfer, read from the destination.
Receive checklist
Run every row before you tell the sender to go. Skipping one item is how native USDC lands on a chain you do not monitor, or how a wrapper shows up labeled as USDC.
| Check | Pass means | Fail mode |
|---|---|---|
| Address | Copied from the wallet that controls the destination, then verified after paste | Clipboard swap, typed error, or a chat-supplied string |
| Chain | Sender will use the same network the wallet is watching | Tokens sit on a chain you are not looking at |
| Official contract | Inbound token equals Circle's published address for that chain | Clone, old wrapper, or ticker-only match |
| Visibility | Wallet displays Circle's official USDC on that network | Zero row because the contract was never imported |
| Explorer confirm | Hash, token contract, amount, and your address all match | Pending mempool sighting, wrong token, or wrong destination |
1. Share the address that monitors that chain
Copy the public address from the wallet you control. MetaMask shows the Ethereum (EVM) address under the account dropdown by default; click it to copy.
On MetaMask, other network addresses for the same account, including Solana, appear when you hover. Copy the address for the family the sender will use; a Solana mint is not an EVM 0x string.
After you paste, compare the first and last characters to the wallet. MetaMask warns that a mismatch can mean clipboard malware.
Do not send a seed phrase, a private key, or a screenshot of a recovery phrase. A receive never requires those.
Name the chain in the same message as the address. "Send USDC to 0x…" without a network is how an Ethereum send becomes a Base problem.
2. Treat the chain as part of the address
On EVM wallets the 0x string often looks identical across Ethereum, Base, Arbitrum, and Polygon. The address is not a global inbox.
Circle's native USDC on Arbitrum is 0xaf88d065e77c8cC2239327C5EDb3A432268e5831; on Polygon PoS it is 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359. Solana's mint is EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v.
Tell the sender the network by name. An Ethereum deposit is not a Base deposit even when the destination string matches.
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.
3. Display Circle's official contract
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 book the inbound as dollars. Circle states, on X Layer and by the same split elsewhere, that a separate bridged representation is not issued or backed by Circle.
A wallet may hide a correct receive until you import the contract. How to add USDC to MetaMask is that display step; importing does not mint a balance.
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. On Ethereum, Etherscan's Circle USDC token page lists the same contract, with 6 decimals.
If the wallet fills a different symbol or a different decimal count after you paste, you pasted the wrong contract. Stop and go back to Circle's list.
4. Confirm the credit on the explorer
Broadcast is not received. Wait for the confirmations your policy already uses on that chain, then open the explorer for that network.
Match four fields: transaction hash, token contract, amount, and destination address. The token must equal Circle's published string for that chain, not a ticker.
Circle's transfer quickstart treats the recipient as an address on the selected EVM chain and waits for a successful receipt. Copy that same check: success on the explorer, then a visible native-USDC balance.
Store the hash with the receivable. Booking a ticker in the wallet without the explorer match is not confirmation.
5. Exchange deposits need the tag
A venue deposit is not a self-custody receive. The exchange publishes an address plus, on some networks, a memo, destination tag, or payment ID.
Omit the tag and the venue may not credit you. The chain can still show a success hash to an address you do not control.
Use the deposit screen for the named asset and the named network. Do not reuse a USDT deposit, an Ethereum address for a Solana send, or a screenshot from an old ticket.
After the receive
The receive is done when native USDC is visible under Circle's official contract at your address on that chain. A zero row after a correct import means you do not hold that contract on that network yet.
Sending the USDC onward is a new transfer. The sending wallet needs the chain's native token for gas; Circle's transfer guidance funds the sender with both USDC and native tokens.
If you later need dollars in a bank, that is a separate cash-out. Do not fold an ACH or a wire into the receive.
What not to do
Do not share a seed phrase with anyone who offers to "complete" or "unstick" a receive. A receive is an inbound transfer; it is never remote-control of your wallet.
Do not paste a contract a stranger labeled USDC. Importing or approving a clone can display a fake balance and open a drain.
Do not tell the sender to "just use the 0x; it works on every chain." It does not.
Do not treat a pending mempool sighting as paid. Wait for explorer success and the official-contract balance.
Do not send a second amount to "unlock" a missing credit. If the first hash used the wrong network, stop and recover; do not repeat it.
Conclusion
Receiving USDC in a wallet is a same-chain credit of Circle's official contract. Share the address that monitors that network, display the official token, then verify the hash.
If the sender used a different chain, stop and recover. If you need dollars in a bank, stop and off-ramp after you already hold native USDC.
FAQ
1. Can I receive Ethereum USDC at a Base address if the 0x string is the same?
No. A receive stays on one chain.
The same EVM string on Base is a Base address; Ethereum USDC does not appear there.
2. Why is my receive not showing in the wallet?
You are on the wrong network, the official contract is not displayed, or the inbound is a different contract. Switch network, import Circle's published address, then check the explorer.
3. How do I know I received native Circle USDC?
Match the token contract on the explorer to Circle's published address for that chain. If the address is a bridge or a USDC.e wrapper, you did not receive Circle-issued USDC.
4. Do I need ETH or another gas token to receive USDC?
No. The sender pays gas.
Circle's transfer quickstart funds the sending wallet with native tokens; the recipient address does not sign the inbound.
5. What if the sender already used 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 request a second send until that is done.
6. Is receiving USDC in a wallet the same as accepting USDC payments?
No. A wallet receive is a same-chain credit at an address you control.
Merchant checkout quotes a sale, takes native USDC on a named chain, and reconciles the hash to an invoice.
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}