Stripe announced Stripe Treasury for agents on October 21, 2026. Its announcement describes balance checks, invoice payments, transfers between accounts and currency conversion from agent tools connected through MCP. Card creation and agent spending limits are future additions in that announcement, rather than features to assume are available at launch.
Five Treasury tools, all in public preview
Stripe’s Treasury agent documentation lists five Treasury-specific MCP tools. MCP is the interface through which a compatible agent client calls the provider’s functions.
| Tool | Documented action |
|---|---|
get_balance_summary | Display Stripe and Treasury balances |
convert_currency | Convert currencies within a Treasury account |
send_money | Send to a recipient |
setup_recipient | Configure a recipient account |
transfer_money | Move funds between supported Stripe balances |
Each is labelled public preview. Permissions differ by operation: balance access is read access, while conversion, recipients and outbound movements require their corresponding write permissions. The documentation says live money movement requires review and approval by default.
For an implementation team, that distinction separates a reporting assistant from a payment executor. A useful acceptance test is to ask whether the same client can prepare a payment without releasing it, and which person approves the final instruction. That is an operational check, not evidence that a particular deployment has passed it.
Access belongs to an account and environment
Stripe’s MCP documentation supports OAuth for interactive clients and agent API keys for applications needing persistent access. An OAuth authorization can cover different accounts and permissions in live mode and sandboxes. Administrators can manage access, and authorized sessions can be revoked.
Stripe also sets a migration deadline: by November 30, 2026, MCP clients using full-access secret keys or restricted keys without the Agent tag must move to agent API keys or OAuth. Its documentation says unsupported keys will receive a 401 response from December.
A product launch does not make every Treasury capability available in every country. Stripe maintains a separate money-management availability matrix, with distinct preview and roadmap entries. Teams should check their legal entity, account and intended currency before designing a workflow around a capability.
What this changes for platforms
The practical change is a new place from which treasury instructions can originate. An agent can work inside a business’s operating tools while Stripe exposes the financial functions. The business still needs to distinguish who may view balances, create recipients and approve transfers.
Those roles fit into the wider embedded finance stack. Readers mapping the bank, software platform and customer responsibilities can start with what is a sponsor bank and the Stripe Connect provider profile.
