Stripe's November 19, 2026 blog says it is adding the ability for AI assistants connected to Treasury, its business money account, to move money, in public preview. Stripe's agreement says the user is solely responsible for actions an AI agent starts, and its Treasury terms say a transaction that has begun cannot be canceled or reversed. The pages we read do not say which payout price applies.
Stripe, which lets businesses take payments (our short description), says it is adding the ability for AI assistants to move money from Treasury, its business money account. The connection runs through MCP, a standard that lets an assistant use the tools of other products. Think of a bookkeeper's login with a spending limit and a second signer for anything large (our comparison, not Stripe's). Two questions come first: who is responsible for what the assistant does, and can a payment it sends be pulled back?
An AI assistant that can send money raises two questions for an owner, in our framing: who is responsible for what it does, and can a payment it sends be pulled back? The first part of this page sets out what Stripe's terms say about each.
Short on time? Read the two clauses under the first heading, the approvals takeaway, the November 30 note and the four checks.
Status as of November 19, 2026. We fetched Stripe's pages starting at 14:49 PST and tested nothing. We are not lawyers or financial advisers, and we do not advise anyone to use or avoid Stripe or any AI assistant.
Stripe's Treasury documentation lists the United States and the United Kingdom as available, and Australia and Europe as "Private preview (Request access)"; the pages we read do not say whether Treasury for agents is open in each.
Who is responsible for an AI agent's actions, and can a transfer be canceled?
Two clauses answer the two questions: one puts responsibility for an AI agent's actions on the user, and the other says an outbound transaction that has begun cannot be canceled or reversed. Neither clause was written for Treasury for agents as such: the first covers any AI agent and does not mention Treasury, the second covers every outbound transaction and does not mention AI agents. Both apply only to the extent these documents apply to you.
Responsibility. Section 1.7 of Stripe's Services Agreement (General Terms) says that a user who uses an AI agent to access Stripe's services "is solely responsible for each action initiated by or through the AI Agent". The Atlas terms repeat the clause.
Reversibility. Section 3.4 of the Treasury Terms says the user acknowledges that "once an Outbound Transaction has commenced, it cannot be cancelled or reversed", and that Stripe "is under no obligation to attempt to" retrieve the money. Section 3.8 separately lets a user stop a "scheduled or preauthorized" transaction within the timeframe in Stripe's documentation.
Preview. Section 1.4 says that "to the maximum extent permitted by Law" Stripe "provides no warranty, indemnity, or support for Preview Services" (an indemnity is a promise to cover someone's losses; our gloss), and caps its liability for them at "the lesser of" the fees paid in the prior 12 months and USD 1,000. The agreement's definition of "Preview" lists "public preview" among its release phases. No page we read says that this feature is a Preview Service, so applying the clause to it is our reading. The general cap (section 8.4) is the prior 12 months of fees, with exceptions.
What we cannot say. The Treasury Terms incorporate Stripe's Financial Services Terms by reference, and we did not read those or the Privacy Policy. So this page says nothing about who bears the cost if an agent-started transfer goes wrong. Other clauses may bear on this; see How we know.
What did Stripe announce, and when?
Stripe's newsroom item of October 21, 2026 announcing Treasury for agents already says agents "can check balances, pay invoices, transfer funds between accounts, and convert currencies". The blog post of November 19, 2026 says "we're adding write access and customizable controls" (write access: permission to change things, not only look; our gloss) and that the capabilities are "now available in public preview". The pages do not reconcile the two, so we do not call any of it new on November 19.
What can an AI agent do, and who has to say yes?
Stripe's blog describes two ways to connect an assistant to Stripe's MCP server. With OAuth (a sign-in flow), the agent acts as a signed-in person and inherits that person's permissions. With an agent API key (a key made for one agent), it has its own identity, and you set its permissions, expiration date and rotation schedule (how often the key is replaced; our gloss).
In short: the blog says a person approves money-moving actions by default, and the docs add detail, with some differences.
| Question | Stripe's blog | Stripe's docs |
|---|---|---|
| Default approval? | "By default, agent-initiated refunds, payouts, and outbound transfers require human approval" | The approvals page lists six default rules for agent-tagged keys and says you can "modify conditions or designated reviewers for default rules, or delete them" |
| Agent acts as you (OAuth)? | "You need to confirm every action that moves money, including a refund or payout" | "Confirmation depends on the action, not only the tool name". Three of the five Treasury tools carry a "Human confirmation" badge; the tool that sets up a recipient has none |
| Amount rule? | Stripe's example, for agent API keys: an agent "could process an ACH transfer under $50 automatically" | Amount, actor and rate-limit conditions; no default amount printed |
| Who approves, and for how long? | A payment can be routed "to a designated approver" | "A user can't approve their own request." Requests "expire automatically" after 14 days; the MCP page gives 24 hours for a confirmation under user credentials |
The $50 line is Stripe's example, not a default. We do not reconcile the blog's three default actions with the approvals page's six, or the 14-day and 24-hour limits, which belong to different flows.
Can agents issue cards?
The pages disagree. Stripe's Treasury page says agents can "issue cards". The blog lists "including creating cards with spending limits" as next, and the October 21 item said cards would come soon. The April 29, 2026 Sessions recap says it announced agent-ready financial accounts that "create cards". The MCP page lists five Treasury tools, none named for cards.
What does it cost?
Stripe's pricing page prints no agent-specific fee, and no page we read says which row applies to a payment an agent starts. Its Treasury block says "No minimums or monthly fees." The first 50 monthly domestic payouts on local rails (domestic payment networks; our gloss) are "Included with Treasury"; after that, and for currency conversion, the page lists these rows (others are left out):
| Row as printed | Price as printed |
|---|---|
| ACH (next day) | $0.50 per payout |
| ACH (same day) | $1.00 per payout |
| Real time payments (instant) | $2.50 per payout |
| Fedwire | $25.00 per payout |
| Currency conversion | Starting at 0.5% of the converted amount |
ACH and Fedwire are US payment systems (our gloss).
What do the pages leave out?
The pages we read (listed under Sources) do not state:
- which price applies to a payment an agent starts, or any default maximum amount per payment or per day;
- whether adding a payee needs approval (the approvals page does not mention recipients; it lists "Bank account is added, updated or deleted" as an action you can require approval for);
- any agent-specific refund or reimbursement path if an approved or automatic agent payment is wrong.
What is the November 30 date?
Stripe's MCP docs carry a notice headed "Update API key authentication by November 30, 2026". From December, Stripe MCP stops accepting full-access keys and restricted keys without the Agent tag (our gloss: the tag marks a key made for an agent), and the docs say to replace them with newly created agent API keys or reconnect with OAuth. The notice covers anyone connecting through that server, not only Treasury users, and the page prints no date for it.
What can you check this week?
Four checks, in our reading
These are our suggestions, not Stripe's advice and not legal or financial advice.
- Before November 30, 2026, ask whoever connected an assistant to Stripe which method it uses and, if it uses a key, which kind.
- Start with read access (look only) before any write access (change things, including moving money; our gloss).
- Before any write access, write down who approves what: amount rules, named reviewers, and what happens to a request nobody answers. Check which default rules exist on your account, since they can be changed or deleted. On a one-person account, two-party rules apply only to agent-tagged keys.
- Ask Stripe in writing which fee row applies to a payment an agent starts and whether this feature falls under the preview clause. Then read the clauses above with your lawyer or accountant.
Starting at 14:49 PST on November 19, 2026 we loaded the pages under Sources (the Sessions recap at about 15:24) and rendered the pricing page in a browser. We read the blog, newsroom item and docs pages in full, plus the legal clauses cited, their definitions and the Treasury section (searched for agent, AI and MCP), and matched every quote word for word. We did not read the Financial Services Terms, the Privacy Policy, any separate Preview Service Terms, the documentation on stopping payments, the API keys page or the founder guide. We saw only parts of the checking-account agreement and of the regional terms (General Terms section 13, Treasury Terms section 11) and do not analyze them here, nor other Treasury Terms clauses that bear on this (for example section 3.9, "Liability Related to Financial Account Transactions").
Read next
- Our teardown of an ad-running agent
- Our guide to approvals and limits
- The digest of November 19 and the teardowns hub
AI agent development for written approval rules.
Sources
- Stripe blog: Give your agents controlled access to analyze your data and move funds ("November 19, 2026"), read November 19, 2026
- Stripe newsroom: Introducing Stripe Treasury for agents ("October 21, 2026"), read November 19, 2026
- Stripe docs: Treasury for agents (labeled "Public preview"; no date printed), read November 19, 2026
- Stripe docs: Model Context Protocol (MCP) (labeled "Public preview"; no date printed), read November 19, 2026
- Stripe docs: Set up two-party approvals (labeled "Public preview"; no date printed), read November 19, 2026
- Stripe docs: Treasury, availability (no date printed), read November 19, 2026
- Stripe Treasury page (no date or stage label printed), read November 19, 2026
- Stripe pricing page (no date printed; Treasury and Global Payouts blocks, also read rendered in a browser), read November 19, 2026
- Stripe blog: Everything we announced at Sessions 2026 ("April 29, 2026"), read November 19, 2026
- Stripe Services Agreement, General Terms ("Last modified: September 28, 2026"), read November 19, 2026
- Stripe Checking Account Agreement (parts only; "Last updated: September 23, 2026"), read November 19, 2026
- Stripe Service Terms, Stripe Treasury section ("Last updated: September 28, 2026"), read November 19, 2026