Crypto deposit not credited

A deposit starts when the cashier generates an address for one specific coin on one specific network, quotes the exact amount to send, and holds that quote for the countdown shown on the page. You send from your wallet, the network confirms the transfer, and the balance moves. None of that is instant, and the middle step is where the waiting happens.

A confirmation is a block built on top of the one holding your transaction. Networks differ in how many they need, and the same count means very different waits depending on how fast the chain produces blocks. These are the counts and typical times we credit against:

Two floors apply to every deposit: ours, which is $25.00, and the network's own. The higher of the two wins, so the last column above is the number that matters to you — not whatever your wallet or your exchange calls its minimum. A transfer below it is not credited automatically and has to be traced by hand.

One pairing sits above that: USDT on Ethereum (ERC-20) needs $50.00, because that network's own minimum is higher than ours. Sending $25.00 there will not credit, and it is the most common version of this problem.

1. 1

   It has not confirmed yet

   By far the most common, and not a fault. Open your transaction in a block explorer and read the confirmation count. If it is below the number in the table above, the deposit is doing exactly what it should. Fee-sensitive chains slow down when they are busy, so a transfer sent with a low fee can sit unconfirmed for hours before it moves at all.

2. 2

   The amount landed below the floor

   The minimum is enforced on what arrives, not on what you typed. An exchange normally takes its withdrawal fee out of the amount you asked it to send, so a transfer that cleared the floor on your screen can land underneath it. Read the received amount on the explorer rather than the figure you entered at the exchange.

3. 3

   It went out on the wrong network

   The address you were given is watched on one network only. Several coins here are issued on more than one, and some of those share an address format, so the transfer succeeds on a chain nobody is watching. This case has its own guide, because the answer is different from every other one on this page.

4. 4

   The address had expired

   Deposit addresses are issued for one deposit and stop being watched once the countdown on the page runs out. A payment that lands afterwards is not gone, but it is no longer matched automatically: it becomes a manual trace, so raise it rather than waiting on it.

5. 5

   A memo or tag was left out

   Some networks identify the recipient with a memo or destination tag as well as an address. Where one is required, the deposit page shows it beside the address and the transfer cannot be matched without it. If your deposit page shows no memo field, none is needed and you can rule this one out.

Your wallet gives every transfer a transaction hash, usually labelled TXID or transaction ID. Copy it, open a block explorer for the network you sent on, and paste it in. Five things settle almost every case:

• The confirmation count. Below the number in the table above, the answer is to wait — nothing else.
• The receiving address. Compare it against the one on your deposit page character by character; checking the first five and the last five catches a bad paste.
• The chain the explorer belongs to. If the explorer that found your transaction is not the one for the network printed on your deposit page, you have a wrong-network case.
• The amount that actually arrived, rather than the amount you asked your wallet to send. Compare it against the minimum in the table.
• The time it landed. Anything that arrived after the countdown on the deposit page expired needs raising rather than waiting.

Write in once the transaction is confirmed on the right network, above the floor, and still not in your balance. Do not wait at all if you already know it went out on the wrong network, arrived under the minimum, or landed after the address expired — those three never resolve on their own.

One message with everything in it saves a day of back and forth. Include:

• The email address on your account.
• The coin and the network you sent on, exactly as your wallet or exchange named them.
• The amount, as the explorer shows it.
• The transaction hash.
• The receiving address you sent to, copied rather than retyped.
• The date and time you sent it, with your time zone.

If you send only one of those, send the hash. Without it nobody can trace anything, and every reply will be a request for it.