Enable Stripe Treasury in your platform settings and ensure your connected accounts have the treasury capability approved via the Accounts API (capabilities: {treasury: {requested: true}})
Create a Financial Account: POST /v1/treasury/financial_accounts with supported_currencies: ['usd'] and optionally features such as inbound_transfers, outbound_payments, and card_issuing enabled
Retrieve the financial account's routing and account numbers via GET /v1/treasury/financial_accounts/{id}/features or the financial_addresses array on the FinancialAccount object for inbound ACH or wire setup
Initiate an OutboundPayment to an external bank account: POST /v1/treasury/outbound_payments with financial_account, amount in cents, currency, destination_payment_method_data (type: 'us_bank_account' with routing/account numbers), and statement_descriptor
Monitor financial account activity via GET /v1/treasury/transactions and subscribe to treasury.outbound_payment.* and treasury.inbound_transfer.* webhook events
Known gotchas
Stripe Treasury is only available to platforms using Stripe Connect; you cannot use Treasury on a standalone account without the Connect platform structure
Financial account features (e.g. outbound_payments, card_issuing) must be explicitly requested and approved; attempting to use an unapproved feature returns a capability error
OutboundPayment to a new bank account may be subject to a short delay for fraud review; do not assume immediate processing and always build status-based logic rather than time-based assumptions
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?