Minimum deposit by coin: why small sends don't credit

By the ChainDeposit Research Desk · Updated 23 June 2026

A deposit that's below an operator's minimum can silently fail to credit — and if it's small enough, the network fee to send it back can be worth more than the deposit itself. Knowing the minimum before you send avoids the whole problem.

Why minimums exist

Operators set minimums because crediting and later moving tiny amounts costs them network fees. On expensive chains the minimum is higher; on cheap chains it can be very low. A sub-minimum send isn't "lost" on-chain — it reached the wallet — but it may not auto-credit, and recovering it can be uneconomical.

A worked example shows how this plays out. Say an operator sets a $5 minimum and you send $3. The transfer confirms on-chain and reaches the operator's deposit address, so a block explorer marks it successful. But the crediting system checks the amount against the threshold, sees it falls short, and quietly skips it. Nothing in your balance moves. There is usually no automatic refund and no on-screen error either, which is why a sub-minimum send feels like it vanished. The money sits in the operator's wallet, and getting it back means opening a ticket and asking a human to act.

Typical minimum ranges by coin

Exact minimums are set per operator, so treat the figures below as broad ranges, not fixed numbers. The underlying logic is consistent: cheaper networks allow smaller minimums because the operator's own cost to handle the deposit is lower.

The figures move with each operator's policy and the network you pick, so the table is a starting point, not a promise. For the exact minimum on the coin and network you're using, check the operator's own figures: we publish per-operator minimums on each operator's deposit guide as they're confirmed, and most operators also state it on their help centre (a help. support page) and on the deposit screen before you send.

The minimum-vs-fee double trap

A small deposit on an expensive network faces two problems that compound. The first is obvious: the network fee can swallow much of what you send, so a $4 deposit that costs $3 in gas leaves little behind. The second is sneakier. If fees are deducted along the way and you misjudge how much actually arrives, an amount you thought cleared the minimum can land just under it — and then nothing credits at all. You pay the high fee and still miss the threshold.

This is mostly an Ethereum-mainnet problem, because ERC-20 gas rises with demand and can reach several dollars when the network is busy. The fix is to route small deposits over a low-fee network the operator supports, such as Tron, Solana or Litecoin, where the fee is a fraction of a cent and won't erode the amount below the minimum. Our cheapest network to deposit guide breaks down the fee tiers chain by chain.

Why a tiny deposit can become unspendable "dust"

The trap isn't only the operator's rule — it's arithmetic on the chain itself. Returning or moving a deposit costs a network fee, charged in the chain's native asset regardless of how much you sent. When the stranded amount is worth less than the fee needed to move it, the funds are economically stuck even though they still exist on-chain; this leftover is called dust. On Ethereum mainnet a $2 deposit can cost more than $2 to send back, so nobody moves it. On Tron or Solana, where a transfer costs a fraction of a cent, the same tiny amount is cheap to return. You can see the exact amount and the fee paid on a block explorer — Etherscan for Ethereum, Tronscan for Tron — which tells you whether a return is even worth requesting.

Rounding adds a smaller version of the same problem. Operators usually credit balances to a fixed number of decimal places, so the last few units of a tiny deposit can be rounded off rather than shown. Partial credits work the same way: if a deposit lands right at the edge of the minimum, some operators credit the part that clears the threshold and treat the remainder as dust. None of this is a glitch. It's the predictable result of sending an amount small enough that fees and rounding matter, which is the strongest argument for depositing comfortably above the minimum rather than right at it.

Per-operator minimums

The exact minimum deposit per coin and operator is being verified and will appear on each operator deposit guide as it's confirmed — we publish only checked figures. If a small deposit hasn't credited, open a ticket with your transaction hash.

What to do if a small deposit didn't credit

Before assuming the minimum is the cause, rule out the more common reasons a deposit goes missing, because each has a different fix. Work through them in order.

1. Give it time to confirm. A deposit that's still waiting for block confirmations hasn't failed — it just isn't final yet. Our stuck-deposit guide explains how many confirmations each chain needs and how long that takes.
2. Check the network matched. Sending USDT over a network the operator doesn't credit is a wrong-network problem, not a minimum one, and it's resolved differently.
3. Check for a missing memo or tag. Chains like XRP, XLM and some exchange-style addresses need a memo or destination tag; leave it off and the deposit can sit unassigned regardless of size.
4. Compare the arrived amount to the minimum. Open the transaction on the chain's explorer, note the exact amount credited to the address, and check it against the operator's stated minimum for that coin and network. If you sent less, a missing credit is expected.
5. Contact support with the TXID. Send the operator your transaction hash and ask whether they can credit or return the deposit. Their help centre — usually a help. support page — lists the contact route and often the minimum itself, so quote both the figure and the hash to speed things up.

Avoid minimum headaches

Operators with low minimums and cheap-network support make small deposits painless.

FAQ

Related: cheapest network to deposit · deposit still pending? · check if a small deposit will credit.