WAITING
Almost everyone using one of these for the first time gets ten minutes of quiet panic here. The gap is normal. This explains where the wait comes from, how to check progress without asking anybody, and the one case that is genuinely a problem.
First establish whether the operator broadcast a transaction; a successful kiosk screen is not the same as an on-chain confirmation.
You pressed confirm, the screen said complete, the receipt printed. You open your wallet and the balance is zero.
The feeling is familiar. The answer first: this is normal.
After the machine broadcasts, the bitcoin network still has to include your transaction in a block before your wallet shows anything. Blocks come roughly every ten minutes on average, so a wait of fifteen minutes to an hour is ordinary, and longer when the network is busy or the fee attached was low.
"The machine says complete" and "the coins are in my wallet" are two separate events. The first only means it was sent.
A few seconds, usually. Some operators do internal processing first rather than broadcasting immediately, in which case the receipt may not carry a transaction ID yet.
Transactions wait in a queue — the mempool — and miners select from it, largely by fee rate. Bitcoin produces a block about every ten minutes on average, and being included gives you your first confirmation. Most of the wait sits here.
Wallets differ on what counts as arrived. Some show a balance on the first confirmation; others hold until three or six. Each additional one is roughly another block, so a cautious wallet can mean an hour before funds are spendable. That's the wallet protecting you, not a fault.
Take the transaction ID from the receipt, paste it into any public block explorer, and you can see exactly where it stands.
mempool.space works fine. What you'll see:
No transaction ID on the receipt? Search your own wallet address instead — every incoming transaction to it will be listed. Lots of people don't realise this works.
Worth noting in passing: all of this is public. Anyone with your address can see its history, which is why the anonymity people assume is there is weaker than they think.
A confirmation count measures how hard the transaction would be to undo. Each block stacked on top means more work to rewrite, and after a few it becomes practically impossible.
There's no central authority declaring a transfer final. Instead the network keeps adding blocks, and your transaction sits under all of them. In principle, enormous computing power could rebuild a longer chain excluding it — but the cost of that rises steeply with each confirmation, so waiting is really waiting for "too expensive for anyone to bother".
At the amounts involved in an ATM purchase, one or two confirmations already passed that point long ago. A wallet asking for three or six is being conservative by default, not signalling a risk.
Another common confusion. The wallet has seen an incoming transaction so it displays a balance, but hasn't reached its own confirmation threshold so it won't let you spend it. It unlocks by itself; nothing to do.
Miners pick by fee rate. A generous fee likely means the next block; a thin one waits for a quiet period. You don't control this at a machine — the operator set it. It does explain why the same machine is noticeably slower at busy times, and current congestion is visible on any explorer.
| Time passed | State | Action |
|---|---|---|
| 0 to 1 hour | Visible, unconfirmed | Normal, wait |
| Several hours | Still unconfirmed, visible | Probably a low fee, keep waiting |
| Over a day | Still unconfirmed | Contact the operator with the ID |
| Any time | Not found on any explorer | Contact the operator promptly |
The last row is the only one that needs action rather than patience. Not found means it never reached the network, which is a machine-side problem.
Prime time to be targeted
There are services online offering to "accelerate" or "unfreeze" transactions, asking for a payment upfront or for your recovery phrase. Anything asking for a recovery phrase is theft, without exception — hand it over and the wallet is emptied. For a genuinely delayed transaction there are only two options: wait, or talk to the operator.
Yes. The machine showing complete only means it broadcast the transaction to the network. The coins still need to be included in a block before your wallet shows them, and blocks arrive roughly every ten minutes on average, so a wait of fifteen minutes to an hour is ordinary and longer when the network is congested.
Take the transaction ID from your receipt and search it on any public block explorer to see whether it is queued or confirmed and how many confirmations it has. If the receipt has no transaction ID, search your own wallet address instead and every incoming transaction to it will be listed.
It depends on your wallet. Some display a balance after one confirmation while others wait for three or six before releasing funds for spending. Each additional confirmation is roughly another block, about ten minutes, so reaching fully spendable can take about an hour. That is the wallet being cautious rather than a sign of a problem.
No. The methods for accelerating a transaction require control of the sending side, and the machine sent it rather than you. Low-fee transactions generally clear once the network is less busy. If more than a day passes with no confirmation, or the transaction cannot be found on any explorer at all, contact the operator with your receipt and transaction ID.
Bitcoin's roughly ten-minute block interval is a protocol design target; actual gaps between blocks vary randomly. Different wallets require different numbers of confirmations before showing or releasing funds.