Stripe Treasury vs Treasury Prime

Account opening

1. developerOpen a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launch

   weight 3 · round to Treasury Prime
   Stripe Treasury~partialclaimed4/10

   Docs confirm financial accounts can be created and funded via API (money_manager configuration, OutboundPayments, Connect flows), but the evidence pack never states that these accounts are FDIC-insured deposit accounts, nor does it mention any sandbox/test-mode parity for the Treasury account-opening flow. missing for 10: explicit FDIC/insurance documentation, sandbox-vs-production parity evidence, full automated 'application to active account' onboarding details.

   • [claimed-docs] “A financial account can hold fiat balances such as USD, EUR, and GBP, and eligible businesses can also hold a stablecoin balance in USDC.”
   • [claimed-docs] “Create financial accounts that can hold funds (`money_manager` configuration)”
   • [claimed-docs] “As the platform, you can move money from your payments [Balance] to your financial accounts or from your connected accounts’ payments balanc…”
   • [claimed-docs] “There are no monthly fees or minimum balance requirements to open or maintain a financial account.”

   proof ↗⚑ flag

   Treasury Prime~partialclaimed7/10

   Docs show a clear API-driven account opening flow (Person → Business → Account Application) with KYC/KYB integration, plus a Developer Sandbox with API keys and Postman collection for pre-launch testing (treasury-prime-docs-4, treasury-prime-docs-5, treasury-prime-docs-1, treasury-prime-docs-12). However, there is no explicit documentation confirming FDIC/NCUA deposit insurance status or an end-to-end 'application to active account' status confirmation step, and no independent/hands-on corroboration of sandbox-to-production parity. Missing for 10: explicit insured-deposit language, documented account-activation/status lifecycle, and third-party verification of sandbox parity.

   • [claimed-docs] “create a free Developer Sandbox account. This provides access to the Developer Sandbox where you can create and manage API keys, and safely …”
   • [claimed-docs] “To apply to open a new bank account 1. Create a Person Application 2. Create a Business Application ... 5. Create an Account Application”
   • [claimed-docs] “Programs can seamlessly integrate their bank-approved third-party KYC/KYB vendor into the account opening process.”
   • [claimed-docs] “you can do your testing as in command line or using our Postman Collection to speed up your initial exploration of our APIs.”

   proof ↗⚑ flag

Fbo structures

1. finance leadThe 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

   weight 3 · round drawn
   Stripe Treasury—none0/10

   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.

   ⚑ flag

   Treasury Prime—none0/10

   The evidence covers account creation, KYC, ACH/wire/book transfers, and statements, but nowhere documents FBO pool vs individual account structure, where FDIC insurance attaches, or who can view the ledger. This is a fair and material question for a banking-as-a-service platform, so the axis applies, but no supporting evidence exists.

   ⚑ flag

Virtual accounts

1. developerIssue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structure

   weight 2 · round to Stripe Treasury
   Stripe Treasury~partialclaimed5/10

   Docs confirm Stripe Treasury lets platforms create per-connected-account financial accounts (money_manager configuration) that can hold funds, move money, and be used for reconciliation via transactions/activity feeds — supporting sub-account and per-customer account provisioning at scale. However, the evidence never explicitly confirms that each financial account gets unique account and routing numbers, nor details on bulk/programmatic issuance mechanics beyond account creation. Missing for 10: explicit documentation of unique account/routing number assignment per financial account, and evidence of scale/bulk provisioning workflows or API rate/volume specifics.

   • [claimed-docs] “Create financial accounts that can hold funds (`money_manager` configuration)”
   • [claimed-docs] “As the platform, you can move money from your payments [Balance] to your financial accounts or from your connected accounts’ payments balanc…”
   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”
   • [claimed-docs] “allows Connect platforms to offer financial services, such as funds separation and storage, bill pay, and cash flow management, to eligible …”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   Evidence confirms Treasury Prime supports creating bank accounts via Person/Business/Account Applications and listing accounts, but there is no mention of issuing unique routing numbers, virtual accounts for reconciliation, or sub-account/master-account hierarchies anywhere in the docs pack. Since Treasury Prime is a banking-as-a-service platform, this capability is a fair and expected axis, but no evidence substantiates it here.

   • [claimed-docs] “Get a list of all the available accounts using the `account` endpoint.”
   • [claimed-docs] “To apply to open a new bank account 1. Create a Person Application 2. Create a Business Application ... 5. Create an Account Application”

   proof ↗⚑ flag

Yield

