Stripe Treasury vs Column
usage-based
·usage-based
Column wins · 4–23 (16 drawn)
Account provisioning — stories about account provisioning in this arenaAccount provisioning
Stories about account provisioning in this arena
Account opening
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 ColumnDocs 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.”
Docs confirm programmatic FDIC-insured account opening/management (column-docs-2) and a full sandbox environment with simulate endpoints for wires/ACH (column-docs-3), matching the story's application-to-active-account and sandbox parity requirements. Community feedback corroborates a smooth signup/setup flow (column-comm-5) and strong documentation quality (column-comm-8). Missing for 10: independent hands-on confirmation that the entire account application/approval step (not just account management) is fully API-driven without manual review, and explicit sandbox-to-production parity testing evidence beyond simulate endpoints.
- [claimed-docs] “Programmatically open and manage FDIC insured bank accounts at Column on behalf of your customers. We support FBO, sweep, clearing and custo…”
- [claimed-docs] “To simulate an incoming transfer, or just to set an initial balance on your account, you can use the `/simulate/receive-wire` endpoint. To s…”
- [community] “User: 'I created an account just to check it out and the signup and initial setup flow is very well done. Nice work.'”
- [community] “User noted the business model implication: 'looks like there is basically one really rich guy self-funding for a couple of years' to build c…”
Fbo structures
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 to ColumnStripe Treasurynone0/10The 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.
Column's docs explicitly state accounts are FDIC insured and describe support for FBO, sweep, clearing, and custom account types, giving some transparency into account structure (column-docs-2). However there is no explicit documentation on how FDIC pass-through insurance attaches to underlying customers, nor on ledger access controls/who can view sub-ledger data — these are not addressed in the evidence pack. missing for 10: explicit FDIC pass-through insurance mechanics, documentation on ledger visibility/access permissions, and independent confirmation of these structural details.
- [claimed-docs] “Programmatically open and manage FDIC insured bank accounts at Column on behalf of your customers. We support FBO, sweep, clearing and custo…”
- [community] “Commenter praised Column's ACH permissioning feature: 'Create account numbers that point to a single bank account and create specific permis…”
Virtual accounts
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 ColumnDocs 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 …”
Column's docs explicitly support programmatic bank account creation including FBO, sweep, clearing and custom account types (column-docs-2), and community evidence confirms per-account-number permissioning ('Create account numbers that point to a single bank account and create specific permissions and limits for each one') which maps to virtual/sub-account use cases (column-comm-7). This directly supports issuing unique account/routing numbers at scale for reconciliation and sub-account structures. Missing for 10: explicit documentation of routing-number issuance mechanics and a dedicated 'virtual accounts' or 'sub-accounts' product page with scale/rate-limit details.
- [claimed-docs] “Programmatically open and manage FDIC insured bank accounts at Column on behalf of your customers. We support FBO, sweep, clearing and custo…”
- [community] “Commenter praised Column's ACH permissioning feature: 'Create account numbers that point to a single bank account and create specific permis…”
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
Yield
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 to ColumnStripe Treasurynone0/10The 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…”
Column documents that it supports 'sweep' as one of its bank account types (alongside FBO, clearing, custom), which addresses the 'documented sweep options' half of the story, but there is no mention anywhere of interest-bearing accounts, rate mechanics, or who keeps the spread. Missing for 10: interest rate documentation, spread/economics disclosure, and any explanation of how sweep proceeds are shared.
- [claimed-docs] “Programmatically open and manage FDIC insured bank accounts at Column on behalf of your customers. We support FBO, sweep, clearing and custo…”
- [community] “Feedback to Column: nit that the uptime status page (status.column.com) defaults to 'Sandbox' instead of Production, which 'can mislead a re…”
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to ColumnStripe'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.
Column serves a live llms.txt file (HTTP 200, confirmed by direct probe) plus markdown-rendered agent-friendly docs pages (e.g. .md versions of guides) and an OpenAPI spec, all of which an agent could be pointed at directly. This is concrete first-party evidence of agent-oriented documentation delivery. Missing for 10: independent/community confirmation that an agent was actually pointed at llms.txt and successfully used it.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.column.com/llms.txt # Column Documentation > Column N.A. is the first nationally chartered bank cr…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.column.com/openapi.json — contains "openapi" key”
- [claimed-docs] “we are going to build a basic payment workflow consisting of a wire, a book transfer, and an ACH credit”
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to ColumnTreasury 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.”
Column is a pure HTTP API/banking platform with an OpenAPI spec, sandbox simulate endpoints, and webhooks — all of which are usable in headless, scripted, or CI-driven workflows without any UI dependency. However, there is no explicit documentation or example of running Column in a CI pipeline, and the company notes it deliberately provides no first-party SDKs, relying on customers to generate their own from the OpenAPI spec. Missing for 10: explicit CI/CD examples or guides, first-party SDKs/tooling for automated test pipelines, and any community confirmation of headless/CI usage.
- [claimed-docs] “To simulate an incoming transfer, or just to set an initial balance on your account, you can use the `/simulate/receive-wire` endpoint. To s…”
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
- [probe] “PROBE openapi: HTTP 200 at https://docs.column.com/openapi.json — contains "openapi" key”
- [community] “Engineer at Column: 'we have definitely considered creating SDK's but most of our customers prefer the HTTP API's, which will likely remain …”
ai-native userConnect an agent via an official MCP server
weight 3 · round to Stripe TreasuryStripe 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”
Columnnone0/10Column is a banking-as-a-service API platform; no evidence of an official MCP server for agent connectivity is present, only a REST API with OpenAPI spec. This axis applies since a developer-facing API platform could plausibly ship an MCP server, but absence of any such evidence yields none. missing for 10: any mention of an MCP server, agent integration, or AI-native tooling.
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
- [probe] “PROBE openapi: HTTP 200 at https://docs.column.com/openapi.json — contains "openapi" key”
ai-native userUse an official CLI
weight 2 · round to Stripe TreasuryStripe 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”
Columnnone0/10Column is a banking API platform with no evidence of an official CLI; in fact a Column engineer explicitly states they don't even provide SDKs, only HTTP APIs, and no CLI is mentioned anywhere in docs or community evidence.
- [community] “Engineer at Column: 'we have definitely considered creating SDK's but most of our customers prefer the HTTP API's, which will likely remain …”
ai-native userDrive the product through a documented public API
weight 3 · round to ColumnStripe 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”
Column is API-first: extensive first-party docs cover a full public API for payments, accounts, wires, ACH, cards, checks, webhooks, and reporting, backed by a documented OpenAPI spec (confirmed live at openapi.json) usable to generate client SDKs, plus a verified llms.txt for AI-native consumption. Community corroboration from a Column engineer confirms HTTP API is the primary supported interface. Missing for 10: no independent third-party audit of API completeness or hands-on agent-driven integration report.
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.column.com/llms.txt # Column Documentation > Column N.A. is the first nationally chartered bank cr…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.column.com/openapi.json — contains "openapi" key”
- [community] “Engineer at Column: 'we have definitely considered creating SDK's but most of our customers prefer the HTTP API's, which will likely remain …”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnStripe Treasurynone0/10The 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.
Columnnone0/10Column is a banking/payments API platform; there is no evidence of scoped or least-privilege API credential issuance for agents specifically (no API key scoping, permission roles, or agent-specific credential management mentioned). The ACH account-number permissioning feature (column-comm-7) relates to bank account routing limits, not API credential scoping for AI agents. Missing for 10: any documentation of API key/token scoping, role-based access control, or agent-specific credential issuance.
ai-native userBuild against official SDKs
weight 2 · round to Stripe TreasuryThe 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…”
Columndisputedcontradicted3/10Docs point to an OpenAPI spec that can be used to 'generate type-safe client SDKs in any language' (column-docs-10), but this is code-gen from a spec, not official first-party SDKs. A Column engineer directly contradicts any SDK-first narrative, stating 'we have definitely considered creating SDK's but most of our customers prefer the HTTP API's' (column-comm-1), confirming no official SDKs exist. Missing for 10: actual first-party maintained SDKs in specific languages, official SDK repos/docs, and any retraction of the engineer's statement.
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
- [community] “Engineer at Column: 'we have definitely considered creating SDK's but most of our customers prefer the HTTP API's, which will likely remain …”
ai-native userSubscribe to events via webhooks
weight 2 · round to ColumnStripe Treasurynone0/10The 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.”
Column's docs explicitly document webhook subscription for events, configurable via API or Dashboard (column-docs-7), enabling programmatic/agentic consumption of platform events. missing for 10: no independent/hands-on confirmation of webhook reliability or payload schema details, and no mention of event types or filtering granularity.
- [claimed-docs] “You can configure webhook endpoints via APIs or Dashboard in your platform to be notified about events from Column.”
Agentic features
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnStripe Treasurynone0/10The 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.)
ai-native userOperate the product with natural-language commands
weight 2 · round to Stripe TreasuryThe 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”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to ColumnStripe Treasurynone0/10The 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…”
Column publishes an OpenAPI spec and markdown docs (docs.column.com) plus a sandbox environment with simulate endpoints for testing payment flows, which supports some hands-on exploration, but there is no direct evidence of an interactive in-docs API console or embedded runnable code examples typical of 'try it now' reference UIs. missing for 10: explicit interactive API explorer/try-it-out UI, embedded runnable code snippets, independent confirmation of an interactive reference experience.
- [claimed-docs] “To simulate an incoming transfer, or just to set an initial balance on your account, you can use the `/simulate/receive-wire` endpoint. To s…”
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
- [probe] “PROBE openapi: HTTP 200 at https://docs.column.com/openapi.json — contains "openapi" key”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.column.com/llms.txt # Column Documentation > Column N.A. is the first nationally chartered bank cr…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to ColumnStripe Treasurynone0/10The 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/…”
Column explicitly documents an OpenAPI spec available as JSON for generating client SDKs, and a live probe confirms the openapi.json endpoint returns HTTP 200 with a valid 'openapi' key, directly corroborating the vendor claim. missing for 10: no independent third-party review specifically validating the spec's completeness/usability beyond the probe.
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
- [probe] “PROBE openapi: HTTP 200 at https://docs.column.com/openapi.json — contains "openapi" key”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to ColumnStripe Treasurynone0/10Stripe 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.
Column's docs explicitly describe a sandbox environment with simulate endpoints (receive-wire, receive-ach-credit/debit) to test payment flows without touching production data, and community mentions confirm a separate Sandbox status page exists distinct from Production. missing for 10: no independent hands-on account of using the sandbox for a full workflow, and no explicit statement about data isolation guarantees between sandbox and production.
- [claimed-docs] “To simulate an incoming transfer, or just to set an initial balance on your account, you can use the `/simulate/receive-wire` endpoint. To s…”
- [community] “Feedback to Column: nit that the uptime status page (status.column.com) defaults to 'Sandbox' instead of Production, which 'can mislead a re…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnStripe Treasurynone0/10No 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.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnStripe Treasurynone0/10The 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.
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round drawnStripe Treasurynone0/10The 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.”
Columnnone0/10Column exposes webhooks so external systems can be notified of events (column-docs-7), but there is no evidence of a native rules/automation engine within Column that lets a user define conditions and have Column itself trigger actions automatically — building on the webhook would require external logic. Missing for 10: any documented in-product rule/trigger definition, conditional action execution, or automation workflow builder.
- [claimed-docs] “You can configure webhook endpoints via APIs or Dashboard in your platform to be notified about events from Column.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnStripe Treasurynone0/10The 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.)
Banking agent access — stories about banking agent access in this arenaBanking agent access
Stories about banking agent access in this arena
Agent operations
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 drawnStripe Treasurynone0/10The 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”
Columnnone0/10Column's docs describe general API capabilities (transfers, account permissioning, webhooks) and one community mention of per-account-number permissions/limits, but nothing documents scoped credentials, amount caps, or counterparty allowlists specifically for an AI agent use case by name. missing for 10: any mention of 'agent' or AI-native access patterns, documented amount-cap/allowlist controls tied to agent credentials, and a named agent-banking product or guide.
- [community] “Commenter praised Column's ACH permissioning feature: 'Create account numbers that point to a single bank account and create specific permis…”
- [claimed-docs] “Programmatically open and manage FDIC insured bank accounts at Column on behalf of your customers. We support FBO, sweep, clearing and custo…”
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
Agent visibility
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 ColumnStripe 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/…”
Column exposes a comprehensive REST/OpenAPI surface covering accounts, transactions, transfers (including pending/status), wires, checks, and reporting (CSV/JSON/Parquet), letting an agent programmatically read the full banking picture instead of scraping a dashboard. However, there is no evidence of an MCP server or agent-native surface — only a standard HTTP API with OpenAPI spec for SDK generation, and the company explicitly says most customers use raw HTTP APIs, not SDKs or agent tooling. Missing for 10: MCP server/tool-calling interface, explicit 'documents' retrieval endpoint beyond checks, and any AI-agent-specific integration evidence.
- [claimed-docs] “Programmatically open and manage FDIC insured bank accounts at Column on behalf of your customers. We support FBO, sweep, clearing and custo…”
- [claimed-docs] “Column provides the following reports: `bank_account_transaction` and `bank_account_summary`. All reports are available in CSV, JSON, and Pa…”
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
- [claimed-docs] “we receive full raw data for all domestic and international wires. You can access the raw message for domestic wires using our get wire tran…”
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
- [community] “Engineer at Column: 'we have definitely considered creating SDK's but most of our customers prefer the HTTP API's, which will likely remain …”
Builtin ai
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 drawnStripe Treasurynone0/10No 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.”
Columnnone0/10Column's evidence pack is entirely about banking-as-a-service APIs (wires, ACH, cards, reporting, webhooks) with no mention of any built-in AI features like natural-language transaction search, dispute drafting, or anomaly summaries. missing for 10: any AI/NLP capability, dispute-response drafting, anomaly detection or summarization features, natural-language search over transactions.
Banking cards — stories about banking cards in this arenaBanking cards
Stories about banking cards in this arena
Card issuance
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 ColumnEvidence 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.”
Column docs confirm a card program supporting both physical and virtual cards via major networks/issuer processors, and a Column engineer corroborates issuing bank/card program status. However, evidence lacks detail on spend controls (limits, MCC restrictions) and digital wallet (Apple/Google Pay) provisioning specifics. missing for 10: documented spend control APIs, digital wallet tokenization/push-provisioning support, independent hands-on confirmation of card issuance flow.
- [claimed-docs] “Build a card program with Column to offer your customers any type of card. We work with all major networks and issuer processors.”
- [community] “Column engineer: 'We're an issuing bank and sponsor card programs on Visa & Mastercard. Our partners can offer both physical and virtual car…”
Disputes
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 drawnStripe Treasurynone0/10The 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.
Banking ledger — stories about banking ledger in this arenaBanking ledger
Stories about banking ledger in this arena
Balances events
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 ColumnDocs 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.”
Column documents configurable webhooks for transaction/event notifications and a unified endpoint to query transfers across payment types, supporting an event-driven integration pattern, but there is no explicit documentation of balance reads reflecting holds/pending activity or a full enumeration of webhook events per transaction state change. missing for 10: explicit balance-with-holds/pending semantics, a complete list of webhook events per state transition, and independent confirmation of real-time accuracy.
- [claimed-docs] “You can configure webhook endpoints via APIs or Dashboard in your platform to be notified about events from Column.”
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
- [claimed-docs] “Column provides the following reports: `bank_account_transaction` and `bank_account_summary`. All reports are available in CSV, JSON, and Pa…”
Data quality
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 ColumnDocs 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.”
Column documents raw rail-level data access (full raw wire messages), a unified cross-rail transfers endpoint, and structured reporting/webhooks, suggesting transaction data goes beyond a raw bank feed. However, there is no explicit documentation of counterparty enrichment fields, stable transaction identifiers across rails, or a described enrichment/categorization layer for building customer-facing product experiences. Missing for 10: explicit counterparty detail schema, documented stable identifier scheme across payment rails, and independent/hands-on verification of enrichment depth beyond raw message passthrough.
- [claimed-docs] “we receive full raw data for all domestic and international wires. You can access the raw message for domestic wires using our get wire tran…”
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
- [claimed-docs] “Column provides the following reports: `bank_account_transaction` and `bank_account_summary`. All reports are available in CSV, JSON, and Pa…”
- [claimed-docs] “You can configure webhook endpoints via APIs or Dashboard in your platform to be notified about events from Column.”
Statements
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 drawnStripe Treasurynone0/10No 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.
Banking onboarding — stories about banking onboarding in this arenaBanking onboarding
Stories about banking onboarding in this arena
Kyc kyb
developerCustomer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application states
weight 3 · round drawnStripe Treasurynone0/10The 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.
Review queues
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 drawnStripe Treasurynone0/10The 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.
Banking risk controls — stories about banking risk controls in this arenaBanking risk controls
Stories about banking risk controls in this arena
Limits holds
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 to ColumnStripe Treasurynone0/10The 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.”
Only a single thin community mention (comm-7) references per-account-number permissions and limits, hinting at some risk-control primitives, but there is no documentation of transaction/velocity limit configuration, holds on suspicious activity, account freezes, or reinstatement paths. missing for 10: documented velocity/transaction limit APIs, hold/freeze mechanisms, reinstatement workflow documentation, per-program risk configuration.
- [community] “Commenter praised Column's ACH permissioning feature: 'Create account numbers that point to a single bank account and create specific permis…”
Loss allocation
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 drawnStripe Treasurynone0/10Docs 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.”
Columnnone0/10No evidence in the pack addresses fraud liability allocation for ACH returns, card disputes, or account takeover losses, nor any documentation pairing prevention tooling with a stated liability split. Docs cover payment rails, reporting, webhooks, and account features but never discuss fraud economics or who bears losses.
Program scaling
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 drawnStripe Treasurynone0/10No 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…”
Columnnone0/10No evidence pack item documents program-level transaction/volume limits, approval or underwriting stages, or a defined process for raising limits as a growing customer scales; docs cover product features (wires, ACH, cards, checks) but not risk/compliance limit governance. Community threads mention account permissioning per sub-account but not program-wide growth limits or escalation paths.
Money movement — stories about money movement in this arenaMoney movement
Stories about money movement in this arena
Ach
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 ColumnStripe Treasurynone0/10The 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.”
Column's docs confirm ACH credit/debit origination via API, sandbox simulation of incoming ACH credits/debits, and general webhook event support, plus a unified transfers endpoint that would include ACH. However, there's no direct evidence of same-day ACH windows, or first-class objects/webhooks for returns, NOCs, or reversals — the specific 'unhappy path' modeling the story asks for is unaddressed. Missing for 10: explicit documentation of same-day ACH windows, return/NOC/reversal objects, and webhook events tied to those unhappy paths.
- [claimed-docs] “we are going to build a basic payment workflow consisting of a wire, a book transfer, and an ACH credit”
- [claimed-docs] “To simulate an incoming transfer, or just to set an initial balance on your account, you can use the `/simulate/receive-wire` endpoint. To s…”
- [claimed-docs] “You can configure webhook endpoints via APIs or Dashboard in your platform to be notified about events from Column.”
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
Checks
ops userChecks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paper
weight 2 · round to ColumnStripe Treasurynone0/10No 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.
Column's docs confirm check issuance and deposit via API (column-docs-4), but there is no explicit mention of image capture mechanics, and a Column engineer noted in community discussion that 'Checks are currently in beta' (column-comm-2), suggesting immaturity. missing for 10: explicit image-capture/deposit workflow details, confirmation of GA (non-beta) status, and independent hands-on verification of check deposit reliability.
- [claimed-docs] “Column provides customers the ability to issue and deposit checks through our APIs.”
- [community] “Column engineer: 'We're an issuing bank and sponsor card programs on Visa & Mastercard. Our partners can offer both physical and virtual car…”
Instant rails
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 ColumnStripe Treasurynone0/10The 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.”
Column's docs explicitly cover domestic wires (with raw message access), RTP and FedNow send/receive/RFP through unified APIs, plus a unified transfers query endpoint across payment types, all under one OpenAPI-defined API surface. Per-rail nuances (e.g., wire raw data, simulate endpoints for sandbox testing) are documented, meeting the developer story well. Missing for 10: independent hands-on verification of RTP/FedNow origination beyond docs, and more granular per-rail limits/SLA documentation.
- [claimed-docs] “Column enables you to immediately send funds, receive funds, and request payment (RFP) through both the Federal Reserve's FedNow Service and…”
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
- [claimed-docs] “we receive full raw data for all domestic and international wires. You can access the raw message for domestic wires using our get wire tran…”
- [claimed-docs] “To simulate an incoming transfer, or just to set an initial balance on your account, you can use the `/simulate/receive-wire` endpoint. To s…”
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
- [probe] “PROBE openapi: HTTP 200 at https://docs.column.com/openapi.json — contains "openapi" key”
International
founderMoney can cross borders — international wires or SWIFT, FX with transparent rates, and the coverage map of currencies and corridors documented
weight 2 · round to ColumnStripe Treasurynone0/10The 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.”
Column documents sending/receiving international transfers via SWIFT and full raw wire message access, showing genuine cross-border wire capability, but there is no evidence of transparent FX rate disclosure or a documented map of supported currencies/corridors. missing for 10: FX rate transparency/pricing details, list of supported currencies and corridors, independent confirmation of SWIFT reliability.
- [claimed-docs] “Via our APIs, you can send and receive international transfers through the SWIFT network.”
- [claimed-docs] “we receive full raw data for all domestic and international wires. You can access the raw message for domestic wires using our get wire tran…”
- [claimed-docs] “we are going to build a basic payment workflow consisting of a wire, a book transfer, and an ACH credit”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to ColumnTreasury 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.”
Column's documentation shows an extensive, comprehensive API surface (accounts, wires, ACH, checks, SWIFT, real-time payments, cards, reporting, webhooks) with OpenAPI spec for SDK generation, and explicitly notes some features like webhooks can be configured 'via APIs or Dashboard' implying parity; a Column engineer also states most customers prefer raw HTTP APIs over SDKs, reinforcing API-first design. Missing for 10: an explicit statement or audit confirming every dashboard-only admin/config feature has an API equivalent, and independent verification of full UI-API parity beyond webhooks.
- [claimed-docs] “Programmatically open and manage FDIC insured bank accounts at Column on behalf of your customers. We support FBO, sweep, clearing and custo…”
- [claimed-docs] “Column provides customers the ability to issue and deposit checks through our APIs.”
- [claimed-docs] “Via our APIs, you can send and receive international transfers through the SWIFT network.”
- [claimed-docs] “Column enables you to immediately send funds, receive funds, and request payment (RFP) through both the Federal Reserve's FedNow Service and…”
- [claimed-docs] “You can configure webhook endpoints via APIs or Dashboard in your platform to be notified about events from Column.”
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
- [community] “Engineer at Column: 'we have definitely considered creating SDK's but most of our customers prefer the HTTP API's, which will likely remain …”
ai-native userExport all of my data in open formats and leave
weight 3 · round to ColumnStripe Treasurynone0/10No 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.
Column documents open, standard export formats for account data (CSV, JSON, Parquet reports) and API access to raw transaction/wire message data, plus a public OpenAPI spec for building custom integrations, which supports data portability for an AI-native user. However there is no explicit documentation of a full account-data export or an account-closure/migration workflow addressing 'leaving' the platform. Missing for 10: explicit full-account export/backup feature, documented account closure/data migration process, independent confirmation of export completeness.
- [claimed-docs] “Column provides the following reports: `bank_account_transaction` and `bank_account_summary`. All reports are available in CSV, JSON, and Pa…”
- [claimed-docs] “we receive full raw data for all domestic and international wires. You can access the raw message for domestic wires using our get wire tran…”
- [claimed-docs] “Column's API is defined by an OpenAPI spec (also available as JSON). Use it to generate type-safe client SDKs in any language”
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
Sponsor model — stories about sponsor model in this arenaSponsor model
Stories about sponsor model in this arena
Charter clarity
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 ColumnStripe 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…”
Column clearly discloses it is itself a nationally chartered bank (not a middleware or partner-bank model) via its docs tagline 'Column N.A. is the first nationally chartered bank created to serve developers and builders' and confirms FDIC-insured accounts and being 'an issuing bank' sponsoring card programs directly. This answers 'who holds the charter' clearly, but the evidence pack has no explicit statement on what happens to customer funds/accounts in a failure/receivership scenario beyond the general FDIC-insurance mention. Missing for 10: explicit failure/receivership disclosure, pass-through insurance mechanics, and independent verification of charter claims beyond Column's own docs/HN comments.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.column.com/llms.txt # Column Documentation > Column N.A. is the first nationally chartered bank cr…”
- [claimed-docs] “Programmatically open and manage FDIC insured bank accounts at Column on behalf of your customers. We support FBO, sweep, clearing and custo…”
- [community] “Column engineer: 'We're an issuing bank and sponsor card programs on Visa & Mastercard. Our partners can offer both physical and virtual car…”
Compliance tooling
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 drawnStripe Treasurynone0/10Evidence 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…”
Columnnone0/10Evidence covers payment rails, account management, reporting, and webhooks, but there is no mention of transaction monitoring tooling, sanctions screening, alert case management, or SAR-filing support/workflow for ops users. Missing for 10: transaction monitoring dashboard/API, sanctions screening tooling, case management for compliance alerts, SAR filing workflow, and documented division of compliance duties between platform/bank/customer.
Reconciliation
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 drawnStripe Treasurynone0/10Evidence 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.”
Columnnone0/10Column is a chartered bank itself and provides reporting/transaction query APIs (bank_account_transaction, bank_account_summary, unified transfer endpoint), but there is no documentation or community evidence describing an explicit daily reconciliation process between the ledger/API and actual held bank funds — the exact assurance a finance lead burned by Synapse would need. Missing for 10: any explicit reconciliation SLA/process documentation, third-party audit or attestation of ledger-to-bank-balance matching, and any commentary addressing the Synapse-style failure mode directly.
- [claimed-docs] “Column provides the following reports: `bank_account_transaction` and `bank_account_summary`. All reports are available in CSV, JSON, and Pa…”
- [claimed-docs] “Query transfers across all payment types from a single unified endpoint.”
- [claimed-docs] “Programmatically open and manage FDIC insured bank accounts at Column on behalf of your customers. We support FBO, sweep, clearing and custo…”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableStripe Treasuryn/aStripe Treasury is a financial-account/banking-as-a-service API and dashboard product, not an agent, IDE, or assistant host that would consume external MCP servers to gain new tool capabilities. The evidence only shows Stripe exposing its own MCP server for others to connect to (probe-4), which is the opposite (server) role, not evidence of Treasury acting as an MCP client/host.
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · not comparableStripe Treasurynone0/10Evidence 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.
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableStripe Treasuryn/aStripe Treasury is a banking-as-a-service infrastructure product for building financial accounts, not a consumer-facing tool with a built-in AI assistant; delegating tasks to an embedded assistant is a category mismatch for this kind of API/backend product.
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableStripe Treasuryn/aStripe Treasury is a banking-as-a-service infrastructure product for storing/moving money, not an automation-building or workflow tool; versioning, reviewing, and rolling back 'automations' is not a concept that applies to this product category.
ai-native userRead the product's source under an open license
weight 2 · not comparableStripe Treasuryn/aStripe Treasury is a closed, proprietary banking-as-a-service product, not an open-source project; source code availability under an open license is not a fair axis for this kind of commercial financial API.
ai-native userSelf-host the core product
weight 3 · not comparableStripe Treasuryn/aStripe Treasury is a regulated banking-as-a-service financial infrastructure product built on partner bank relationships; self-hosting a banking core is a category error, not a fair question for this product type.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableStripe Treasurynone0/10No 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.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableStripe Treasuryn/aStripe Treasury is a banking-as-a-service financial infrastructure product for storing/moving money, not an AI model or AI product with training data policies; opting out of AI training data usage is a category error for this product type.
ai-native userControl data retention and deletion
weight 2 · not comparableStripe Treasurynone0/10No 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.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableStripe Treasuryn/aStripe Treasury is a banking-as-a-service financial infrastructure product, not an AI agent/tool whose telemetry or usage-tracking opt-out would be relevant to an 'AI-native' user's privacy posture; this axis is a category error for this product type.