Stripe Lets AI Agents Move Money From Treasury Accounts, With Approval Rules Set by the Business
Stripe said on 19 November 2026 that AI agents connected through its MCP server can now transfer funds, convert currencies and pay vendors from Stripe Treasury within limits a business sets, in public preview. Refunds, payouts and outbound transfers need human approval by default; agents with their own API keys can run under custom rules, such as approving ACH transfers under $50 automatically.

By Daniel Osei, Journalist, Payments and Cards
Stripe said on 19 November 2026 that businesses can now let AI agents move money in Stripe Treasury: transfer funds, convert currencies and pay vendors within limits the business sets. The capability is in public preview. Until now, Stripe said, more than 24,000 businesses used Stripe Treasury for agents with read access only, letting agents review transactions, build cash-flow models and reconcile payments.
Businesses connect a compatible AI tool, Stripe names Claude and Codex as examples, through Stripe's Model Context Protocol (MCP) server. They then choose what data the agent can see, which actions it can take and when a human must approve.
Two ways to connect, two levels of control
Stripe offers two routes:
Route — How it works — Money movement
Through an authorised user (OAuth) — The agent acts as an extension of that user and inherits their permissions — Every action that moves money, including a refund or payout, must be confirmed before it completes
Agent API key — The agent gets its own identity and persistent access; the business sets the key's permissions, expiry and rotation — By default, agent-initiated refunds, payouts and outbound transfers need human approval; rules can be customised
The second route lets agents work in the background, for example preparing reports overnight or staging a vendor payment and routing it to an approver. Stripe gives one example of a custom rule: an agent could process an ACH transfer under $50 automatically and send larger ones for approval. Businesses can also require approval for sensitive account changes, such as adding or removing an administrator or updating a bank account.
Stripe describes use cases including a payables agent that tops up bill-pay accounts and prepares vendor payments, and a payroll agent that converts currencies so staff are paid on time. Because Treasury sits next to Stripe's payment processing, an agent can see incoming payments, balances and outgoing transfers in one place and match receipts to bills.
Next, Stripe said, agents will be able to create cards with spending limits.
Agents are moving into the back office
Most agentic payments news this autumn has been about agents buying things: card networks issuing tokens to agents, OpenAI's ChatGPT Wallet, Visa opening its Agentic Ready testing programme to more than 140 initial participants on the acceptance side. Stripe's release covers the other side of a business: an agent moving the company's own money between accounts, across currencies and out to suppliers.
That changes where the controls sit. In card-based agent commerce, the network and issuer supply tokens, authentication and dispute rules. In account-to-account treasury flows there is no card network involved, so the limits and approval rules are set by the account provider and the business. Stripe's defaults reflect that: a person must approve outbound money unless the business explicitly loosens the rule.
Mastercard is approaching the same problem from the card side. On 19 November it said it had completed a pilot of Agent Pay for Machines with Ant International's Antom in Singapore, in which a business credentialed its AI agent, defined what it could buy and spend, and had those limits enforced at the point of payment.
A regulator asks the same questions
The release landed on the same day that the Monetary Authority of Singapore's managing director, Chia Der Jiun, told the Singapore FinTech Festival that some users are giving agents the login credentials to their financial accounts, and advised against it "as there is insufficient assurance of safety." He said financial institutions need to know whether an agent is acting with the customer's full authorisation, whether it is staying within its mandate, and who is responsible if it gets things wrong. MAS will facilitate a "know your agent" protocol to carry that information.
Stripe's agent API key answers part of that: it is a dedicated credential with its own permissions, expiry and rotation instead of a shared human login, and money movement defaults to human approval. What the release does not cover is liability. Stripe does not say who bears the loss if an agent sends a payment it should not have within the rules a business set, nor does it list the countries or account types where agent money movement is available, or any fees.
What to watch
Public preview means terms can change. The signals to watch are when Stripe makes the feature generally available, how many of the 24,000 read-access businesses switch on write access, whether businesses loosen the default approvals in practice, and how the planned agent-created cards with spending limits are governed.
Sources
- Stripe: Give your agents controlled access to analyze your data and move funds (19 Nov 2026)
- Mastercard via PR Newswire: Mastercard and Ant International Advance Trusted Agentic Commerce in Asia Pacific (19 Nov 2026)
- MAS: Keynote address by managing director Chia Der Jiun at the Singapore FinTech Festival 2026 (19 Nov 2026)
- Visa: Visa Expands Agentic Ready to Help Scale Trusted AI Commerce Globally (corrected release, 19 Nov 2026)