1. finance leadIdle balances can earn — interest-bearing accounts or documented sweep options, with the rate mechanics and who keeps the spread spelled out

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The evidence pack describes Treasury's account-holding, fund-movement, disclosure, and fraud-control features but contains no mention of interest-bearing balances, sweep programs, yield rates, or how any spread is split between Stripe/partner banks and the customer. Since financial-account products could plausibly offer this, the axis applies, but there is no evidence it delivers it.

   • [claimed-docs] “A financial account can hold fiat balances such as USD, EUR, and GBP, and eligible businesses can also hold a stablecoin balance in USDC.”
   • [claimed-docs] “There are no monthly fees or minimum balance requirements to open or maintain a financial account.”
   • [claimed-docs] “As the platform, you can move money from your payments [Balance] to your financial accounts or from your connected accounts’ payments balanc…”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   No evidence pack item mentions interest-bearing accounts, sweep programs, yield/rate mechanics, or spread-sharing arrangements for idle balances; documentation covers account opening, ACH/wire/book transfers, KYC, and statements only.

   ⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Treasury Prime
   Stripe Treasury✓fullprobed8/10

   Stripe's shared docs platform confirms llms.txt exists at docs.stripe.com/llms.txt (HTTP 200) and per-page markdown versions (e.g., treasury.md) are served for agent consumption, which covers Treasury docs. Missing for 10: Treasury-specific llms.txt content (rather than site-wide) and independent confirmation an agent has successfully used it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/treasury.md # Treasury Learn how to securely manage money with a financial account. Loo…”

   proof ↗⚑ flag

   Treasury Prime✓fullprobed9/10

   A probe confirms Treasury Prime hosts a valid llms.txt file returning HTTP 200 with structured links to its developer docs, directly satisfying the story of pointing an agent at an llms.txt/agent-oriented doc index. Missing for 10: no independent third-party confirmation of agent usage or OpenAPI spec discoverability (openapi.json probes 404).

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.treasuryprime.com/llms.txt # Treasury Prime Developer Documentation - [Getting Started](https://do…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.treasuryprime.com/openapi.json, https://docs.treasuryprime.com/swagger.json, https://do…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Treasury Prime
   Stripe Treasury~partialprobed3/10

   Treasury is exposed as a set of API objects (financial accounts, OutboundPayments, transactions) that can in principle be scripted/automated, and Stripe provides an official CLI, implying headless/API-driven usage is possible. However there is no evidence specifically addressing running Treasury in CI pipelines or headless automation workflows. missing for 10: explicit CI/automation documentation, examples of scripted/headless Treasury operations, evidence of CLI use for Treasury objects specifically.

   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [claimed-docs] “OutboundPayment objects represent push-based transfers from: A platform’s financial accounts to a financial account owned by connected accou…”
   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”

   proof ↗⚑ flag

   Treasury Prime~partialprobed4/10

   Treasury Prime is an API-first banking platform, so its REST API can be called headlessly/in CI via HTTP Basic Auth (sandbox + ping/account endpoints, command-line or Postman testing), which supports automation-style usage. However there is no evidence of CI-specific tooling, an official SDK/CLI, webhooks for async automation, or a public OpenAPI spec (probe found 404s), so full headless/CI suitability is not demonstrated. Missing for 10: official CLI/SDK for CI pipelines, documented OpenAPI/machine-readable spec, CI examples or automation guides, and evidence of non-interactive auth flows beyond basic API key testing.

   • [claimed-docs] “Call the `ping` endpoint using HTTP Basic Auth, providing your API Key ID as the username, and the API Secret Key as the password.”
   • [claimed-docs] “you can do your testing as in command line or using our Postman Collection to speed up your initial exploration of our APIs.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.treasuryprime.com/openapi.json, https://docs.treasuryprime.com/swagger.json, https://do…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Stripe Treasury
   Stripe Treasury✓fullprobed6/10

   Stripe documents an official MCP server at docs.stripe.com/mcp, which spans Stripe's platform including Treasury APIs, though Treasury-specific MCP tooling isn't separately detailed. Missing for 10: Treasury-specific MCP tool examples, independent/hands-on confirmation of MCP server usage with Treasury endpoints.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   Treasury Prime is a banking-as-a-service API platform; no evidence of an official MCP server or agent-connectivity offering is present in the evidence pack, only REST API docs.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.treasuryprime.com/llms.txt # Treasury Prime Developer Documentation - [Getting Started](https://do…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.treasuryprime.com/openapi.json, https://docs.treasuryprime.com/swagger.json, https://do…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Stripe Treasury
   Stripe Treasury✓fullprobed7/10

   Stripe documents an official CLI at docs.stripe.com/stripe-cli, which applies platform-wide including Treasury's API. missing for 10: Treasury-specific CLI examples/workflows and independent hands-on confirmation of CLI usage with Treasury endpoints.

   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   Treasury Prime is a banking-as-a-service API platform; no evidence of an official CLI tool exists—only mentions of API testing via command line (curl) or Postman, not a dedicated CLI product. No CLI documentation, package, or download is referenced anywhere in the evidence.

   • [claimed-docs] “you can do your testing as in command line or using our Postman Collection to speed up your initial exploration of our APIs.”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Stripe Treasury✓fullprobed8/10

   Stripe Treasury is accessed entirely through Stripe's documented REST API (financial accounts, OutboundPayments, transactions, received debits, etc.), with machine-readable docs (.md endpoints, llms.txt) and an official CLI, indicating a mature, documented public API surface suitable for AI-native/agentic consumption. Missing for 10: no discoverable OpenAPI/swagger spec was found (404s), and no independent hands-on developer report specifically validating AI-driven API usage.

   • [claimed-docs] “Create financial accounts that can hold funds (`money_manager` configuration)”
   • [claimed-docs] “OutboundPayment objects represent push-based transfers from: A platform’s financial accounts to a financial account owned by connected accou…”
   • [claimed-docs] “You can authorize third parties to debit funds from a financial account.”
   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/treasury.md # Treasury Learn how to securely manage money with a financial account. Loo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Treasury Prime✓fullprobed8/10

   Treasury Prime is fundamentally an API-first banking platform with extensive documented REST endpoints (accounts, ACH, wires, book transfers, KYC, applications), Basic Auth API keys, a free Developer Sandbox, and a Postman collection for testing — clearly enabling programmatic, AI-native usage. Missing for 10: a discoverable machine-readable OpenAPI/swagger spec (probe returned 404s) and independent/hands-on corroboration beyond vendor docs.

   • [claimed-docs] “create a free Developer Sandbox account. This provides access to the Developer Sandbox where you can create and manage API keys, and safely …”
   • [claimed-docs] “Call the `ping` endpoint using HTTP Basic Auth, providing your API Key ID as the username, and the API Secret Key as the password.”
   • [claimed-docs] “Get a list of all the available accounts using the `account` endpoint.”
   • [claimed-docs] “you can do your testing as in command line or using our Postman Collection to speed up your initial exploration of our APIs.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.treasuryprime.com/llms.txt # Treasury Prime Developer Documentation - [Getting Started](https://do…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.treasuryprime.com/openapi.json, https://docs.treasuryprime.com/swagger.json, https://do…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The evidence pack contains no mention of scoped or restricted API keys, OAuth scopes, or any mechanism for issuing least-privilege credentials for agents within Stripe Treasury's documentation or community discussion. While such a capability is plausible for an API-driven financial product, nothing in the provided evidence demonstrates it.

   ⚑ flag

   Treasury Prime—none0/10

   Evidence shows Treasury Prime issues API Key ID/Secret Key pairs via HTTP Basic Auth for sandbox and production access, but there is no mention of scopes, roles, permission levels, or least-privilege credential configuration, nor anything AI-agent-specific.

   • [claimed-docs] “create a free Developer Sandbox account. This provides access to the Developer Sandbox where you can create and manage API keys, and safely …”
   • [claimed-docs] “Call the `ping` endpoint using HTTP Basic Auth, providing your API Key ID as the username, and the API Secret Key as the password.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Stripe Treasury
   Stripe Treasury~partialprobed3/10

   The evidence pack only hints at an SDK ecosystem via a stray note about checking npm registry for 'Stripe packages' (stripe-treasury-probe-1); there is no dedicated documentation of official SDKs, language coverage, or Treasury-specific SDK usage. Missing for 10: explicit official SDK docs (e.g., stripe-node, stripe-python), Treasury-specific SDK code samples, and independent corroboration of SDK quality/coverage.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   The evidence pack covers REST API endpoints, a Postman collection, and a sandbox, but contains no mention of official client SDKs in any language, and OpenAPI spec probes all returned 404s. Missing for 10: any documented official SDK (e.g., Python, Node, Java client libraries), SDK installation/usage guides, or GitHub SDK repos.

   • [claimed-docs] “you can do your testing as in command line or using our Postman Collection to speed up your initial exploration of our APIs.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.treasuryprime.com/openapi.json, https://docs.treasuryprime.com/swagger.json, https://do…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The evidence pack describes Treasury's financial-account features, money movement, and transaction tracking but never mentions webhooks, event objects, or event subscription mechanisms for Treasury activity. missing for 10: any documentation of Treasury-specific webhook events, event types (e.g., financial_account.updated, treasury.*), or subscription setup instructions.

   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”
   • [claimed-docs] “Stripe runs automatic risk controls that help reduce your fraud exposure within Treasury and Issuing without requiring action to enable.”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   The evidence pack covers onboarding, KYC, ACH, wires, book transfers, and account statements, but contains no mention of webhooks or event subscription mechanisms anywhere in the docs or probes. Since webhook support is a plausible and common feature for a banking-as-a-service API platform, its complete absence from the evidence means the story is unmet rather than out-of-scope.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Stripe Treasury—none0/10

   Evidence covers Treasury's banking-as-a-service features (financial accounts, payments, disclosures, fraud controls) but nothing about AI-generated insights or suggestions surfaced from user data within the product. missing for 10: any mention of AI/ML-driven analytics, insight generation, or in-product suggestions from financial data.

   ⚑ flag

   Treasury Prime—none0/10

   No evidence of AI-generated insights, analytics, or suggestions surfaced within the product; documentation covers banking-as-a-service APIs (accounts, ACH, wires, KYC) but nothing about AI-driven data insights.

   ⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Treasury Prime—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round to Stripe Treasury
   Stripe Treasury~partialprobed4/10

   The only agenticness-relevant evidence is a probe confirming Stripe hosts an official MCP server (docs.stripe.com/mcp), which could in principle let an AI agent issue natural-language-driven commands against Stripe APIs, but no evidence ties this specifically to Treasury operations (financial accounts, OutboundPayments, etc.) or shows a working example of natural-language control of Treasury features. Missing for 10: Treasury-specific MCP tool coverage, documented natural-language examples/use cases, and independent confirmation that Treasury actions can be driven conversationally.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Treasury Prime
   Stripe Treasury—none0/10

   The evidence pack includes general Treasury docs, llms.txt/docs-md probes, and CLI/MCP mentions, but nothing describes an interactive API reference with runnable/executable code examples for Treasury endpoints. The openapi.json probe even returned 404, suggesting no discoverable spec-driven reference was found in this pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/treasury.md # Treasury Learn how to securely manage money with a financial account. Loo…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”

   proof ↗⚑ flag

   Treasury Prime~partialprobed4/10

   Docs mention a Postman Collection and sandbox for testing API calls, which offers some runnable-example capability, but there's no evidence of an interactive in-browser API reference (e.g., Swagger/OpenAPI explorer) — a probe for openapi.json/swagger.json returned 404s. missing for 10: interactive embedded API reference UI, OpenAPI/Swagger spec, in-browser runnable code snippets.

   • [claimed-docs] “you can do your testing as in command line or using our Postman Collection to speed up your initial exploration of our APIs.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.treasuryprime.com/openapi.json, https://docs.treasuryprime.com/swagger.json, https://do…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The evidence pack explicitly probes for an OpenAPI/Swagger spec at all standard locations and finds only 404s, and no other evidence pack item links to a downloadable machine-readable API spec for Treasury; the docs offer markdown/llms.txt versions but not a formal OpenAPI schema.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   Probe explicitly checked common OpenAPI/swagger paths and all returned 404, and no docs reference a downloadable machine-readable spec (only a Postman Collection is mentioned, which is not OpenAPI/equivalent).

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.treasuryprime.com/openapi.json, https://docs.treasuryprime.com/swagger.json, https://do…”
   • [claimed-docs] “you can do your testing as in command line or using our Postman Collection to speed up your initial exploration of our APIs.”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Treasury Prime
   Stripe Treasury—none0/10

   Stripe generally offers test-mode/sandbox environments across its API, but no evidence in this pack specifically documents a Treasury sandbox or test-mode capability that isolates test data from production for financial account testing. Missing for 10: any documentation of Treasury-specific test mode, sandbox API keys, or test financial accounts.

   ⚑ flag

   Treasury Prime✓fullclaimed8/10

   Treasury Prime provides a free Developer Sandbox for creating API keys and testing endpoints (ping, accounts) separately from production, plus a documented "Testing in Sandbox" guide with a Postman Collection for exploration. This directly enables development/testing without touching production data. Missing for 10: independent/hands-on confirmation of sandbox fidelity and explicit documentation of sandbox-to-production promotion workflow.

   • [claimed-docs] “create a free Developer Sandbox account. This provides access to the Developer Sandbox where you can create and manage API keys, and safely …”
   • [claimed-docs] “Call the `ping` endpoint using HTTP Basic Auth, providing your API Key ID as the username, and the API Secret Key as the password.”
   • [claimed-docs] “Get a list of all the available accounts using the `account` endpoint.”
   • [claimed-docs] “you can do your testing as in command line or using our Postman Collection to speed up your initial exploration of our APIs.”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Stripe Treasury—none0/10

   No evidence pack items mention API versioning schemes or a documented deprecation policy for Stripe Treasury's APIs; docs cover product features, and probes find no OpenAPI spec, changelog, or version policy reference.

   ⚑ flag

   Treasury Prime—none0/10

   No evidence of API versioning scheme or a documented deprecation policy anywhere in the docs; OpenAPI spec probes all 404, and no changelog or version-lifecycle documentation is cited.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.treasuryprime.com/openapi.json, https://docs.treasuryprime.com/swagger.json, https://do…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The evidence pack describes individual Treasury operations (fund accounts, outbound payments, received debits, transactions) but contains no mention of batch/bulk endpoints or multi-item operations for AI-native or programmatic bulk processing.

   ⚑ flag

   Treasury Prime—none0/10

   No evidence of any batch/bulk endpoints (e.g., bulk ACH, bulk transfers, or list-mutation APIs) in the docs pack; all endpoints described are single-item (single account, single ACH, single wire). Bulk operations are a plausible axis for a banking API platform, so absence of evidence yields 'none'.

   • [claimed-docs] “An ACH credit is used when you wish to send or "push" funds to a recipient. ... An ACH debit is used when you wish to "pull" funds from an e…”
   • [claimed-docs] “You can track the progress of a wire by checking the `status` attribute on the Wire Transfer object.”
   • [claimed-docs] “A book transfer is an electronic funds transfer between two accounts at the same bank... Book transfers are the fastest and cheapest type of…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Stripe Treasury—none0/10

   The evidence pack covers financial-account creation, fund movement, transactions, and fraud controls, but nowhere describes a rules engine or event-triggered automation (e.g., 'if X happens, do Y automatically') configurable by users; automatic risk controls are pre-set by Stripe, not user-defined rules. Missing for 10: any documentation of user-defined conditional rules/triggers, an automation/rules API or webhook-based rule builder, or evidence of event-driven action configuration.

   • [claimed-docs] “Stripe runs automatic risk controls that help reduce your fraud exposure within Treasury and Issuing without requiring action to enable.”
   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   Treasury Prime's evidence pack covers account opening, KYC, ACH/wire/book transfers, and sandbox testing, but contains no mention of webhooks, event subscriptions, or a rules/automation engine that lets users define triggers for automatic actions. Given BaaS platforms commonly expose event-driven webhooks, this axis is a fair question, but no supporting evidence exists in the pack.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Treasury Prime—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Agent operations

