The Vault Model: Rain Just Gave AI Agents Their Own Payment Account

AI agents can already find products, compare suppliers and initiate workflows. But giving them a way to pay raises a harder question: how do you grant useful spending authority without handing over an open-ended payment credential?

Rain’s Agent Vaults, introduced on 10 November 2026, point to a third architecture for agentic payments. The idea is to give an agent access to a funded account governed by enforceable rules, rather than a permanent card number or a separate third-party wallet. For platforms, the shift is significant: payment authority can sit inside their own product, with controls applied before a transaction proceeds.

Why the two familiar models fall short

A raw card number is a standing permission. Once an agent has the credential, it can potentially reuse it beyond the original task unless additional controls intervene. It is a blunt instrument for a system expected to make decisions repeatedly and at speed. As Rain’s launch framing suggests, few businesses would give an employee an unrestricted card for a single job and call that adequate control.

A third-party wallet creates a different problem. It can insert another company’s login into the platform experience, put that provider’s name on the customer’s statement and apply a single balance-wide limit in its own app. The platform may have introduced the agent, but the wallet provider can end up owning the payment relationship and its visibility.

Neither architecture cleanly connects an agent’s authority to a specific purchase while keeping the customer experience and commercial relationship within the platform that built it.

How the agent vault works

With Rain’s model, an owner funds a vault through bank transfer, including ACH, Fedwire, FedNow, SEPA and FPS, or by card or stablecoin. The funds are held as stablecoins in a non-custodial wallet. The agent does not directly handle the balance. Instead, Rain applies the owner’s rules when the agent attempts to spend or move money.

For a card purchase, the agent submits transaction details and Rain issues a scoped virtual Visa or Mastercard. The amount, merchant and expiry are fixed at issuance, then checked at authorisation. After one approved purchase, the card is retired. Rain says the system supports Visa Intelligent Commerce and Mastercard Agent Pay credentials alongside partner-defined rules, so the network credential can signal user consent as well as enabling the transaction.

The distinction is important: a balance can be available while a particular purchase remains unauthorised. Rain also says agents can send funds to bank accounts in more than 80 countries, while its cards are accepted at 175 million merchant locations.

Consider a bakery owner who puts $5,000 into a vault, allows supplier purchases and requires approval for spending above $1,500. The agent makes two qualifying flour purchases, for $640 and $800, and both proceed. It then finds a $2,400 mixer. Although the funds are there, equipment is outside the rules, so the purchase is held for approval. The vault separates “can pay” from “may pay for this”.

A more useful trust boundary, with a caveat

The vault model addresses an accountability gap we explored in our analysis of who owns the trust layer in agentic payments. The agent cannot raise its own limit, and the card credential expires after a single approved use. The platform embedding the vault can retain its brand, customer relationship and statement name, rather than handing those touchpoints to a separate wallet provider.

There is, however, an important boundary to understand. At authorisation, a scoped card is still a card credential and the transaction still travels over a card network. The vault enforces its controls when a card is issued and the network processes the card transaction; it does not replace card acceptance or make the transaction invisible to existing payment systems.

That is a practical compromise. Merchants can continue accepting familiar network payments while the agent’s authority is constrained upstream. Compatibility with Visa Intelligent Commerce and Mastercard Agent Pay also indicates that the agent credential layer is becoming part of payment infrastructure, not just an experimental add-on. The same questions of identity, intent and responsibility are emerging in Visa’s live B2B supplier invoice pilot.

The settlement layer is changing too

The vault is the agent-facing account and control layer. Underneath it, funds are held as stablecoins and Rain says it settles with card networks in stablecoins. Users do not need to buy or manage stablecoins to use the product. The technology choice is therefore largely behind the experience, while the platform’s rules determine what an agent can do.

A parallel shift is underway in network settlement. On 10 November, reporting on Visa’s US expansion described financial institutions, including Cross River Bank and Lead Bank, settling obligations to Visa in USDC over Solana. This is institutional settlement, not a new checkout method: it does not require cardholders to hold crypto, and it does not automatically change when merchants receive their payouts.

A separate seven-day Lloyds and Visa pilot settled $750,000, with funds reaching Visa in under an hour. Taken together, these developments suggest that two layers are advancing at once: the credentials and controls that allow agents to transact, and the settlement infrastructure that moves obligations between financial institutions.

What Australian platforms should assess

For Australian businesses building agent experiences, the strategic question is not simply whether an AI agent can make a payment. It is whether its authority can be defined, enforced, evidenced and reconciled without pushing the customer into another provider’s product. Because Rain vaults are issued through partners embedding them in their own apps, merchants can keep their own brand and existing card acceptance experience.

Before choosing an agent vault or similar architecture, assess:

The emerging vault model does not remove the need for governance, dispute handling or clear commercial responsibility. It does offer a more bounded way to give an agent payment capability. For platforms, that can mean automation without making a permanent card number or an external wallet the centre of the customer relationship.

Frequently asked questions

What is an agent vault?

An agent vault is a funded account for agent-led payments, with rules that govern how the agent can spend, receive or send money. In Rain’s model, funds are held as stablecoins and the agent accesses them through Rain-enforced rules and scoped payment credentials.

Does an agent vault require merchants to change how they accept payments?

Not necessarily. Rain says its scoped virtual cards work through Visa and Mastercard acceptance, so merchants can process the payment through existing card acceptance arrangements.

Do users need to handle stablecoins?

Rain says no. Users can fund a vault by bank transfer or card, while stablecoins are used underneath the payment flow. Users who already hold stablecoins can also send them into a vault.

Authoritative sources