Why You Should Always Send a Small Test Amount First

Is paying one extra fee worth it?

Yes. That's this guide's entire position: before sending a large amount to any address you haven't successfully transferred to before, send a small amount first, wait for the recipient to confirm it arrived, and then send the rest. The extra fee is the best money you'll spend in that transaction. Below, we'll explain the logic, when it applies, how small "small" should be, and then take apart the two most common objections — by the end, you'll probably agree: if this site could only give you one habit, this would be it.

A test transfer verifies the entire route — not just the address

A common misunderstanding: "I'll send a test amount to make sure I copied the address right." That's part of it, but the test is checking much more than address accuracy. It verifies the complete route:

• Was the address copied correctly? Both whether you copied it accurately and whether a clipboard hijacker swapped it before you pasted;
• Is the network actually supported? You selected TRC20, but does the receiving platform or wallet actually process TRC20 deposits?
• Was the Memo filled in? For coins that require a Memo or Tag, leaving it blank means the platform receives the funds but can't assign them to the right account;
• Can the recipient receive normally? Platform maintenance, account restrictions, or wallet issues on their end are invisible to you when you're sending.

Any one of those four failure modes can result in funds that are very difficult or impossible to recover — on-chain transactions are irreversible, there's no cancel button, and no one can intercept a transaction that's already been broadcast. For a vivid picture of just how hard recovering a wrong-address transfer can be, the wrong-address guide spells it out in detail. A small test transfer turns all four question marks into a confirmed green light in one go. Once it lands, you know this specific address, network, and Memo combination works. Sending the bulk amount along the same proven path converts "gambling on it" into "repeating what already worked."

When a test transfer is non-negotiable

Not every transfer needs this step. Three situations where you should treat it as required:

• First transfer to any new address, regardless of who the recipient is — a friend, a merchant, an exchange;
• Any time you switch networks, even if the address hasn't changed. Successfully sending TRC20 last time doesn't guarantee that sending ERC20 to the same address this time will work;
• Any amount large enough that losing it would hurt, by your own definition — if losing it would ruin your day for a week, that qualifies as large.

When can you skip it? When you're sending a routine small amount to a recipient you've sent to successfully very recently, using the same address and the same network. Also worth noting: "new address" is per-address, not per-person. If a friend gets a new wallet, that's a new address, and the test applies again. If you haven't done your first-ever withdrawal yet, start with the first withdrawal guide — every step is written out there.

How small should "small" be — and how soon to send the rest

Two calibrations: the minimum floor and the timing.

The floor: stay above the receiving platform's minimum deposit amount. Exchanges set a lower threshold for deposits on each coin and network — go below it and the deposit typically doesn't get credited and isn't refunded. If your test amount is below the minimum, you haven't verified the route; you've just lost a small amount for nothing. Check the minimum on the deposit page before deciding your test amount, then go somewhat above it. The mechanics of this threshold are explained in the minimum deposit guide. Sending to a self-custody wallet has no equivalent minimum — but don't send so little that an issue would be impossible to spot.

The timing: send the bulk amount soon after confirming the test arrived. Clipboard-hijacking malware can swap your address between when you paste it the first time and when you paste it again later. This isn't theoretical — the address poisoning guide explains the mechanics. The right sequence: confirm the test arrived, copy the address directly from that successful transaction record, and send the rest immediately after. If hours or days pass between the test and the bulk send, treat it like a fresh transfer — verify the address from scratch as if it's the first time.

The two objections, examined

"It wastes money — paying a fee twice isn't worth it." Run the math. The extra fee you pay is typically a few dollars or less. What it insures is the full amount of the bulk transfer — potentially thousands. Think of it as insurance: you buy it only when you need it, and the premium is one of the lowest rates you'll find anywhere. The only transfers where "it's not worth it" is plausible are transfers so small that the test fee is proportionally large — and for those, the full amount is already small enough that a loss is survivable.

"It's too much hassle." The test transfer takes an extra two to three minutes. Filing a support ticket after a transfer to the wrong address, waiting for a manual investigation that may conclude "unrecoverable," and then accepting that outcome — takes a lot longer than three minutes. Side by side, there's no real comparison.

There's also a third attitude worth addressing: "I've skipped this dozens of times and nothing ever went wrong." That's true — and it will remain true right up until the one time it doesn't. The test transfer habit doesn't protect you from every transfer. It protects you from the one transfer you could least afford to lose. You don't know which transfer that will be until it happens.

No technical skill required. No special knowledge. Just an extra two minutes before you send the bulk. For a structured way to make sure you don't forget this step, run through the Transfer Checklist before each transfer — test transfer is a checkbox on it.