1. ai-native userAn 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

   weight 3 · round drawn
   Stripe Treasury—none0/10

   The evidence pack documents Treasury's financial-account, Connect, and OutboundPayment features and even an MCP server listing, but nothing describes scoped credentials for agents with amount caps or counterparty allowlists, nor any vendor-named 'agent banking' use case. missing for 10: documentation of agent-scoped API keys/permissions, amount-cap enforcement, counterparty allowlist controls, and an explicit vendor-named agentic banking use case.

   • [claimed-docs] “OutboundPayment objects represent push-based transfers from: A platform’s financial accounts to a financial account owned by connected accou…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   The evidence pack shows standard API key auth (API Key ID/Secret) and general account/transfer endpoints, but nothing about scoped credentials, per-transaction amount caps, counterparty allowlists, or any agent/AI-specific access model documented by name. This is a fair axis for a banking API platform, but no evidence supports it.

   • [claimed-docs] “Call the `ping` endpoint using HTTP Basic Auth, providing your API Key ID as the username, and the API Secret Key as the password.”
   • [claimed-docs] “Get a list of all the available accounts using the `account` endpoint.”
   • [claimed-docs] “An ACH credit is used when you wish to send or "push" funds to a recipient. ... An ACH debit is used when you wish to "pull" funds from an e…”
   • [claimed-docs] “You can track the progress of a wire by checking the `status` attribute on the Wire Transfer object.”
   • [claimed-docs] “A book transfer is an electronic funds transfer between two accounts at the same bank... Book transfers are the fastest and cheapest type of…”

   proof ↗⚑ flag

