Agent payments are secured in layers, and no single layer does the whole job. Single-use or scoped cards cap what an agent can spend. Payment tokens keep your real card number away from the agent and the merchant. Card networks issue agent-specific tokens to registered agents. Signed mandates and agent signatures prove who authorised what. Your own approval setting sits above all of these and is still the control that matters most. This explainer is based on the official docs and launch coverage as of November 2026.
The layers at a glance
- Your approval
- Scoped card or token
- Network agent token
- Signed mandate or agent signature
- Merchant checkout
| Layer | What it protects against | Examples | Who controls it |
|---|---|---|---|
| Per-purchase approval | Wrong or injected orders | Duet money actions always ask; Muse approves every purchase | You and the agent vendor |
| Single-use card | Overspending, card reuse | Link by Stripe one-time cards (Muse, Duet) | Payment provider |
| Scoped token | Card number exposure, overspend | Stripe Shared Payment Tokens | Payment provider |
| Network agent token | Unregistered agents, card exposure | Mastercard Agentic Tokens, Visa Intelligent Commerce, Amex ACE | Card network |
| Signed mandate | Disputes over what you authorised | AP2 Checkout and Payment Mandates | Protocol participants |
| Agent signature | Bots posing as trusted agents | Visa Trusted Agent Protocol, Web Bot Auth | Agent operator and merchant |
As of November 2026.
Single-use and scoped cards
The simplest protection is a card that only works once. Meta Muse pays with single-use Link by Stripe cards that come with Link purchase protection. Claude Duet's one-time Link cards are limited to one merchant and one amount, according to Anthropic. If the agent is tricked into a second purchase, or the merchant tries to charge more, the card declines.
Stripe's Shared Payment Tokens work similarly for merchants. Stripe calls them a "scoped grant": the token is limited by currency, maximum amount and expiry, and it can be revoked. The agent passes the token to the seller instead of a card number.
Network agent tokens
Card networks have built agent-specific versions of the tokenisation already used by phone wallets.
- Mastercard Agent Pay launched on 29 April 2025 with Agentic Tokens. Agents must be registered and verified before they can use them, per Mastercard.
- Visa Intelligent Commerce is a portfolio covering credentials, spending limits, approval workflows and authentication, per Visa.
- Amex ACE is American Express's equivalent for agentic commerce.
These tokens let the issuer see that a transaction came from an agent, which matters for fraud scoring and, in time, for disputes.
Signed mandates: proof of what you approved
The Agent Payments Protocol (AP2), announced on 16 September 2025, uses signed mandates as tamper-evident records of what the user authorised. The current spec has a Checkout Mandate and a Payment Mandate, each with open and closed stages. The launch spec called them Intent and Cart mandates. Mastercard was a launch partner. We found no Visa statement on AP2. The protocol has been donated to the FIDO Alliance, the body behind passkeys.
- Mastercard launches Agent Pay with Agentic Tokens
- Cloudflare introduces signed agents
- Google announces AP2 with signed mandates
- Visa announces Trusted Agent Protocol, built with Cloudflare
- Cloudflare Trusted Agent Delegation coalition announced
Passkeys and agent signatures
Two kinds of proof are being added. Agent signatures prove which agent is knocking. Visa's Trusted Agent Protocol, built with Cloudflare, uses cryptographic signatures so merchants can tell trusted agents from bad bots. Cloudflare's signed agents and the IETF Web Bot Auth draft do similar work. Note the limit: Web Bot Auth verifies the agent operator, not the human user.
Passkeys answer the other question: did a real person approve this? A passkey confirmation ties approval to your device and a biometric or PIN, which a prompt injection cannot fake. The AP2 donation to the FIDO Alliance points in this direction, but consumer agents do not yet widely document passkey confirmation for purchases. Treat it as emerging.
How the layers fit together in one purchase
Picture a single order. You ask the agent to buy a kettle. It finds one and shows you an approval screen with the merchant, price and delivery address. You approve. The payment provider issues a one-time card or a scoped token good only for that merchant and amount. If the merchant uses a card network's agent programme, the network sees a registered agent token rather than your card number. If the merchant supports agent signatures, it can check that the request came from a known agent operator rather than a scraper. Where AP2 is in use, signed mandates record what you authorised, which can help if the order is later disputed. Each layer narrows what can go wrong, and you can see only the first one: the approval screen.
What the layers do and don't cover
Pros
- Single-use cards and scoped tokens cap the amount at risk
- Your real card number stays away from the agent and the merchant
- Network tokens flag agent transactions to your issuer
- Mandates create evidence of what you authorised
Cons
- Nothing stops a purchase you approved by mistake
- Agent signatures verify the operator, not you
- Passkey confirmation for agent purchases is not yet standard
- Protection varies by vendor and payment method
Bottom line
Agent payment security is real and improving: single-use cards, scoped tokens, network agent tokens and signed mandates each close a gap. None replaces your own approval of each purchase. Choose agents that ask every time, pay through scoped cards rather than a raw card number, and keep transfers out of reach entirely, as covered in can AI agents move your money. If something slips through, see who pays when an AI agent gets it wrong. The way agents handle credentials more broadly is covered in does your AI agent see your passwords. For the wider picture, see AI agent payments explained and, for UK rules, agent payments in the UK.



