Skip to main content
Our Top Pick: Revolut — Best overall crypto bank for most users Open Account ↗ (affiliate)
transactional United States · US USDC

How to send USD Coin in United States

Verified 2026-06-02 · 6 primary regulators · 5 venues compared

SK
Reviewed by Stephan Kulik · Last updated: · How we rank

Short answer

Sending USDC in the US in 2026 is straightforward technically — the strategic question is WHICH CHAIN. USDC is natively issued on 16+ blockchains (Ethereum + L2s + Solana + Avalanche + Polygon + Stellar + Aptos + Sui + others) and Circle's CCTP (Cross-Chain Transfer Protocol) burn-mints USDC between chains for ~1-3 minute finality at near-zero cost. Send fees range from $0.001 (Solana, Stellar) to $5-$30 (Ethereum mainnet during congestion). Travel Rule applies at $3,000+ regulated-venue → regulated-venue transfers. Sending is NOT itself a taxable event (same property, same address-equivalent owner).

Fee comparison

All-in cost per venue across the most-common payment + settlement paths. Verified 2026-06-02.

Venue Send FeeSpeedUse CaseCcp Support
Solana ~$0.0001-$0.001 per transactionSub-second finality (block time ~400ms); 1-2 confirmations recommendedHighest-throughput chain for USDC; ideal for payments + retail flowsYes; CCTP v2 supports Solana ↔ Ethereum + L2s natively
Base (Ethereum L2) $0.02-$0.30 typical2-3 second finality; 5-10 sec safety marginCoinbase-aligned L2; deep USDC liquidity; default for Coinbase-Wallet usersYes; CCTP supports Base
Arbitrum / Optimism (Ethereum L2) $0.05-$0.50 typicalSame as Base; finality < 5 secBroader DeFi protocol coverage than Base; cheaper than mainnetYes; CCTP supports both
Ethereum mainnet $5-$30 typical; $50+ during peak congestion12 second blocks; 12 confirmations recommended for finality (~3 min)Highest counterparty acceptance; most institutional support; cost-prohibitive for retail-size sendsYes; CCTP origin/destination for cross-chain mint-burn
Stellar ~$0.00001 per transaction (100 stroops)3-5 second finalityRemittance + payment-rails focus; Circle's original USDC chain (2018)Native USDC on Stellar but CCTP integration limited as of 2026-06-02

Regulatory framing — United States

FinCEN's Travel Rule (31 CFR 1010.410(f)) requires regulated VASPs to transmit originator + beneficiary information for transfers ≥ $3,000 between regulated entities. CEX → CEX transfers are covered; CEX → self-custody requires the originating CEX to collect beneficiary information (which most CEXes interpret as collecting a label/note + counterparty exchange name if applicable). FATF Recommendation 16 is the international parallel — US-domiciled CEXes apply it globally to outbound transfers. Sending USDC between self-custody addresses is NOT regulated under the Travel Rule (no VASP intermediary). The 2024 OFAC sanctions framework requires CEXes to screen destination addresses against the SDN list — sends to sanctioned addresses are blocked automatically. Tax: sending USDC between your own addresses is NOT a taxable event (no disposal); sending USDC as payment for goods or services IS a taxable event (treated as if you sold the USDC for USD then paid in USD).

Primary regulators: FinCEN · SEC · CFTC · IRS · OCC · State MTL