Agent visibility

1. ai-native userAn agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboard

   weight 2 · round to Stripe Treasury
   Stripe Treasury~partialprobed6/10

   Stripe Treasury exposes a documented API for financial accounts, transactions, outbound/inbound payments, and received debits (docs-2,7,10,11,13), and Stripe has an official MCP server (probe-4), giving agents programmatic access without dashboard scraping. However, no evidence covers document retrieval (e.g., statements) via API/MCP, and no OpenAPI spec was found (probe-3), and it's unclear the MCP surface specifically exposes Treasury endpoints. Missing for 10: explicit document/statement API coverage, confirmation that the MCP server exposes Treasury-specific resources, and independent hands-on confirmation of MCP usage for banking data.

   • [claimed-docs] “A financial account can hold fiat balances such as USD, EUR, and GBP, and eligible businesses can also hold a stablecoin balance in USDC.”
   • [claimed-docs] “Create financial accounts that can hold funds (`money_manager` configuration)”
   • [claimed-docs] “OutboundPayment objects represent push-based transfers from: A platform’s financial accounts to a financial account owned by connected accou…”
   • [claimed-docs] “You can authorize third parties to debit funds from a financial account.”
   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   Treasury Prime~partialprobed5/10

   Treasury Prime offers a clean REST API to list accounts, transactions, ACH/wire/book transfers, and statements, avoiding screen-scraping, and provides an llms.txt for AI discoverability. However, there is no evidence of a documented MCP server, no consolidated 'pending activity' or document-retrieval endpoint explicitly described, and the OpenAPI spec probe returned 404s, suggesting no easily machine-consumable schema for agents. Missing for 10: an official MCP surface or agent-native integration, explicit endpoints for pending transactions/documents, and a working OpenAPI/swagger spec for automated discovery.

   • [claimed-docs] “Get a list of all the available accounts using the `account` endpoint.”
   • [claimed-docs] “You can track the progress of a wire by checking the `status` attribute on the Wire Transfer object.”
   • [claimed-docs] “Generate and retrieve branded monthly account statements for your customers.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.treasuryprime.com/llms.txt # Treasury Prime Developer Documentation - [Getting Started](https://do…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.treasuryprime.com/openapi.json, https://docs.treasuryprime.com/swagger.json, https://do…”

   proof ↗⚑ flag

