Payments for software agents emerge

A software agent can already book a flight, compare prices, and call an application programming interface. The missing step was money: most checkouts still expect a human to log in, pick a plan, type a card, and click buy. (stripe.com) Stripe and Tempo launched the Machine Payments Protocol on March 18, 2026 to move payment into the same request-and-response loop that software already uses for data. A server can answer a request with the web’s old “402 Payment Required” code, tell the agent what to pay, and then deliver the result after proof of payment comes back. (stripe.com) (docs.tempo.xyz) That turns payment into something closer to a toll booth than a checkout page. Tempo’s documentation shows one mode for one-time charges and another mode for continuous usage, where an agent opens a payment session once and then sends off-chain vouchers for later requests. (docs.tempo.xyz) (tempo.xyz) Stripe says businesses can accept Machine Payments Protocol transactions through its PaymentIntents system, and it says those payments can be settled with stablecoins or with ordinary methods like cards and buy now, pay later through Shared Payment Tokens. Tempo says its chain was built for this with about 500 millisecond finality, sub-cent fees, and fee sponsorship so the client can hold stablecoins without also managing gas. (stripe.com) (docs.tempo.xyz) Visa is attacking a different part of the same problem. On April 8, 2026, Visa announced Intelligent Commerce Connect, which it describes as a network-, protocol-, and token-vault-agnostic on-ramp that lets merchants, agent builders, and payment enablers connect through a single integration on the Visa Acceptance Platform. (corporate.visa.com) (investor.visa.com) Visa says that single integration can handle payment initiation, tokenization, spend controls, and authentication for agent-led purchases. It also says the product is in pilot with partners including Aldar, Amazon Web Services, Diddo, Highnote, Mesh, Payabli, and Sumvin, with broader rollout planned later in 2026. (corporate.visa.com) These two efforts fit together more than they compete. The Agentic Commerce Protocol from OpenAI and Stripe handles how a merchant and an agent exchange catalog data, checkout state, and a delegated payment request, while Machine Payments Protocol handles machine-to-machine payment over plain Hypertext Transfer Protocol calls, and Visa is trying to make card acceptance work across whichever agent protocol wins traffic. (openai.com) (docs.stripe.com) (stripe.com) (corporate.visa.com) The hard part is no longer “can software send money.” The hard part is proving which person or business authorized the software, what limits were attached to that authority, and whether a merchant can reverse, refund, or dispute a transaction when the buyer was a bot following instructions. (developers.openai.com) (norwest.com) OpenAI’s delegated payment spec shows one answer for consumer shopping: the token is single-use, capped by a maximum amount, and expires, while the merchant still processes the payment on its own systems and can accept or decline the order. That is a strong fit for “buy this one item for up to $50,” but it is a different shape from an agent making thousands of tiny machine purchases per hour. (developers.openai.com 1) (developers.openai.com 2) So the news here is not that autonomous shopping suddenly arrived this week. The news is that two layers of plumbing are appearing at once: one layer for agents to negotiate and complete purchases, and another layer for payment networks to recognize that the “customer” at the point of sale may be software acting under tightly scoped human permission. (openai.com) (stripe.com) (corporate.visa.com)