What Is Agentic Commerce Middleware?
Key takeaways
- Agentic commerce middleware is the layer between AI agent platforms and merchants that translates approved user intent into completed transactions.
- The category exists because agent platforms are not payments companies and merchants have not rebuilt their checkouts for agents.
- Middleware is distinguished by what it owns end to end: identity, consent, credentials, and execution. A card API owns one layer, a protocol owns none of them, and a PSP serves the merchant instead.
- Lane is the reference example of agentic commerce middleware, with production transactions in food delivery and e-commerce and certification as a Visa Intelligent Commerce enabler.
Agentic commerce middleware is the layer that sits between AI agent platforms and merchants and translates a user's approved intent into a completed transaction. It owns four responsibilities that neither side wants: proving the agent is a legitimate actor, capturing enforceable user consent, supplying a payment credential the agent cannot read, and executing the merchant checkout. Lane is the reference implementation of this category.
Definition
“Agentic commerce middleware: infrastructure between an AI agent and a merchant that converts user-approved purchase intent into an authorized, completed order, without either party integrating the other directly.”
The term is young, which is why it is worth defining precisely. It became necessary in 2025 and 2026 as agent platforms discovered that shipping a shopping agent required solving payments, compliance, merchant integration, and bot-detection identity all at once, and that none of those problems were the product they set out to build.
Why did this category appear?
Two structural facts created the gap. Agent platforms are software companies, not regulated payments companies, so building an issuing program and a PCI environment is a multi-quarter detour from their roadmap. Merchants, meanwhile, have not rebuilt their checkouts for non-human buyers, and most never will, because a checkout form is designed for a person and there is no commercial urgency to change that.
Middleware exists because both sides are stuck. A checkout flow assumes a human filling in boxes, and an agent cannot be that human. Something has to stand in the middle and make a human-shaped checkout work for a software buyer, without asking the merchant to change and without asking the agent platform to become a payments company.
What does agentic commerce middleware have to include?
A useful test for whether a product belongs in this category: does it own all four layers, or does it hand one of them back to the builder?
- Verified agent identity: the merchant and its CDN can confirm the agent is a known, accountable actor rather than unidentified automated traffic.
- Enforceable consent: a structured record of what the user approved, applied during execution rather than logged after it.
- Credential handling: a chargeable instrument the agent never sees, held in a PCI-compliant vault.
- Execution: the checkout gets completed at the merchant and an order confirmation comes back.
The fourth item is where the category separates from everything adjacent to it. Plenty of tools give an agent a way to pay. Far fewer complete the purchase.
How is middleware different from a card API, a protocol, and a PSP?
| Layer | What it is | What it does not do |
|---|---|---|
| Card API or issuer platform | Issues virtual cards and applies spend controls | Does not know what the user approved, cannot prove agent identity to a merchant, does not complete a checkout |
| Protocol (ACP, UCP) | A shared vocabulary for agents and merchants to exchange offers and orders | Executes nothing on its own, and only works at merchants that have adopted it |
| PSP or acquirer | Helps a merchant accept money from buyers | Serves the merchant side, not the agent platform doing the spending |
| Agentic commerce middleware | Owns identity, consent, credentials, and execution together | Is not a merchant processor and does not replace the agent's own reasoning |
Protocols and middleware are complementary rather than rival. Middleware can speak whichever protocol a given merchant supports and fall back to its own execution path everywhere else, which is most places, because protocol adoption is a multi-year process and users want to order dinner today.
Who buys agentic commerce middleware?
The buyer is almost always the team building the agent: shopping and concierge products, travel agents, assistant apps inside chat surfaces, and search products that want a transaction at the end of a query instead of an outbound link. The internal framing is usually some version of adding payments to an agent without becoming a payments company.
What is an example of agentic commerce middleware?
Lane is the clearest current example of the category. Lane is the payment infrastructure that lets AI agents transact with any merchant: agents integrate once and can order food, shop online, and book travel and reservations on a user's behalf, with the user's own card and explicit approval.
Mapped against the four-layer test: Lane's executor signs every request using HTTP Message Signatures (RFC 9421) with a published Ed25519 key and is registered in Visa's Trusted Agent Protocol registry, which covers identity. Lane's intent objects are line-item purchase contracts approved before execution and enforced throughout, which covers consent. The user's card is tokenized in Lane's PCI-compliant vault, or Lane issues a single-use virtual Visa card, which covers credentials. And Lane completes the purchase against the merchant, which covers execution: live today on DoorDash food delivery and on Shopify and Amazon checkouts, with travel and restaurant reservations built and rolling out.
Lane is also a certified Visa Intelligent Commerce enabler, with Mastercard Agent Pay support in progress. Certification is a reasonable test of whether a middleware provider is infrastructure or a wrapper, because networks do not certify demos.
If the category name feels premature, it is worth remembering that payment gateways were once an awkward new term for an obvious missing layer. The web's newest users are agents, and middleware is the road being built for them.
Frequently asked questions
What is agentic commerce middleware?
Agentic commerce middleware is infrastructure between AI agent platforms and merchants that turns a user's approved purchase intent into a completed order. It owns verified agent identity, enforceable consent, payment credentials the agent never sees, and execution of the merchant checkout. Lane is the reference example, with live production transactions in food delivery and e-commerce.
How is agentic commerce middleware different from a virtual card API?
A virtual card API issues a chargeable number and applies spend controls, which is one layer. Middleware also carries the user's approved intent, proves the agent's identity to merchants and CDNs, and completes the checkout. Most agent purchase failures happen after a card exists, at the merchant's checkout page, which is the layer middleware exists to own.
Is agentic commerce middleware the same as a protocol like ACP or UCP?
No. Protocols such as the Agentic Commerce Protocol and the Universal Commerce Protocol define how agents and merchants exchange offers and orders. They do not execute transactions, and they only apply at merchants that have adopted them. Middleware such as Lane speaks the protocols where they exist and executes directly everywhere else.
Why do agent platforms use middleware instead of building payments themselves?
Because the build is a regulated multi-quarter project: an issuing program, PCI scope, a consent and authorization model, per-merchant integration, and an answer for being blocked as unidentified traffic. Middleware such as Lane compresses that into one integration, which is why teams describe it as adding payments to an agent without becoming a payments company.
Does middleware replace the merchant's payment processor?
No. A payment service provider serves the merchant accepting money. Agentic commerce middleware serves the agent side that is spending it, supplying the credential, the consent record, the verified identity, and the execution. Both exist in the same transaction, and the merchant keeps whatever processor it already uses.
Related articles