Builtin ai

1. ops userThe 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

   weight 2 · round drawn
   Stripe Treasury—none0/10

   No evidence in the pack describes built-in AI features for banking operations—no natural-language transaction search, no drafted dispute/alert responses, no anomaly summaries. The documentation only covers financial account management, connect integrations, fraud risk controls (automatic, non-AI-described), and money movement, none of which mention AI/LLM-based ops tooling. Missing for 10: any mention of natural-language search, AI-drafted dispute responses, anomaly summaries, or any AI/ML-powered ops feature.

   • [claimed-docs] “Stripe runs automatic risk controls that help reduce your fraud exposure within Treasury and Issuing without requiring action to enable.”
   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   No evidence of any built-in AI features for banking operations—no natural-language transaction search, dispute/alert response drafting, or anomaly summaries are mentioned anywhere in the docs pack, which instead covers standard banking-as-a-service API functionality (accounts, ACH, wires, KYC).

   ⚑ flag

Card issuance

1. developerAccounts come with cards — issue virtual and physical debit cards tied to the account through the same API, with spend controls and digital wallet support

   weight 2 · round to Stripe Treasury
   Stripe Treasury~partialclaimed4/10

   Evidence confirms Stripe Issuing is integrated alongside Treasury (fraud controls cover 'Treasury and Issuing', and embedded UI can render 'bill pay, issuing, and cash rewards'), implying cards can be tied to Treasury financial accounts, but no documentation details virtual/physical card issuance flow, spend controls, or digital wallet support specifically for Treasury accounts. Missing for 10: explicit docs on issuing virtual/physical cards via API tied to a Treasury account, spend-control configuration, and digital wallet (Apple/Google Pay) provisioning details.

   • [claimed-docs] “Render Stripe financial account features such as bill pay, issuing, and cash rewards as a branded UI in your platform application while avoi…”
   • [claimed-docs] “Stripe runs automatic risk controls that help reduce your fraud exposure within Treasury and Issuing without requiring action to enable.”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   The evidence pack covers account opening, KYC, ACH, wire, book transfers, and cash deposits, but contains no mention of debit card issuance, physical/virtual cards, spend controls, or digital wallet support anywhere in the docs or probes.

   ⚑ flag

Disputes

1. ops userCard and ACH disputes are handled properly — Reg E investigation timelines, provisional credit mechanics, and my operational responsibilities documented and tooled

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The evidence pack covers Treasury's account structure, connect integration, money movement, and fraud controls, but contains no mention of dispute handling, Reg E investigation timelines, provisional credit mechanics, or documented operational responsibilities for card/ACH disputes.

   ⚑ flag

   Treasury Prime—none0/10

   Evidence covers ACH/wire/book transfer mechanics and returns but contains no mention of Reg E dispute investigation timelines, provisional credit mechanics, or documented ops responsibilities for card/ACH disputes.

   ⚑ flag

Balances events

1. developerThe 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

   weight 3 · round to Stripe Treasury
   Stripe Treasury~partialclaimed3/10

   Docs mention using 'transactions' to build account activity feeds and reconcile against internal systems, implying a transaction-log based ledger, but there is no explicit documentation of webhook events for transaction state changes or of balance reads that reflect holds/pending activity as described in the story. missing for 10: explicit webhook event types for Treasury transaction lifecycle, documentation of balance fields showing holds/pending vs settled amounts, and any independent/hands-on confirmation of real-time event delivery.

   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   The evidence pack shows account, ACH, wire, and book-transfer status fields (e.g., wire 'status' attribute) but contains no mention of webhooks, event notifications, or real-time balance/hold semantics reflecting pending activity — core to this story. missing for 10: webhook/event API docs, balance endpoint showing holds/pending distinctions, any real-time push notification mechanism.

   • [claimed-docs] “You can track the progress of a wire by checking the `status` attribute on the Wire Transfer object.”
   • [claimed-docs] “Get a list of all the available accounts using the `account` endpoint.”
   • [claimed-docs] “An ACH credit is used when you wish to send or "push" funds to a recipient. ... An ACH debit is used when you wish to "pull" funds from an e…”

   proof ↗⚑ flag

Data quality

1. developerTransaction 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

   weight 2 · round to Treasury Prime
   Stripe Treasury~partialclaimed3/10

   Docs mention that Treasury transactions can be used to build account activity feeds and reconcile against internal systems, implying transaction records exist, but there is no detail on counterparty data, rail-specific metadata, stable identifiers, or enrichment fields. missing for 10: documentation of transaction object schema (counterparty fields, rail metadata like ACH/wire trace numbers, stable IDs), examples of enrichment/categorization, independent developer corroboration of usability of raw feed data.

   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”

   proof ↗⚑ flag

   Treasury Prime~partialclaimed4/10

   Docs describe transaction types (ACH credit/debit, wire with status tracking, book transfers) and basic account data, implying some structured metadata exists, but there is no explicit documentation of counterparty detail fields, rail-specific metadata enrichment, or stable identifier schemes that would let a developer build rich in-product transaction views. missing for 10: explicit counterparty/beneficiary data fields, rail-specific metadata (e.g., ACH company entry description, wire OBI/BBI fields), stable identifier documentation, and any enrichment/categorization features.

   • [claimed-docs] “An ACH credit is used when you wish to send or "push" funds to a recipient. ... An ACH debit is used when you wish to "pull" funds from an e…”
   • [claimed-docs] “You can track the progress of a wire by checking the `status` attribute on the Wire Transfer object.”
   • [claimed-docs] “A book transfer is an electronic funds transfer between two accounts at the same bank... Book transfers are the fastest and cheapest type of…”
   • [claimed-docs] “To return an ACH transfer you originated, use the Update an ACH endpoint.”

   proof ↗⚑ flag

Statements

