Three Problems Wearing One Costume
Almost every crypto payment that appears to have gone wrong is one of three specific situations, and they need completely different responses. Telling them apart quickly saves a lot of anxious refreshing.
The first is a payment that has been sent but not yet confirmed. The second is a payment that arrived short of the invoiced amount. The third is one that arrived over it. This guide covers what each looks like, why it happened, and what actually resolves it, assuming you already know the basics from how to use Bitcoin to buy a fake ID.
What a Confirmation Actually Is
When you send a transaction it goes first to the mempool, a waiting area of broadcast but unrecorded transactions. It is real and visible to anyone watching the network, but it is not yet part of the permanent ledger and can in principle still be replaced.
A confirmation happens when a block containing your transaction is mined. Each subsequent block adds another. Most sellers wait for a small number before treating a payment as settled, because a single confirmation is very unlikely to be reversed but not impossible. So when an invoice still shows as unconfirmed it usually means everything is fine and the network simply has not caught up yet.
Why Confirmations Stall
Blocks arrive at roughly fixed intervals and hold a limited amount of data, so when the network is busy the mempool backs up and transactions compete on fee.
- A low fee at a busy moment can leave a transaction waiting for hours.
- Wallets that estimate fees automatically sometimes underestimate during a spike.
- A transaction spending unconfirmed change waits for its parent first.
- Different networks confirm at very different speeds by design.
Two mechanisms exist for a stuck payment. Replace-by-fee lets you rebroadcast the same transaction with a higher fee if your wallet supports it and you flagged it as replaceable. Child-pays-for-parent works by spending the output at a high fee so miners take both together. If neither is available, waiting is genuinely the only option, and an unconfirmed transaction that never confirms eventually drops out of the mempool and the funds become spendable again.
Underpayments
An underpayment is when less arrives than the invoice asked for, and the usual cause is a wallet deducting the network fee from the amount sent rather than adding it on top. You entered the invoiced figure, the wallet took its fee out of that figure, and the seller received slightly less.
The other frequent cause is a send-max button that leaves a wallet empty at whatever the balance happened to be. Either way an underpaid invoice does not usually auto-complete, because payment processors match on amount and a short payment does not match.
The fix is a top-up transaction for the difference to the same address, followed by a support message with both transaction identifiers so the two can be credited together. Do not start a second full-price order; that creates two invoices and a harder reconciliation.
Overpayments and Rate Movement
Overpayment is the more comfortable failure. A crypto invoice quotes a fixed amount of currency calculated from a rate at issue time, and that quote holds for a window, often ten to thirty minutes. Pay inside the window and the amount is what it is.
Pay after it expires and the amount you sent no longer corresponds to the invoice, which can read as an overpayment or an underpayment depending on which way the rate moved. This is why a payment sent an hour after the invoice was generated so often lands wrong even though the sender copied the figure correctly. Refresh the invoice and pay against a current quote instead.
The One Genuinely Serious Mistake
Sending the wrong asset to an address, or sending on the wrong network, is the error that is usually unrecoverable. Addresses are asset-specific and network-specific, and funds delivered to an address that was never meant to receive them are frequently gone for good.
Check three things before pressing send: the asset matches the invoice, the network matches the invoice, and the first and last several characters of the address match what you were given. Comparing the ends of the string catches clipboard-hijacking malware, which quietly swaps a copied address for the attacker's. Choosing between payment options in the first place is covered in choosing the right payment method for your order.
What to Send Support
Whatever the situation, one message with the transaction identifier, the invoice reference, the amount actually sent, and the time it was broadcast resolves things far faster than a series of status enquiries. The identifier is the decisive item because it lets anyone verify the payment independently on the public ledger. Practical guidance on that exchange is in how to contact support about your order, and the wider ordering sequence sits in the buying guide hub.
Frequently Asked Questions
Why does my payment show as unconfirmed?
Because it has been broadcast but not yet included in a mined block. It is sitting in the mempool, which is normal, and it becomes confirmed once a block containing it is found.
How long should confirmation take?
Usually minutes, but a low fee during a busy period can stretch it to hours. Blocks arrive at fixed intervals with limited capacity, so transactions effectively compete on fee when the network is congested.
What causes an underpayment?
Most often a wallet subtracting the network fee from the amount you entered instead of adding it on top. Using a send-max button is the other common cause, since it sends whatever the balance is rather than the invoiced figure.
How do I fix a short payment?
Send the difference to the same address and message support with both transaction identifiers so the payments can be credited together. Placing a second full order instead just creates two invoices to reconcile.
What if I paid after the invoice expired?
The quote was calculated from a rate at issue time and only holds for a short window, so a late payment can land over or under depending on how the rate moved. Refresh the invoice and pay against a current quote.
Can a payment sent to the wrong network be recovered?
Usually not. Addresses are specific to an asset and a network, and funds sent to an address not meant to receive them are typically unrecoverable, which is why verifying both before sending matters more than speed.