Miami BeachAI agents cannot open bank accounts.
Know-your-customer rails were built for humans; Google Cloud and PayPal told Consensus Miami stablecoins are the only machine-readable payment layer.
Google donated its Agentic Payments Protocol to the FIDO Foundation; 120 partners including PayPal are signed on.
Sources: CoinDesk
THE KYC WALL
Every bank account in the developed world requires Know Your Customer verification — a government ID, a face, a residential address. The Bank Secrecy Act (1970) and FATF's 40 Recommendations built this regime to fight money laundering. An AI agent has none of these attributes, which is why no regulated bank can legally onboard one as an account holder.
WHY STABLECOINS FIT
A stablecoin wallet is just a cryptographic keypair. No identity, no jurisdiction, no business hours. An agent can generate one in milliseconds, hold dollar-pegged value, and settle a payment in seconds for fractions of a cent. The same properties that worry regulators — permissionless creation, instant finality — are exactly what machine-to-machine commerce requires.
THE STABLECOIN MARKET
Two issuers dominate. Tether (USDT) and Circle (USDC) together hold roughly 90% of the stablecoin float, backed mostly by US Treasury bills. The total supply has grown from near-zero in 2018 to over $200bn — Tether alone is now among the top 20 holders of US government debt, larger than Germany.
WHAT FIDO ACTUALLY IS
The FIDO Alliance is the industry consortium behind passkeys — the cryptographic replacement for passwords now built into every major browser and operating system. Its standards are royalty-free and developed openly. Donating a protocol to FIDO is the standard move when a single company wants its spec adopted as neutral infrastructure rather than a proprietary moat.
THE AGENT AUTHORIZATION PROBLEM
If an agent can spend, who is liable when it spends wrongly? Existing card networks resolve this with chargebacks — the consumer disputes, the merchant eats the loss, the bank arbitrates. Stablecoin transactions are final on settlement; there is no chargeback. Agentic commerce protocols must encode authorization scope (what, how much, for how long) into the payment itself, because the rails offer no recourse after the fact.
THE PRECEDENT
Machine-readable payments are not new. SWIFT (1973) standardized interbank messaging. ISO 20022 standardized payment data. EDI standardized supplier invoicing in the 1980s. Each replaced human-mediated workflows with deterministic rails. The pattern: when a new class of actor needs to transact at scale, the rail gets rebuilt around the actor's constraints, not retrofitted onto the old one.