A payment mandate is a user-signed, tamper-evident authorisation that permits an agent to pay for a specific transaction. It is the mechanism by which an autonomous agent can move money without holding the user’s raw card credentials, and it is defined concretely by the Agent Payments Protocol (AP2).
Why it matters
Payments are the sharpest test of agent trust. An agent that can spend is an agent whose authority must be bounded by amount, merchant, item, and time — and whose authorisation must be provable later, when a charge is disputed. A payment mandate answers both: it scopes what the agent may pay for, and it produces evidence of consent. This is why agentic payments are a proving ground for KYA more broadly. See KYA for agentic payments.
How AP2 defines it
AP2 (Agentic Payment Protocol, v0.2) is a protocol for securing agent-performed payment transactions, built on an agent-authorisation model in which mandates are the core means AP2 uses to authorise agents. It defines two linked mandate types:
- a Checkout Mandate, securing what is being purchased, with a receipt; and
- a Payment Mandate, securing the payment for that checkout, with its own receipt.
The mandates are assembled by the Shopping Agent once it has determined the user’s intent, then signed via a Trusted Surface — a UI surface that is trusted to obtain informed user consent before creating a user-signed mandate. Because the mandate is signed and bound to the specific checkout, it can later serve as evidence at the time of dispute.
AP2 sets out five roles — Shopping Agent, Credential Provider, Merchant, Merchant Payment Processor, and Trusted Surface — and distinguishes agentic roles (those whose communication is handled by a non-deterministic LLM) from non-agentic ones. The Trusted Surface MUST be non-agentic, and it treats the agent itself as a potential attacker when either side of a flow is agentic.
Mandate vs delegation vs credential
A payment mandate is a narrow, purpose-built case of delegation: the user grants a scoped, signed right to an agent. It differs from a general scoped credential in being bound to a specific purchase and in carrying its own receipt for dispute resolution. Both the principal and the agent remain visible — the property that separates delegation from impersonation, and the defence against a confused deputy spending on borrowed authority.
Related terms
Sources
- AP2, Agent Payments Protocol specification (v0.2) (Accessed 2026-10-08)
- AP2, Payment Mandate (Accessed 2026-10-08)
- AP2, Checkout Mandate (Accessed 2026-10-08)
- AP2, Agent Authorization (Accessed 2026-10-08)
Know Your Agent (KYA) explains agent identity, verification and accountability. This is an explainer, not legal or compliance advice — see our Sources & methodology. New to KYA? Start with What is Know Your Agent? and the glossary.