An internet code left empty for twenty-five years has become the way programs pay each other

The HTTP code 402, “payment required”, was defined in 1999 and went unused for 26 years. On October 27, 2025 Bitcoin closed at $114,108, −0.4% against the previous day.

How it works, in four steps

The payment moves from one wallet to another in digital dollars, with no bank in the middle, and it takes a few seconds. There are $298 billion of those digital dollars in circulation today, $71.62 billion of them in the coin used almost every time for this round trip. Those are our own numbers, recomputed from the public source rather than copied from a press release.

Behind the standard are the largest American exchange and one of the companies that keep half the internet’s traffic running. That matters more than the technology. It means whoever writes a service doesn’t need to understand any of this. They lean on an intermediary, which collects in crypto and pays them in ordinary dollars. The complexity stays hidden, as it has in every payment system that went on to succeed.

Why it was really needed

As long as there are five services and one person sets them up once, the problem doesn’t exist. It appears when the program has to work out for itself which data it needs, and finds out only while it’s working. At that point every new service is a new registration, and the program stops to wait for somebody.

Taking the person out of that spot is the whole story. The technology underneath matters less, because a similar system could be built without it, and anyone who says otherwise is selling something. What the public infrastructure adds is that anyone can take part without asking permission, and that the payments stay verifiable from outside.

And how you know who you’re dealing with

The proposal circulating alongside the payment standard sets out exactly these three public registers: one for identity, one for reputation, one for checks done by third parties. The interesting part is that the two pieces fit together, because every payment that goes through becomes a line in the reputation of whoever received it.

Together they make the equivalent of a bank account and an ID card for software. One says how much you can spend, the other says who you are and how you’ve behaved so far. Without the second, the first alone wasn’t enough to move real money.

The proposal sets out three public registers: identity, which answers “is it really you”; reputation, which answers “how did it go with everyone else” and is fed by the payments that went through; validation, which answers “who checked it” by way of independent verifiers.

The part to be wary of, and the price

Meanwhile dozens of tokens have appeared claiming to serve this purpose, some worth hundreds of millions within a few days. For the vast majority there’s no reason a payment between two programs should go through them rather than a digital dollar. That’s the question to ask each of them before any other.

The serious risk is more concrete: giving a program a wallet with money in it. If it makes a mistake, the money is spent; if somebody hijacks it, the money is stolen. It needs spending caps, double signatures and alarms, and that is the least developed part of all. Bitcoin, meanwhile, closed at $114,108, practically where it opened. When the plumbing gets built, the price usually doesn’t notice.

Put bluntly: where a person with a credit card used to be needed, nobody is needed anymore, and that’s the whole story, more than the public infrastructure the payments run on.