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 27 October 2025 Bitcoin closed at $114,108, −0.4% against the previous day.

How it works, in four steps

The payment doesn’t go through a bank: it is a digital dollar moving from one wallet to another, and it takes a few seconds. There are 308 billion of those digital dollars in circulation today, of which 72.87 billion in the coin used almost always for this particular round trip — those are our own numbers, recomputed from the public source and not copied out of a press release.

Behind the standard are the largest American exchange and one of the companies that keep half the internet’s traffic on its feet, and that counts for more than the technology: it means whoever writes a service has to understand none of this. They lean on an intermediary, which collects in crypto and hands them ordinary dollars. The complication gets hidden away, as it was in every payment system that went on to work.

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 exists when the program has to work out on its own which data it needs, and find that out while it is 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 of the news. It isn’t the underlying technology — a similar system can be built without it, and anyone saying otherwise is selling something. What the public infrastructure adds is that anybody can take part in it without asking permission from anyone, 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 lock together — every payment that goes through becomes a line in the reputation of whoever received it.

Put together they come to the equivalent of a bank account and an identity document for software: one says how much you can spend, the other says who you are and how you have behaved so far. As long as the second was missing, the first on its own wasn’t enough to move real money through it.

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 squint at, and the price

Meanwhile dozens of tokens have turned up claiming to serve this purpose, some with hundreds of millions in market value within a few days. For the vast majority there is no reason a payment between two programs should go through them rather than through a digital dollar, and that is the question to put to each of them before any other.

The serious risk, though, is a different and more concrete one: 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. Spending ceilings, double signatures and alarms are needed, and that part is the least built of all. Bitcoin, in the middle of all this, closed at $114,108, practically where it opened: the days when the plumbing gets built are not the days when the price moves.

Put bluntly: the news isn’t that payments run over a public infrastructure, it is that the spot where a person with a credit card used to be needed now needs nobody at all.