The same pattern is playing out in API payments right now. Traditional API billing (Stripe subscriptions, API keys, monthly invoices) is the "bank branch" model: it works, but it requires human setup, identity verification, and ongoing account management for every provider.

HTTP 402 "Payment Required" has been a reserved status code since 1997, unused for nearly 30 years. Now protocols like x402 and L402 are finally implementing it: a server returns a 402 with a payment instruction, the client pays (stablecoins or Lightning), and gets access. No signup, no API key, no billing relationship.

This isn't replacing Stripe any more than ATMs replaced tellers. Most API providers will keep using traditional billing. But there's a new category of consumer that can't use the old model at all: autonomous software agents. An AI agent can't fill out a signup form, pass KYC, or manage a credit card. Per-request micropayments over 402 let agents acquire API access without any human in the loop.

The parallel to the article is exact. ATMs automated a task within the existing branch paradigm. Mobile banking eliminated the need for the branch. Similarly, better developer portals automated API key management within the existing billing paradigm. Machine-to-machine micropayments eliminate the need for the billing account entirely.