How to send Monero in United States

Fee comparison

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

Regulatory framing — United States

FinCEN Travel Rule applies to XMR sends in principle — VASPs that handle XMR transfers ≥ $3,000 must transmit originator + beneficiary information. The privacy-coin design makes Travel Rule compliance technically near-impossible (you can't transmit beneficiary info if the protocol hides beneficiary by design), which is the primary driver of the US CEX delisting wave. For peer-to-peer self-custody XMR sends, no VASP intermediary = no Travel Rule trigger. OFAC SDN-screening is also technically difficult on XMR (you can't screen a recipient address against the SDN list if recipient is hidden by stealth-address design). Tax: sending XMR between your own wallets is NOT a taxable event; sending XMR as payment for goods/services IS a taxable event treated as if you sold XMR for USD then paid in USD.

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

Common gotchas

• Monero addresses are LONG. Standard XMR addresses: 95 chars (starts with '4'). Integrated addresses (with payment ID embedded): 106 chars. Subaddresses: 95 chars (starts with '8'). Verify carefully — wrong format = wallet rejects at submission.
• Payment IDs are deprecated. Older XMR transactions used 64-char payment IDs to identify deposits at exchanges. Post-2019, subaddresses replaced payment IDs in most flows. If a recipient still asks for a payment ID, verify their wallet supports the legacy format; otherwise use a subaddress.
• Sync is required before sending. Light wallets (Cake, Edge, MyMonero) sync the wallet view-key to a remote node + can send relatively quickly. Monero Core full-node requires the full blockchain sync (~150GB) before sending. Mining-revenue XMR holders running their own node have the cleanest privacy + slowest setup.
• Fee market dynamics. Monero has a dynamic fee market; congestion spikes can raise the fee to ~$0.05-$0.20 (still cheap by Ethereum standards). Wallets typically auto-suggest the appropriate fee tier.
• Privacy is on by default — there's no 'public mode'. Unlike Zcash (z-addr opt-in vs t-addr default) or DAI's MWEB (opt-in privacy), Monero is privacy-by-default. There's no option to send a 'transparent' XMR transaction. This is a feature for users who want privacy + a constraint for compliance-bound recipients.
• Confirmation timing for high-value sends. Monero: 10 confirmations (~20 min) for retail; 30+ confirmations (~60 min) for high-value or post-reorg-incident windows. Use a Monero block explorer (xmrchain.net) to verify the tx confirmed — but the explorer cannot show sender / recipient / amount (privacy design).

Step-by-step

1. Verify destination address format. Standard XMR address: 95 chars, starts with '4'. Subaddress: 95 chars, starts with '8'. Integrated address: 106 chars. Most modern wallets default to subaddresses for incoming deposits.
2. Ensure wallet is synced. Light wallets (Cake, Edge, MyMonero): sync in minutes via remote view-key node. Monero Core full-node: requires initial full sync (~150GB, hours). Hardware-wallet-backed flows (Ledger + Monero companion app): sync via host wallet.
3. Set fee (auto-suggested is usually fine). Wallet auto-suggests fee tier based on current network conditions. Default tier is typically appropriate. For urgent high-value sends, choose a higher tier (~2x-4x the auto-suggested).
4. Do a test-send for first-time large sends. Any send > $1,000 to a new destination: test with $5-$10 first. Wait for 10 confirmations on destination before sending the rest. XMR address-poisoning is less common than Solana but verification matters.
5. Confirm finality on the destination side. Monero: 10 confirmations (~20 min) for retail-confidence; 30+ confirmations (~60 min) for high-value. Use xmrchain.net to verify the tx confirmed (note: explorer cannot show sender/recipient/amount — only that the tx exists).
6. Record the send for tax purposes (if applicable). Self-to-self: no tax event; document the transaction hash + your own wallet addresses for record-keeping. Payment for goods/services: taxable disposal at FMV. Note: XMR's privacy design means transaction details aren't recoverable from the chain — your own records are the only evidence.

Tax summary

Sending XMR between your own wallets is NOT a taxable event. Sending XMR as payment for goods/services IS a taxable disposal (XMR FMV - cost basis = gain/loss). Travel Rule typically inapplicable due to privacy design (no VASP intermediary in self-custody-to-self-custody flows). OFAC SDN screening technically difficult on XMR. Your own records are the primary tax-reporting source since chain data isn't recoverable post-tx. See /crypto-taxes-us/.

Where to read further

• United States crypto tax primer
• Best crypto banks in United States
• Best crypto tax software for United States filers
• /how-to/buy-monero-us/
• /how-to/sell-monero-us/
• /how-to/swap-monero-us/
• /how-to/send-bitcoin-us/
• /crypto-taxes-us/

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.