How to Send Crypto Safely: A Checklist Before You Confirm

A safe crypto transfer starts before you paste an address. You need to know who should receive the funds, which asset and network they accept, what the receiving service requires, and what your wallet will actually authorize. A familiar token symbol or a green confirmation button answers only part of that checklist.

Use the following process when sending through a wallet or exchange you already control. UniBankWallet.com is an educational site; it does not execute transfers. If you are still choosing a setup, explore our wallet guides before attempting a first transaction.

1. Confirm the purpose and recipient independently

Start with a sentence: who am I paying, what am I paying for, and how did I verify the request? This is particularly useful for an unexpected invoice, an urgent request from a friend, or instructions claiming you must move funds to protect them.

Verify changed payment details through a channel you already trust. Replying to the same message that supplied the new address does not provide an independent check. A familiar name, logo, or account photograph is not enough to establish who controls the destination.

If the transfer is to your own exchange account, open the service directly and retrieve current deposit instructions while signed in. If it is to another person, ask them to confirm the exact asset, network, and address through your established communication method.

2. Match both the asset and the network

The same asset name can appear on several networks. A receiving service may support only some combinations. Confirm the network at both ends, and distinguish the native asset from wrapped or bridged versions. Do not choose a network solely because its displayed fee is lower.

An address that looks valid does not prove that the receiving service supports the asset on that network. Check the current deposit screen and documentation for the precise combination. Coinbase's guidance on assets supported across multiple networks illustrates why send and receive settings must be checked together.

If an instruction introduces a bridge or swap, stop treating it as a simple transfer. Those actions add contracts, routes, and other conditions to evaluate. Our Ethereum wallet guide explains why selecting a wallet and selecting a network are separate decisions.

3. Get the address from its original source

Copy the destination from the recipient's verified instructions or the current deposit screen. Avoid copying an address from an unsolicited transfer or recent activity entry. Address poisoning scams insert lookalike addresses into transaction history, hoping you will reuse the wrong one.

Compare the entire destination, including the middle characters, against the trusted source. A matching beginning and ending are insufficient. If your wallet shows only a shortened address, expand it before approving. Review the destination again on a hardware wallet's trusted display when that is part of your setup.

Scanning a QR code helps with data entry but does not establish that the code belongs to the intended recipient. Check what the wallet decoded. If the address changes unexpectedly, pause and investigate instead of assuming that the wallet corrected a harmless formatting issue.

4. Check deposit conditions before choosing an amount

Some services require a memo or destination tag in addition to an address. Others impose minimum deposits, address expiration rules, or confirmation requirements. Follow the current instructions for the specific deposit, and never assume another asset uses the same requirements.

Make sure a planned test amount will exceed any applicable minimum after deductions. An amount below a platform's crediting threshold may not appear as a usable balance even if a blockchain explorer shows the transfer. That is a poor test because the result is difficult to interpret.

Also check whether the receiving service is processing deposits normally. If a deposit is paused or the required information is unclear, waiting for clarification is more useful than sending a small amount into an uncertain process. Keep a private record of the instructions you verified.

5. Review units, fees, and the total debit

Read the amount in the asset's own units as well as any approximate currency conversion. Check the decimal point carefully. A displayed fiat estimate can change with market prices and is not a guarantee of the recipient's eventual value.

Distinguish the network fee from a service's withdrawal fee or other charge. Determine whether a fee is added to your debit or deducted from the amount delivered. Review both the amount leaving your account and the amount the recipient should receive.

Many transfers require the network's native token for fees. Solana network fees, for example, are paid in SOL, though an application can arrange a separate fee payer. Sponsored transactions and wallet-specific fee options can change what you personally need to hold. Read the actual payment arrangement instead of assuming every wallet works identically.

6. Use a test transfer for the right question

What the test establishes

A small transfer can help test whether a particular address, network, asset, and deposit process work together. Wait until the intended recipient confirms usable receipt, not merely that your wallet shows a submission message. For an exchange deposit, check the credited balance in your authenticated account.

What it cannot establish

A successful test does not prove that the recipient is honest, that a smart contract is safe, or that your device is uncompromised. A scammer can accept a small payment and encourage a larger one. A later transaction can also contain different details.

Repeat the review for the main amount. If the address, network, asset, or deposit conditions change, the earlier test no longer checks the same situation. Balance the benefit against the additional fee and complexity; a test is one checkpoint, not a universal guarantee.

7. Inspect what you are authorizing

The final prompt should match your intended action. Confirm the selected account, recipient, asset, amount, network, and charges. Where the wallet supplies a readable transaction summary, compare it with the request that brought you there.

A token approval grants permission for a contract to spend specified tokens. That is different from directly sending a chosen amount to a recipient. A signature can also have consequences beyond a simple login, including permissions that another party may use later. The absence of an immediate network fee does not establish that signing is harmless.

If an ordinary payment unexpectedly requests broad spending permission or an unexplained signature, do not approve it merely to continue. Ask why it is needed through verified support. Review our guide to crypto wallet scam warning signs if the explanation relies on pressure or secrecy.

8. Confirm the result and keep a record

Record the transaction identifier, network, amount, date, and destination. Use the correct network's explorer to distinguish submission, inclusion, and the relevant confirmation or finality status. A transaction record and a service's account credit are related but separate checkpoints.

If the result is unclear, investigate before sending again. Repeatedly pressing send can create additional transfers. For a provider deposit issue, contact that provider through its verified support channel with the transaction details, excluding passwords and recovery secrets.

Confirmed transfers generally cannot be reversed by a wallet support agent. Wrong-network recovery depends on the exact custody and network situation and may be unavailable. Do not pay an unsolicited recovery service simply because it claims to recognize your transaction.

A hypothetical two-stage transfer

Imagine Omar is moving tokens to his own exchange account. He confirms the exact supported network, checks the current deposit address, and discovers a minimum deposit. He chooses a test amount that satisfies the requirement and waits for his account to show the credit.

Before the main transfer, he repeats the destination and fee review. An unexpected signature request appears, so he cancels and checks which application initiated it. The earlier successful deposit gave him evidence about receipt; it did not authorize a different action or replace that final review.

Make confirmation a deliberate decision

Each checkpoint answers a different question: identity, compatibility, destination, amount, authorization, and receipt. Work through them in that order, and pause whenever an answer changes. The goal is a transfer you can explain before approving and verify afterward, with no reliance on a promise that someone can undo a mistake.