> ## Content Index
> Fetch the complete content index at: https://www.doitwithfriday.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Stripe Treasury for Agents Now Moves Money Within Limits
- URL: https://www.doitwithfriday.com/news/stripe-treasury-agents-move-funds/
- Published: 2026-11-20T08:42:47.000Z
- Updated: 2026-11-20T15:04:30.000Z
- Description: Stripe lets AI agents transfer funds, convert currencies and pay vendors from Treasury, within limits the business sets, in public preview. What to set first.
- Author: Kevin Anderson
- Tags: News, What's New

Stripe put agent money movement in public preview on November 19, 2026\. Agent-initiated refunds, payouts and outbound transfers need human approval by default.

In Friday's view, set your limit and approval rule before connecting Stripe Treasury for agents. The defaults leave out new recipients and bank account changes.

## Stripe Treasury for agents can now move money in preview

Stripe Treasury for agents started with read access to financial data, for analysis work. Stripe's November 19 announcement adds the ability to move funds, inside limits the business sets.

### What an agent can now do from a Treasury account

[Stripe's announcement](https://stripe.com/blog/give-your-agents-controlled-access-to-analyze-your-data-and-move-funds?ref=doitwithfriday.com) puts the change in one sentence: "With Stripe Treasury, you can allow agents to transfer funds, convert currencies, and pay vendors within limits you set." The post is dated November 19, 2026, and it says the agentic money movement capabilities "are now available in public preview." Because it is a preview, check Stripe's docs again before you rely on any default described here.

Stripe's own example is a payables agent. In Stripe's words, it "could monitor balances across accounts, transfer funds to keep bill pay accounts topped up, and prepare vendor payments." Stripe also describes an agent that reconciles settled payments to invoices, updates the cash forecast, looks up the vendor recipient's details and readies vendor payments for approval. The verb Stripe uses at the end is "ready," and the payment itself still waits for a person.

### From read access to write access

The read side came first. Stripe says more than 24,000 businesses already use Stripe Treasury for agents with read access, for tasks such as reviewing transactions, building cash flow models and reconciling payments. One example request in Stripe's post is a daily financial report that combines incoming payments, balances, card spend and bills paid. The new step is write access to money. Stripe frames the condition plainly: for agents to take on more operational work, "they need access to the right capabilities but also clear limits on what they can do."

## Human approval is on by default for three money actions

The central default in the preview is the approval step. Stripe names three agent actions that wait for a person, and its MCP documentation shows how that approval reaches you and how long it lasts.

![Stripe's Confirm agent action dialog for an outbound payment requested by an agent, with the Deny and Confirm buttons highlighted.](https://storage.ghost.io/c/67/23/6723d566-f4a4-4c03-8b45-4f8f0948342b/content/images/2026/11/stripe-confirm-agent-action.webp)

Stripe's blog shows the confirmation step: an outbound payment requested by an agent waits until a person confirms or denies it. Source: Stripe, Give your agents controlled access to analyze your data and move funds, checked Nov 20, 2026.

### Which actions wait for a person

Stripe's post is direct: "By default, agent-initiated refunds, payouts, and outbound transfers require human approval." [Stripe's MCP documentation](https://docs.stripe.com/mcp?ref=doitwithfriday.com) marks a slightly different set: three Treasury tools in public preview carry a Human confirmation badge. They are convert\_currency, which converts funds between currencies within a Treasury account; send\_money, which sends money from a Treasury account to a recipient; and transfer\_money, which moves money between supported Stripe balances. Creating a refund through the general write tool carries the same badge.

One Treasury tool in that table has no badge: setup\_recipient, which sets up a recipient account for sending money. Adding a payee and paying a payee are separate steps, and only the payment is marked for human approval in the table.

### How an approval works in the Dashboard

When an agent hits one of these actions, Stripe can require human approval: you review and approve the request in the Dashboard. You click the URL the agent provides and review the details. Stripe says that when you click Approve, it gives the agent an approval token, "but you need to tell the agent to retry the operation." If you do not approve the action within 24 hours, it expires. Stripe also notes that its confirmation requirement is separate from your MCP client's tool-approval setting, and it asks users to turn that client setting on so they can review tool calls before they run.

## Set the limit and the approval rule before you connect

Stripe gives the business two controls on top of the defaults: a limit on what an agent can move alone, and custom approval rules for other sensitive actions. Set both before the agent connects.

### Stripe's $50 ACH example

Stripe's announcement gives one concrete limit: "an agent could process an ACH transfer under $50 automatically but route larger transfers for approval." That example shows the shape of an approval rule. Below a threshold the agent acts alone, and above it the request goes to a person. Stripe presents the $50 figure as an example of what you can configure, and it does not state a recommended threshold or a default dollar amount.

### Custom approval rules beyond money

The second control covers actions that are not payments. Stripe says businesses "can also create custom approval rules for other agent actions, such as adding or removing an account administrator or updating a bank account." The MCP documentation adds that account-specific approval rules "can require review of additional actions." In Friday's view, bank account and administrator changes deserve human approval as much as payments do. An agent that can change where payouts land, or who controls the account, can do more damage than one $49 transfer.

### A starting rule set for a small business

For example, a six-person design studio pays about a dozen contractors and software vendors each month and plans to connect Stripe Treasury for agents to its payables. A sensible first approval rule set, in Friday's view, looks like this: transfers between the studio's own accounts under a small limit run alone, once you set a rule that allows it; every vendor payment and every currency conversion waits for the owner; any new recipient, bank account change or administrator change waits for the owner too. Write the rule set on one page, with the limit in dollars, the person who approves, and who covers approvals during a vacation. Raise the limit only after a month of approvals shows the agent prepares payments correctly.

## How an agent connects through Stripe MCP

An agent connects through Stripe's Model Context Protocol server, and the way it signs in decides whose permissions it carries and how you can take them back later.

### OAuth means the agent inherits your permissions

Stripe says businesses grant access by connecting a compatible AI tool, "such as Claude or Codex," through Stripe MCP and choosing what data the agent can see, which actions it can take and when human approval is required. The detail to read twice: "When you connect an agent to Stripe MCP through OAuth, the agent acts as an extension of that user and inherits their permissions." In plain terms, an agent connected by an administrator can reach what that administrator can reach. Stripe's Treasury docs say administrator access is required to add funds and manage financial account settings. In Friday's view, the person who connects the agent should be the user with the narrowest role that still covers the job.

Stripe's docs add two details about an OAuth connection. You can grant access to live mode accounts or sandboxes with different permissions for each, and OAuth refresh tokens expire after 14 days from the first authorization, after which you reconnect and authorize again.

### Agent API keys and the November 30 deadline

For agents that run on their own and cannot use OAuth, Stripe's docs tell you to create an agent API key "with only the permissions the client needs." There is a dated change here. Stripe asks users to migrate by November 30, 2026: "Starting in December, Stripe MCP will stop accepting full-access secret keys and restricted API keys without the Agent tag." A workflow your builder set up earlier with an ordinary secret key will stop working with Stripe MCP in December unless it moves to an agent API key or to OAuth.

### Revoking a session and turning MCP off

Your authorized MCP clients appear under OAuth sessions in your Stripe user settings, where you can revoke one. An administrator can revoke another user's sessions, or every listed session at once, and can enable or disable MCP access for the whole team, separately for live mode and sandboxes. Revoking applies only to the account and environment, live mode or sandbox, that you are viewing, so check each one. Stripe's docs also warn users to exercise caution when using Stripe MCP with other servers to avoid prompt injection attacks. In Friday's view, that warning is one more reason for the approval rule: an agent that reads email or web pages can be fed instructions by them.

## What Stripe Treasury for agents leaves open

The preview answers how Stripe Treasury for agents moves money, and the announcement leaves three questions open: where it is offered, what it costs and what comes next.

### Where Treasury is offered and who holds the funds

The announcement does not name the countries where Stripe Treasury for agents can move money. [Stripe's Treasury docs](https://docs.stripe.com/treasury?ref=doitwithfriday.com) list Treasury itself as available in the United States and the United Kingdom, with Australia and a group of European countries in private preview. In the US, the same page says: "Stripe is not a bank. Checking accounts are provided exclusively by Fifth Third Bank, National Association, Member FDIC." Account structures in the UK and other countries can differ. The page also says there are no monthly fees or minimum balance requirements to open or maintain a financial account. Stripe's post gives no price for the agent features, so ask Stripe or your builder before you assume they cost nothing extra.

### What comes next for Stripe Treasury for agents

Stripe lists one next step: "Next, we’ll expand the financial actions agents can take, including creating cards with spending limits." That is a plan: Stripe Treasury for agents cannot create those cards in the preview today. If your use case depends on giving an agent its own card for subscriptions or ad spend, wait for Stripe to announce it as available before you plan around it.

### Friday's view on owning the limits and the logs

Stripe Treasury for agents puts the controls inside the account the business already owns, which is the right place for them. The risk moves to the setup. In Friday's view, three things should stay in the owner's hands rather than a vendor's or an agency's: the approval rule set, written down and reviewed each quarter; the OAuth session or agent API key, created under a named person who can revoke it; and the record of what the agent did. Stripe's docs point to MCP tool call logs in Workbench. Ask your builder to show you where those logs live before the agent touches a live account. For the other side of agent payments, where an agent buys from merchants, see our note on [Visa Agentic Ready](https://www.doitwithfriday.com/news/visa-agentic-ready/).

A small business with two or three repeated money tasks, such as topping up a bill pay account and preparing a weekly vendor run, may be better served by one narrow agent with a written approval rule than by an agency-run platform account that holds the payments, approvals and logs under the agency's name. If you want that built, [a Stripe MCP connection scoped to your rules](https://www.doitwithfriday.com/services/mcp-tools/) is the kind of work we set up.

## Before you connect an agent to your Treasury account

Stripe Treasury for agents is in public preview, with human approval on by default for refunds, payouts and outbound transfers, and a limit you choose for anything the agent does alone.

Before you connect an agent, write down four things: the dollar limit for unattended transfers, the actions that always need approval, the person who approves, and how you revoke access. Move any full-access secret key, or restricted key without the Agent tag, off Stripe MCP before November 30\. If you want a second pair of eyes on your approval rule set, [send us the rules you plan to use](https://www.doitwithfriday.com/contact/).

Last checked: November 20, 2026, against Stripe's November 19, 2026 announcement of agentic money movement in Stripe Treasury, the Stripe MCP documentation and the Stripe Treasury documentation.

Product details come from Stripe's November 19, 2026 announcement and Stripe's MCP and Treasury documentation, which are the primary sources, checked November 20, 2026\. The agent money movement features are in public preview and can change. Friday has no relationship with Stripe. Statements marked as Friday's view are opinion.