1. ops userThe paper obligations are automated — monthly statements generated per account, and tax documents (1099-INT) produced and retrievable through the API

   weight 2 · round to Treasury Prime
   Stripe Treasury—none0/10

   No evidence in the pack mentions monthly statement generation or 1099-INT tax document production/retrieval via API for Treasury financial accounts; docs cover fund movement, disclosures, fraud controls, and connect features but not statements or tax forms.

   ⚑ flag

   Treasury Prime~partialclaimed4/10

   Monthly account statements are documented as generated and retrievable via API ("Generate and retrieve branded monthly account statements"), but there is no evidence of 1099-INT tax document generation or retrieval anywhere in the pack. missing for 10: 1099-INT tax document generation/retrieval via API, any tax-reporting endpoint documentation, independent confirmation of statement/tax automation in production.

   • [claimed-docs] “Generate and retrieve branded monthly account statements for your customers.”

   proof ↗⚑ flag

Kyc kyb

1. developerCustomer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application states

   weight 3 · round to Treasury Prime
   Stripe Treasury—none0/10

   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. This is a fair axis for a banking product since Treasury requires verified connected accounts, but no supporting evidence exists here.

   ⚑ flag

   Treasury Prime~partialclaimed6/10

   Docs confirm a programmatic application flow (Person/Business/Account Application) and third-party KYC/KYB vendor integration, plus an Incremental KYC mode that runs KYC outside account opening — supporting the core 'programmatic verification' story. However, evidence does not show explicit document collection endpoints, watchlist screening details, or a full state-machine model of application statuses. missing for 10: explicit document upload/collection API details, watchlist/OFAC screening specifics, documented application state enumeration and transitions.

   • [claimed-docs] “To apply to open a new bank account 1. Create a Person Application 2. Create a Business Application ... 5. Create an Account Application”
   • [claimed-docs] “Programs can seamlessly integrate their bank-approved third-party KYC/KYB vendor into the account opening process.”
   • [claimed-docs] “Incremental KYC lets you run KYC **without opening an account**.”

   proof ↗⚑ flag

Review queues

1. ops userWork the onboarding queue — see why an application is pending, supply additional documents, and understand which decisions are mine versus the bank's

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The evidence pack covers financial account creation, money movement, disclosures, and fraud controls, but contains no mention of an onboarding queue, reasons for pending applications, document collection workflows, or a clear delineation between platform/ops decisions and the partner bank's decisions. This is a plausible axis for a banking-as-a-service product, but nothing in the docs or community evidence addresses it.

   ⚑ flag

   Treasury Prime—none0/10

   The evidence pack only documents developer API endpoints for creating Person/Business/Account applications and KYC/KYB integration hooks — it never describes an ops-facing queue UI showing why an application is pending, a way to request/upload additional documents, or any distinction between platform-owned vs. bank-owned decisions. This is a plausible axis for a bank-partner onboarding platform, but nothing in the evidence shows such an ops console or decision-attribution feature.

   • [claimed-docs] “To apply to open a new bank account 1. Create a Person Application 2. Create a Business Application ... 5. Create an Account Application”
   • [claimed-docs] “Programs can seamlessly integrate their bank-approved third-party KYC/KYB vendor into the account opening process.”
   • [claimed-docs] “Incremental KYC lets you run KYC **without opening an account**.”

   proof ↗⚑ flag

Limits holds

1. ops userSet risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement paths

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The only relevant evidence describes Stripe's own automatic, built-in fraud/risk controls for Treasury and Issuing that 'do not require action to enable' — this is the opposite of what the story asks for (ops-configurable per-account/per-program transaction and velocity limits, manual holds, account freezes, and documented reinstatement paths). No documentation shows ops-facing controls for setting limits, freezing accounts, or reinstatement workflows. Missing for 10: any API/dashboard capability to set per-account transaction/velocity limits, manually place holds, freeze/unfreeze accounts, or documented reinstatement procedures.

   • [claimed-docs] “Stripe runs automatic risk controls that help reduce your fraud exposure within Treasury and Issuing without requiring action to enable.”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   No evidence pack items mention transaction/velocity limits, suspicious-activity holds, account freezes, or reinstatement workflows; documentation covers account opening, KYC, ACH/wire/book transfers, and statements but nothing about risk-control configuration. Missing for 10: any documentation of per-account/program limit settings, hold/freeze mechanisms, or reinstatement procedures.

   • [claimed-docs] “To apply to open a new bank account 1. Create a Person Application 2. Create a Business Application ... 5. Create an Account Application”
   • [claimed-docs] “Programs can seamlessly integrate their bank-approved third-party KYC/KYB vendor into the account opening process.”
   • [claimed-docs] “An ACH credit is used when you wish to send or "push" funds to a recipient. ... An ACH debit is used when you wish to "pull" funds from an e…”
   • [claimed-docs] “To return an ACH transfer you originated, use the Update an ACH endpoint.”
   • [claimed-docs] “Generate and retrieve branded monthly account statements for your customers.”

   proof ↗⚑ flag

Loss allocation

1. finance leadFraud 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

   weight 2 · round drawn
   Stripe Treasury—none0/10

   Docs mention that Stripe runs automatic risk controls for fraud exposure within Treasury/Issuing, but there is no evidence documenting an explicit liability split for who bears ACH return fraud, card dispute losses, or account takeover losses. Missing for 10: explicit liability-split documentation for ACH return fraud, card disputes, and ATO losses; any first-party or independent confirmation of how losses are allocated between Stripe, the platform, and connected accounts.

   • [claimed-docs] “Stripe runs automatic risk controls that help reduce your fraud exposure within Treasury and Issuing without requiring action to enable.”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   Evidence shows ACH return handling mechanics (initiating returns) and general product docs, but nothing addresses who bears financial liability for ACH return fraud, card disputes, or account takeover losses, nor any documented liability split alongside fraud prevention tooling.

   ⚑ flag

Program scaling

1. founderGrowth 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

   weight 2 · round drawn
   Stripe Treasury—none0/10

   No evidence in the pack documents program-level limits, approval stages, or a documented path to raising limits — docs cover account features, money movement, and disclosures but not risk/limit escalation processes. One HN comment even highlights the landing page 'doesn't really explain' the underlying constraints, and another surfaces surprise breach notifications rather than transparent limit documentation, reinforcing the absence of documented escalation paths.

   • [community] “A commenter noted the Treasury landing page "doesn’t really explain what kinds of problems Treasury solves," and asked for clarity on target…”
   • [community] “HN thread reports that the Evolve Bank and Trust hack impacted both Mercury and Stripe Treasury customers; a user confirmed receiving a noti…”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   The evidence covers API onboarding, KYC, account opening, ACH/wire/book transfers, and statements, but nothing addresses program-level transaction/volume limits, approval stages, or a documented process for raising limits as growth occurs.

   ⚑ flag

