Guide // MandateGuard
What is an AP2-style intent mandate for agent payments?
By the Ingenious AI team · Published 2026-11-14 · Reviewed 2026-11-14
▸ Run the free live demo See pricing
Free covers 1 agent and 1 policy with the full authorize flow, signed receipts and the approval inbox — no card required to start.
Short answer
An AP2-style intent mandate is a mandate built to be shared: a registered object holding the principal, the agent, the merchant scope, a cumulative budget, optional per-period budgets and a recurring authority window, all referenceable by one intent_id. In MandateGuard's interoperable intent service, the agent buys against it, the merchant verifies receipts against it with a read-only key, and the issuer manages its status — suspend, resume, revoke — while every event lands in the intent's own hash-chained log. It is the mandate shape for agent payments that cross organisational boundaries.
What is an AP2-style intent mandate?
An AP2-style intent is a registered mandate object: principal, agent, merchant scope, cumulative budget, optional per-period budget, recurring authority window and status, identified by one intent_id. In MandateGuard's interoperable intent service, issuers (Pro and Team) register intents; authorize calls can reference an intent, decrementing its cumulative budget atomically on ALLOW; and the intent keeps its own hash-chained event log, aligned with the EMVCo draft framework for agentic payments (a draft alignment, not a certification).
From private policy to shared object
A MandateGuard policy is private: it lives in your workspace and governs your agent. Many real mandates are not private. A customer authorises an agent to shop on their behalf; a platform authorises agents to buy within a marketplace; an issuer stands behind a class of agent transactions. In those cases the mandate must be an object the parties share — created by one, referenced by all, changed by none unilaterally. That is the intent. Registering it produces an intent_id, and from then on the agent's purchases, the merchant's verification and the issuer's oversight all point at the same record: same budgets, same scope, same status, same event history.
The fields that make an intent
An intent names its principal — the human or organisation whose authority stands behind it — and optionally the agent and its identity. It scopes the merchants the mandate covers; empty scope falls back to the policy allowlist, and naming merchants makes the mandate legible to outsiders. It carries a total budget and optionally a per-period budget with a period length, plus an authority window bounding when the mandate is alive. Status — active, suspended, revoked — is managed by the issuer. Read that field list again and notice what it is: the answers to every question a merchant or checker would ask before honouring an agent's purchase, written once, in one place, by the party with the authority to answer.
Authorising against an intent
When an authorize call carries an intent_id, MandateGuard runs the ordinary policy evaluation and, on ALLOW, atomically decrements the intent's cumulative budget — atomicity matters, because concurrent purchases must not each see the same remaining budget and jointly overshoot. The receipt links into the intent's own hash-chained event log, so the intent accumulates a tamper-evident history of everything done under it. Refunds, adjustments and chargeback notes are appended as events that restore or adjust the budget accordingly, which keeps the shared numbers truthful after the real world's messiness — returns, partial credits, disputes — arrives.
Why merchants and issuers care
A merchant honouring an agent's order faces a verification problem: was this purchase inside a real mandate? The intent service answers with evidence rather than assertions. A merchant-role key — read and verify only, incapable of registering or modifying anything — can fetch the intent, see its status and remaining budget, and verify a specific receipt against it: hash, signature, workspace chain and intent linkage. Issuer-side checkers get the same view for oversight. This is the interoperability the name promises: not a shared brand, but a shared state that parties with different interests and different keys can each confirm independently.
Intents versus policies and envelopes
The three mandate shapes differ by audience. A policy governs your agent inside your workspace — the default tool for your own fleet. A spend envelope governs one task with a defined maximum, vendor set, period and approval conditions, reviewed on a single card. An intent governs a mandate that outside parties must be able to reference and verify. Choosing wrongly has costs: a policy cannot be shown to a merchant; an intent is heavier than a one-team task needs; an envelope cannot serve as a standing fleet control. Most deployments end up using policies for their own agents and intents for the mandates they issue to, or accept from, others.
Standing up your first intent
Register with the registry UI or API: principal, agent if known, merchant scope, total budget, and a period budget if the spend should pace itself. Share the intent_id with the parties who must reference it, and issue each party a role key scoped to its function — merchants verify, they never write. Agree operationally what suspension means between you (a pause for review, reversible) versus revocation (the mandate ends). Then watch the intent's gauge and chain the way you watch receipts: the budget burn rate against the authority window is the earliest signal that the mandate's shape and the agent's behaviour disagree.
Five actions to take now
- Register the intent with principal, agent and merchant scope named explicitly
- Set a cumulative budget from the campaign's real total cost
- Add a per-period budget so a front-loaded month cannot consume the quarter
- Issue role keys per party — merchant keys read and verify only
- Rehearse a verify-receipt check with the merchant before launch
Worked example: one intent, three parties, 90 days
A retailer (principal) authorises a shopping agent to buy a defined equipment list from two merchants, total budget 900 dollars, per-period budget 300 dollars per 30 days, authority window 90 days. The issuer registers the intent and shares the intent_id with both merchants. In month one the agent buys 264 dollars of equipment; each authorisation decrements the intent's spent total, and the merchants verify the receipts against the intent with their read-only keys.
In month two a 120-dollar request arrives that fits the period budget but would serve a purpose outside the equipment list's merchant scope. Scope, not money, stops it: the merchant is outside the intent's scope for that category, the issuer is notified through the intent's state, and the purchase is renegotiated as a separate intent rather than stretched into this one. One ID, one budget, one scope — readable identically by all three parties throughout.
Frequently asked questions
What does AP2-style mean here?
The intent follows the mandate-centred shape of Google's Agent Payments Protocol: verifiable, scoped spending permission. MandateGuard describes its service as AP2-style and EMVCo-draft-aligned, not certified.
Who can register an intent?
An issuer on a Pro or Team workspace, using an issuer-role key or the workspace key. Merchant and agent role keys cannot register or modify intents.
Does an intent replace a policy?
No. Authorisations under an intent still pass the existing policy and receipt path; the intent adds shared budgets, scope and cross-party state on top.
What happens when the budget runs out?
Authorisations against an exhausted intent cannot proceed under it; the intent's spent and remaining figures make exhaustion visible to every party before it bites.
Can an intent be changed mid-flight?
Its status can be managed — suspend, resume, revoke — and every change is an event in the intent's own chain. Budgets and scope are the registration's terms; new terms usually mean a new intent.
Keep reading
- What is an interoperable intent service for agent mandates?
- How do cumulative budgets work on an agent intent?
- What is the EMVCo draft framework for agentic payments?
Put the policy in force: spend envelopes · intent registry · approval inbox · how the proof works · all MandateGuard guides