Common gotchas

  • Chain mismatch = lost funds. Sending USDC from a Solana-address to an Ethereum-address WITHOUT bridging via CCTP results in irrecoverable loss. The exchange UI typically prompts you for the destination chain — verify carefully. Coinbase, Kraken, and Crypto.com all default the chain incorrectly in some flows; double-check.
  • Memo/tag requirements: Stellar USDC requires a memo for exchange deposits (similar to XRP destination tags). Sending without the memo means the deposit credits the exchange's pool address but doesn't credit YOUR account — recovery requires exchange support intervention + days of delay.
  • Travel Rule data collection at CEX outbound: for transfers ≥ $3,000 to another regulated VASP, Coinbase + Kraken now collect counterparty information (recipient name + VASP name). This is a 2-3 minute UX friction but not a hard block. For self-custody recipients, you confirm 'this is my own wallet' or 'this is a personal contact's wallet.'
  • OFAC screening can produce false-positive blocks. If your destination address has ANY historical connection to a sanctioned address (even one-hop through a DEX), the CEX may flag + delay or block the send. Resolution requires support ticket + sometimes attorney letter. Pre-clear large self-custody destinations against Chainalysis or TRM Labs.
  • Stablecoin yield protocols re-route USDC: if you send USDC into Aave, Compound, or other lending pool, you receive the receipt token (aUSDC, cUSDC) — these are NOT 1:1 USDC and have their own tax basis. The 'send' is functionally a deposit + receipt-token mint event. Tax treatment differs (deposit = generally non-taxable; receipt-token redemption = capital-gain event vs deposit basis).
  • 1099-DA reporting on sends: CEX sends > $10,000 to non-CEX addresses can trigger an 8300 Cash Transaction Report (Form 8300 + FinCEN CTR equivalent) under Treasury's 2024 broker rules. The threshold + applicability are contested + may shift. Document large sends + retain records.

Step-by-step

  1. Verify the destination chain matches your USDC location. If your USDC is on Solana, the destination must accept Solana-chain USDC OR you must bridge via CCTP first. Most chain mismatches happen at this step. Read the destination address's chain requirement explicitly.
  2. Verify the destination address character set + length. Ethereum + L2 addresses: 0x... prefix, 40 hex chars. Solana: base58, 32-44 chars. Stellar: G... prefix, 56 chars. Wrong format = transaction will reject (best case) or send to a wrong-chain address (worst case, irrecoverable).
  3. Initiate the send + handle memo/tag if required. Solana, Ethereum, L2s: no memo. Stellar: required memo for many exchange deposits. XRP-style memo prompt in the UI? You must fill it or the deposit won't credit your destination account.
  4. Do a test-send for first-time large sends. For any send > $10k to a new destination, test with $10-$50 first. The 5-15 minutes of extra time amortizes well against the catastrophic loss scenario of a chain-mismatch or address-typo.
  5. Confirm finality on the destination side. Solana: 1-2 confirmations. L2: 5-10 seconds. Ethereum mainnet: 12 confirmations (~3 min) for high-stakes sends. Stellar: 1 confirmation. Until finality, the send isn't safe (chain re-orgs can theoretically revert).
  6. Record the send for tax purposes (if applicable). Self-to-self: no tax event; document for record-keeping. Payment for goods/services: taxable disposal at FMV. Gift > $18k/recipient: file Form 709. Document the transaction hash for proof-of-send to whoever asks.

Tax summary

Sending USDC between your own wallets is NOT a taxable event. Sending USDC as payment for goods/services IS a taxable disposal (USDC FMV - cost basis = gain/loss). Sending as a gift: > $18,000/recipient/year (2024 threshold) triggers Form 709 (no tax owed by typical givers, but reporting required). Travel Rule data collection happens at the CEX level for ≥ $3,000 outbound. See /crypto-taxes-us/.

Where to read further

Methodology

Fee data verified directly against each venue's public fee schedule on 2026-06-02. Regulatory framing cross-referenced against the Stage 1d info-layer + primary government sources (bsa-fincen, us-cftc-cea, us-fdic-12cfr330, us-state-mtl, ny-bitlicense, irs-1099-da-broker). Gotchas reflect operating experience + community-reported failure modes during the verification window. This page is editorial reference content — not financial, tax, or legal advice. Always verify the current state of each venue and the current law in United States before transacting.

Disclaimer

This page is general information, not financial, tax, or legal advice. Cryptocurrency regulation in United States evolves; verify the current rules with a qualified professional in your jurisdiction before relying on any specific approach. See terms.

esc
↑↓ navigate ↵ open esc close