Stripe Treasury API
Stripe Treasury REST API — enables platforms to embed financial accounts, money movement (ACH, wire, card), and balance management into their products via Stripe Connect, acting as a BaaS layer.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
SOC2 Type II, PCI-DSS Level 1, ISO 27001. Treasury involves real money movement — Stripe enforces strict security controls. Restricted keys with treasury-only scopes are essential. Connect OAuth provides strong delegation model. Platform approval process provides additional gatekeeping.
⚡ Reliability
Best When
You are building a fintech platform on Stripe Connect and need to offer your users financial accounts, programmatic money movement, or embedded card issuing without becoming a bank.
Avoid When
You are not an approved Stripe Treasury platform, need non-US banking infrastructure, or require banking features outside Stripe's ecosystem.
Use Cases
- • Agents managing financial account balances for platform users — checking available funds before initiating payouts or transfers
- • Automated money movement — agents triggering ACH or wire transfers in response to business events (invoice paid, milestone reached)
- • Reconciliation workflows — agents fetching transaction histories from Treasury financial accounts and matching against internal ledgers
- • Float management — agents monitoring platform-level Treasury balances and triggering top-ups when thresholds are breached
- • Embedded banking onboarding — agents automating KYC/account creation flows for new platform users via Treasury financial account provisioning
Not For
- • Consumer banking applications — Treasury is a B2B BaaS platform for Stripe Connect platforms, not a consumer product
- • Non-Stripe payment stacks — Treasury requires Stripe Connect and is not available as a standalone banking API
- • Crypto or international wire-heavy use cases — Treasury is optimized for US ACH/domestic wires; international money movement needs additional providers
Interface
Authentication
Stripe secret key auth with Stripe Connect OAuth. Platform uses its own secret key; acting on connected accounts requires the Stripe-Account header with the connected account ID. Restricted keys with treasury-specific scopes are strongly recommended for least-privilege access.
Pricing
Requires Stripe Treasury platform approval — not available to all Stripe accounts. Pricing is usage-based per financial transaction. API access itself is free; charges occur on money movement operations.
Agent Metadata
Known Gotchas
- ⚠ Treasury requires platform approval — agents will receive auth errors until the platform account is whitelisted for Treasury access
- ⚠ ACH transfers are not instant — OutboundTransfers settle T+1 to T+3 business days; agents must handle async settlement status via webhooks
- ⚠ Connected account context is required — all Treasury operations must include Stripe-Account header; forgetting this causes confusing errors
- ⚠ Financial account creation requires KYC completion on the connected account — agents cannot create accounts for unverified users
- ⚠ Balance checks must account for pending transactions — available_balance differs from current_balance during in-flight transfers
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Stripe Treasury API.
Scores are editorial opinions as of 2026-03-06.