Signal · Agentic payments
AI agents are getting ways to pay. Only you know if the booking is real.
Between 29 April and 12 May 2026, AWS, Stripe, Adyen and the Machine Payments Protocol group turned agent payments into building blocks, some still in preview or draft. Our read: none of it says if your 19:00 table is free.
Published Updated
29 April to 12 May 2026
Four releases turned agent payments into building blocks
In two weeks, four separate moves treated paying as something an agent simply does: for tools, content and data. Some are still in preview or draft.
Stripe · 29 April 2026
Agent commerce in one payment stack
At Sessions 2026 Stripe broadened agent access through its dashboard, added Google AI Mode and the Gemini app as routes to discovery and checkout, and introduced Link agent wallets and Machine Payments Protocol support.
Adyen · 6 May 2026
Adyen joined the x402 Foundation
In its first-quarter update Adyen said it joined the foundation behind x402, an open way for software to pay over the web, to help set standards tied to agentic commerce.
AWS · 7 May 2026
Payments built into an agent platform, in preview
Amazon Bedrock AgentCore Payments launched in preview with x402 support, Coinbase and Stripe Privy wallets and spending limits per session. AWS calls micropayments the first step towards wider buying. Don’t assume a preview equals a production-grade way for customers to buy.
Machine Payments Protocol · 12 May 2026
Draft rules for paid tool calls
Two linked Internet-Drafts give the web’s “402 Payment Required” a clear meaning and define how an AI tool call can be paid for over MCP, a common way assistants use tools.
Our read: this settles who may pay and how money moves. It doesn’t settle whether the thing being paid for can be delivered.
Who does what
Paying is being solved. Keeping the promise isn’t.
Now public payment infrastructure
- Managed agent payments inside a major cloud platform (AWS)
- Agent wallets and machine payments in one payment provider (Stripe)
- Web payment rules, including paid tool calls, in draft standards (Machine Payments Protocol)
- Open payment standards backed by a major provider (Adyen and x402)
Still up to the business
- Whether the table, seat, appointment or parking bay is free at the moment of booking
- Cancellation, deposit, late-arrival, change and refund rules that can be read before money moves
- Whether you can take this particular booking now, not just in general
- Confirmations, fulfilment and disputes that hold up outside pilots
September 2026
Three moves in September, and none is a customer buying
They’re easy to hear as one story about agents shopping. They sit at three different layers, and only one is on the business side: the back office, not the till.
The plumbing
A payment library got more careful
- What it isn’t
- Adoption, transaction volume or any business doing anything.
On 15 September 2026 the maintainers of the x402 Python SDK, the ready-made code for one payment protocol, released version 2.23.0 with safer retries, longer time limits and spending caps applied everywhere. Version 2.24.0 followed on 22 September 2026.
Software paying software
More than 20 million tiny agent payments, by t54’s count
- What it isn’t
- Purchases from businesses. It’s t54’s own figure, not an independently audited one.
On 1 September 2026, in an AWS blog article written by AWS and t54 staff, t54 said its x402-secure service had processed more than 20 million AI-agent-initiated transactions since launch, each between $0.001 and $0.01. The example: an agent buying market data from a paid API. Why it matters to a café: it shows agents already pay on their own, but for data, not for a table.
The business’s back office
Assistants can handle refunds and disputes
- What it isn’t
- A shopper buying from a business. Checkout.com’s plan for a “native payment layer for merchant agents” is a stated intention, not a product.
On 1 September 2026 Checkout.com described an MCP server through which a business’s own assistant can check payment status, manage payment links and run refunds, disputes and voids. About a week later IXOPAY announced an Agentic Suite for merchants.
The detail behind each layer
x402 2.23.0: during settlement, when the money actually lands, the code reuses a check it already made; permanent setup errors are caught at start-up while temporary timeouts can be retried; waits for the facilitator (the service that checks and executes a payment) and for paid tool calls were lengthened and capped; route validation was hardened against a disguised web address; and the developer’s spending cap now reaches every payment method the library supports.
t54’s founder describes the transactions as “the kind of fast, small call for data or an API that no person could review in real time”, and the article says they happen “without a human approving a single one”. The nearest local-business comparison is the automatic data top-up on a card machine: constant, unapproved, and not a customer buying a table.
Checkout.com: a refund returns money already paid, a dispute is a customer’s challenge to a charge, and a void cancels a payment authorised but not yet collected. The assistant’s permissions mirror the business’s Checkout.com Dashboard account, in test and live.
IXOPAY’s Agentic Suite has three parts: a Payment Agent, Universal Tokens that carry agent identity, customer consent and purchase intent with the payment credential, and an MCP Server for approved AI assistants. The announcement dates itself 8 September 2026 in its header and 9 September 2026 in its dateline; we report both. A quote from Tilopay, a partner, says its merchants “can start growing with agentic transactions today”: a partner statement in the vendor’s own announcement, not independent evidence.
IXOPAY’s product page adds that initial protocol support begins with Visa’s Trusted Agent Protocol (TAP), on a foundation it describes as protocol-agnostic: a starting point, not a commitment to one network.
October 2026
October: tighter payment accounting, still no sale
Sources checked on 5 October 2026. Each item keeps its own source date.
Packaged release
- mppx 0.13.1, released 2 October 2026. The TypeScript library for the Machine Payments Protocol now reserves streamed charges in one step, releases or expires reservations that go unused, and stops reporting a new payment when a request reuses existing access. These are accounting controls in one library, not evidence that any local business made a sale.
Merged, not yet released
- x402, merged 5 October 2026: “authorise now, capture later” support for EVM networks (blockchains that work like Ethereum) in the Go server and facilitator code, where a Go client already existed. It’s merged code, not a packaged Go release. The project’s own feature table doesn’t list Python support for it, and an authorisation held for later isn’t a merchant’s reservation or booking.
These sources describe two open-source projects and their code. They don’t show an integration with Obenan, a merchant deployment, a booking or a customer sale.
Sources checked 1 November 2026
Agents pay within a limit, and the payment code gets stricter
Two developments from 20 and 21 October 2026, checked on 1 November 2026. Both are for developers whose agents pay for digital services.
Early access for developers
- Mastercard Agent Pay for Machines, 20 October 2026. After pilots with named partners including Cloudflare, Coinbase and Hype, Mastercard opened early access for developers, with APIs, tools and documentation. A business gives an agent a job and a spending limit. When a paid digital service answers “402 Payment Required”, the agent signs a voucher, a promise to pay within that limit, and the service checks it before delivering.
Packaged release
- mppx 0.15.0, released 21 October 2026, follows the 0.13.1 release covered above. This library for the Machine Payments Protocol now rejects replayed payment claims that cross an expiry time, needs a matching configured realm before it accepts standalone credentials, and keeps a successful charge receipt when a payment challenge expires during settlement. Releases in between tightened how spending and deposits are bounded, and settle the largest voucher at or below what was actually spent. Two later releases, on 28 and 29 October, include breaking changes and aren’t covered here.
What it means for you: agent payments are getting limits, checks and receipts. These are early access and open-source tools for digital services. No customer sale or local booking is shown, and none of it tells an agent whether your table, slot or seat is free.
The announcement and the release notes:
What to do now
Four things that stay your job
For bookings, appointments, classes, tickets, parking and other local services.
Make free places checkable
Keep tables, slots, seats or capacity in a system that shows them as they are now, so they can be checked before anyone commits.
Write your rules down
Cancellation, deposits, late arrival, changes and refunds, in clear, consistent terms that can be read before money moves.
Confirm only what you can keep
Make every confirmation match what you can actually honour at that moment.
Don’t count releases as customers
A new library version, a vendor’s own transaction count or a launch announcement isn’t evidence that customers are booking through agents.
Keep reading
From paying to a promise you can keep
The committability ladder sets out where each of these steps sits, and why they are separate.
Getting your business facts ready for AI agents
Write to Obenan if you want to talk it through, or see how we approach merchant infrastructure.
Sources
Where this comes from
Built from public sources only. The May releases are read together; the September and October items are kept apart, each number credited to whoever reported it. Obenan isn’t a payment service provider, acquirer, checkout, tokenisation service, agent wallet or settlement network, and has no integration, pilot or partnership with AWS Bedrock AgentCore Payments, Stripe, Coinbase, Privy, Adyen, the x402 Foundation, the Machine Payments Protocol, OpenAI, Visa, Mastercard, American Express, the Universal Commerce Protocol, the Agentic Commerce Protocol, AP2 or any payment network or developer program. No private partner names, meeting details or confidential material are used.
01AWS Published Checked
Agents that transact: Introducing Amazon Bedrock AgentCore Payments, built with Coinbase and StripeAgentCore Payments in preview: paid resources and tools, wallets and per-session spending limits.
02Stripe Published Checked
Stripe builds out the economic infrastructure for AI with 288 launches at Sessions 2026Agent distribution, agent wallets and machine payments in one Stripe stack.
03paymentauth.org Published Checked
Payment Authentication Scheme: JSON-RPC and MCP Transport (draft-payment-transport-mcp-00)How paid tool calls, resource reads and prompt retrievals are expressed over MCP, as an Internet-Draft.
04paymentauth.org Published Checked
The "Payment" HTTP Authentication Scheme (draft-httpauth-payment-00)A structured meaning for “402 Payment Required”, as an Internet-Draft.
05Adyen Published Checked
Adyen publishes Q1 2026 Business UpdateAdyen joining the x402 Foundation for open web payment standards.
06Stripe Published Checked
Everything we announced at Sessions 2026The Sessions 2026 details: Link agent wallets, Machine Payments Protocol support and dashboard access for agents.
07x402 maintainers (GitHub) Published Checked
x402 Python SDK Changelog — 2.23.0The maintainers’ notes for 2.23.0; the same file already lists 2.24.0, dated 22 September 2026. About library code, not merchants.
08AWS Published Checked
How t54 built a trust layer with Amazon Bedrock AgentCore paymentsThe origin of t54’s transaction count, reported by t54 in an article by AWS and t54 staff. Not an audit, and not merchant commerce.
09Checkout.com Published Checked
Building trusted AI infrastructure with the Checkout.com MCPBack-office payment operations through an MCP server, and the stated intention to build a native payment layer.
10IXOPAY Checked
IXOPAY Launches Agentic Suite to Help Merchants Support Agentic Commerce and Automate Payment WorkflowsThe Agentic Suite launch and the Tilopay partner quote. The page dates itself 8 September 2026 in its header and 9 September 2026 in its dateline, so no single publication day is shown.
11IXOPAY Checked
Payment Agent: Get Started with Agentic CommerceThe product page naming TAP as the initial protocol. Last modified 8 September 2026.
12mppx maintainers (GitHub) Published Checked
mppx@0.13.1 release notes (GitHub)The 0.13.1 packaged release and its accounting changes for streamed payments.
13x402 maintainers (GitHub) Published Checked
x402 commit cb0ec5b: EVM auth capture for the Go server and facilitator SDKs (GitHub)Authorise-and-capture support merged for the Go server and facilitator, filed under unreleased changes.
14Mastercard Published Checked
What happens when AI agents start paying each other? Watch Mastercard Agent Pay for Machines in actionEarly access for developers after end-to-end pilots: spending limits, 402 Payment Required and signed vouchers for digital services.
15mppx maintainers (GitHub) Published Checked
mppx@0.15.0 release notes (GitHub)Replay, realm and settlement-receipt fixes in the 0.15.0 packaged release.
16mppx maintainers (GitHub) Published Checked
mppx releases (GitHub)The release list from 0.13.1 to 0.17.0, including the spending, deposit and voucher settlement changes in between.