The Problem Nobody Saw Coming

Here's something wild to think about: the software agents that are quietly reshaping how we shop, book, and transact online can't open a bank account. Not because they're broke. Because they don't exist as legal entities. Banks need identity verification — a name, an address, a human being on the other end of the paperwork. An AI agent can't provide any of that.

And that's not a minor inconvenience. That's a fundamental wall.

Richard Widmann, Google Cloud's global head of Web3 strategy, put it plainly at the Consensus conference in Miami Beach: most products are still built for humans, not agents. The friction isn't technical. It's structural. Traditional banking was never designed for software that acts autonomously on someone else's behalf.

Crypto wallets, though? Those are generated from private keys alone. No identity check required. No branch visit, no notarized forms. That's why the conversation at Consensus kept circling back to blockchain — not because it's trendy, but because it's genuinely the only payment infrastructure that doesn't require a legal person on one end of the transaction.

Google's Quiet Infrastructure Play

Google didn't just show up to Consensus to talk. They've been building.

In late April, Google donated something called the Agent Payments Protocol — AP2, now at version 0.2 — to the FIDO Alliance, the same standards body behind the authentication technology you use every time you log in without a password. That's a meaningful institutional home for something this foundational.

What AP2 actually does is introduce what it calls "Human Not Present" payments. Think about what that means in practice: an AI agent, acting on instructions you've already approved, can execute a purchase on your behalf the moment conditions are met — like snapping up limited concert tickets the second they drop. You set the parameters, the agent acts, no additional approval needed in the moment.

Around 60 organizations have already signed on. PayPal, Mastercard, American Express, Coinbase, UnionPay International — that's not a pilot program, that's the beginning of an industry standard forming in real time. Mastercard even contributed a companion framework, co-developed with Google, called Verifiable Intent. It creates a tamper-proof record of everything a user has approved an agent to do. Think of it as a paper trail built for machines.

PayPal Sees Agents as Its Next Commerce Channel

May Zabaneh, PayPal's senior vice president and general manager of crypto, was equally direct at Consensus. AI agents aren't a future consideration for PayPal — they're already the next commerce channel.

Her vehicle of choice for this agent-driven economy is PYUSD, PayPal's own stablecoin. The pitch makes sense: stablecoins are programmable, they settle fast, and they don't need a bank in the middle. For software executing thousands of micro-transactions autonomously, that matters enormously.

Here's the number that really sticks, though. Zabaneh noted that while 95% of merchants already encounter AI agent traffic — meaning agents are already browsing, comparing, and attempting to buy — only 20% have adapted their product catalogs to be machine-readable. The agents are already at the door. Most merchants just haven't unlocked it yet.

A Standards Race With Real Stakes

AP2 isn't the only protocol trying to become the backbone of agent commerce. OpenAI and Stripe launched the Agentic Commerce Protocol, which is already powering purchases inside ChatGPT and onboarding over one million Shopify merchants. Visa has its own agent-focused payment framework. Mastercard has one too.

Everyone is racing to define the infrastructure, and honestly, that makes sense when you look at the numbers. McKinsey estimates that AI agents could mediate up to $5 trillion in global consumer commerce by 2030. Five trillion dollars. Whoever builds the rails that agents run on has an extraordinary amount of leverage over what comes next.

And the parallel development of things like x402 — an open protocol that repurposes HTTP's "Payment Required" status code as a machine-native payment layer, now under Linux Foundation governance — shows that this isn't just big corporate positioning. The open-source world is building the same infrastructure from a different angle.