Habits from paying for things · habit 24 of 40

The address that worked last time

The last one went through. Nothing about it bounced, nothing complained, and the obvious move is to use it again. That inference is sound for almost every set of payment details a person deals with, and it does not hold for this one.

The habit

You reuse a destination that already worked rather than fetching a new one.

Why it is automatic

Consider how much of adult life runs on stable identifiers. A sort code and account number outlive several jobs. A card number lasts until the plastic expires and then only the digits at the end change. A direct debit set up once keeps working while the payee changes bank behind the scenes without telling you. Stability is not a lucky accident there, it is engineered, because instability would be expensive for everyone.

The same expectation gets reinforced by everything around payments. Saved addresses at shops. Stored details in a browser. A payee list that autocompletes after three letters. Every one of those systems is telling you that the details you used before are still the details, and every one of them is right.

There is also the plain evidence of the last time. It worked. Nothing went wrong. In most of life that is exactly the right basis for doing something again, and treating a successful past attempt as weak evidence would make a person impossible to live with.

What it actually does here

Reuse can send a transfer somewhere nothing is watching. If an address was issued for a single deposit and that deposit completed, the system may have no reason to associate anything further with it, and value arriving afterwards may not be credited to anybody. Nothing bounces, because there is nothing to bounce.

The failure is silent, which is what makes it different from the other habits in this section. There is no error message, no rejection, no red banner. From the sending side the action looks identical to the one that worked. The absence of a complaint is not confirmation, and the reflex reads absence of complaint as confirmation because everywhere else it is.

Reuse is also the one habit here that links records together on purpose. A destination used twice is a shared value across two events, and shared values are exactly what anybody analysing records looks for. Even where the two events are otherwise unconnected, the repeated string connects them.

And it cannot be taken back. Nearly every mistake a person makes in a day is recoverable: the wrong tab, the wrong file, the wrong turning, a message unsent within the grace period. This category has no grace period at all. The action completes and the state afterwards is the state, which is a property people have almost no practice with.

Two things that look identical in a text box

The reason this habit survives contact with warnings is that the two kinds of identifier are indistinguishable in the place people meet them. Both are a string of characters in a box with a copy button next to it. Both are pasted the same way. Both look, in a notes file a week later, like a detail worth keeping.

The difference is not in the string, it is in who guarantees it and for how long. A bank account number is guaranteed by an institution that would be in trouble if it silently stopped working. A deposit address usually comes with no such guarantee, and the system issuing it is under no obligation to keep any particular one meaningful once it has served its purpose.

That is why the advice on this page is a rule rather than a judgement call. There is no way to look at an address and tell which kind it is. The only reliable move is to treat every one as single use, which costs a few seconds when it was not necessary and saves the whole amount when it was.

Where the old one is still sitting

The reason people reuse is rarely a decision. It is that a copy is still lying around, and the easiest thing on the screen wins. Clipboard history keeps it. A notes app keeps it. The saved payee list keeps it and offers it after three letters. A screenshot of a confirmation keeps it in an image, which is how this habit joins hands with keeping the receipt.

That means the practical work is removal rather than resolve. An address you cannot find is an address you cannot reuse at two in the morning. Clearing the copies is a five minute job that does not depend on you being alert later, which is the only kind of fix that survives contact with real life.

What to do instead

Treat every destination as valid once, and make the old copies hard to reach rather than trusting yourself to ignore them.

1. Fetch a fresh destination for every deposit, even when the previous one completed without any problem.
2. Never save one in a payee list, a notes app or a password manager. Those tools exist to make reuse effortless and they will succeed.
3. Clear clipboard history after use if your system keeps one, since that is where the last copy usually survives.
4. Check the first and last several characters against the source page immediately before sending, on the same screen rather than from memory.
5. If you have already saved one somewhere, delete it now rather than resolving to be careful with it.
6. Do not accept a destination that arrives in a message, however plausible the sender or the explanation.

How to notice you did it anyway

Look for copies rather than for the act, because the copies are what make the act happen.

• Open your saved payee or contact list and look for anything that is a long string rather than a name.
• Search your notes, documents and chat drafts for fragments of a destination you have used before.
• Check clipboard history, if your system has one, and see how far back it goes.
• Look through screenshots and photos for images that contain a destination, including ones taken to remember it.
• If you find the same string in two places, treat that as the finding, since the duplication is the part that matters.

What readers ask about this habit