Agentic payments: what merchants should know in 2026
Agentic payments are transactions initiated by AI agents on a customer's behalf. In 2026 the idea moved from research papers to product launches - here is what actually shipped, what the protocols do, and what a merchant should (and shouldn't) do about it yet.
What changed in 2026
Agentic payments stopped being a thought experiment this year. Adyen announced an agentic commerce suite in June 2026; Stripe has been shipping agentic tooling into its platform; and x402 - the HTTP-native payment protocol built on the long-dormant 402 status code - moved under Linux Foundation stewardship. When the largest payment companies in the world ship product and a neutral foundation takes custody of a protocol, the theme has left the lab.
The premise is simple to state: software agents, acting on instructions from a customer, find products, compare options, and complete purchases - including payment - without the customer clicking through a checkout. The engineering question is how a merchant's systems tell a legitimate, authorised agent from a scraper with a stolen card.
The protocol stack, in plain language
Three layers are emerging, and they answer three different questions.
Checkout protocols (ACP, UCP) answer "how does an agent buy something?" They give agents a machine-readable way to discover products, prices and purchase flows, instead of screen-scraping HTML meant for humans.
Authorisation (AP2) answers "was this agent allowed to do that?" AP2 carries verifiable mandates - cryptographic proof that a customer authorised an agent to spend, within limits, for a purpose. This is the layer that matters most for disputes: "my AI bought this without asking" is the chargeback category nobody wants to pioneer.
Settlement (x402) answers "how does money actually move between machines?" x402 puts payment negotiation directly into HTTP - a server can respond to a request with "402 Payment Required" plus terms, and an agent can pay and retry programmatically.
What merchants should do now
The honest answer for most merchants: prepare, don't build. Three practical steps cost little and age well. First, keep your product data clean and machine-readable - structured data, accurate stock and pricing in your feeds; agents buy from catalogues they can parse. Second, keep strong customer authentication current - delegation frameworks build on the same foundations as 3-D Secure 2. Third, ask your payment provider what they are building - an agent-ready checkout is a provider capability, not something each merchant should engineer alone.
That third point is where we show our hand: LekkaPay is building agent-ready checkout, mandate verification and protocol interoperability, honestly badged as in development, and we participate in the DAIAA Agentic Commerce working group. If you want to be early, join the waitlist - and if you want a healthy dose of scepticism with your roadmap, the FAQ on that page includes "is this hype?", answered candidly.
Last updated:
