Sending Crypto Payments Without Mistakes

A blockchain transaction is a one-way write. Once it is confirmed, no one — not you, not the platform, not the payment processor — can reverse it. This is the opposite of card payments, where a dispute can claw money back weeks later. It is also why crypto deposits are non-refundable once credited; the balance they fund never expires instead.

The practical consequence: errors that would be trivial with a card are permanent with crypto. Wrong network, wrong address, missing memo, wrong amount — each has a different failure mode, and only some of them are recoverable. The sections below cover each one.

Run through this list every time, even for small amounts. It takes under a minute.

• Right coin. The invoice states a specific coin. Sending a different asset — even a similar one — to the same address will not be recognized.
• Right network. Many coins exist on multiple networks. USDT alone runs on several chains with different address formats and fees — see USDT networks explained. Send on exactly the network you selected when creating the invoice.
• Exact amount. The invoice shows a precise crypto amount. That amount must arrive — not merely be sent. More on this below.
• Address verified. Copy-paste the address, then compare at least the first and last several characters against what is shown in the dashboard. Clipboard-hijacking malware exists specifically to swap crypto addresses.
• Memo or tag included. If the invoice or exchange order shows a memo, destination tag, or comment field, it is mandatory. Omitting it can lose the funds.
• Network fee paid on top. Your wallet's fee must come out of your balance, not out of the amount being delivered. If the invoice says send 0.005, the recipient must receive 0.005.

When an invoice says "send 0.00250000 BTC", it means that amount must land at the destination address. Automatic crediting matches incoming transactions against the expected amount; a payment that arrives short may not be recognized and credited.

The most common cause of underpayment is not carelessness — it is fees deducted from the send. Two cases to watch:

• Wallet network fees. Most wallets charge the network fee on top of the amount you type, which is what you want. A few subtract it from the amount instead. Check which behavior yours uses before confirming.
• Exchange withdrawal fees. If you are paying an invoice by withdrawing from a trading platform, the platform's withdrawal fee is usually deducted from the amount you enter. Withdrawing 0.0025 BTC with a 0.0002 fee delivers 0.0023 — an underpayment. Add the withdrawal fee to the amount you request.

Invoice expects:        0.00250000 BTC to arrive
Exchange withdrawal fee: 0.00020000 BTC (deducted from send)
Amount to withdraw:      0.00270000 BTC
Amount that arrives:     0.00250000 BTC  — correct

Make the arriving amount exact.

Some blockchains route many users through a shared address and use a secondary identifier — called a memo, destination tag, or comment depending on the chain — to tell deposits apart. On those networks, the address alone is not enough.

If a memo is shown on your invoice or exchange order, your wallet has a field for it. Fill it in exactly as displayed, with no extra spaces or characters. A transaction sent to the right address with a missing or wrong memo lands in the shared address but cannot be attributed to you; recovering it ranges from slow to impossible.

After you broadcast a transaction, the network must confirm it — include it in a block, then build further blocks on top. Each additional block is one confirmation. Recipients wait for a set number of confirmations before treating a payment as final, because a transaction with zero confirmations can still fail or be replaced.

This is why your deposit does not credit the instant your wallet says "sent". The platform credits funds automatically once the required confirmations are reached; how long that takes depends on the chain — some networks confirm in seconds, others in tens of minutes, and congestion or a low fee can stretch it further. The same logic applies to the built-in exchange, where most swaps complete in 10-30 minutes end to end.

Deposit invoices are not open-ended. An invoice runs on a 2-hour countdown, and you can have at most 3 active invoices at once. The exact crypto amount is locked to that window because exchange rates move; an expired invoice's amount is no longer valid.

1. 01Create the invoice only when you are ready to pay, and send within the countdown.
2. 02If you sent the funds but the invoice expired before confirmation, or the amount arrived short, do not send again to the same address.
3. 03Find your transaction ID (hash) in your wallet or on a block explorer.
4. 04Contact the support tickets page in your dashboard with the transaction ID, the coin and network, and the amount sent. The support team can investigate late or mismatched payments.

On the exchange side, orders that fail or expire after your deposit arrived can be refunded after 2 hours, minus a 5% refund fee — another reason to get the amount and network right the first time.

For a large first-time transfer — a new wallet, a new exchange withdrawal path, a network you have not used before — split the payment. Send a small amount first, wait for it to confirm and credit, then send the remainder. You pay one extra network fee, typically a small fixed cost that varies by chain, and in exchange you verify the entire path: coin, network, address, memo, and fee behavior.

This matters most when any link in the chain is new. Once a route has worked end to end, repeating it at full size is low-risk. Until then, the test send is the cheapest insurance available.