Install
npm install stripeProducts
Stripe, product by product →Stripe ships more than one product — each judged line competes in its own arena on the same stories as everyone else.
| Line | Arena | Rank | PA Score | Agent-ready |
|---|---|---|---|---|
| Payments | Online Payments | #1/10 | 55/100 | 89/100 |
| Terminal | Mobile & In-Person Payments | #1/4 | 32/100 | 59/100 |
| Atlas | Startup Legal & Incorporation | #6/7 | 11/100 | 32/100 |
| Clerkyacquired | Startup Legal & Incorporation | #4/7 | 14/100 | 37/100 |
| Billing | Billing & Subscriptions | #3/7 | 28/100 | 65/100 |
| Metronomeacquired | Billing & Subscriptions | #5/7 | 21/100 | 28/100 |
| Connect | Marketplace & Platform Payments | #2/6 | 31/100 | 65/100 |
| Radar | Payment Fraud Prevention | #2/5 | 22/100 | 50/100 |
| Tax | Sales Tax Automation | #1/6 | 22/100 | 43/100 |
| TaxJaracquired | Sales Tax Automation | #6/6 | 13/100 | 26/100 |
| Issuing | Card Issuing Platforms | #1/5 | 33/100 | 65/100 |
| Treasurythis page | Banking as a Service | #4/6 | 17/100 | 44/100 |
| Identity | Identity Verification & KYC | #3/6 | 24/100 | 47/100 |
| Financial Connections | Banking Data APIs | #4/7 | 22/100 | 54/100 |
| Crypto & Stablecoins | Stablecoin Payments | #6/6 | 19/100 | 39/100 |
| Agentic Commerce | Agentic Commerce | #1/7 | 37/100 | 80/100 |
Not yet judged (10 — no arena where they compete): Invoicing · Capital · Revenue Recognition · Sigma · Data Pipeline · Managed Payments · Lemon Squeezy · Directory · Projects · Climate
Try itExperimental
See what an agent can do with Stripe Treasury before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); the live MCP handshake runs real requests from our edge, right now — including, where the server allows it, one real read-only tool call (bring your own key for auth-gated servers); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si https://api.stripe.com/v1/treasury/financial_accounts | head -4 # Treasury financial-accounts API, keyless → 401recorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Account provisioning — stories about account provisioning in this arenaAccount provisioningevidence →
Stories about account provisioning in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Banking agent access — stories about banking agent access in this arenaBanking agent accessevidence →
Stories about banking agent access in this arena
Banking cards — stories about banking cards in this arenaBanking cardsevidence →
Stories about banking cards in this arena
Banking ledger — stories about banking ledger in this arenaBanking ledgerevidence →
Stories about banking ledger in this arena
Banking onboarding — stories about banking onboarding in this arenaBanking onboardingevidence →
Stories about banking onboarding in this arena
Banking risk controls — stories about banking risk controls in this arenaBanking risk controlsevidence →
Stories about banking risk controls in this arena
Money movement — stories about money movement in this arenaMoney movementevidence →
Stories about money movement in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Sponsor model — stories about sponsor model in this arenaSponsor modelevidence →
Stories about sponsor model in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Stripe Treasury stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Account provisioning — stories about account provisioning in this arenaAccount provisioning
Stories about account provisioning in this arena
Open a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launch
~4/10
The account structure is transparent — whether funds sit in FBO pools or individual accounts, where FDIC insurance actually attaches, and who can see the ledger, all documented plainly
—–
Issue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structure
~5/10
Idle balances can earn — interest-bearing accounts or documented sweep options, with the rate mechanics and who keeps the spread spelled out
—0/10
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Scoped API keys · Machine-readable spec · Versioning policy · API sandbox · Full data export · An agent can operate an account within policy — scoped credentials that let it read balances and initiate transfers under amount caps and counterparty allowlists, a use the vendor documents by name · The product ships its own AI for banking operations — natural-language search over transactions, drafted responses to disputes and alerts, anomaly summaries — built in, not bolted on
Subscribe to events via webhooks
—0/10
Build against official SDKs
~3/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
✓6/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
~4/10
unlocks → Autonomous automations
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
—–
Set up automations that run autonomously in the background
—–
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Banking agent access — stories about banking agent access in this arenaBanking agent access
Stories about banking agent access in this arena
An agent can operate an account within policy — scoped credentials that let it read balances and initiate transfers under amount caps and counterparty allowlists, a use the vendor documents by name
—0/10
An agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboard
~6/10
The product ships its own AI for banking operations — natural-language search over transactions, drafted responses to disputes and alerts, anomaly summaries — built in, not bolted on
—0/10
Banking cards — stories about banking cards in this arenaBanking cards
Stories about banking cards in this arena
Accounts come with cards — issue virtual and physical debit cards tied to the account through the same API, with spend controls and digital wallet support
~4/10
Card and ACH disputes are handled properly — Reg E investigation timelines, provisional credit mechanics, and my operational responsibilities documented and tooled
—–
Banking ledger — stories about banking ledger in this arenaBanking ledger
Stories about banking ledger in this arena
The ledger is real-time and event-driven — balance reads that reflect holds and pending activity, and webhooks for every transaction state change so my system mirrors the bank exactly
~3/10
Transaction data is rich enough to build on — counterparty details, rail-specific metadata, stable identifiers, and enrichment that makes a raw bank feed usable in-product
~3/10
The paper obligations are automated — monthly statements generated per account, and tax documents (1099-INT) produced and retrievable through the API
—–
Banking onboarding — stories about banking onboarding in this arenaBanking onboarding
Stories about banking onboarding in this arena
Customer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application states
—–
Work the onboarding queue — see why an application is pending, supply additional documents, and understand which decisions are mine versus the bank's
—–
Banking risk controls — stories about banking risk controls in this arenaBanking risk controls
Stories about banking risk controls in this arena
Set risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement paths
—0/10
Fraud economics are explicit — who eats ACH return fraud, card disputes, and account takeover losses, with the platform's prevention tooling documented alongside the liability split
—0/10
Growth doesn't hit invisible walls — program-level limits, approval stages, and the path to raising them are documented rather than discovered in an email from the bank
—0/10
Money movement — stories about money movement in this arenaMoney movement
Stories about money movement in this arena
Originate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhooks
—0/10
Checks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paper
—–
The faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documented
—0/10
Money can cross borders — international wires or SWIFT, FX with transparent rates, and the coverage map of currencies and corridors documented
—0/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Sponsor model — stories about sponsor model in this arenaSponsor model
Stories about sponsor model in this arena
Exactly who holds the charter — whether the platform is a bank, a direct program with a named partner bank, or middleware between me and someone else's sponsor — and what happens to my customers if the platform fails
~4/10
The compliance workload is tooled — transaction monitoring, sanctions screening, case management for alerts, and SAR-filing support with a clear split of duties between me, the platform, and the bank
—0/10
The platform ledger reconciles to the bank core — documented daily reconciliation between what the API reports and what the bank holds, the failure that sank Synapse-era programs
—0/10
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 6/10 | Tprobed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Exactly who holds the charter — whether the platform is a bank, a direct program with a named partner bank, or middleware between me and someone else's sponsor — and what happens to my customers if the platform fails C Charter clarity | founder | Sponsor model — stories about sponsor model in this arenaSponsor model | 3 | partial | 4/10 | Xcommunity | |
Open a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launch C Account opening | developer | Account provisioning — stories about account provisioning in this arenaAccount provisioning | 3 | partial | 4/10 | Cclaimed | |
The ledger is real-time and event-driven — balance reads that reflect holds and pending activity, and webhooks for every transaction state change so my system mirrors the bank exactly C Balances events | developer | Banking ledger — stories about banking ledger in this arenaBanking ledger | 3 | partial | 3/10 | Cclaimed | |
An agent can operate an account within policy — scoped credentials that let it read balances and initiate transfers under amount caps and counterparty allowlists, a use the vendor documents by name C Agent operations | ai-native user | Banking agent access — stories about banking agent access in this arenaBanking agent access | 3 | none | 0/10 | ||
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | 0/10 | ||
Originate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhooks C Ach | developer | Money movement — stories about money movement in this arenaMoney movement | 3 | none | 0/10 | ||
The platform ledger reconciles to the bank core — documented daily reconciliation between what the API reports and what the bank holds, the failure that sank Synapse-era programs C Reconciliation | finance lead | Sponsor model — stories about sponsor model in this arenaSponsor model | 3 | none | 0/10 | ||
Customer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application states C Kyc kyb | developer | Banking onboarding — stories about banking onboarding in this arenaBanking onboarding | 3 | none | untested | none yet | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
The account structure is transparent — whether funds sit in FBO pools or individual accounts, where FDIC insurance actually attaches, and who can see the ledger, all documented plainly C Fbo structures | finance lead | Account provisioning — stories about account provisioning in this arenaAccount provisioning | 3 | none | untested | none yet | |
An agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboard C Agent visibility | ai-native user | Banking agent access — stories about banking agent access in this arenaBanking agent access | 2 | partial | 6/10 | Tprobed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Cclaimed | |
Issue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structure C Virtual accounts | developer | Account provisioning — stories about account provisioning in this arenaAccount provisioning | 2 | partial | 5/10 | Cclaimed | |
Accounts come with cards — issue virtual and physical debit cards tied to the account through the same API, with spend controls and digital wallet support C Card issuance | developer | Banking cards — stories about banking cards in this arenaBanking cards | 2 | partial | 4/10 | Cclaimed | |
Transaction data is rich enough to build on — counterparty details, rail-specific metadata, stable identifiers, and enrichment that makes a raw bank feed usable in-product C Data quality | developer | Banking ledger — stories about banking ledger in this arenaBanking ledger | 2 | partial | 3/10 | Cclaimed | |
Fraud economics are explicit — who eats ACH return fraud, card disputes, and account takeover losses, with the platform's prevention tooling documented alongside the liability split C Loss allocation | finance lead | Banking risk controls — stories about banking risk controls in this arenaBanking risk controls | 2 | none | 0/10 | ||
Growth doesn't hit invisible walls — program-level limits, approval stages, and the path to raising them are documented rather than discovered in an email from the bank C Program scaling | founder | Banking risk controls — stories about banking risk controls in this arenaBanking risk controls | 2 | none | 0/10 | ||
Idle balances can earn — interest-bearing accounts or documented sweep options, with the rate mechanics and who keeps the spread spelled out C Yield | finance lead | Account provisioning — stories about account provisioning in this arenaAccount provisioning | 2 | none | 0/10 | ||
Money can cross borders — international wires or SWIFT, FX with transparent rates, and the coverage map of currencies and corridors documented C International | founder | Money movement — stories about money movement in this arenaMoney movement | 2 | none | 0/10 | ||
Set risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement paths C Limits holds | ops user | Banking risk controls — stories about banking risk controls in this arenaBanking risk controls | 2 | none | 0/10 | ||
The compliance workload is tooled — transaction monitoring, sanctions screening, case management for alerts, and SAR-filing support with a clear split of duties between me, the platform, and the bank C Compliance tooling | ops user | Sponsor model — stories about sponsor model in this arenaSponsor model | 2 | none | 0/10 | ||
The faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documented C Instant rails | developer | Money movement — stories about money movement in this arenaMoney movement | 2 | none | 0/10 | ||
The product ships its own AI for banking operations — natural-language search over transactions, drafted responses to disputes and alerts, anomaly summaries — built in, not bolted on C Builtin ai | ops user | Banking agent access — stories about banking agent access in this arenaBanking agent access | 2 | none | 0/10 | ||
Card and ACH disputes are handled properly — Reg E investigation timelines, provisional credit mechanics, and my operational responsibilities documented and tooled C Disputes | ops user | Banking cards — stories about banking cards in this arenaBanking cards | 2 | none | untested | none yet | |
Checks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paper C Checks | ops user | Money movement — stories about money movement in this arenaMoney movement | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
The paper obligations are automated — monthly statements generated per account, and tax documents (1099-INT) produced and retrievable through the API C Statements | ops user | Banking ledger — stories about banking ledger in this arenaBanking ledger | 2 | none | untested | none yet | |
Work the onboarding queue — see why an application is pending, supply additional documents, and understand which decisions are mine versus the bank's C Review queues | ops user | Banking onboarding — stories about banking onboarding in this arenaBanking onboarding | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 42 stories with headroom
What would move Stripe Treasury’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Money movement — stories about money movement in this arenaOriginate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhooks
nonemoves PA Scoreimpact 30
The evidence describes Treasury's general money-movement objects (OutboundPayment, ReceivedDebit, financial accounts, transactions) but never mentions ACH-specific mechanics like same-day windows, NOCs, or return/reversal objects with webhooks — the core of this story's ask is unaddressed.
Banking agent access — stories about banking agent access in this arenaAn agent can operate an account within policy — scoped credentials that let it read balances and initiate transfers under amount caps and counterparty allowlists, a use the vendor documents by name
nonemoves PA Scoreimpact 30
Missing: documentation of agent-scoped API keys/permissions, amount-cap enforcement, counterparty allowlist controls, and an explicit vendor-named agentic banking use case.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
Missing: any documentation of user-defined conditional rules/triggers, an automation/rules API or webhook-based rule builder, or evidence of event-driven action configuration.
Account provisioning — stories about account provisioning in this arenaThe account structure is transparent — whether funds sit in FBO pools or individual accounts, where FDIC insurance actually attaches, and who can see the ledger, all documented plainly
nonemoves PA Scoreimpact 30
The evidence covers general Treasury features (balances, funding flows, disclosures) but contains no documentation addressing FBO pooling vs individual account structure, where FDIC insurance attaches, or who has ledger visibility — the specific transparency the finance lead is asking about is absent.
Banking onboarding — stories about banking onboarding in this arenaCustomer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application states
nonemoves PA Scoreimpact 30
The evidence pack covers Treasury's account funding, money movement, disclosures, and fraud controls, but never mentions KYC/KYB flows, document collection, watchlist screening, or application state modeling for verifying individuals or businesses onboarding to Treasury.
Sponsor model — stories about sponsor model in this arenaThe platform ledger reconciles to the bank core — documented daily reconciliation between what the API reports and what the bank holds, the failure that sank Synapse-era programs
nonemoves PA Scoreimpact 30
Evidence only shows Stripe Treasury lets platforms reconcile their own internal systems against Treasury's transaction feed (docs-13), not documented evidence that Stripe's ledger itself reconciles daily against the underlying partner bank's core records — the exact failure mode that broke Synapse-era programs.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
No evidence of any data export, data portability tools, or open-format export functionality for Stripe Treasury; docs cover money movement, financial accounts, and compliance but nothing about exporting account/transaction data in open formats or an account-closure export path.
Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product
nonemoves Built-in AIimpact 30
Missing: any mention of AI/ML-driven analytics, insight generation, or in-product suggestions from financial data.
Showing the top 8 of 42 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map6 surfaces · 15 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Treasury docs11 stories
- Open a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launch
- Issue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structure
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- An agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboard
- Accounts come with cards — issue virtual and physical debit cards tied to the account through the same API, with spend controls and digital wallet support
- The ledger is real-time and event-driven — balance reads that reflect holds and pending activity, and webhooks for every transaction state change so my system mirrors the bank exactly
- Transaction data is rich enough to build on — counterparty details, rail-specific metadata, stable identifiers, and enrichment that makes a raw bank feed usable in-product
- Do everything through the API that I can do in the UI
- Exactly who holds the charter — whether the platform is a bank, a direct program with a named partner bank, or middleware between me and someone else's sponsor — and what happens to my customers if the platform fails
llms.txt3 stories
MCP docs3 stories
Stripe CLI docs3 stories
OpenAPI spec2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si https://api.stripe.com/v1/treasury/financial_accounts | head -4 # Treasury financial-accounts API, keyless → 401reproduced$ curl -si https://api.stripe.com/v1/treasury/financial_accounts | head -4 # Treasury financial-accounts API, [redacted]less → 401 HTTP/2 401 server: nginx date: Tue, 15 Sep 2026 09:12:27 GMT content-type: application/json
$curl -sL https://docs.stripe.com/llms.txt | head -3reproduced$ curl -sL https://docs.stripe.com/llms.txt | head -3 # Stripe Documentation When installing Stripe packages, always check the npm registry for the latest version rather than relying on memorized version numbers. Run `npm view stripe version` or check https://www.npmjs.com/package/stripe before pinning a version. For Python, check https://pypi.org/project/stripe/. Never hardcode an old version number from training data — always install with `@latest` or verify the current version first.
$curl -si -X POST https://mcp.stripe.com/ -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # the remote MCP server Stripe documents at docs.stripe.com/mcpreproduced$ curl -si -X POST https://mcp.stripe.com/ -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # the remote MCP server Stripe documents at docs.stripe.com/mcp HTTP/2 401 www-authenticate: Bearer resource_metadata=https://mcp.stripe.com/.well-known/oauth-protected-resource
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
0 of 4 testable claims verified · 3 contradicted → integrity 0/100
14 distinct capability claims found in Stripe Treasury’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
0
Verified
1
Unverified
3
Contradicted
14
Undersold
Unverified (1)
“Financial accounts that hold funds can be created programmatically via a money_manager configuration”
Open a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launchpartialproof ↗
Contradicted (4)
“OutboundPayment objects model push-based transfers from a platform's financial account to a connected account's financial account”
Originate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhooksnoneproof ↗
“Third parties can be authorized to debit funds directly from a financial account”
Originate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhooksnoneproof ↗
“Transactions can be used to build account activity feeds and reconcile against internal systems”
The platform ledger reconciles to the bank core — documented daily reconciliation between what the API reports and what the bank holds, the failure that sank Synapse-era programsnoneproof ↗
“Automatic risk controls reduce fraud exposure across Treasury and Issuing without requiring setup”
Fraud economics are explicit — who eats ACH return fraud, card disputes, and account takeover losses, with the platform's prevention tooling documented alongside the liability splitnoneproof ↗
Undersold (14)
Issue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structurepartialproof ↗
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Operate the product with natural-language commandspartialproof ↗
An agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboardpartialproof ↗
Accounts come with cards — issue virtual and physical debit cards tied to the account through the same API, with spend controls and digital wallet supportpartialproof ↗
The ledger is real-time and event-driven — balance reads that reflect holds and pending activity, and webhooks for every transaction state change so my system mirrors the bank exactlypartialproof ↗
Transaction data is rich enough to build on — counterparty details, rail-specific metadata, stable identifiers, and enrichment that makes a raw bank feed usable in-productpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Exactly who holds the charter — whether the platform is a bank, a direct program with a named partner bank, or middleware between me and someone else's sponsor — and what happens to my customers if the platform failspartialproof ↗
Claims outside our story set (9)
Real capability claims found in Stripe Treasury’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Combines payments and financial accounts so businesses can store, spend, and send money from one place”
source ↗“Financial accounts can hold multiple fiat currency balances (USD, EUR, GBP) and, for eligible businesses, a USDC stablecoin balance”
source ↗“No monthly fees or minimum balance requirements to open or maintain a financial account”
source ↗“Financial accounts can be viewed and managed via the Stripe Dashboard or mobile app”
source ↗“Connect platforms can offer embedded financial services (funds separation/storage, bill pay, cash flow management) to connected accounts”
source ↗“Businesses can store funds, add recipients, and pay contractors and vendors”
source ↗“Financial account features (bill pay, issuing, cash rewards) can be rendered as branded embedded UI without custom coding or compliance review”
source ↗“Platforms can move money from their own payments balance to financial accounts, or from connected accounts' payments balance to their financial accounts”
source ↗“A Treasury disclosure component can be embedded on a website to auto-display up-to-date compliance disclosures”
source ↗
Business model
No published Treasury pricing: marketing says no monthly fees or minimum balances, but platform economics (including an administrative facilitation fee) are negotiated, and access is gated to approved Stripe Connect platforms.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
