Answers · agent payments
Rain launched Agent Vaults on November 10, 2026: a funded balance inside our agent, rules the owner sets, and a scoped Visa or Mastercard card for each purchase. What do those rules actually stop the agent from spending, and what do we still have to control ourselves?
Last updated
TL;DR: An Agent Vault holds money the owner put in first, by bank transfer, card or stablecoins, and the agent can only pay or send what is in it. For each purchase Rain issues a scoped virtual card with its amount, merchant and expiry fixed when it is issued, and Rain checks those at authorization, so a card for one job doesn't work for another, and a single-use card stops working after one approved purchase. On top of that the vault owner (or the platform that embeds the vault) sets rules through Rain's Agent Control Layer: how much per purchase, card, day, week or month, which merchant or category, until when, and which purchases wait for a person. Rain says the agent can't raise its own limit. What the rules can't do is judge the purchase itself: a card scoped to a supplier at a set amount will pay for whatever the agent orders from that supplier within the amount, the approval threshold only catches what you configured it to catch, and the rules live in the app that embeds the vault, so whoever can edit them there controls the agent's budget.
What should I check, step by step?
1. Fund the vault with only what the agent should be able to spend in the period. Rain's model is that the balance must be in the vault before a card is issued against it, so the balance itself is your outer cap.
- Scope cards to one merchant where you can, rather than a category. A category rule such as travel or software lets the agent pay any merchant in that category.
- Set a sign-off rule for anything above a threshold or outside the usual merchants, the way Rain's own example holds a 2,400 USD equipment purchase for the owner even though the money is in the vault.
- Keep expiry short: an hour, a trip or a single purchase. A card that outlives its task is a standing permission again.
- Decide who in your app can change vault rules and record every change. Rain's Agent Control Layer announcement says changes to money-movement terms require explicit action by a human administrator; make the same true for card rules in your own product.
- Use platform caps if you run many agents: Rain lists caps on the number of active cards and total spend across all vaults.
- Watch Rain's real-time balance, authorization and decline notifications, and reconcile each scoped card against the order the agent placed.
- Build against Rain's sandbox before anything is live, and test that a purchase above the threshold is actually held.
What do Rain Agent Vaults and the Agent Control Layer enforce when an AI agent pays?
Rain describes three layers. The vault: a balance the owner funds, which the agent can only spend from. The scoped card: one virtual card per job, issued from the vault with the amount, merchant and expiry set at issuance and checked by Rain when the merchant asks for authorization, so the merchant changes nothing. And the Agent Control Layer: rules for how much (per purchase, per card, per day, week or month), where (one merchant, a category, or anywhere), until when (an hour, a trip, a month, a single purchase) and who signs off (which purchases wait for a person).
- Rain's FAQ says an agent using a vault can only make payments within the user's rules, can't raise its own limit, and that a single-use card stops working after one approved purchase. Sending money out follows send rules: approved recipients only, with limits set by the owner or the platform.
- Rain also says it is enabling its programs for Visa Intelligent Commerce and Mastercard Agent Pay, so scoped cards will carry the networks' agent credential, which tells the merchant and issuer an agent is paying with the user's consent. That signal sits alongside the vault rules; it doesn't replace them.
What does a Rain scoped card fix at issuance, and what can an agent still buy with it?
Because amount, merchant and expiry are fixed when the card is created, the important decision is the moment the agent asks for a card. Rain's bakery example shows the pattern: the owner funds 5,000 USD, allows suppliers only and asks to approve anything above 1,500 USD. Two supplier purchases of 640 and 800 USD go through on their own cards; a 2,400 USD mixer is held because equipment is outside the rules.
- The card proves the charge matched the scope, not that the order was right. Within the merchant and amount the card allows, the agent can still buy the wrong item, the wrong quantity or something a seller page talked it into. If that matters, require sign-off at a lower amount or have the agent show the order before it asks for a card.
What don't Rain Agent Vault rules protect against when an AI agent spends?
Who sets the rules. The vault lives in the partner's app under the partner's brand, and Rain says the partner keeps the user, the rules and the balance. So the rules are only as protected as that app's settings screen and API keys. An agent, or anyone with access to the app, that can edit the rules can raise the limit; Rain's statement that the agent can't raise its own limit depends on the agent not having that access.
- Your own budget per task or project. Vault rules bound what the vault can spend. If several agents or tasks share one vault, or you want a separate budget per project, keep that total in your own system and check it before each card request.
- What happens after the charge. Rain's announcement doesn't describe refunds, disputes or partial shipments; a single-use card that has paid is spent even if the order is later cancelled. Keep the order record, the card and the approval together so you can follow up with the merchant.
How do I ask Rightshold about this (free, no key)?
Add the MCP server https://www.rightshold.com/mcp to Claude, Cursor, ChatGPT, Grok or VS Code, then ask: “Before my agent asks its Rain vault for a scoped card to pay 640 USD to mill.example for flour, check it against this agent's own spending policy and give me a signed allow or deny with the order number as the reference.”
{
"tool": "authorize_spend",
"arguments": {
"credential_id": "<this agent's credential id>",
"amount_minor": 64000,
"currency": "USD",
"merchant_domain": "mill.example",
"category": "supplies",
"reference": "<order number>"
}
}- Set the policy first with set_spend_policy (owner account key, toolset=trust): per_tx_max_minor, daily_max_minor, allowed_domains and allowed_categories per agent credential, so each agent or task has its own budget under the vault's rules. The daily total resets at 00:00 UTC.
- authorize_spend returns a signed allow or deny receipt with reasons such as over_per_transaction_cap, over_daily_cap or merchant_not_allowed and records it on Rightshold's ledger; anyone can check it with verify_spend_authorization.
- It doesn't create, fund or approve Rain vaults or cards, read the vault's rules or hold any card details. It only sees purchases the agent checks with it first, so keep Rain's own rules and sign-off on as the owner's control.
Rightshold records spending decisions your agent asks it for. It never holds or moves money, isn't a wallet, card issuer or payment processor and isn't affiliated with Rain, Visa or Mastercard. Rain Agent Vaults behavior is as described in Rain's November 10, 2026 announcement, its Agent Vaults product page and its June 2026 Agent Control Layer announcement, all read on November 11, 2026; Rain says Agent Vaults are available through its partners and sales team, and features may change, so check the linked pages before relying on them. Not financial advice.
What are the sources?
- Rain: Rain Agent Vaults bring embedded payments to AI agents (announcement, November 10, 2026)
- Rain: Agent Vaults product page (agentic control layer rules, scoped cards, send rules, sandbox)
- Rain: Introducing the Agent Control Layer
- Rain: Scoped cards
Related
- How to give an AI agent a virtual card with a spending limit
- Can an AI agent raise its own spending limit, and how do you stop it?
- How do Visa Intelligent Commerce mandates cap what an AI agent can charge to your card?
- How do Mastercard Token Spend Controls cap what an AI agent can charge on an Agent Pay token?
- Reserve against a shared team spend pool so concurrent AI agents can't overspend it
Not legal advice. JSON · Markdown · All answers
Get a free API key in one call
No card and no email needed. 100 free credits; the license and policy checks stay free without a key.
curl -s -X POST https://www.rightshold.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export RIGHTSHOLD_API_KEY=rs_... # the api_key from the reply (shown once)
curl -s https://www.rightshold.com/v1/licenses/check -H "Authorization: Bearer $RIGHTSHOLD_API_KEY" \
-H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'