Ach

1. developerOriginate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhooks

   weight 3 · round to Treasury Prime
   Stripe Treasury—none0/10

   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.

   • [claimed-docs] “OutboundPayment objects represent push-based transfers from: A platform’s financial accounts to a financial account owned by connected accou…”
   • [claimed-docs] “You can authorize third parties to debit funds from a financial account.”
   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”

   proof ↗⚑ flag

   Treasury Prime~partialclaimed5/10

   Docs confirm ACH credits and debits (push/pull) and returns handled via an 'Update an ACH endpoint' pattern suggesting first-class transfer objects, but there's no evidence of same-day ACH windows, NOC (notification of change) handling, reversals, or webhook events tied to ACH lifecycle changes. missing for 10: same-day ACH window support, NOC objects/webhooks, reversal handling, explicit webhook event documentation for ACH status changes.

   • [claimed-docs] “An ACH credit is used when you wish to send or "push" funds to a recipient. ... An ACH debit is used when you wish to "pull" funds from an e…”
   • [claimed-docs] “To return an ACH transfer you originated, use the Update an ACH endpoint.”

   proof ↗⚑ flag

Checks

1. ops userChecks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paper

   weight 2 · round drawn
   Stripe Treasury—none0/10

   No evidence pack items mention check issuance, check deposit, or image capture capabilities within Stripe Treasury; documentation focuses on ACH, wires, card issuing, and internal transfers, not paper check handling.

   ⚑ flag

   Treasury Prime—none0/10

   The evidence pack covers ACH, wire, FedNow, book transfers, cash deposits, and account statements, but contains no mention of check issuance or check deposit/RDC (remote deposit capture with image capture) anywhere in the docs.

   ⚑ flag

Instant rails

1. developerThe 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

   weight 2 · round to Treasury Prime
   Stripe Treasury—none0/10

   The evidence pack never mentions domestic wires, RTP, or FedNow, nor any per-rail origination/receipt documentation—only generic OutboundPayment/ReceivedDebit constructs are described without rail specifics. missing for 10: any mention of wire, RTP, or FedNow rails, per-rail capability docs, and origination/receipt distinctions.

   • [claimed-docs] “OutboundPayment objects represent push-based transfers from: A platform’s financial accounts to a financial account owned by connected accou…”
   • [claimed-docs] “You can authorize third parties to debit funds from a financial account.”
   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”

   proof ↗⚑ flag

   Treasury Prime~partialclaimed6/10

   Docs confirm wire transfer status tracking and FedNow instant settlement (24/7/365) through the API, and ACH/book transfer rails are documented, suggesting multi-rail origination exists. However, there's no explicit mention of RTP (Real-Time Payments) origination/receipt, no clear per-rail capability comparison table, and no confirmation of wire/FedNow receipt (only origination-side details are shown). missing for 10: explicit RTP documentation, per-rail capability matrix, wire/FedNow receipt confirmation, and independent corroboration beyond vendor docs.

   • [claimed-docs] “You can track the progress of a wire by checking the `status` attribute on the Wire Transfer object.”
   • [claimed-docs] “Instant Settlement: Payments settle within seconds, 24/7/365”
   • [claimed-docs] “An ACH credit is used when you wish to send or "push" funds to a recipient. ... An ACH debit is used when you wish to "pull" funds from an e…”
   • [claimed-docs] “A book transfer is an electronic funds transfer between two accounts at the same bank... Book transfers are the fastest and cheapest type of…”

   proof ↗⚑ flag

International

