Visa and OpenAI are building the rails for agents to spend money, and Mastercard is racing them

Agents can plan a purchase. They couldn't actually pay for one. That gap is closing fast, and the card networks are sprinting to own the layer that fills it.

Visa partnered with OpenAI to let AI agents make payments directly across OpenAI's platform. The same week, Mastercard launched "Agent Pay for Machines" (AP4M) on June 10, an open protocol for agents to pay each other at machine speed, including micropayments worth fractions of a cent. Agent credentials and spending permissions live on public chains (Polygon, Solana, Base), and the launch partner list is serious: Coinbase, Adyen, Stripe, and Cloudflare, 31 in all.

Two networks, same week, same idea. When that happens, it's not coincidence, it's a land grab over a standard nobody owns yet. The card networks watched the agent ecosystem grow without a settlement layer and decided they'd rather define it than be disintermediated by it.

This is the piece that's been missing under usage-based and outcome-based pricing. You can meter an agent all you want, but somebody has to authenticate it, authorize a spend limit, and settle the transaction. That's commerce infrastructure, and it's hard. Sub-cent micropayments specifically unlock agent-to-agent economics: one agent pays another for a tool call, a data lookup, a compute slice. That's a different world than "human buys SaaS seat."

I'm genuinely unsure how the blockchain-credential part shakes out. Putting spending permissions on public chains is either the clean answer to agent identity or a privacy and key-management mess waiting to happen. Probably both, depending on implementation.

What to do: don't build your own agent payment-auth scheme. This is going to standardize, and you want to be on the rails the networks bless, not a bespoke thing you maintain forever. If you're building anything where an agent transacts, watch AP4M's protocol spec and Visa's API surface as they open up. The interesting design question for builders is spending limits and revocation: how do you cap what a delegated agent can spend, and kill its authority instantly when it misbehaves? Get that boundary right and agent commerce is tractable. Get it wrong and you've handed an autonomous process your credit card.