There is a point in AI adoption where curiosity turns into discomfort, and that point is money. Most people are fine letting an AI explain things, summarize documents or suggest decisions. Suggest letting it actually spend money and you see the faces change. Fair enough, because traditional payment systems were never designed for non human actors.
Meanwhile the market is moving in exactly that direction. Agents inside experiences like AI Mode in Search, Gemini or ChatGPT are starting to place real orders: buying products, rebooking travel, renewing software and managing subscriptions. Whether AI will be allowed to spend money is pretty much settled by now. What's left to decide is how we build the rails, so that when it spends, it stays inside clear boundaries you can audit.
Payment infrastructure assumes a person on the other end, someone who owns a card, confirms intent and carries legal responsibility. Large language models break every one of those assumptions. They don't own money, they don't have intent in the human sense and you can't hold them accountable. And yet they keep showing up in places where economic action can't be avoided.
The commerce side is getting sorted out. Google's Universal Commerce Protocol (UCP) makes the order itself machine readable and agent friendly, so an LLM can reason about line items, totals and terms before it commits (Under the Hood: Universal Commerce Protocol). On the app side, OpenAI's Agentic Commerce and the Agentic Commerce Protocol (ACP) describe how ChatGPT agents discover purchasable actions, handle checkout flows and keep users informed while they buy.
That leaves the payments layer. Agentic Pay is about letting agents move money within those commerce protocols, without handing them a blank check.
With Agentic Pay, the AI gets delegated authority, which is a very different thing from access to money. A human or an organization sets the rules: what the agent may buy, how much it may spend, under which conditions and for how long. The agent works strictly inside that mandate. Payments stop being a hidden risk and become an explicit capability with boundaries around it.
Two simple cases that business leaders can map onto their own workflows:
- A procurement agent may reorder specific SKUs from approved vendors when stock drops below a threshold. It has a monthly limit, logs every purchase and escalates anything outside the contract price.
- A travel agent that rebooks a flight when a delay exceeds two hours, but only within policy, only for preapproved employees, and only if the cost delta is under 200 USD.
Neither agent can spend freely. Each one carries out a narrow mandate, with guardrails anyone can inspect.
The big players come at Agentic Pay from different directions. Google starts from governance with its Agent Payments Protocol, usually called AP2, and the core idea there is traceability. Every action an agent takes has to trace back to a delegation granted by a real entity. Limits are enforced by design (a convention or a polite request wouldn't cut it), and observability is built in. Put that together with UCP and you get a stack where the commerce flow and the payment authorization are both explicit, signed and provable end to end.
Stripe and OpenAI lean toward execution with the Agentic Commerce Protocol, ACP. Their approach plugs straight into how LLMs already reason and plan. The model finds a purchasable action, checks the constraints, asks for approval when it needs to and completes the transaction without falling back to checkout flows built for humans, which is exactly the pattern the Agentic Commerce guides describe.
So both camps solve the same problem from opposite sides, one starting from control and the other from flow. Agentic Pay sits where they meet. I'd describe it as the discipline of designing delegated payment rights that plug cleanly into these new commerce protocols.
Once payments are agent native, LLMs move from systems that talk about work to systems that do it. Procurement agents optimize spend all the time. Travel agents rebook the moment conditions change. Finance agents handle recurring obligations without anyone sending reminders or chasing follow ups. And ecommerce agents go from "here are some sneakers you might like" to "I have selected the best option under your budget and policy and placed the order using your delegated payment instrument." Once money is involved, reasoning comes with responsibility.
“The future of online ordering is that it should feel as streamlined as a McDonald’s drive‑through: clear choices, fast confirmation, and no surprises. Only this time, your agents are the ones in the driver’s seat.”
Len Debets
For a business, the first gain is speed with control, since routine purchases go faster and the approval boundaries stay where they are. You also get cost discipline, because your policies become executable code instead of a PDF with guidelines that nobody opens. Audits get easier when every action is attributable, logged and reviewable. And the same rules can govern thousands of micro decisions without adding headcount.
Mistakes now cost actual money. Incentives matter, and a security failure stops being a theoretical exercise. That's why every serious Agentic Pay design is built around limits, reversibility and auditability. Giving an agent autonomy without control would simply be negligent, however clever it looks on a slide.
Agentic Pay is uncomfortable because it forces you to make trust explicit. I also think it's inevitable. Once intelligence can reason, plan and act within defined boundaries, organizations will stop sending everything through a human by default. What I care about now is who designs the rules it spends under.
At Blits.ai we work with large banks and financial institutions, and we partner with one of the major global credit card networks, to design and implement Agentic Pay architectures that meet real world regulatory, risk and governance requirements.
Updated on 12 October 2026.
