How to Send and Receive Crypto on Mobile (2026)

The First Transaction Always Feels High-Stakes

Your wallet holds a public key for receiving funds and a private key for authorizing outgoing transfers. The private key stays on your device and never touches the network. What moves on the blockchain is a signed instruction, proof that the key holder approved the transfer. That distinction matters because a confirmed transaction cannot be reversed. The blockchain doesn't know whether you typed the destination address correctly or made a typo. It processes the instruction as written. So the skill you're building here isn't speed, it's the habit of checking before you confirm.

Here's what the next sections cover: how to share your address so someone can send to you, how to send crypto to someone else, and the one pre-confirmation check that prevents the most common costly mistake.

How to Send and Receive Crypto on Mobile

Receiving crypto: share your address, not your key

Receiving is simpler than sending. Open the Tangem Wallet app, select the token you want to receive, and tap "Receive." The app generates your wallet address for that network and displays it as a QR code alongside the alphanumeric string. Share that address, or let the sender scan the QR code directly from your screen. Your address is public information. Sharing it cannot expose your funds.

One thing to confirm with the sender: the network. Many tokens exist on more than one blockchain. USDT, for example, runs on Ethereum, Tron, BNB Smart Chain, Polygon, and others. If the sender transfers USDT on Tron but your address was generated for Ethereum, the tokens land on a network your wallet isn't watching. They're not lost from the blockchain, but they're inaccessible until you add the correct network. In some cases, a mismatch with an incompatible chain means permanent loss. Confirm the network before the sender hits confirm.

The Tangem app shows your address per network, so you can share the exact address for the right chain rather than a generic wallet address. Say a friend plans to send you 100 USDT. Ask them to name the network before either of you copies an address. Then open USDT on that same network in the app and share the address shown there. The address and QR code tell them where to send funds. They do not settle the question of the network. A quick message confirming the token and network gives both sides the same details before the transfer begins.

Sending crypto: the pre-confirmation checklist

The sending flow in the app has four inputs: recipient address, network, amount, and fee. Each one is a decision point.

Take a beat before tapping send. Put the destination address and the chosen network next to the details the recipient gave you, then compare them. Check the amount one more time and review the fee before approval. This short pause catches a copied address that belongs to somebody else and a network choice that does not match the recipient's wallet. It also gives you a moment to decide whether the fee level fits the urgency of the transfer.

Recipient address. You can enter it manually, paste it from the clipboard, or scan the sender's QR code. If you're scanning a QR code from an untrusted source, a screenshot forwarded through a messaging app, say, verify the decoded address on your screen matches the recipient through a second channel before proceeding. Compare the first and last several characters of the address; a substituted address often looks plausible at a glance. For contacts you pay regularly, the app's address book saves frequently used addresses so you skip manual entry entirely.

Network. All EVM-compatible chains (Ethereum, BNB Smart Chain, Base, Polygon, Arbitrum, and others) share the same address format. That means a valid-looking address gives you no signal about which network it belongs to. Say you're sending 100 USDT to a recipient on Ethereum. Select Ethereum, review the fee estimate, and confirm the network with them. A wrong choice can leave the transfer inaccessible. A low fee during congestion can delay confirmation.

Amount. The app lets you enter the amount in crypto or its fiat equivalent, and a "Max" button fills in your full available balance. If you're sending the full balance of a native token (ETH, BNB, MATIC), leave enough to cover the network fee before you tap Max.

Network fee. The fee goes to validators or miners who include your transaction in a block. The Tangem app offers three preset levels: Slow, Market, and Fast, plus a custom option with real-time estimates. Tangem itself charges no fee beyond the blockchain network fee. A lower fee during high network congestion means your transaction waits longer in the mempool, the pool of valid but unconfirmed transactions, because validators prioritize higher-fee transactions when block space is limited. For routine transfers, Market is fine. If you need fast confirmation, pick Fast.

Once you've reviewed all four inputs, approve the transaction. If you're using a Tangem hardware wallet (card or ring), a physical tap of the card to your phone is required at this step: the secure element on the card signs the transaction offline, and the app broadcasts the signed data to the network. The private key never leaves the chip.

That approval step is where the details become final. The network receives the signed transaction only after you approve it, so treat the last screen as a checkpoint. Read the recipient address, network, amount, and fee together rather than checking each at a different time. If anything looks unfamiliar, back out and verify the recipient's details before you sign. It is easier to pause in the app than to trace a transfer after it reaches the network.

After you send, read the transaction status

Once broadcast, your transaction gets a TXID (transaction identifier). You can find it in the app's transaction history. Tap the entry to see the amount, fee, status, and a link to the blockchain explorer for that network. A "pending" status means the transaction reached the network and is sitting in the mempool. It's not failed. Confirmation timing depends on network congestion, the fee you set, and the chain's block time. Recipient apps or exchanges often wait for multiple confirmations before crediting the balance, so a short delay after the transaction shows as confirmed is normal.

If you need to share proof of a transfer, share the TXID, not your wallet address. Your address identifies where funds go; the TXID identifies a specific transaction.