Yesterday, when I saw Decrypt’s November 4 update explaining x402, my first reaction wasn’t excitement—I tightened my grip on my wallet a little.
First, let’s be clear about what this is, so we don’t get carried away by the idea that “AI can pay for things on its own.” x402 is an open payment standard launched by Coinbase in May 2025, with partners including Circle, Anthropic, AWS, and NEAR. The idea is straightforward: put to use HTTP’s 402 “Payment Required” status code, which the internet has had for ages but never really used. When a server receives a request, it responds with a 402 specifying the price, which currency it accepts, and which wallet to pay; the client signs and sends the request again, and once the on-chain settlement provider verifies it, the service is delivered. Most payments are in USDC and mainly go through the Base chain. In April 2026, the Linux Foundation announced the formation of the x402 Foundation, which officially began operating in July. Its membership grew from 40 to 57 organizations, including Visa, Mastercard, and Google. Source: Decrypt’s November 4 explainer.
It sounds seamless, but the data in the same analysis brought me back down to earth. As of November 1, x402 had processed over 196 million transactions and settled more than $42 million, according to agenteconomy.to, cited by Fireblocks. But in October 2026 alone, it handled only about 5.1 million transactions and roughly $274,000. What’s more, over half of all lifetime transactions came from a wave of automated scripts minting PING in the final two months of 2025. In other words, the protocol works and the member list looks impressive, but the volume of real, everyday machine payments is still tiny. The activity may not necessarily reflect demand.
My take is that the real risk with machine payments has never been whether the technology works. It’s about “who’s in control.” It’s fine for AI to pay a few cents for an API call on my behalf. But if it can renew a subscription for a month without my approval, switch to a currency and chain I haven’t checked, or keep paying after the price changes, then what I’m giving up isn’t time—it’s control. The protocol offers efficiency, but I still need to keep hold of the budget, limits, and approval authority.
So I’ve set three rules for AI payments. First, I have to approve anything before money moves. Reminders can be automated, but reconciliation and authorization can’t be outsourced. Second, I set a limit for every subscription and top it up as needed before renewal—I don’t preload a large amount onto the card. Third, I reconcile once a month: which service, currency, and chain each payment was for. If anything changes, I stop and ask why.
That’s how I use PayAll now: I use PayAll Agent to check my subscriptions and due dates with a simple prompt. It lays out clearly what needs renewing and what I should cancel. When it’s time to renew, I top up my U Card as needed and reconcile the payment afterward. The Agent helps me keep track of payments and sends reminders, but I still tap to approve the actual payment myself—I don’t plan to hand that step over to anything “fully automated.”
AI being able to pay isn’t a bad thing. But I need to set the rules first, so the efficiency works for me. Otherwise, every click I save could turn into a line on my bill at the end of the month asking, “When did this get charged?”