Received Less Than You Withdrew? Where the Missing Amount Went

"The network fee will be deducted from this amount, and the recipient will receive the remaining balance." That line sits under the Withdrawal amount option in Binance's English guide to withdrawing crypto (checked October 2026), and it's the first place to look when less arrives than you withdrew: if you picked that option, you typed the total, the fee came out of it, and the other side got what was left. Binance's fee page describes that fee as a flat charge on every withdrawal, paid "to cover the transaction costs of moving the cryptocurrency out of their Binance account."

So if the gap equals the network fee the withdrawal page showed when you submitted, nothing went missing. A bigger gap means looking further along. Some token contracts keep a slice every time the token moves. And the receiving platform credits deposits by its own rules. Each stage leaves a number behind; put the three side by side and the gap points to one of them.

Reconcile it stage by stage

Write down three numbers
Stage one: was the fee added on top, or taken out?
Stage two: the token contract took its own cut
Stage three: the receiver credits by its own rules

Write down three numbers

No tools needed. Three numbers, from three places:

The number	Where to find it	What it tells you
1. Network fee and final amount at submission	Once you enter an amount, the withdrawal page shows the network fee and the final amount the recipient will get; if you didn't screenshot it, open this withdrawal in your history	What the sending platform meant to deliver
2. What landed at the receiving address	Search the transaction ID in the explorer for that chain; for a token, read the token transfer section	What the chain actually delivered
3. What the receiver credited	The other exchange's deposit history, or the transfer as it shows in their wallet	What the recipient ended up with

If 1 and 2 disagree, the gap opened on chain. If 2 and 3 disagree, it opened at the receiver. If the final amount in 1 was already lower than you remember, you've found it in stage one and can stop there. Where the TxID lives, and which explorer line shows what the address really received, is covered in the token section of the TxID guide.

Stage one: was the fee added on top, or taken out?

Binance's guide says you "can choose between 2 receivable amount options," and the difference matters more than its one-line treatment suggests:

Receive amount. "Enter the amount you want the recipient to receive." The network fee "will be added to the total withdrawal amount," so the recipient gets exactly what you typed and the fee comes out of your balance on top.
Withdrawal amount. "Enter the total withdrawal amount." The fee is deducted from it, and the recipient gets the remainder.

Type 100 under each option and the two arrivals differ by exactly one network fee. (100 is just an easy number; it isn't tied to any coin.) When we've promised someone a round figure, Receive amount is the one we'd pick: they get the agreed number, the fee stays on our side, and nobody has to send a small top-up afterwards.

We don't quote a fee figure here, on purpose. Binance's fee page says withdrawal rates "are determined by the blockchain network and can fluctuate without notice due to factors such as network congestion," and sends you to each withdrawal page for current numbers. So the figure to reconcile against is the network fee shown at the moment you hit submit, not whatever the page says when you look again three days later. Switch networks and that fee changes too. Picking one before you send is covered in the network guide; why Ethereum costs more is explained in Why ETH / ERC20 withdrawals cost so much.

Stage two: the token contract took its own cut

Stage one checks out, yet less landed at the address. Look at the token itself. MetaMask has a help article for exactly this situation (a successful transaction where the amount received is far lower than the amount confirmed), and its first suggestion is to "check if the token you received is subject to a 'tax'." Its examples: "a 10% tax applies on SAFEMOON transactions, and OKTA transactions are subject to an 8% tax." Those are MetaMask's examples as we read them in October 2026, and MetaMask points you to the token issuer's documentation for details. Our own reading, not MetaMask's: the issuer sets the rate, so it may change, and the issuer's docs are the place to check before you send.

No exchange takes this slice. The contract does, at the moment the token moves. The token transfer section in the explorer shows what actually reached the receiving address; subtract that from what you sent and there's your gap. We wouldn't use a taxed token to pay anyone, and before sending one we hadn't heard of, we'd skim the issuer's docs first. It's quicker than reconciling afterwards.

Stage three: the receiver credits by its own rules

The first two numbers agree. The chain delivered the full amount. The account on the other side still shows less. That puts it with the receiver.

If the receiver is Binance, the fee page is plain about it: "Binance does not charge deposit fees." For any other exchange or wallet service, we haven't gone through their rules one by one, so their own deposit page is where the answer is. The sending platform can't help at this stage, because it can't see inside another platform's books; the receiver's support team can. Send them what the table at the end of the completed-but-not-received guide lists: TxID, network, token contract, receiving address and memo, amount and time. Add your three numbers. "It came in short" on its own tends to cost a few extra rounds of email.

Two situations look like a short arrival and aren't. If nothing arrived at all, that's the guide just linked. If the coins went out on the wrong network or to the wrong address, start with wrong network: are the funds safe? and sent to the wrong address.

ChainTunnel Editorial

"ChainTunnel Editorial" is ChainTunnel's site byline on deposit and withdrawal guides, not a verifiable team of real people, and we don't invent credentials. The two amount options and the fee wording here were checked against Binance's English withdrawal guide and fee page, and the token-tax section against MetaMask's help center; no account was used and no transfer was made to write this. Spot an error and email [email protected]; we'll fix it and date the change.