Waiting for confirmations

A transfer is not instant and is not meant to be. There is a period between sending something and it being treated as settled, and during that period nothing you do speeds it up. That is the whole mechanism in one sentence.

The frustrating part is not the wait, it is the visibility. Different interfaces show different amounts of information about progress, some show none, and none of them can tell you how long the remainder will take.

You would like a figure. So would everybody, which is exactly why so many pages publish one, and every published figure in this space is somebody generalising from their own experience.

This board has no experience to generalise from. It has never made a transfer, cannot observe one, and holds no data about any system involved. A number here would be invented, and an invented number about a wait is worse than silence, because readers use it to decide when something has gone wrong.

The tiles measure this page instead. That is not evasion, it is the same rule the board applies everywhere: when the interesting quantity is unavailable, show the available ones and say what happened.

1. Something is sent and nothing appears immediately.
2. The interface shows little or nothing about progress.
3. A reasonable amount of time passes with no change.
4. The person decides something has gone wrong.
5. They act on that decision, and the acting is where the actual damage happens.

Steps one to three are normal. Step four is a guess dressed as a conclusion. Step five is the only part with consequences, and it is the part that follows automatically once step four has happened.

• Note what you did and when, at the time, in a form you will still have later.
• Wait considerably longer than feels reasonable before treating anything as a problem.
• Do not repeat anything. Repetition during an unclear period is how one situation becomes two.
• Do not go looking for a different route while a transfer is outstanding. That combination produces the worst outcomes in the whole process.

It is worth being clear about what kind of claim this is. The board is not saying waits are usually short, or that yours will resolve. It has no basis for either.

It is saying something structural: during a period where you cannot observe progress, acting is more likely to make things worse than better, because every available action creates a second situation rather than resolving the first. That argument does not need data, only the observation that the information is unavailable.

That is the general shape of every recommendation in this section. Where a figure would be needed, the board gives none. Where the reasoning holds without a figure, it gives the reasoning.

There is one action worth taking at the start of a wait, and it takes under a minute. Write down what you did, roughly when, and what you saw. Not for anybody else, and not as evidence. For yourself, later, when the details have gone.

The reason is that waits erode memory in a specific way. After a few hours the sequence blurs, and the version you reconstruct is the version that fits your current mood, which by then is worried. People end up confidently misremembering the order of steps, which is exactly the thing that makes an unclear situation harder to sort out.

A note made at the time is immune to that. It also has a second effect that is worth more than the record itself: writing it down converts an anxious open loop into something with a shape, and that alone takes some of the pull towards acting out of the situation.

How long should a confirmation take?

Unknown here. No figure is published on this site because none was measured and a made up one would be used as though it were real.

Does anything speed it up?

Nothing you can do from a browser. Waiting is not a strategy, it is the situation.