The asset-and-network pair is the real identifier
A ticker is not a universal serial number. Separate issuers, contracts and counterfeit tokens can use the same or similar display names. A legitimate stablecoin may also be deployed on several blockchains, with different fee assets, finality models and recipient support.
“I am sending USDC” is therefore incomplete. A useful description includes the USDC version, the blockchain, and both endpoints. Between custodial platforms, both screens must explicitly list the same network. From a self-custody wallet, also verify that the token contract held by the wallet matches the version accepted at the destination.
Use issuer documentation to identify contracts
On chains that represent tokens with smart contracts, the contract address distinguishes one token from another on that chain.
Do not copy it from a search ad, chat group, comment or unsolicited message. Begin with the issuer's official documentation and cross-check the network and token in a reputable explorer.
Circle’s contract-address documentation lists USDC mainnet contracts or asset identifiers by blockchain and separates mainnet from testnet. That is the right shape of verification: choose the chain first, then take the identifier assigned to that chain. The list does not mean that every exchange or wallet supports every listed route.
Native, bridged and wrapped versions are not interchangeable labels
A native token is generally issued or recognised directly by its issuer on a chain. A bridged representation is typically minted or mapped through a cross-chain system. A wrapped asset represents another asset through a contract or custody arrangement. Similar names do not erase different contracts, redemption routes and counterparties.
If a destination says it accepts native USDC, do not substitute a token labelled bridged, .e, Wormhole or another origin without explicit support. Circle Mint’s supported-chain documentation warns that unsupported tokens or bridged USDC sent to specified addresses may be lost or stuck. Support can also differ between products operated by the same company.
A pre-transfer checklist
- Asset: match the full stablecoin name, not just its icon.
- Network: match the chain name and mainnet state at both ends; “EVM compatible” does not mean “the same chain.”
- Version: in self-custody, compare the contract or official asset identifier.
- Destination: compare the complete address and enter a memo or tag only when the current deposit screen supplies one.
- Amount: account for the withdrawal charge and ensure the expected arrival clears any minimum.
- Gas asset: a self-custody wallet may need the chain's native asset to pay the network fee.
- Test: for a new route or material amount, consider a small first transfer and wait for crediting.
A test transfer reduces the amount exposed while validating a route; it does not make an unsupported network recoverable. If the recipient explicitly excludes the route, even a tiny transfer is still a wrong transfer.
Why matching address prefixes are not enough
Many EVM-compatible networks use addresses beginning with 0x, while keeping separate ledgers. The same characters may be controlled by the same key yet remain invisible to a custodial recipient on an unsupported chain. An interface accepting pasted text confirms only its format—not the deposit route.
A QR code also encodes information without proving compatibility. Scan it only from the current recipient screen, then recheck asset and network. Clipboard malware can replace an address, so important transfers deserve a full comparison or a carefully checked saved address—not a glance at the first and last four characters.
Memo and tag fields can be part of the destination
Some custodial services share an onchain address among users and use a memo, tag or similar identifier to credit an internal account. In that case, the address and identifier form one destination. Do not invent a value from an order number or reuse an old memo.
Enter an extra identifier only when the current deposit screen provides it. The memo and tag guide explains this account-allocation layer in more detail.
If the transfer has already gone to the wrong route
Stop sending more. Preserve the sender record, transaction hash, network, token contract, sending and receiving addresses, amount and time. Find the transaction on the correct network, then contact the party that actually controls the destination address or crediting system. Only that party can assess whether recovery is technically and operationally supported.
Never give a “recovery specialist” a seed phrase, private key, one-time code or remote access, and never send another payment to a supposed verification address. Recovery depends on the chain, address control and recipient policy; it cannot be guaranteed. Before submitting a transfer, the network-selection guide explains what to compare at both ends.