1. founderMoney can cross borders — international wires or SWIFT, FX with transparent rates, and the coverage map of currencies and corridors documented

   weight 2 · round drawn
   Stripe Treasury—none0/10

   The evidence shows Treasury supports multi-currency balances (USD, EUR, GBP) and USDC, but there is no documentation of international wire/SWIFT transfers, FX rate transparency, or a coverage map of currencies/corridors. Missing for 10: cross-border wire/SWIFT transfer documentation, FX rate/spread transparency, and a documented list of supported currency corridors.

   • [claimed-docs] “A financial account can hold fiat balances such as USD, EUR, and GBP, and eligible businesses can also hold a stablecoin balance in USDC.”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   Evidence covers only US-domestic rails (ACH, domestic wires, FedNow, book transfers, cash deposits); there is no mention of international wires/SWIFT, FX rates, or a currency/corridor coverage map.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Stripe Treasury~partialclaimed6/10

   Treasury is fundamentally API-first: financial accounts, OutboundPayments, ReceivedDebits, transactions, and disclosures are all API objects, and the Dashboard/mobile app view is described as just one access point built on top of these APIs (docs-4, docs-9, docs-10, docs-13). Platforms can even render Stripe-hosted UI components (bill pay, issuing) driven entirely by the API (docs-8), suggesting strong API/UI parity, but no evidence explicitly confirms every Dashboard action (e.g., manual account configuration, dispute handling, fraud review tools) has a corresponding API endpoint. missing for 10: explicit documentation enumerating full UI-to-API parity, independent confirmation that dashboard-only features (e.g., risk controls in docs-14) are also API-exposed.

   • [claimed-docs] “you can access your financial account on the Treasury page in the Stripe Dashboard or from the Dashboard mobile app”
   • [claimed-docs] “Render Stripe financial account features such as bill pay, issuing, and cash rewards as a branded UI in your platform application while avoi…”
   • [claimed-docs] “As the platform, you can move money from your payments [Balance] to your financial accounts or from your connected accounts’ payments balanc…”
   • [claimed-docs] “OutboundPayment objects represent push-based transfers from: A platform’s financial accounts to a financial account owned by connected accou…”
   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”
   • [claimed-docs] “Stripe runs automatic risk controls that help reduce your fraud exposure within Treasury and Issuing without requiring action to enable.”

   proof ↗⚑ flag

   Treasury Prime~partialprobed6/10

   Treasury Prime's docs show broad API coverage across core banking workflows (account opening, KYC, ACH, wires, book transfers, statements, cash deposits), consistent with an API-first BaaS platform, but there is no explicit claim of full UI/API feature parity and the OpenAPI/swagger spec could not be located (404s), making it hard to verify completeness. missing for 10: explicit parity statement, discoverable OpenAPI spec, independent confirmation that dashboard-only actions (e.g. admin/dashboard configuration) are also API-exposed.

   • [claimed-docs] “To apply to open a new bank account 1. Create a Person Application 2. Create a Business Application ... 5. Create an Account Application”
   • [claimed-docs] “Programs can seamlessly integrate their bank-approved third-party KYC/KYB vendor into the account opening process.”
   • [claimed-docs] “Incremental KYC lets you run KYC **without opening an account**.”
   • [claimed-docs] “An ACH credit is used when you wish to send or "push" funds to a recipient. ... An ACH debit is used when you wish to "pull" funds from an e…”
   • [claimed-docs] “You can track the progress of a wire by checking the `status` attribute on the Wire Transfer object.”
   • [claimed-docs] “A book transfer is an electronic funds transfer between two accounts at the same bank... Book transfers are the fastest and cheapest type of…”
   • [claimed-docs] “Generate and retrieve branded monthly account statements for your customers.”
   • [claimed-docs] “Enable customers to add funds to their accounts using cash at 90,000+ retail locations nationwide”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.treasuryprime.com/openapi.json, https://docs.treasuryprime.com/swagger.json, https://do…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Stripe Treasury—none0/10

   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.

   ⚑ flag

   Treasury Prime—none0/10

   Treasury Prime is a banking-as-a-service API; there is no evidence of a data export/portability feature for account or transaction data in open formats, nor any documented account-closure/data-export process. This is a fair axis for a data-holding platform, but nothing in the evidence shows such capability.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Stripe Treasury—none0/10

   No evidence in the pack addresses data residency, regional data storage choices, or geographic control over where customer/financial data is stored; documentation focuses on financial account features, money movement, and Connect integration rather than data-location controls.

   ⚑ flag

   Treasury Prime—none0/10

   No evidence in the pack addresses data residency, regional storage options, or any data-location controls; Treasury Prime's docs focus entirely on banking/API functionality with no mention of data residency choices.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Stripe Treasury—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy/data-lifecycle management for Stripe Treasury; the documentation focuses on financial account features, money movement, and platform integration, not data governance controls for AI-native users.

   ⚑ flag

   Treasury Prime—none0/10

   No evidence in the pack addresses data retention or deletion controls for AI-native users; the documentation covers banking APIs, KYC, ACH/wire transfers, and account statements but nothing about data lifecycle management or deletion policies.

   ⚑ flag

Charter clarity

1. founderExactly 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

   weight 3 · round to Stripe Treasury
   Stripe Treasury~partialcommunity4/10

   Stripe documents a mandatory 'Treasury disclosure component' for compliance transparency (docs-12) and community discussion confirms partner-bank relationships (e.g., Goldman Sachs) exist and are scrutinized (comm-6), and the Evolve Bank breach thread shows real customer impact when a partner bank had problems (comm-1). However, there is no first-party documentation naming the specific sponsor bank(s), explaining FDIC pass-through insurance mechanics, or detailing what happens to end-customer funds if the platform or partner bank fails. missing for 10: explicit documentation of the sponsor-bank identity/relationship, FDIC insurance pass-through terms, and a documented failure/wind-down process for customer funds.

   • [claimed-docs] “You can embed the Treasury disclosure component directly on your website to automatically display currently compliant disclosure information…”
   • [community] “A user questioned the optics of Stripe Treasury's bank partnerships: "Partnering with companies such as Goldman Sachs is typically not a goo…”
   • [community] “HN thread reports that the Evolve Bank and Trust hack impacted both Mercury and Stripe Treasury customers; a user confirmed receiving a noti…”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   None of the evidence addresses which bank holds the charter, how Treasury Prime's middleware role relates to a named sponsor bank, or what happens to end customers if Treasury Prime fails — the docs only cover API mechanics (KYC, ACH, wires, account opening) with no sponsor-bank disclosure or failure/continuity language.

   ⚑ flag

Compliance tooling

1. ops userThe 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

   weight 2 · round drawn
   Stripe Treasury—none0/10

   Evidence covers automatic fraud/risk controls and disclosure requirements, but there is no mention of transaction monitoring workflows, sanctions/OFAC screening tooling, case management for compliance alerts, or SAR-filing support with defined ops/platform/bank duties. missing for 10: transaction monitoring, sanctions screening, alert case management, SAR-filing support/duty split.

   • [claimed-docs] “Stripe runs automatic risk controls that help reduce your fraud exposure within Treasury and Issuing without requiring action to enable.”
   • [claimed-docs] “You can embed the Treasury disclosure component directly on your website to automatically display currently compliant disclosure information…”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   Evidence only covers KYC/KYB during account opening; there is no mention of transaction monitoring, sanctions screening, alert case management, or SAR-filing support, nor any description of duty splits between ops/platform/bank for these compliance functions.

   • [claimed-docs] “Programs can seamlessly integrate their bank-approved third-party KYC/KYB vendor into the account opening process.”
   • [claimed-docs] “Incremental KYC lets you run KYC **without opening an account**.”

   proof ↗⚑ flag

Reconciliation

1. finance leadThe 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

   weight 3 · round drawn
   Stripe Treasury—none0/10

   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. No first-party or independent evidence describes a bank-to-API reconciliation process, audit, or guarantee.

   • [claimed-docs] “Use transactions to build account activity feeds, reconcile against your internal systems, and track money movement through your platform.”

   proof ↗⚑ flag

   Treasury Prime—none0/10

   The evidence pack covers account opening, KYC, ACH/wire/book transfers, and statements, but there is no mention of ledger-to-bank-core reconciliation, daily reconciliation reports, or any process for verifying API-reported balances against actual bank holdings — the exact failure mode referenced in the story. Nothing in the docs addresses reconciliation guarantees or audit processes for sponsor-bank programs.

   ⚑ flag