# Mastercard added Token Spend Controls for Agent Pay and virtual card tokens. What limits can be set on an agent's payment token, who sets them, how are they enforced, and what do I still have to build myself as an AI agent developer?

**Short answer:** They put the limit on the payment token itself, and Mastercard enforces it on the network. Mastercard's MDES Customer Service release notes (July 2026 release, in production since August 5, 2026, available globally) let issuers enabled for the Mastercard Agent Pay and Mastercard Virtual Card Token programs set token-level rules: a per-transaction limit, daily, weekly and monthly limits, an absolute lifetime limit, a single-use setting (with an expiry date; the token stops working after its first successful non-zero transaction), and allow or block lists by merchant category code, merchant ID, transaction category code, transaction type and geography. Mastercard evaluates each tokenized transaction against those rules and declines the ones that break them, so the agent can't argue its way past them. The catch for developers is who holds the controls. They are issuer APIs (search, create, update and delete), and creating or changing a rule happens after cardholder authentication through the issuer. Issuers can optionally support them, so you get them only if the bank or card-issuing platform behind your agent's card exposes them. They also can't see what's in the cart, a budget that spans several cards or rails, or whether the purchase made sense. Treat them as the last stop: keep your own task-level check before the agent pays, and treat a network decline as final.

## Checklist
1. Ask your issuer or card-issuing platform whether it supports Mastercard Token Spend Controls for the tokens your agents use, which rule types it exposes, and whether the cardholder or your platform can set them through its app or API. The release notes make support optional for issuers.
2. Set the tightest token rule that fits the task: single use with a short expiry for one purchase; a per-transaction limit plus an absolute lifetime limit for a recurring job; weekly or monthly limits only where the job really repeats.
3. Lock the token to where the agent should buy: a merchant ID allowlist for a known seller, or merchant category codes and geography for a class of sellers. Block lists are useful for categories the agent should never pay, such as gambling or cash-like transactions.
4. Find out from the issuer how daily, weekly and monthly windows are counted (time zone, calendar boundaries) and how foreign-currency amounts count against a limit. The release notes say calendar week and calendar month but don't define the day boundary or currency handling.
5. Keep the rule-changing step away from the agent. Rules are created and updated after cardholder authentication; if the agent can reach that authentication (an emailed code, a signed-in banking session), it can widen its own token.
6. Check each purchase against your own policy before the agent pays: task, quote, merchant, running total across every card and rail the agent uses. The token can't see your other tokens, your stablecoin wallet or your budget for the task.
7. Handle declines on purpose. A token-rule decline means the purchase is outside what was set; the agent should stop and report it, not retry, split the charge or switch to another payment method.
8. Record which token, rule set and limit each purchase ran under, so a dispute or audit can match the charge to what was allowed at the time.

## What limits can Mastercard Token Spend Controls put on an Agent Pay or virtual card token?
- Mastercard's MDES Customer Service release notes for July 2026 introduce Token Spend Controls APIs. Issuers enabled for the Mastercard Virtual Card Token (MVCT) and Mastercard Agent Pay programs can define token-level spending rules, and Mastercard evaluates each tokenized transaction against them and declines those that violate them. The notes list the MTF test date as July 29, 2026 and production as August 5, 2026, with the functionality available globally.
- Spend-limit controls: Daily Spend Limit; Weekly Spend Limit (a calendar week); Monthly Spend Limit (a calendar month); Transaction Limit (one transaction); Single Use Control (one-time use with an expiration date; after the first successful non-zero transaction the token can't be used again); and Absolute Spend Limit (a cumulative cap the token can't exceed over its lifetime).
- List-based controls, as allow lists or block lists: Acceptor Business Code (merchant category code), Merchant ID, Transaction Category Code, Transaction Type and Geography. The notes describe them as usage control beyond card or account-level settings, so one card account can carry differently restricted tokens for different agents or tasks.

## Who can set Mastercard Token Spend Controls on an AI agent's token, and does every issuer support them?
- The four APIs are search, create, update and delete token spend controls, and they sit in MDES Customer Service, which is for issuers and their customer service. In Mastercard's flow the cardholder logs in to the issuer's app, and the issuer creates, updates or deletes rules after cardholder authentication. An agent developer doesn't call these APIs directly; they come to you, if at all, through the issuer or the card-issuing platform you work with.
- The impact section says issuers can optionally support the new APIs once they are in production. So the same Agent Pay token can have rich network-side limits at one issuer and none at another. Ask before you rely on it.
- Enforcement is on the network side: the rule is evaluated against each tokenized transaction and a violating one is declined. That's the strongest place for a hard cap, because instructions the agent reads, or a bug in your own code, can't move it. New error codes cover a rule that doesn't exist for the token, a token that can't be found and a rule that already exists.

