Write down the required asset and network before opening a withdrawal or wallet flow. If the receiving instructions are ambiguous, resolve them before sending.
A pre-send checklist
Confirm the destination asset.
Is the recipient asking for USDT, native USDC or a particular bridged representation? Similar names do not make tokens interchangeable.
Match the network.
Use the receiver’s explicit network name. Ethereum, TRON, Base, Solana and Polygon PoS have distinct records and balances.
Verify the contract or mint.
For native tokens, compare the issuer’s current registry. For a bridged or pegged token, establish its separate provenance and recipient support.
Verify the recipient instructions.
Check the address, any service-specific memo or reference, minimums and deposit restrictions through a trusted channel.
Review the final operation and cost.
Read the wallet or provider confirmation. Check the asset, chain, destination, amount and fees; inspect spending permissions if the operation is an approval.
Use the issuer as the token-identity source
Circle publishes mainnet USDC contract addresses and Solana mint information. Tether publishes supported protocols and token contracts. Open those registries directly; do not use a search ad or a forwarded screenshot as the only authority.
Registries establish issuer documentation, not recipient support. You still need the receiving service’s current instructions. No single source resolves both sides of the transfer.
Common combinations that need extra attention
Scroll horizontally to read all columns.
| Looks similar | What differs |
|---|---|
| Ethereum and Base addresses | The network and balances; address shape is not a chain identifier. |
| USDC and USDbC on Base | Native versus bridged contracts. |
| USDC and USDC.e on Polygon PoS | Native versus bridged contracts and recipient acceptance. |
| Solana wallet and token account | Owner and token-specific storage; follow recipient instructions. |
| USDT and a pegged representation | Issuer, backing arrangement and redemption path. |
A test transfer has limits
Where fees and minimums make it practical, a small test can reveal a mistake before a larger transfer. It is not proof of future acceptance, permanent support or legal eligibility. The larger transfer can face different thresholds or review.
Do not repeatedly send while the first outcome is unclear. Reconcile the chain receipt and recipient credit first. Check whether a small test would fall below the platform’s minimum and therefore fail to establish anything useful.
If you discover a mismatch afterward
Find the transaction on the chain actually used and identify the token that moved. Contact the recipient through its official support route with those facts. Do not assume the chain can be reversed or that possession of a similar address guarantees recovery.
A legitimate assessment may conclude that recovery is unavailable. Be wary of unsolicited helpers promising certainty in exchange for another payment or your signing secrets.
Sources & review
Editorial review: Sep 21, 2026. Source-specific dates and retrieval limits are stated where relevant. Issuer and service statements are attributed, not independently audited; a citation is not an endorsement.
- Circle · USDC contract registry (opens in a new tab)
Mainnet and testnet token identity by blockchain.
- Tether · Supported protocols (opens in a new tab)
Issuer-published protocol and token contract information.
- Circle · Native USDC on Base (opens in a new tab)
Native USDC and the separate bridged USDbC asset.
- Circle · Native USDC on Polygon PoS (opens in a new tab)
Native USDC and bridged USDC.e are distinct tokens.
- Solana · Token accounts (opens in a new tab)
Token mints, owners and associated token accounts.
- FTC · Refund and recovery scams (opens in a new tab)
Warnings about unsolicited recovery offers and upfront fees.