How to receive crypto safely into a self-custody wallet

You already know sending crypto is irreversible. Receiving feels safer: someone else presses the button. That comfort is only half true. If you hand out the wrong address, the wrong network, or an address you never verified on a trusted screen, the funds can land where neither of you can spend them. The sender did their job. Your setup failed.

This guide is the counterpart to sending safely from self-custody. It walks you through generating a receive address, matching the network the sender will use, sharing the details without inviting error, and confirming arrival on a block explorer. If you are still moving coins off an exchange for the first time, start with the self-custody 101 walkthrough.

Not financial advice. Receiving cryptocurrency still involves permanent loss risk when the address or network is wrong. Practice with small amounts. Always follow the latest official docs for your specific wallet.

What “receive” actually means

A receive address is a public identifier derived from your keys. Anyone who knows it can send value to you. Only the matching private keys (held in your wallet or hardware device) can spend what arrives.

Three properties matter in practice:

• Addresses are public by design. Posting one on a bill does not empty your wallet. What empties wallets is signing a spend, leaking a seed phrase, or approving a malicious transaction.
• Addresses are chain-specific. A Bitcoin address is not an Ethereum address. USDT on Tron (TRC-20) is not USDT on Ethereum (ERC-20), even though the ticker is identical.
• Your wallet may show many addresses. Bitcoin wallets often generate a fresh address per receive. EVM wallets (Ethereum, Base, Polygon, and similar) usually reuse one 0x address across many tokens on that same network. Reuse there is normal; mixing networks is still fatal.

Receiving is “safer” only because the sender bears the final click. You still own the job of giving correct coordinates.

Before anyone sends you anything

1. Decide asset and network. Write both down. “USDT” alone is not enough. “USDT on Tron (TRC-20)” or “USDC on Base” is enough.
2. Confirm your wallet supports that exact pair. Open the receive screen for that asset and network. If the option is missing, do not improvise with a similar-looking chain.
3. Plan for later network fees. To spend what you receive on many chains, you need a small balance of the native coin (TRX on Tron, ETH on Ethereum, SOL on Solana). Receiving USDT with zero native coin can leave a balance you cannot move until you top up gas.
4. Agree details with the sender in writing. Include asset, network/token standard, and the full address. Keep the thread until the funds arrive.

Family remittances and freelance payments in the region often default to USDT on Tron because fees are low and exchanges list it widely. That is a practical default, not a rule. Match what both sides can actually use.

The receiving checklist

Do these steps in order every time the amount matters.

1. Open the correct account and network

In your app (Ledger Live, Trezor Suite, BlueWallet, Sparrow, Trust Wallet, MetaMask, and so on):

• Select the asset the sender will use.
• Explicitly select the matching network or token standard.
• Open Receive (sometimes Deposit or Show address).

Do not copy an address from an old chat until you have re-displayed it under the correct network today.

2. Display the address on a trusted path

For a hardware wallet, the critical step is on the device screen. The address on your phone or computer must match the hardware display. Confirm on the device before you copy anything. That defeats clipboard malware and a compromised companion app.

For a software-only wallet, open receive from the official app you installed yourself. Do not follow “receive here” links from strangers.

3. Copy the full address and verify it

Paste it into a plain text note on the same device. Check the first six and last six characters against what the wallet still shows. Prefer full-string comparison when the amount is material.

If you use a QR code, scan it so you can read the decoded string. Do not approve unknown wallet-connect prompts that appear after a scan.

4. Tell the sender three things, not one

Send them:

1. The full address as plain text (not only a screenshot).
2. The asset and network in plain language (“USDT, Tron / TRC-20”).
3. A request for a small test first if the amount is large.

For large transfers, ask them to read back the first and last characters on a second channel (voice call, different app).

5. Wait for the txid, then verify on an explorer

When the sender claims the transfer is done, ask for the transaction ID. Open the official explorer for that chain yourself. Confirm status, full recipient address, amount, token, and confirmations. Details and explorer URLs live in the block explorer guide.

6. Only then treat the payment as received

Wallet apps can lag on mobile data. The explorer is the public record. Archive the txid for your own notes.

A simple receive flow

Figure: Receive flow — agree network, verify the address on a trusted path, share both address and network, then confirm on a block explorer.

Mistakes that lose funds

Wrong network, same ticker. You shared a Tron USDT address. The sender picked Ethereum USDT because the exchange listed “USDT” first. The transfer may confirm on Ethereum while your Tron balance stays empty. Treat that as preventable, not as a support ticket you will win.

Wrong account or passphrase. Multi-account wallets can show a familiar UI for the wrong keys. Match the address on the device before sharing.

Clipboard swap. Malware replaces a copied address with an attacker address that may look similar at the ends. Hardware-screen verification and a re-check after paste stop this.

Address poisoning. Attackers send tiny amounts from lookalike addresses so a careless “copy from history” later points to them. Never copy a send destination from history. When receiving, still compare the full string you shared against the explorer recipient field.

Unsolicited QR or “support” links. Generate the address yourself. Share it outward on a channel you control.

Assuming the wallet balance updates instantly. Mobile sync lag can hide a real transfer. Use the explorer with the txid before you accuse the sender or ask for a second payment.

Sharing addresses in everyday LatAm use

Stablecoin P2P, family support across borders, and freelance invoices often move over WhatsApp or Telegram. Make the channel work for you:

• Paste the address as text, not only an image.
• Put the network name on its own line so it cannot be cropped out of a screenshot.
• For recurring payers, save a labeled contact after the first successful test. Re-verify if either of you changes wallets.
• Prefer low-fee networks both sides already use.
• Keep a personal note of successful txids. Tax and platform reporting (for example Brazil’s DeCripto wallet statements) reward clean personal records.

A short message template is enough:

Please send USDT on Tron (TRC-20) only.
Address:
TYourAddressHere...
Please send $5 test first, then the rest after I confirm.

Adapt the asset and network. Keep the structure.

When something looks wrong

• No funds, no txid. The sender has not broadcast, or used a different account. Do not share a new address until you know which.
• Txid exists, wrong recipient. Stop. Do not send “return” payments. Document everything.
• Correct recipient, wrong amount. Check decimals and token type on the explorer.
• Txid on the wrong chain’s explorer. The payment is not in the wallet you are staring at. Re-open the network conversation before anyone sends again.

Never “fix” a failed receive by guessing a different network and asking for a second full amount. Resolve the first transfer first.

Quick reference

1. Agree asset + network in writing.
2. Open that exact pair in your wallet.
3. Show the receive address; verify on the hardware screen when you have one.
4. Copy, paste, and re-check characters (full string when the amount is large).
5. Share address + network as text; request a test send for large amounts.
6. Get the txid and verify recipient, amount, and confirmations on the right explorer.
7. Archive the txid. Only then call it done.

The bottom line

Receiving is a coordinates problem before it is a waiting problem. The public ledger will faithfully deliver value to whatever address and network the sender used. Your job is to make sure those coordinates are yours, on the chain you both named, verified on a screen you trust.

Pair this habit with careful sending and explorer checks and you close the everyday self-custody loop: take custody, receive cleanly, send deliberately, and prove each step on-chain without asking an exchange for permission.

Generate the address yourself. Name the network out loud. Test small when it hurts to be wrong. Confirm on the explorer. That is the whole skill.