Stripe Treasury for agents: ChatGPT and Claude can pay invoices

Stripe launched Stripe Treasury for agents on October 21. AI agents like ChatGPT and Claude can now check your balances, pay invoices, move funds between accounts, and convert currencies, all through Stripe's MCP server. Your AI agent just got a bank login. By default, a human approves every live money movement. The real work is deciding when that default changes.

What actually happened

From Stripe's announcement and the Treasury for agents docs:

• The connection: Agents reach Treasury through Stripe's MCP server at mcp.stripe.com. Setup paths exist for Claude Code, Claude Desktop, ChatGPT, Codex, Cursor, and VS Code.
• Five new tools, all public preview: get_balance_summary (read only), plus send_money, setup_recipient, transfer_money, and convert_currency. Four of the five move money or set up where it goes.
• Permissions: You pick which accounts and data the agent sees, whether it can only read or can also act, and when money movement needs human approval. Each tool maps to a specific Stripe permission, such as Money Management Outbound Payments: Write for send_money.
• The default: Per the docs, you must review and approve any agent action that results in live money movement.
• Auth: OAuth for an agent acting as you, or an agent API key for an app that needs its own persistent access. Admins can switch MCP access off for the whole team and revoke sessions in the Dashboard.
• Coming next: Agent-created cards and spending limits for agents, which Stripe says arrive "in the coming weeks."

Stripe's example customer is Kubrio, a one-person company. Its founder runs a morning agent that reports balances, failed payments, and refunds, and plans to let it pay contractors, with the founder approving every payment.

Why Stripe Treasury for agents matters for your business

Reading is the safe win. A daily cash report from get_balance_summary costs nothing in risk. Start there. Most owners check balances in three tabs every morning, and an agent can do it before you wake up.

Recipients are the real attack surface. send_money with approval is fine. setup_recipient is where fraud lives. A poisoned invoice that tricks your agent into adding a new payee turns your next "approve" tap into a wire to a stranger. Keep recipient setup manual.

Approval fatigue is a real failure mode. If the agent asks you 15 times a day, you'll stop reading. Batch payments into one daily review instead of one prompt per invoice.

Use agent keys, not your login. An agent API key can be scoped and revoked without touching your own session. That's the setup you want for anything that runs unattended.

Sources: Stripe: Introducing Stripe Treasury for agents, Stripe Docs: Treasury for agents.