AI Agent Payment Permissions: What the Protocols Don’t Cover

AP2 treats agents as potential attackers and uses signed mandates to constrain purchases. Those signatures do not establish that product claims are true or settle who pays for every mistake.

Published: Sep 26, 2026

6-8 mins

By Grace

AI agent payment permissions deserve a separate review from permission to search for products. Google’s Agent Payments Protocol, AP2, assumes prompt injection cannot reliably be prevented and includes agents in its threat model as potential attackers. That is a conservative protocol assumption, not a proof that prevention is impossible in every system.

I use assistants with connectors and access to local folders. At the time I first wrote this article, I had not encountered a money or billing permission prompt in my own setup. That is a limit of my experience, not evidence that agent checkout is unavailable to other users.


What AI agent payment permissions grant

AP2 distinguishes a purchase approved while the human is present from a purchase completed later under delegated conditions. In the first, the user reviews a cart through a Trusted Surface. In the second, the user authorizes conditions that an agent later attempts to satisfy.

Those are different decisions. Approving an exact order is not the same as allowing an agent to choose one within a budget. AP2 uses signed mandates to represent authority and constraints; an open mandate can be closed when its conditions are met. Its checkout specification includes permitted merchants and item constraints.

For someone approving a tool at work, the useful question is therefore concrete: does this permission let the agent suggest purchases, submit a specific order, or keep spending authority for later? A button labeled “approve” does not answer that by itself.


Why AP2 treats the payment agent as a possible attacker

AP2’s security document describes a shopping agent making poor choices after prompt injection. Its controls include verification of mandate signatures, binding payments to their checkouts, and checking permitted amounts and payees. It also requires transaction receipts to be protected from modification by the shopping agent’s model.

The design aims to constrain consequences even when the model makes a bad decision. Whether a deployment achieves that depends on its verification and enforcement, not merely on claiming protocol support.

That distinction is the same one behind prompt injection detection: a model’s judgment and an independently enforced permission are different controls. A signature adds useful evidence, but does not turn an untrusted recommendation into a reliable one.


Signed payment mandates leave an upstream trust question

An August 2026 analysis of AP2 v0.2 catalogued 48 threats across five attack families. Eight reached the authors’ High rating in at least one of five deployment architectures. These are research classifications, not a count of observed payment breaches.

The researchers built their own testbed because a complete public implementation was unavailable at the time of evaluation. They explicitly limit claims about whether future third-party deployments will fail in the same way; they also did not measure downstream effects on payment-rail systems.

Their central finding concerns the inputs used before authorization. Signed Checkout and Payment Mandates protect covered transaction data against modification. They do not by themselves establish that upstream product descriptions, agent messages, or MCP tool results were truthful.

That is narrower than saying everything before signing is unprotected and everything after it is safe. Other controls can protect earlier steps, and signatures cover specified data rather than the whole commercial outcome. A valid delegated signature also need not mean a person clicked at the moment of purchase.

This is why MCP tool poisoning matters to payments. A tool’s output can shape the purchase before a mandate is created. My review would ask what supplied the cart and which claims were independently checked, as well as whether its signature verifies.


AP2 and Visa’s agent protocol have different emphases

Visa introduced its Trusted Agent Protocol with Cloudflare in October 2025. Its announcement emphasizes recognizing legitimate agents and communicating commerce context to merchants. It describes agent-specific cryptographic signatures built on HTTP Message Signatures, plus information about intent, consumer recognition, and optional payment data.

Question AP2 emphasis Visa Trusted Agent Protocol emphasis
What is being verified? Transaction authority and constraints represented by mandates Agent identity and commerce context conveyed to merchants
What operational problem is highlighted? Constraining delegated purchases and providing evidence Distinguishing recognized agent traffic from malicious automation
What should not be inferred? Every recommendation is accurate Recognizing an agent authorizes every purchase it requests

These are overlapping parts of a commerce system, not opposite halves that together guarantee safety. Visa’s launch announcement scoped its initial specifications to its network at that phase; it should not be read as a complete description of every later integration.


Set the payment limits before granting access

Limiting AI agent permissions explains when a person should approve an action. For purchases, I would make that approval review specific:

  • Define what may be bought. Record permitted merchants, items, amounts, and any expiry or repeat-purchase limits the implementation actually enforces. A natural-language preference alone is weak evidence that a validator will enforce it.
  • Review the source of the cart. Check material claims such as seller identity, availability, total price, and refund terms at the merchant. Decide what requires a fresh human review when those details change.
  • Check delegated authority. Find out how to revoke it and what happens to an order already submitted. Do not infer those behaviors from the presence of a signed mandate.
  • Locate the dispute route. Identify the merchant, agent provider, payment provider, and records you can obtain if the result is wrong.

AP2’s overview says accountability evidence is an objective. Its list of possible responsible parties is not a ruling that only an agent contract determines liability. Existing law, payment rules, contracts, and the facts of a transaction matter. For example, US CFPB guidance describes credit-card billing-dispute rights and procedures separately from an AI provider’s terms. It does not decide whether any particular agent purchase was authorized.


FAQ

Q

Can ChatGPT buy things for me right now?

OpenAI’s help page checked in October 2026 says eligible products and merchants may offer Instant Checkout. Its merchant page also says it is moving away from standalone Instant Checkout toward discovery and merchant-owned checkout. Availability therefore needs checking in the actual flow; these pages do not establish unrestricted unattended purchasing.
Q

Will an AI shopping agent recommend whatever pays it the most?

A payment signature cannot establish a recommendation’s independence. OpenAI says ChatGPT product results are not ads and are not influenced by its partnerships, with ads separate from product results. That is a vendor policy statement, and other agents need their own assessment.
Q

I run an online store. Do I need to do anything about AI agents?

Visa identifies legitimate agent traffic being blocked by bot defenses as one integration issue. Assess the agent traffic and checkout flows you intend to support before changing controls. Recognizing an agent should not mean exempting it from payment authorization or fraud checks.
Q

Who is liable if an AI agent buys the wrong thing?

The protocol alone does not answer that. Responsibility depends on the applicable law, payment rules, agreements, and what was authorized or delivered. Preserve the order and authorization records and use the relevant merchant or payment-provider dispute process.
Q

Does a signed approval mean the transaction is safe?

It provides evidence about the signed data and the signing authority, subject to valid keys and verification. It does not by itself prove an informed human click, an accurate product description, or satisfactory delivery. Delegated authority makes that distinction especially important.

Sources

Documentation checked in October 2026. The cited security study concerns AP2 v0.2 on a research testbed. Protocol support, product availability, and legal responsibility are separate questions.

Written by Grace

I test AI tools and agents in my own workflow, and write down what I find, including the settings that surprised me. About Grace and how posts are verified

Leave a Comment