How to send USDC: match the token, network and destination
A concise sending reference for an actual USDC requirement, with the checks that matter before and after a transfer.
TL;DR
Use the destination's current USDC deposit instructions, match its network and exact asset, review fees and verify the credited balance. There is no universal timing or sub-penny fee promise.
Key Takeaways
- ✓Follow the receiving service's current instructions.
- ✓Review the complete token/network/address details.
- ✓Verify the destination credit as well as the chain transaction.
Check what the destination accepts
Confirm the token, network, full address, any memo/tag and the minimum deposit. The destination service's own instructions matter even when the issuer supports the network. Check that sending and receiving functions are currently enabled.
Do not substitute a bridged token or another stablecoin into a deposit that expects native USDC. A shared address format is not enough evidence that two networks are interchangeable.
Review the send and verify receipt
Check the amount the recipient should receive after charges and the native resources or fee asset needed for a self-custody transaction. Read the final preview before signing. A small test on a new route can check that route's behavior, but does not establish that an unknown recipient is trustworthy.
After sending, check both chain status and destination credit. A receiving platform may have its own confirmation and processing requirements. A transaction hash is not proof of a completed cash-out or bank receipt.
Choose the asset before forcing a route
If the destination actually requires USDC, meet that requirement. If you are choosing a digital-dollar route more generally, the USDT network and transfer guide is our featured guide. Neither asset is automatically cheapest or eligible on every service.
Keep reading
Cite this page
USDC.org. "How to send USDC: match the token, network and destination." USDC.org. https://usdc.org/guides/how-to-send-usdc.