## What doesn't a card-network token spending limit protect against when an AI agent pays?
- It limits amounts and places, not purchases. A charge for the wrong item at an allowed merchant under the limit passes every rule. Records of what the customer actually asked for are a different layer; Mastercard's own Agent Pay work points to its Verifiable Intent for that, and protocols like AP2 carry signed mandates.
- It sees one token. An agent that pays with several cards, a stablecoin wallet and an x402 client has a separate limit on each and no shared budget unless you keep one. Your own check, before the agent pays, is where a task or fleet budget lives.
- It protects the rules only as well as the authentication that changes them. If the agent can complete the cardholder's authentication, it can ask for a wider token. Keep that step with a person, on a channel the agent can't read.

## Ask Rightshold (free, no key)
Add the MCP server https://www.rightshold.com/mcp to Claude, Cursor, ChatGPT, Grok or VS Code (one-click setup: https://www.rightshold.com/start?ref=seo), then ask: "Before my travel agent pays the hotel with its Mastercard agent token, check the $412 charge against its own spending policy for this task and record the decision with the token reference, so I have a record that doesn't depend on the card network's logs."

```json
{
  "tool": "authorize_spend",
  "arguments": {
    "credential_id": "YOUR_AGENT_CREDENTIAL_ID",
    "amount_minor": 41200,
    "currency": "USD",
    "merchant_domain": "hotel.example",
    "category": "travel",
    "reference": "agent-token-ref-and-booking-id"
  }
}
```
- Needs a key for your account. It checks the purchase against the policy set with set_spend_policy (owner account key only): currency, per-transaction cap, UTC-day cap, allowed merchant domains and categories, expiry. It returns a signed allow or deny with reasons such as over_daily_cap or merchant_not_allowed, recorded on Rightshold's ledger.
- It doesn't read, set or enforce Mastercard Token Spend Controls, can't see the card network's decision, and has no weekly, monthly or lifetime cap. It only sees purchases the agent checks with it first. Keep the token's own limits as the hard stop behind it.
- A merchant or auditor can check the receipt free with verify_spend_authorization; an allow is valid for 15 minutes.

_Rightshold records spending decisions your agent asks it for. It never holds or moves money, isn't a card issuer or part of Mastercard, and doesn't connect to card networks, issuers or payment processors. The Token Spend Controls details come from Mastercard's MDES Customer Service release notes for July 2026 as checked on November 10, 2026; what your issuer offers may differ. Not financial advice._

## Sources
- [Mastercard Developers: MDES Customer Service release notes, July 2026 (Token Spend Controls APIs)](https://developer.mastercard.com/mdes-customer-service/documentation/release-history/release-notes-july2026/)
- [Mastercard: Agent Pay (registered agents, Mastercard network tokens)](https://www.mastercard.com/global/en/business/artificial-intelligence/mastercard-agent-pay.html)
- [Mastercard press release: Mastercard unveils Agent Pay (April 2025, Agentic Tokens)](https://www.mastercard.com/us/en/news-and-trends/press/2025/april/mastercard-unveils-agent-pay-pioneering-agentic-payments-technology-to-power-commerce-in-the-age-of-ai.html)
- [Mastercard press release: Mastercard launches Agent Pay for Machines (June 10, 2026)](https://www.mastercard.com/us/en/news-and-trends/press/2026/june/mastercard-launches-agent-pay-for-machines.html)
- [Mastercard Developers: Agentic commerce guide, Level 3 programmatic checkout](https://developer.mastercard.com/merchant-cloud/documentation/tutorials-and-guides/agentic-commerce-guide/23/)

## Related
- [How to give an AI agent a virtual card with a spending limit](https://www.rightshold.com/answers/how-to-give-an-ai-agent-a-virtual-card-with-a-spending-limit)
- [How do Stripe shared payment tokens limit what a seller can charge for an AI agent purchase?](https://www.rightshold.com/answers/how-do-stripe-shared-payment-tokens-limit-what-a-seller-can-charge-for-an-ai-agent-purchase)
- [How to cap an AI agent's spend per vendor per day across multiple tasks](https://www.rightshold.com/answers/how-to-cap-an-ai-agents-spend-per-vendor-per-day-across-multiple-tasks)
- [Can you dispute a purchase your AI agent made with your card?](https://www.rightshold.com/answers/can-you-dispute-a-purchase-your-ai-agent-made-with-your-card)

_Not legal advice. Updated 2026-11-10. JSON: https://www.rightshold.com/answers/how-do-mastercard-token-spend-controls-cap-what-an-ai-agent-can-charge-on-an-agent-pay-token.json_