The cryptography arrived before the governance did. Over the past twelve months the payments industry built a credible technical answer to a hard question: how do you prove that an autonomous software agent was genuinely authorized by a specific human to spend a specific amount at a specific merchant? That problem is largely solved, signed, and heading toward standardization. The question nobody answered is the one that lands on your desk. Inside your company, who is allowed to grant an agent spend authority, against which budget, up to what limit, and how would your controller reconstruct the decision six months later during an audit? Most enterprises cannot answer that today, and their agents are already spending money.
In September 2025, Google published the Agent Payments Protocol (AP2), an open, vendor-neutral, payment-method-agnostic specification backed by more than 60 partners including Mastercard, PayPal, Coinbase, American Express, and Salesforce. AP2 was designed to be rail-agnostic from the start. Cards, bank transfers, and stablecoins are all treated as first-class settlement options rather than bolt-ons.
The important milestone came on April 28, 2026, when the FIDO Alliance announced that AP2, along with Mastercard's Verifiable Intent (co-developed with Google), had been contributed to it. That contribution is what moves this from a single vendor's initiative toward something that behaves like an industry standard, with the governance and conformance machinery that implies.
Then the card networks moved. On June 10, 2026, at its Payments Forum, Visa announced a partnership with OpenAI to support Visa payments inside agentic commerce experiences, and the same day Mastercard launched Agent Pay for Machines, aimed at software-to-software payments with no human in the loop at transaction time. Visa also operates the Trusted Agent Protocol and Mastercard operates Agent Pay. Both are network-specific programs on card rails, and the two networks chair the FIDO working group developing AP2, which points toward layering rather than competition.
Outside the card rails, in August 2026 OSL Group launched AgentPay, a stablecoin payment system that lets AI agents pay on behalf of developers, with the API handling routing, transaction signing, and settlement. Its design target is intent-based, high-frequency, small-dollar payments, which is exactly the shape of machine-to-machine spend that card interchange handles poorly. A week earlier, on July 30, 2026, Google gave its Gemini Spark agent the ability to operate desktop Chrome in the US using the user's logged-in accounts and saved passwords, handing control back to the user at the payment step.
Read that last item carefully, because it is the one that should worry a CISO. An agent driving a real browser session with saved passwords is not using a mandate at all. It is using your employee's credential delegation by default, with no cryptographic record of what was authorized.
AP2's core construct is the signed Mandate. The current v0.2 specification defines two types, the Checkout Mandate and the Payment Mandate, secured as SD-JWT verifiable digital credentials. When an agent acts with no human present, each comes in two stages: an open Mandate the user signs in advance, and a closed Mandate for the specific transaction. The original 2025 release used the names Intent, Cart, and Payment Mandate, and many vendor explainers still do. They are worth understanding plainly, because the distinctions map directly onto controls you already run.
The genuinely new thing here is not the payment. Cards and tokenization have existed for decades. The new thing is a signed, non-repudiable record of authorization that travels with the transaction. Historically, "who approved this purchase" lived in a workflow tool, a purchase order, or somebody's inbox, disconnected from the payment rail. AP2 makes the authorization itself a first-class, verifiable artifact, which means for the first time a controller can, in principle, cryptographically tie a charge back to the specific grant of authority that permitted it. That is a large improvement over the status quo, and it is precisely why the internal governance gap is now the binding constraint rather than the technology.
AP2's signed Mandates (Checkout and Payment, secured as verifiable digital credentials) let a merchant, payment network, and auditor verify that a specific agent was authorized by a specific principal for a specific transaction. What no standard supplies is the internal answer: which role inside your company may grant an agent spend authority, at what single-transaction and cumulative limit, against which GL account, over which approved vendors, and with what expiry. Enterprises that adopt agentic payment rails without first defining that authorization model will inherit auditable evidence of spending they never governed. The correct sequencing is to build the internal spend authority model first, then attach it to the rail, because the rail will faithfully sign whatever authority you were careless enough to grant.
The consumer framing of agentic commerce, an assistant booking a flight or buying groceries, is a distraction. It hides the fact that in most mid-market and enterprise environments, agents and agent-adjacent automations are already committing funds, usually without a single line item in policy that says so. Gartner has predicted that 40% of enterprise applications will feature task-specific AI agents by the end of 2026, up from less than 5% in 2025. A meaningful slice of those applications sit adjacent to a budget.
Before your company formally approves anything called "agent payments," look here:
None of that arrived through a governance decision. It accumulated. The agentic payment standards simply make the pattern explicit and give it a name.
Treat an agent as a spending entity with a named human owner, not as a feature of an application. The model below is deliberately boring, because it maps onto controls your finance and audit teams already understand.
Spend authority for an agent should be granted by the budget owner for the GL account being charged, not by IT, not by the team that built the agent, and not by whoever holds the API key. Every agent needs a named accountable human, a documented business purpose, and a sponsor who would be asked about the spend in a budget review. Build this on top of proper agent identity and access, meaning each agent has its own distinct identity and credential rather than borrowing a service account or a person's session.
Most of the exposure today is not exotic. It is ordinary control weakness, applied to a non-human actor that operates faster than the controls assume.
Auditability is where the mandate model pays for itself, but only if you capture the evidence at the time of the transaction. At minimum, retain and link:
Store this as immutable, timestamped records with a retention period matching your financial records policy. This is a specific application of general audit evidence and logging discipline, and it is far easier to build now, while agent volume is low, than to retrofit after a year of untracked spend.
Note that none of this requires adopting AP2 or any agentic payment scheme. It is the prerequisite work that makes adopting one safe, and it produces value immediately regardless. Sequencing matters here in the same way it does for workflow automation. The control model comes before the capability, or you spend the following year unwinding it.
Being honest about maturity is part of the job. Several things are not ready as of November 2026.
The standards are converging but not converged. AP2 is under FIDO Alliance stewardship, which is the right direction, but conformance programs, certification, and the settled details of dispute handling are still maturing. Visa's Trusted Agent Protocol and Mastercard's Agent Pay are network-specific, and interoperability across schemes in production is early.
Liability and dispute rules are unsettled. If an agent buys the wrong thing inside a validly signed mandate, the chargeback and liability picture is not as clear as it is for card-present or card-not-present human fraud. Until that settles, keep agent-initiated spend in categories where an error is recoverable and the amounts are bounded.
Browser-operating agents are the weak link. An agent driving Chrome with saved passwords produces no mandate, no attribution, and no cryptographic evidence. It is convenient and it is the pattern most likely to appear in your environment without approval. Treat it as shadow IT with a payment method attached, and address it in your AI security and governance program rather than through payments policy alone.
Stablecoin rails deserve caution for now. AP2 treats them as first-class and systems like OSL's AgentPay make high-frequency micropayments practical, but for most enterprises the treasury, tax, and accounting handling is a project of its own. Defer unless you have a specific machine-to-machine use case where card economics genuinely fail.
Where to move now: attribution, per-agent identity, limits, evidence capture, and revocation. Where to wait: high-value autonomous purchasing, novel rails, and anything where a mistake is not reversible.
The mandate model is a real advance, and enterprises should welcome it. A signed, verifiable chain from a human's grant of authority to a specific charge is better than every ad hoc approval process it will replace. But the rail only signs what you grant it, and it will produce excellent evidence of a governance failure you did not know you had. The work that determines whether agentic payments become a control improvement or a control incident is entirely internal: naming owners, setting limits that bind, separating selection from payment, and being able to switch an agent off in seconds.
Infonaligy works with companies across Dallas–Fort Worth and remotely nationwide on exactly this kind of work, from custom AI agents that are governed from day one to AI consulting engagements that build the authorization model before the first agent touches a budget. If your agents are already spending and nobody owns the limits, that inventory is the place to start this week.
Infonaligy is an AI-native managed intelligence provider based in Dallas–Fort Worth, working with finance, procurement, and security teams across Texas, Oklahoma, and remotely nationwide.
We inventory every automation and agent that can commit funds, move them off shared cards and standing credentials, set limits that actually bind, and build the evidence trail your controller needs to reconcile an agent transaction.