Agentic payments: authorized purchases made by an agent

Agentic payments are the settlement layer of agentic commerce: the mechanism by which an AI agent pays for a purchase it is making for a buyer. The buyer grants a mandate, an explicit authorization that defines what the agent may buy and under what limits, and the agent settles the transaction within those bounds, without the buyer manually entering card details for each order.

This is more than a payment button inside a chat. It requires a trust framework: the agent must prove it is acting under a genuine mandate, the merchant must be confident the payment is authorized, and the rails must support agent-initiated transactions safely. That framework is what Google’s AP2, the Agent Payments Protocol, is designed to provide.

Agentic payments are one of three protocol concerns in agentic commerce. AP2 governs authorized payment, ACP governs discovery and checkout in ChatGPT, and MCP governs live context in Claude. A complete agentic transaction can touch all three, which is why being payable by agents is part of a broader multi-protocol presence.

AP2, associated with Google and Gemini, is the protocol most directly tied to agentic payments. It defines how an agent carries a verifiable authorization from the buyer to the merchant, so the merchant can distinguish a legitimate agent-initiated purchase from an unauthorized one. The mandate encodes the buyer’s intent and limits, and the agent settles within them.

For a brand, supporting AP2 means its checkout can accept payments that an agent initiates on a buyer’s behalf, with the authorization chain intact. Without it, an agent in Gemini may recommend the brand but be unable to complete the purchase, breaking the agentic transaction at the final and most valuable step.

AP2 rarely acts alone. An agent may discover and check out over ACP, pull context over MCP, and settle payment over AP2 in a single flow. SkuLift keeps the brand’s prices, policies and payable catalog consistent across all three, so the payment an agent settles always matches the offer the buyer was shown.

SkuLift coined the Agentic Commerce Platform category and treats agentic payments as inseparable from discovery and checkout. It maps the brand’s canonical catalog and price book onto AP2 alongside ACP and MCP, so when an agent in Gemini settles a payment, it settles against the same authoritative prices and policies the brand publishes everywhere else.

This consistency is what prevents the most damaging failure in agentic commerce: an agent quoting one price and the brand charging another. By driving payment from the same source of truth as discovery, SkuLift ensures the mandate the buyer authorized matches the order the merchant captures.

The platform also measures agentic outcomes end to end, from recommendation to completed payment, so a brand can see not just whether it is recommended but whether agents can and do complete the purchase. That visibility tells the brand where a payment or data gap is costing it sales.

The most valuable step in agentic commerce is the last one. An agent that recommends a brand but cannot settle the payment leaves the buyer with intent and no order. Supporting agentic payments, notably over AP2, is what turns an agent’s recommendation into revenue rather than a dead end.

Because the major assistants split across protocols, payment readiness has to be plural. A brand payable in Gemini over AP2 but not transactable in ChatGPT over ACP still loses sales. SkuLift treats payment as one facet of a multi-protocol platform, linking agentic payments to AP2, agentic checkout, the machine-readable pricing it depends on, and the hub.