Usually feels like
Minutes
You stay at the keyboard and it finishes there.
A chain works to its own schedule and the first settlement commonly lands at the keyboard, though nothing in the mechanism promises that it will.
The wait, in plain words
You broadcast a payment and the deposit page has not changed. No acknowledgement, no pending line, sometimes not even a hint that anything is on its way. This is the point at which people send the payment again, and it is the worst possible moment to do it.
Broadcasting puts a transaction in front of the network. It does not put it into the chain. Those are separate events, and the gap between them belongs to nobody you can write to.
It sits in the minutes band because a first settlement usually lands while you are still at the keyboard. Waiting for a deposit to be treated as final is a longer wait with a card of its own, and that one starts only where this one ends.
Underneath, while nothing moves
A broadcast transaction goes into a holding area that every node on the network keeps for itself. It is a waiting room rather than a queue with an attendant at the door. Nothing in it is ordered by the time it arrived.
What orders it is what it pays. Whoever assembles the next block chooses from that holding area, and chooses by value to them. When the room is crowded, transactions offering more are taken first and the rest wait for a quieter stretch. A payment that would have settled at once on a slow evening can sit for a long time when everybody is transacting at once.
Before any of that, the payment has to travel. A broadcast starts at whichever nodes your wallet is speaking to and spreads outward from there, node telling node, until most of the network is holding a copy. Until that has happened, only part of the network can even consider your transaction, and the part doing the assembling may not be in it yet.
The chain produces blocks on a schedule of its own, driven by a process with no interface on it. It does not know a market is waiting for you. It does not know you have a tab open. Your urgency has no input into it, and neither has the market.
That is why support cannot help here and why the deposit page has nothing useful to show. The market watches the chain. It can credit what the network has settled, and it can do nothing with what the network has not. A page that stayed blank throughout is a page telling you the truth about where the payment is.
Behaving, and not behaving
The distinction that matters is between a payment waiting its turn and a payment that is never going to be taken as it stands.
A payment waiting its turn
It is visible to the network. Anything that reads the chain can find it sitting there unconfirmed.
The fee it carries is in the range everything around it is paying, so it gets picked up as soon as the crowd thins out.
A payment that will not settle as sent
It was never broadcast at all, because the wallet was offline or the send never left the application it was composed in.
It carries a fee far below what the network is taking, so it can sit indefinitely without ever being wrong, or it went somewhere the market is not watching.
The last one is the expensive case, and it is not a wait at all. A payment sent to the wrong destination is not slow, it is gone, and that has a card in a band with no ceiling in it.
The rest of the time the honest answer is that nobody can make this faster. What is left to you is not making it worse, which is a smaller job than it sounds and is done by sitting still. It is also the only part of this wait that anyone at your end has any influence over.
Safe to do meanwhile
There is one genuinely useful thing to keep hold of and one genuinely harmful thing to avoid doing.
- Keep the transaction identifierIt is the only handle you have on this payment if it ever has to be discussed.
- Confirm the payment actually left the walletA send that never reached the network looks exactly like a slow one from where you are sitting.
- Do not send it a second timeA second payment does not replace the first. It joins it in the same room, and both of them may settle.
- Read what happens after the first settlementThe next wait is longer and it is the one that ends with a balance you can spend.
What makes it longer
Everything below is either a decision made before you pressed send or a crowd you had no way of seeing.
- A fee chosen while the network was quiet and spent into a network that is no longer quiet.
- A wallet that composed the payment and never got it onto the network.
- Paying out of a service that holds and batches, which stacks another wait in front of this one before the network sees anything.
- Sending again, which spends more and settles nothing sooner.
- Watching the deposit page instead of the chain, which tells you less and makes the same wait feel twice as long.
What this card is not. This card does not tell you what fee to pay, which asset to use, or how long any particular network takes to settle anything.
Questions people ask about this wait
Can the market make a payment settle faster?
No. The market is an observer here. It watches the chain and credits what it finds there. Nothing it does reaches the network on your behalf, and support has the same view of it that you do.
Does sending the payment again help?
It does not. The second payment enters the same holding area under the same rules as the first, and if both are taken you have paid twice for one deposit.