How to Do a Test Transaction (and When It's Worth It)
Send a small amount first, confirm it arrived, then send the rest. The cheapest insurance in crypto, and the arithmetic for when to skip it.
TL;DR
- A test transaction is a small send to confirm the address, network and receiving wallet all behave before the full amount moves.
- Blockchain transfers are final, so the test converts one large irreversible risk into one small one.
- Verify the full address at the receiving end, not the first and last four characters, and reuse the exact tested address for the real send.
- The test costs two network fees. When the total is small enough that fees dominate, skip it and rely on address books and small totals instead.
Two network fees are the entire price of knowing, before an irreversible transfer moves, that the address is right, the network is right, and the wallet at the far end actually receives. Set that against what a paste error can cost: one trader sent 1,155 wrapped bitcoin to a lookalike address in May 2024, a story this library's wrong-address guide takes apart, and no fee in the world buys that back.
So people who move serious crypto do something unglamorous first: they send a token amount, watch it arrive, and only then send the balance. The rehearsal exists so the expensive version of the story stops at the rehearsal.
When the test earns its fee
Run a test when any of these is true: the address is new to you, the amount would hurt to lose, the receiving side is an exchange deposit address, which can carry extra requirements like memos or tags, or you are sending across a bridge or to a different network than usual. A first transfer to your own new hardware wallet wants one, and so does emptying an old wallet into a new one.
Skip it when the numbers say to, because two fees on a 50-pound transfer can eat several per cent of it. The test would cost more than the risk it retires, and small totals are their own insurance.
The procedure
1. get the address from the destination, freshly. Copy it from the receiving wallet or the exchange's deposit screen now, not from an old message or a transaction from last month. Exchanges rotate deposit addresses, and clipboard history is where address-swapping malware lives.
2. choose the amount: small but visible. Enough to clear any minimum and be unmistakable on arrival, and a few pounds' worth does it. On networks with meaningful fees, bitcoin at busy times, Ethereum mainnet, weigh the fee, and on low-fee networks the test costs pennies. Fees on Ethereum's layer-2 networks dropped sharply after the Dencun upgrade of March 2024, which made testing there close to free.
3. match the network exactly. The same token often exists on several networks, and the receiving side must support the one you use. A test catches a network mismatch cheaply, but a full send does not.
4. send, then verify properly at the far end. Wait for confirmation and check the funds arrived in the destination wallet itself, not just in a block explorer. Compare the entire address, character by character, at the receiving end. Address-poisoning attacks generate lookalike addresses with matching first and last characters precisely because everyone checks only the ends.
5. send the real amount to the exact same address. Do not re-copy from anywhere: most wallets let you repeat a send to a previous recipient or save it to an address book, so use that, and the address that carried the test is verbatim the one that carries the balance.
Make the second send the sure one
The test's value is only as good as the link between rehearsal and performance. If you re-paste the address from the original source for the big send, you have restarted the risk, and defeated the point, so it comes down to a tested address, a saved recipient, the same network, done.
Exchanges add complements worth using: address whitelisting, which locks withdrawals to pre-approved addresses, and withdrawal delays on newly added ones. Those features turn the test-first habit into standing policy, which is exactly what it deserves to be.
Frequently Asked Questions
Small but unmistakable: a few pounds' worth is typical. It needs to clear any minimum deposit rules and be clearly visible on arrival. The amount is not the point; confirming the route is.
Yes, at least once, at the receiving end. Address-poisoning attacks create lookalike addresses that match the first and last few characters, targeting exactly the people who only check the ends.
No. It costs two network fees, so on small transfers the fee can outweigh the risk it removes. It earns its keep on amounts that would hurt, new addresses, exchange deposits with memo requirements, and cross-network sends.
Only what you reintroduce. Send the real amount to the saved, tested address rather than re-pasting from the original source, keep the same network, and the main send inherits the test's certainty.
Some deposits, XRP tags and various exchange deposit flows among them, need a memo or tag as well as an address. A test confirms the tag routing too: if the test lands credited to your account, the tag worked.
About the author — Dan Clarke
Dan Clarke is the author of Bitcoin: The Complete Guide and a former content lead at Binance Academy, where he wrote crypto education for readers arriving with no background in the subject. He has worked in the cryptocurrency industry since 2017. His rule for these guides: plain language first, precision where it matters, no cheerleading.