Stripe Financial Connections vs Teller

Hosted flows

1. developerLet a user connect their bank with a drop-in hosted flow — create a session server-side, open the widget, and get back a token for the connected account — without building institution UI myself

   weight 3 · round to Stripe Financial Connections
   Stripe Financial Connections✓fullcommunity8/10

   Docs describe a server-side session (client_secret) that launches a hosted collectFinancialConnectionsAccounts widget with built-in institution selection across 12,000+ banks, returning connected account data and firing webhooks on link — exactly the drop-in flow described, and community reports confirm real-world adoption for ACH/fraud use cases (docs-6, docs-7, docs-12, comm-6). missing for 10: no explicit doc snippet naming a returned 'token' object schema, and no independent hands-on write-up specifically validating the create-session-then-widget code path (only high-level docs and general community sentiment).

   • [claimed-docs] “Use collectFinancialConnectionsAccounts to launch the authentication flow from your client using the client_secret returned by your server”
   • [claimed-docs] “Users select their bank from frequently chosen institutions or by searching more than 12,000 supported banks.”
   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “the authentication flow exclusively shows a selection of test institutions managed by Stripe. The client can link accounts from any of these…”
   • [community] “I work at one of the companies that integrated Financial Connections during its beta, moving from Plaid Auth. We use the link to bank accoun…”

   proof ↗⚑ flag

   Teller~partialclaimed6/10

   Teller has a documented Connect widget (React SDK, teller-connect-react) and quickstart flow that lets users link accounts, plus a sandbox environment for testing enrollments and OTP flows, matching the drop-in hosted-flow story. However, evidence lacks explicit detail on server-side session creation and the exact token exchange flow, and no independent hands-on account of the widget UX beyond first-party docs. missing for 10: explicit session-creation API docs, independent/hands-on verification of the widget flow, and detail on token retrieval mechanics.

   • [claimed-docs] “Learn about Teller Connect and how to integrate and customize it for you application.”
   • [claimed-docs] “finish up by linking your first financial accounts to Teller.”
   • [github] “React hook and component for integrating with Teller Connect”
   • [claimed-docs] “`otp` () - Will follow an OTP MFA flow whereby the user will be asked to select a contact to send an OTP code. The correct code is `0000`”
   • [claimed-docs] “The sandbox environment uses simulated data and never connects to real financial institutions.”
   • [claimed-docs] “Connect instantly with more than 7,000 financial institutions and fall back to same-day ACH microdeposit verification for everyone else.”

   proof ↗⚑ flag

Oauth

1. developerConnections to major institutions use bank-hosted OAuth rather than screen-scraped credentials — the platform documents its OAuth coverage and how legacy credential flows are being retired

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   None of the docs mention OAuth explicitly, document which institutions use bank-hosted OAuth versus other methods, or describe retirement of legacy credential-based flows. In fact, community commentary indicates Stripe proxies to Plaid-like providers (i.e., non-OAuth/screen-scraping) for institutions lacking OAuth support, undermining the premise that connections are exclusively OAuth-based.

   • [community] “If Stripe can leverage their banking relationships to leapfrog Plaid by integrating directly with bank's APIs instead of screen scraping, th…”
   • [claimed-docs] “Users select their bank from frequently chosen institutions or by searching more than 12,000 supported banks.”
   • [claimed-docs] “You can use one integration to instantly verify bank accounts for ACH payments, reduce underwriting risk with balances data, mitigate fraud …”

   proof ↗⚑ flag

   Teller—none0/10

   Teller's docs describe connecting via 'Verify Account Details via Microdeposit' and general account-linking language, but nowhere document OAuth coverage of major institutions or a retirement plan for legacy credential-based flows. Community evidence actually points the other way — the founder compares Teller's terms to 'incumbent screen-scrapers in the market, e.g. Yodlee and Plaid,' and users note banks disclaim liability 'if you give your online banking credentials to a third party,' indicating credential-based (not bank-hosted OAuth) connections were in use historically.

   • [community] “Founder response: 'FWIW it is not currently possible for users to move money with Teller... Our terms are comparable to the incumbent screen…”
   • [community] “UK banks don't accept any liability if you give your online banking credentials to a third party. If some fraud was to come about as a resul…”
   • [claimed-docs] “To access account details from these institutions, you can implement the 'Verify Account Details via Microdeposit' flow.”
   • [claimed-docs] “Connect instantly with more than 7,000 financial institutions and fall back to same-day ACH microdeposit verification for everyone else.”

   proof ↗⚑ flag

Repair

1. ops leadBroken connections are repairable — expired or revoked links surface as documented statuses, and users can re-authenticate in an update flow without starting over

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections~partialclaimed6/10

   Stripe documents a dedicated relink API to help reconnect an inactive/broken account, plus webhooks marking refresh completions (balance, ownership, transaction), implying some status tracking for account health. However, the pack lacks explicit documentation of distinct 'expired' vs 'revoked' status codes or a walkthrough showing the re-auth update flow preserving prior account context so users don't start over. missing for 10: explicit status enumeration for expired/revoked links, end-to-end UX documentation of the re-auth flow without data loss, and independent confirmation the relink flow works as described.

   • [claimed-docs] “Use the relink API to help your user reconnect their inactive account.”
   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”

   proof ↗⚑ flag

   Teller—none0/10

   The evidence covers enrollment webhooks, MFA/OTP sandbox flows, and microdeposit verification, but nowhere documents a specific 'broken connection' status taxonomy or a re-authentication/update flow for expired or revoked links. Webhook docs mention 'changes in user enrollments' generically but don't detail reconnect/repair UX.

   • [claimed-docs] “To register a new webhook, you need to have a URL in your app that Teller can call. You can configure a new webhook from the Teller Dashboar…”
   • [claimed-docs] “Teller sends webhook events when specific conditions or changes are detected in user enrollments or their financial data.”
   • [claimed-docs] “`otp` () - Will follow an OTP MFA flow whereby the user will be asked to select a contact to send an OTP code. The correct code is `0000`”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections✓fullprobed8/10

   Stripe hosts a live llms.txt (HTTP 200) and markdown-formatted docs (financial-connections.md) confirmed by direct probes, and there's also agent-oriented documentation like use-cases.md with an explicit 'Financial insights for agents' section referencing agent-powered analysis tools. Missing for 10: independent/community confirmation that agents actually consume these docs successfully, and no dedicated llms.txt content specific to Financial Connections (it's the site-wide docs.stripe.com/llms.txt).

   • [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/financial-connections.md # Stripe Financial Connections Access permissioned data from yo…”
   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”

   proof ↗⚑ flag

   Teller—none0/10

   Probes directly show no llms.txt, no docs.md, and no OpenAPI file at expected locations (all 404), and no evidence of any agent-oriented documentation format elsewhere in the pack.

   • [probe] “PROBE llms.txt: HTTP 404 at https://teller.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://teller.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://teller.io/openapi.json, https://teller.io/swagger.json, https://teller.io/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 2 · round to Teller
   Stripe Financial Connections~partialprobed4/10

   Financial Connections exposes server-side webhooks and a documented testing mode where test institutions can be linked without credentials, which supports some automated/CI testing (docs-15, docs-26, docs-12/13/24/25), and Stripe's broader platform offers a CLI and MCP server for agent-driven automation (probe-4, probe-5, docs-18). However, the core account-linking flow requires a client-side authentication step (collectFinancialConnectionsAccounts) that is inherently interactive, not headless, for real accounts. Missing for 10: explicit documentation of a fully headless/server-only flow for production account linking, and independent confirmation that CI-only automation works end-to-end without any UI step.

   • [claimed-docs] “the authentication flow exclusively shows a selection of test institutions managed by Stripe. The client can link accounts from any of these…”
   • [claimed-docs] “The client can link accounts from any of these institutions without providing credentials.”
   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”
   • [claimed-docs] “Use collectFinancialConnectionsAccounts to launch the authentication flow from your client using the client_secret returned by your server”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Teller~partialcommunity5/10

   Teller is an API-first product (mTLS-authenticated REST API with a sandbox environment) that is inherently callable headlessly from scripts, and a community example shows a script consuming the API to export data. However there is no explicit documentation of CI integration, a CLI, or automation-specific guidance/examples for headless pipelines. Missing for 10: explicit CI/CD documentation, CLI or SDK examples for automated pipelines, and any first-party guidance on non-interactive/headless usage patterns.

   • [claimed-docs] “The Teller API uses mTLS to authenticate the API caller. Teller issues client certificates that you use to connect to the Teller API.”
   • [claimed-docs] “The sandbox environment uses simulated data and never connects to real financial institutions.”
   • [claimed-docs] “`otp` () - Will follow an OTP MFA flow whereby the user will be asked to select a contact to send an OTP code. The correct code is `0000`”
   • [community] “I built a little script to export my accounts to CSV/QIF. Super easy to use API! https://github.com/scottrobertson/teller-export”

   proof ↗⚑ flag

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

   weight 3 · round to Stripe Financial Connections
   Stripe Financial Connections✓fullprobed8/10

   Stripe documents an official MCP server that lets AI agents interact with the Stripe API and knowledge base, and Financial Connections docs explicitly call out an agent use case ('Financial insights for agents' with agent-powered spending analysis and balance/transaction monitoring), confirmed by a live docs probe at docs.stripe.com/mcp. Missing for 10: independent/hands-on confirmation that Financial Connections-specific tools (balances, transactions, ownership) are exposed via the MCP server, and no community reports of using it.

   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s kno…”
   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Teller—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

4. ai-native userUse an official CLI

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections✓fullprobed7/10

   Stripe provides an official Stripe CLI documented at docs.stripe.com/stripe-cli, which applies across Stripe products including Financial Connections, and this is a first-party, well-documented tool rather than just a wrapper. missing for 10: Financial Connections-specific CLI usage examples/workflows and independent hands-on corroboration of CLI use for this product's API.

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

   proof ↗⚑ flag

   Teller—none0/10

   No evidence of an official CLI for Teller; only a REST API, SDKs, and a React connect component are documented, and probes for llms.txt/openapi/docs.md all 404. Missing for 10: any mention of a CLI tool, package, or command-line workflow for AI-native/agentic use.

   • [probe] “PROBE llms.txt: HTTP 404 at https://teller.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://teller.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://teller.io/openapi.json, https://teller.io/swagger.json, https://teller.io/api/openapi.json, …”
   • [github] “React hook and component for integrating with Teller Connect”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Stripe Financial Connections~partialprobed6/10

   Stripe Financial Connections is documented via Stripe's broader public REST API and webhooks (account linking, balance/ownership/transaction refresh events, relink API), and Stripe provides an official MCP server for AI agents to interact with the Stripe API plus a documented CLI, which together support agent-driven use. However, evidence doesn't show Financial Connections-specific MCP tools or agent-native documentation beyond a generic 'Financial insights for agents' use-case mention, and no independent corroboration of agents successfully driving this specific product exists. Missing for 10: dedicated Financial Connections MCP tool documentation, hands-on/independent verification of agentic API usage for this product specifically, and full OpenAPI spec discoverability (404s found).

   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s kno…”
   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”
   • [claimed-docs] “Use collectFinancialConnectionsAccounts to launch the authentication flow from your client using the client_secret returned by your server”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [claimed-docs] “Use the relink API to help your user reconnect their inactive account.”

   proof ↗⚑ flag

   Teller~partialprobed6/10

   Teller documents a full REST API (accounts, balances, transactions, identity, payments, webhooks, mTLS auth, pagination, idempotency) that a developer or agent can drive programmatically, and a community member confirms it as an 'easy to use API' for scripting exports. However, probes show no OpenAPI/Swagger spec or llms.txt/docs.md machine-readable format, which limits easy AI-native discovery/automation of the API surface. missing for 10: OpenAPI/Swagger spec, llms.txt or docs.md for agent-friendly discovery, broader independent evidence of agentic/automated API usage beyond one CSV-export script.

   • [claimed-docs] “The account balances API provides your application with live, real-time account balances.”
   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “The payments resource allows you to send payments to yourself or a 3rd party on behalf of the end-user from their account. Currently the onl…”
   • [claimed-docs] “The Teller API uses mTLS to authenticate the API caller. Teller issues client certificates that you use to connect to the Teller API.”
   • [claimed-docs] “This endpoint supports idempotent requests.”
   • [claimed-docs] “the transactions list endpoint supports pagination controls.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://teller.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://teller.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://teller.io/openapi.json, https://teller.io/swagger.json, https://teller.io/api/openapi.json, …”
   • [community] “I built a little script to export my accounts to CSV/QIF. Super easy to use API! https://github.com/scottrobertson/teller-export”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   The evidence pack covers Financial Connections' bank-linking, data-access, and webhook features, plus a generic Stripe MCP server for agent API access, but nothing about issuing scoped or least-privilege API credentials/keys specifically for agents. No mention of restricted API keys, credential scoping, or permission granularity for agentic use is present.

   ⚑ flag

   Teller—none0/10

   Teller's docs describe mTLS client-certificate authentication and per-enrollment user consent, but there is no evidence of any mechanism to mint scoped, least-privilege API credentials specifically for delegating access to an AI agent (e.g., granular permission scopes, agent-specific keys, or revocable sub-credentials). Missing for 10: any documentation of scoped/limited-permission credential issuance, agent-specific key management, or fine-grained access control beyond whole-enrollment consent.

   • [claimed-docs] “The Teller API uses mTLS to authenticate the API caller. Teller issues client certificates that you use to connect to the Teller API.”
   • [claimed-docs] “The Teller API uses mTLS to authenticate the API caller”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “**100 enrollment limit** — An enrollment represents one bank login, which may include multiple accounts”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections✓fullprobed7/10

   Stripe provides official SDKs and client integration methods (e.g., collectFinancialConnectionsAccounts) for Financial Connections, plus a documented official CLI and an official MCP server enabling AI agents to interact with Stripe APIs including this product, and docs explicitly mention 'Financial insights for agents' use cases. missing for 10: independent hands-on developer confirmation of building an AI-native agent integration specifically with Financial Connections via SDK/MCP, and no explicit SDK code samples in multiple languages shown in evidence.

   • [claimed-docs] “Use collectFinancialConnectionsAccounts to launch the authentication flow from your client using the client_secret returned by your server”
   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s kno…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Teller~partialprobed5/10

   Teller provides an official REST API with documented endpoints and a first-party React SDK (teller-connect-react) for integrating Teller Connect, giving developers something concrete to build against. However, probes show no OpenAPI/swagger spec or llms.txt for machine-readable discovery, and there's no evidence of official SDKs beyond the single React component (e.g., no Python/Node/mobile SDKs), limiting AI-native tooling support. Missing for 10: multi-language official SDKs, machine-readable OpenAPI spec, llms.txt or other AI-agent-friendly documentation.

   • [github] “React hook and component for integrating with Teller Connect”
   • [claimed-docs] “Learn about Teller Connect and how to integrate and customize it for you application.”
   • [claimed-docs] “The Teller API uses mTLS to authenticate the API caller. Teller issues client certificates that you use to connect to the Teller API.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://teller.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://teller.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://teller.io/openapi.json, https://teller.io/swagger.json, https://teller.io/api/openapi.json, …”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Stripe Financial Connections✓fullclaimed7/10

   Stripe Financial Connections documents specific webhook events (account linked, balance/ownership/transaction refresh completed) that any integrator, including AI-native agent backends, can subscribe to for event-driven workflows. This is standard first-party webhook documentation but lacks AI-specific framing or independent corroboration of agentic webhook consumption. Missing for 10: independent/hands-on confirmation of AI agents consuming these webhooks, and explicit agent-oriented event subscription guidance.

   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “Use the relink API to help your user reconnect their inactive account.”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”

   proof ↗⚑ flag

   Teller✓fullclaimed7/10

   Teller documents a webhooks API where users register a URL to receive events for enrollment/data changes, configurable via the Dashboard, covering the core subscribe-to-events capability. missing for 10: no documented event type catalog/payload schema, no independent/hands-on confirmation of webhook reliability, and no AI-agent-specific integration pattern beyond generic docs.

   • [claimed-docs] “To register a new webhook, you need to have a URL in your app that Teller can call. You can configure a new webhook from the Teller Dashboar…”
   • [claimed-docs] “Teller sends webhook events when specific conditions or changes are detected in user enrollments or their financial data.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections~partialprobed3/10

   Docs list 'Financial insights for agents' with 'Agent-powered spending analysis' and 'Balance and transaction monitoring' as a named use case, and Stripe's MCP server lets AI agents query account data — but these are thin, high-level mentions rather than a documented native AI-insights feature inside the Financial Connections product itself; the core product is described as raw data access (balances, transactions, ownership) for developers to build on, not an insight-generation UI. Missing for 10: concrete documentation of an actual AI-generated insights/suggestions feature, UI screenshots or workflow showing insights surfaced to end users, and independent/hands-on confirmation that agent-powered analysis works as described.

   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s kno…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [claimed-docs] “Access an account’s current and available balances.”
   • [claimed-docs] “Access an account’s transaction history.”

   proof ↗⚑ flag

   Teller—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

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

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections~partialclaimed5/10

   Financial Connections supports webhook events (account linked, balance/ownership/transaction refresh completed) and a relink API, which let developers build background automations that react to account/data changes without manual polling, and docs even reference an 'agent-powered spending analysis' use case. However, there's no evidence of built-in scheduling, orchestration, or agent-specific automation tooling beyond webhooks — it's infrastructure a developer must wire up themselves. Missing for 10: native scheduling/orchestration primitives, explicit AI-agent automation framework, and hands-on evidence of autonomous background agents running on this data.

   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “Use the relink API to help your user reconnect their inactive account.”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”
   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”

   proof ↗⚑ flag

   Teller~partialclaimed4/10

   Teller offers webhooks that fire on enrollment/data changes, enabling event-driven background processing without polling, which is the closest analog to autonomous automation for this financial-data API. However there's no evidence of an AI-agent framework, scheduling/orchestration engine, or any AI-native automation tooling — webhooks are a generic API feature, not an agentic automation capability. Missing for 10: AI agent orchestration support, scheduled/recurring automation tooling, explicit AI-native automation framework or examples.

   • [claimed-docs] “To register a new webhook, you need to have a URL in your app that Teller can call. You can configure a new webhook from the Teller Dashboar…”
   • [claimed-docs] “Teller sends webhook events when specific conditions or changes are detected in user enrollments or their financial data.”

   proof ↗⚑ flag

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

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections~partialprobed4/10

   Stripe's docs mention an 'agent-powered spending analysis' use case for Financial Connections and Stripe's general MCP server lets AI agents call the Stripe API, implying some natural-language operability, but there's no detailed documentation of specific natural-language commands or agent workflows scoped to Financial Connections itself. Missing for 10: concrete examples of NL commands/agent interactions specific to Financial Connections, independent/hands-on validation that agents can operate this product conversationally, and clarity on how much of the flow (bank auth, consent) can be agent-driven vs. requiring a human UI step.

   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s kno…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Teller—none0/10

   Teller is a banking-data API/SDK product with no evidence of a natural-language command interface, chatbot, or AI-native interaction layer; probes for llms.txt/docs.md/openapi also failed, and no docs mention NL commands or agent interfaces.

   • [probe] “PROBE llms.txt: HTTP 404 at https://teller.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://teller.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://teller.io/openapi.json, https://teller.io/swagger.json, https://teller.io/api/openapi.json, …”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   The evidence pack shows only text-based documentation pages (feature descriptions, webhooks list, testing docs) and confirms no OpenAPI spec was found at any candidate path (probe-3: all 404). There is no mention of an interactive API reference, live code runner, or runnable examples for Financial Connections specifically.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [claimed-docs] “Access an account’s current and available balances.”

   proof ↗⚑ flag

   Teller—none0/10

   Teller has extensive markdown-based API documentation but no evidence of an interactive reference with runnable examples (e.g., Swagger/OpenAPI explorer). Probes for openapi.json/swagger.json all returned 404, and no docs mention a try-it-now console or code sandbox.

   • [probe] “PROBE openapi: all candidate paths 404 (https://teller.io/openapi.json, https://teller.io/swagger.json, https://teller.io/api/openapi.json, …”
   • [claimed-docs] “Learn about Teller Connect and how to integrate and customize it for you application.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   A direct probe for OpenAPI/swagger specs at expected doc paths returned 404 for all candidates, and no other evidence in the pack shows a downloadable machine-readable API spec for Financial Connections; only markdown docs (.md) and llms.txt are available, which are not an OpenAPI-equivalent spec.

   • [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

   Teller—none0/10

   Probes for llms.txt, docs.md, and common OpenAPI/swagger paths all return 404, and no evidence pack item references a downloadable machine-readable spec; documentation is only in prose/markdown form.

   • [probe] “PROBE llms.txt: HTTP 404 at https://teller.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://teller.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://teller.io/openapi.json, https://teller.io/swagger.json, https://teller.io/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 1 · round to Teller
   Stripe Financial Connections✓fullclaimed7/10

   Stripe documents a dedicated testing mode where the authentication flow shows only Stripe-managed test institutions and accounts can be linked without real credentials, explicitly separating sandbox testing from production data access. Missing for 10: no explicit mention of a fully isolated test API key/environment guarantee for financial data, no independent hands-on confirmation of sandbox fidelity, and no detail on how test data maps to production behavior.

   • [claimed-docs] “the authentication flow exclusively shows a selection of test institutions managed by Stripe. The client can link accounts from any of these…”
   • [claimed-docs] “The client can link accounts from any of these institutions without providing credentials.”

   proof ↗⚑ flag

   Teller✓fullclaimed8/10

   Teller documents a dedicated sandbox environment using simulated data that never connects to real financial institutions, with defined test flows (e.g., OTP MFA with code 0000), letting developers test integrations without touching production data or real accounts. Missing for 10: independent/hands-on developer confirmation of sandbox fidelity and no mention of sandbox-specific rate limits or data reset options.

   • [claimed-docs] “The sandbox environment uses simulated data and never connects to real financial institutions.”
   • [claimed-docs] “`otp` () - Will follow an OTP MFA flow whereby the user will be asked to select a contact to send an OTP code. The correct code is `0000`”
   • [claimed-docs] “**100 enrollment limit** — An enrollment represents one bank login, which may include multiple accounts”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   No evidence pack items reference API versioning, version headers, or a documented deprecation policy for Stripe Financial Connections; only feature descriptions, webhooks, and community sentiment are present.

   ⚑ flag

   Teller—none0/10

   No evidence of API versioning scheme or a documented deprecation policy anywhere in the docs pack; probes for llms.txt/openapi spec also failed, suggesting no machine-readable API contract either.

   • [probe] “PROBE llms.txt: HTTP 404 at https://teller.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://teller.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://teller.io/openapi.json, https://teller.io/swagger.json, https://teller.io/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   No evidence of bulk/batch operations (e.g., batch account linking, bulk transaction pulls, multi-item API calls) for AI-native automation; the closest evidence is a webhook that emits one event per linked account, which is not a bulk-operation capability.

   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”

   proof ↗⚑ flag

   Teller—none0/10

   Teller's docs describe per-item endpoints (single account balances, single transaction list with pagination, single payment with idempotency) but there is no evidence of any batch/bulk endpoint for operating across many accounts, transactions, or payments at once. Pagination controls exist for reading a transaction list, but that is not a bulk operation on multiple items simultaneously.

   • [claimed-docs] “the transactions list endpoint supports pagination controls.”
   • [claimed-docs] “This endpoint supports idempotent requests.”
   • [claimed-docs] “The payments resource allows you to send payments to yourself or a 3rd party on behalf of the end-user from their account. Currently the onl…”
   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Stripe Financial Connections—none0/10

   Financial Connections offers webhooks for events (account linked, balance refresh, etc.) but there is no evidence of a rules engine or automation layer where users can define conditional rules that trigger actions on those events—developers would need to build that logic themselves outside the product. missing for 10: rule-definition interface, conditional trigger-action mapping, any built-in automation/workflow engine.

   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”

   proof ↗⚑ flag

   Teller—none0/10

   Teller offers webhooks for event notifications (teller-docs-7, teller-docs-17), but there is no evidence of a rules engine or automation-configuration capability where users can define conditional actions triggered by events — webhook delivery only notifies an external app, it doesn't let a user define trigger-action rules within Teller itself. missing for 10: any rule/condition builder, action templates, or automation configuration UI/API beyond raw webhook event delivery.

   • [claimed-docs] “To register a new webhook, you need to have a URL in your app that Teller can call. You can configure a new webhook from the Teller Dashboar…”
   • [claimed-docs] “Teller sends webhook events when specific conditions or changes are detected in user enrollments or their financial data.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Stripe Financial Connections—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

   Teller—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

Ach details

1. developerObtain verified account and routing numbers (or tokenized equivalents) from a linked account to fund ACH or bank-debit payments without micro-deposits

   weight 3 · round to Stripe Financial Connections
   Stripe Financial Connections✓fullcommunity8/10

   Docs explicitly describe an 'instant' verification flow with 'no manual entry and microdeposit fallback' for ACH Direct Debit, collecting bank account + ownership/balance data in one integration, eliminating the need for users to locate account/routing numbers, and a real-world adopter (comm-6) confirms using it for instant account verification and ACH fraud signaling in production, replacing Plaid Auth. Missing for 10: explicit technical detail on the exact token/PaymentMethod format returned to the server and any independent benchmarking of ACH failure-rate reduction beyond Stripe's own claims.

   • [claimed-docs] “instant | Financial Connections only, with no manual entry and microdeposit fallback”
   • [claimed-docs] “Reduce your payment failure rate from closed or inactive accounts - Improve payments conversion by keeping users on session, instead of forc…”
   • [claimed-docs] “Collect a bank account for ACH Direct Debit payments while using account data, including balances.”
   • [claimed-docs] “Save development time by eliminating the need to create a custom bank account collection form”
   • [community] “I work at one of the companies that integrated Financial Connections during its beta, moving from Plaid Auth. We use the link to bank accoun…”

   proof ↗⚑ flag

   Teller~partialclaimed7/10

   Teller's docs describe an account-details endpoint providing verified account/routing numbers with instant verification for 7,000+ institutions, explicitly positioned to avoid microdeposits, with balances API used to confirm funds before ACH debit. However the same docs show a same-day microdeposit fallback is still required for institutions outside instant coverage, and there is no independent/hands-on confirmation of the instant-verification success rate or that routing numbers are tokenized rather than plaintext. missing for 10: independent corroboration of instant verification working in practice, clarity on tokenization vs raw account/routing number exposure, and confirmation that non-covered institutions aren't a common real-world limitation.

   • [claimed-docs] “To access account details from these institutions, you can implement the 'Verify Account Details via Microdeposit' flow.”
   • [claimed-docs] “Connect instantly with more than 7,000 financial institutions and fall back to same-day ACH microdeposit verification for everyone else.”
   • [claimed-docs] “Guaranteed live account balances. Used for underwriting or ensuring sufficient funds are available before submitting an ACH debit.”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”

   proof ↗⚑ flag

Balances

1. developerFetch a real-time balance for a connected account before initiating a payment — a documented balance endpoint intended for NSF and risk checks

   weight 3 · round to Teller
   Stripe Financial Connections✓fullcommunity7/10

   Docs explicitly state Financial Connections lets you 'Access an account's current and available balances' and 'reduce underwriting risk with balances data', with a dedicated balance-refresh webhook event, and community evidence confirms real customers use the linked-account data as a fraud/risk signal before ACH debits. This matches the NSF/risk-check use case described in the story. missing for 10: explicit API reference/endpoint schema for the balance object, and confirmation of real-time (vs refresh-triggered) latency guarantees.

   • [claimed-docs] “Access an account’s current and available balances.”
   • [claimed-docs] “Collect a bank account for ACH Direct Debit payments while using account data, including balances.”
   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “reduce underwriting risk with balances data”
   • [community] “I work at one of the companies that integrated Financial Connections during its beta, moving from Plaid Auth. We use the link to bank accoun…”

   proof ↗⚑ flag

   Teller✓fullclaimed9/10

   Teller's docs explicitly provide a dedicated real-time balances API endpoint, and marketing/docs copy directly frames it for underwriting/NSF risk checks before submitting an ACH debit, matching the story precisely. Missing for 10: no independent/hands-on developer confirmation of the balance endpoint's real-time accuracy or latency in production.

   • [claimed-docs] “The account balances API provides your application with live, real-time account balances.”
   • [claimed-docs] “Guaranteed live account balances. Used for underwriting or ensuring sufficient funds are available before submitting an ACH debit.”
   • [claimed-docs] “Teller lets users connect their accounts in seconds, and you verify account ownership, ACH details, balances, and transactions with ease.”

   proof ↗⚑ flag

Ownership

1. ops leadRetrieve account-holder details — names, addresses, contact data on file at the bank — to match the account owner against my customer

   weight 2 · round drawn
   Stripe Financial Connections✓fullcommunity8/10

   Docs explicitly state you can 'Access account owners' names and mailing addresses' and 'mitigate fraud by verifying account ownership details,' plus an ownership-refresh webhook event confirms this data can be kept current for ownership matching. Community evidence corroborates real-world use as a fraud/ownership signal for ACH payments. Missing for 10: explicit documentation of contact/phone/email fields beyond name+address, and independent hands-on verification of the exact data schema returned.

   • [claimed-docs] “Access account owners’ names and mailing addresses.”
   • [claimed-docs] “mitigate fraud by verifying account ownership details”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [community] “I work at one of the companies that integrated Financial Connections during its beta, moving from Plaid Auth. We use the link to bank accoun…”

   proof ↗⚑ flag

   Teller✓fullclaimed8/10

   Teller's Identity API explicitly returns beneficial owner identity information for each authorized account, directly matching the story's need to retrieve account-holder names/identity data for owner matching (teller-docs-4, teller-docs-19), and the docs message frames account ownership verification as a core use case (teller-docs-1). Missing for 10: explicit confirmation that address/contact fields (not just legal name) are included in the Identity payload, and independent/hands-on corroboration beyond vendor docs.

   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “Teller lets users connect their accounts in seconds, and you verify account ownership, ACH details, balances, and transactions with ease.”

   proof ↗⚑ flag

Processor tokens

1. developerLinked accounts plug into my payment processor — documented integrations or token exchange that hand verified account credentials to third-party processors and platforms

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections✓fullcommunity8/10

   Stripe's docs describe explicit, well-documented integrations where Financial Connections hands verified bank-account data (balances, ownership, transactions) to other Stripe payment products—ACH Direct Debit collection, Connect payouts, and underwriting/fraud tooling—via a documented client_secret/token exchange flow and webhooks, and a Hacker News commenter confirms real-world production use for ACH verification and fraud signals alongside other Stripe products. missing for 10: evidence of handoff to non-Stripe third-party processors/platforms specifically, and independent security review of the credential-exchange mechanism.

   • [claimed-docs] “Use collectFinancialConnectionsAccounts to launch the authentication flow from your client using the client_secret returned by your server”
   • [claimed-docs] “Collect a bank account for ACH Direct Debit payments while using account data, including balances.”
   • [claimed-docs] “Collect a bank account to use for Connect payouts, and use account data, such as ownership details, with your integration.”
   • [claimed-docs] “instant | Financial Connections only, with no manual entry and microdeposit fallback”
   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [community] “I work at one of the companies that integrated Financial Connections during its beta, moving from Plaid Auth. We use the link to bank accoun…”

   proof ↗⚑ flag

   Teller—none0/10

   Teller's docs describe its own Payments resource (Zelle transfers) and Identity/Balances APIs, but there is no documented processor-token exchange or integration flow that hands verified account credentials to third-party payment processors/platforms (e.g., a Stripe/Dwolla-style processor token). Community threads even confirm Teller does not enable moving money to arbitrary third parties beyond its own Zelle feature.

   • [claimed-docs] “The payments resource allows you to send payments to yourself or a 3rd party on behalf of the end-user from their account. Currently the onl…”
   • [claimed-docs] “The payments resource allows you to send payments to yourself or a 3rd party on behalf of the end-user from their account.”
   • [community] “Founder response: 'FWIW it is not currently possible for users to move money with Teller... Our terms are comparable to the incumbent screen…”

   proof ↗⚑ flag

Agent data

1. ai-native userThe data comes back agent-consumable — clean structured JSON, documented schemas, and enrichment an automated financial workflow can reason over without heuristic parsing

   weight 2 · round drawn
   Stripe Financial Connections~partialprobed6/10

   Stripe's docs show structured API objects for balances, ownership, and transactions plus typed webhook events (docs-2,3,4,12-14,24,25), and even a dedicated 'Financial insights for agents' use-case section citing agent-powered spending analysis and balance/transaction monitoring (docs-11), supporting agent-consumable data. However, no OpenAPI/schema file could be found (probe-3 shows all openapi.json paths 404), and there's no independent/hands-on evidence confirming an agent can parse this data without additional tooling. Missing for 10: published OpenAPI/JSON schema docs, and independent corroboration of agent-consumability beyond Stripe's own docs.

   • [claimed-docs] “Access an account’s current and available balances.”
   • [claimed-docs] “Access account owners’ names and mailing addresses.”
   • [claimed-docs] “Access an account’s transaction history.”
   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”
   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”
   • [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

   Teller~partialprobed6/10

   Teller's docs describe a REST API with well-defined resources (balances, transactions, identity, payments) and some enrichment like transaction categorization, pagination, and idempotency, suggesting structured, documented data an app could parse programmatically. However, there is no evidence of a machine-readable schema (OpenAPI/swagger) or llms.txt for agent discovery—probes show all such endpoints 404—so an AI agent would have to rely on human-oriented docs rather than a formal schema. missing for 10: machine-readable OpenAPI/schema files, llms.txt or agent-specific docs, richer enrichment metadata (e.g., merchant/location tags) beyond basic categorization.

   • [claimed-docs] “The account balances API provides your application with live, real-time account balances.”
   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “the category that the transaction belongs to. Teller uses the following values for categorization”
   • [claimed-docs] “This endpoint supports idempotent requests.”
   • [claimed-docs] “the transactions list endpoint supports pagination controls.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://teller.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://teller.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://teller.io/openapi.json, https://teller.io/swagger.json, https://teller.io/api/openapi.json, …”

   proof ↗⚑ flag

Agent operations

1. ai-native userAn agent can operate the platform — create link sessions, retrieve balances and transactions, and manage connections through the API or an MCP surface with scoped credentials

   weight 3 · round to Stripe Financial Connections
   Stripe Financial Connections~partialprobed6/10

   Financial Connections' API clearly supports creating link sessions, retrieving balances/transactions, and managing connections (docs-2,3,4,5,6,14), and Stripe publishes both a generic MCP server for AI agents to interact with the Stripe API (docs-18, probe-4) and an explicit 'Financial insights for agents' use case mentioning agent-powered spending analysis and balance/transaction monitoring (docs-11). However, no evidence specifies that the MCP surface exposes Financial-Connections-specific tools (e.g., create_link_session, get_balances) or how scoped/restricted credentials are issued for agent use. missing for 10: explicit MCP tool list for Financial Connections actions, documentation of scoped-credential/permission model for agent access, independent confirmation of agent operation end-to-end.

   • [claimed-docs] “Access an account’s current and available balances.”
   • [claimed-docs] “Access an account’s transaction history.”
   • [claimed-docs] “Use collectFinancialConnectionsAccounts to launch the authentication flow from your client using the client_secret returned by your server”
   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”
   • [claimed-docs] “Use the relink API to help your user reconnect their inactive account.”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s kno…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Teller~partialprobed4/10

   Teller's REST API supports the core primitives (balances, transactions, identity, connect/link sessions via Teller Connect, mTLS-scoped credentials) that an agent could call, but there is no evidence of an MCP server, agent-oriented SDK, or machine-readable API spec — probes for llms.txt, docs.md, and openapi.json all returned 404, indicating no first-class AI-agent integration surface. missing for 10: an MCP server or agent tool-calling interface, machine-readable OpenAPI/llms.txt discovery, and any documentation framing agent-driven scoped access.

   • [claimed-docs] “Teller lets users connect their accounts in seconds, and you verify account ownership, ACH details, balances, and transactions with ease.”
   • [claimed-docs] “The account balances API provides your application with live, real-time account balances.”
   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”
   • [claimed-docs] “The Teller API uses mTLS to authenticate the API caller. Teller issues client certificates that you use to connect to the Teller API.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://teller.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://teller.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://teller.io/openapi.json, https://teller.io/swagger.json, https://teller.io/api/openapi.json, …”

   proof ↗⚑ flag

Consent

1. ops leadEnd users can see and revoke what they've shared — a documented consent surface or portal where a user manages which apps hold access to their bank data

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   No evidence describes an end-user-facing consent dashboard or portal where users can view/revoke which apps hold access to their linked bank data; documentation only covers merchant-side integration flows (linking, webhooks, relink API) and business-side account/balance/transaction access controls. This is a fair axis for a financial data aggregation product (competitors offer such portals), but Stripe's evidence pack contains no mention of a user-facing consent management surface.

   • [claimed-docs] “Use collectFinancialConnectionsAccounts to launch the authentication flow from your client using the client_secret returned by your server”
   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Use the relink API to help your user reconnect their inactive account.”
   • [claimed-docs] “allowing them to save and reuse their bank account details across Stripe businesses”

   proof ↗⚑ flag

   Teller—none0/10

   No evidence of an end-user consent dashboard or portal where users can view or revoke third-party app access to their bank data; docs cover enrollment, data APIs, webhooks, and auth but nothing about consent management/revocation UI. Missing for 10: a documented end-user consent portal, revocation flow/API, and any independent confirmation of such a surface.

   • [claimed-docs] “finish up by linking your first financial accounts to Teller.”
   • [claimed-docs] “**100 enrollment limit** — An enrollment represents one bank login, which may include multiple accounts”
   • [claimed-docs] “Learn about Teller Connect and how to integrate and customize it for you application.”

   proof ↗⚑ flag

Deletion

1. ops leadSever and clean up — a documented way to delete a connection or user and have the platform stop collecting and purge held data

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   No evidence pack item documents a disconnect/delete-account API, data deletion/purge process, or account termination workflow for Financial Connections; the docs focus on connecting, collecting, and refreshing account data, not severing/purging it. Missing for 10: documented disconnect/delete API or account endpoint, data retention/purge policy, and any confirmation that collection stops and data is deleted upon disconnection.

   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Use the relink API to help your user reconnect their inactive account.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/financial-connections.md # Stripe Financial Connections Access permissioned data from yo…”

   proof ↗⚑ flag

   Teller—none0/10

   No evidence in the pack documents a deletion/disconnection flow, data purge process, or user/connection removal API — the docs focus on connecting, verifying, and retrieving financial data (balances, transactions, identity, payments) with no mention of offboarding or data deletion mechanics.

   ⚑ flag

Scopes

1. developerI request only the data scopes I need — product-scoped consents and documented data-minimization controls, not an all-or-nothing grant

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections~partialclaimed6/10

   Docs show Financial Connections lets you request specific data types (balances, ownership, transactions) rather than a single blanket account link, and different use-case flows (ACH, Connect payouts, personal finance apps) pull only the subset of data relevant to that use case, implying product-scoped consent. However, there's no explicit documentation of a formal 'permissions' parameter/API, no description of the actual consent screen showing scoped checkboxes, and no independent/community evidence confirming data-minimization behavior in practice. Missing for 10: explicit permissions/scopes API reference, documented consent UI mechanics, and independent verification that only requested scopes are granted.

   • [claimed-docs] “Access an account’s current and available balances.”
   • [claimed-docs] “Access account owners’ names and mailing addresses.”
   • [claimed-docs] “Access an account’s transaction history.”
   • [claimed-docs] “Collect a bank account for ACH Direct Debit payments while using account data, including balances.”
   • [claimed-docs] “Collect a bank account to use for Connect payouts, and use account data, such as ownership details, with your integration.”
   • [claimed-docs] “Collect user accounts and gain access to account data to build more complex integrations, such as personal finance apps.”

   proof ↗⚑ flag

   Teller—none0/10

   The evidence describes separate API resources (balances, transactions, identity, payments) but there is no documentation of a consent flow where developers can request only specific scopes or where end-users see a product-scoped grant rather than an all-or-nothing authorization. No mention of a 'products' parameter, granular permission toggles, or data-minimization consent screen in Teller Connect.

   • [claimed-docs] “Teller lets users connect their accounts in seconds, and you verify account ownership, ACH details, balances, and transactions with ease.”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “Learn about Teller Connect and how to integrate and customize it for you application.”

   proof ↗⚑ flag

Refresh

1. developerTrigger an on-demand refresh of a connected account's data through the API when my use case needs now-fresh data, with the refresh semantics documented

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections~partialcommunity5/10

   Docs mention webhook events fired after a balance, ownership, and transaction 'refresh' is complete (docs-13, docs-24, docs-25), implying an underlying refresh mechanism exists, but the evidence pack never documents the actual API call/endpoint to trigger an on-demand refresh or its semantics (rate limits, latency, cost). A community report even suggests refresh is limited to daily pulls rather than freely on-demand, indicating real constraints on freshness. Missing for 10: explicit API reference for a refresh endpoint, documented refresh-trigger semantics (frequency limits, sync latency), and confirmation this applies across balance/ownership/transaction data uniformly.

   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”
   • [community] “The limit to only daily pulls and up to 180 days of historical data is pretty disappointing. Would expect Stripe to push the envelope here..…”

   proof ↗⚑ flag

   Teller~partialclaimed4/10

   Teller's balances API is documented as returning "live, real-time account balances" (teller-docs-2, teller-docs-22), implying each API call effectively refreshes data on demand, and webhooks fire on data changes (teller-docs-7, teller-docs-17). However, there is no dedicated refresh/sync endpoint, no documented semantics for how or when transaction data is refreshed, and no explanation of caching or refresh triggers for the transactions API — missing for 10: a documented refresh endpoint/mechanism, explicit refresh semantics (latency, staleness window), and confirmation for transactions data (not just balances).

   • [claimed-docs] “The account balances API provides your application with live, real-time account balances.”
   • [claimed-docs] “Guaranteed live account balances. Used for underwriting or ensuring sufficient funds are available before submitting an ACH debit.”
   • [claimed-docs] “To register a new webhook, you need to have a URL in your app that Teller can call. You can configure a new webhook from the Teller Dashboar…”
   • [claimed-docs] “Teller sends webhook events when specific conditions or changes are detected in user enrollments or their financial data.”
   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”

   proof ↗⚑ flag

Webhooks

1. developerData changes arrive as signed webhooks — new transactions, balance updates, connection state changes — so my system stays current without polling

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections~partialclaimed6/10

   Docs confirm signed webhook events for account linking, balance refresh, ownership refresh, and transaction refresh, directly enabling event-driven freshness instead of polling. However, evidence lacks detail on signature verification specifics, latency/timeliness guarantees, connection state-change events beyond relink, and independent/hands-on confirmation of webhook reliability. missing for 10: signature verification documentation detail, guaranteed latency/freshness SLAs, broader connection-state-change event coverage, independent developer corroboration of webhook reliability.

   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”
   • [claimed-docs] “Use the relink API to help your user reconnect their inactive account.”

   proof ↗⚑ flag

   Teller~partialclaimed5/10

   Teller docs confirm webhook events exist for enrollment/data changes (teller-docs-17) and describe how to register a webhook URL (teller-docs-7), covering the general 'push not poll' data-freshness goal. However, the evidence pack contains no mention of webhook payload signing/verification mechanism, nor independent confirmation that webhooks reliably fire for transactions, balances, and connection-state changes as described. Missing for 10: explicit signature/verification scheme for webhooks, documented list of event types (transaction created, balance updated, enrollment disconnected), and third-party/hands-on confirmation of webhook delivery reliability.

   • [claimed-docs] “To register a new webhook, you need to have a URL in your app that Teller can call. You can configure a new webhook from the Teller Dashboar…”
   • [claimed-docs] “Teller sends webhook events when specific conditions or changes are detected in user enrollments or their financial data.”

   proof ↗⚑ flag

Coverage

1. founderThe platform documents how many institutions it reaches and where — published coverage numbers and geographies I can check against where my users actually bank

   weight 3 · round to Stripe Financial Connections
   Stripe Financial Connections~partialcommunity4/10

   Stripe's docs publish a single coverage figure ("more than 12,000 supported banks") but no official breakdown of geographies or country-level coverage; the only geography signal comes from community reports that the product is US-only (and doesn't work for Canada or other countries), which isn't corroborated by first-party documentation. Missing for 10: official geographic coverage documentation, per-country institution counts, and any first-party statement matching the community's US-only observation.

   • [claimed-docs] “Users select their bank from frequently chosen institutions or by searching more than 12,000 supported banks.”
   • [community] “Curious that they translated it to German based on my phone settings for a product that only supports US banks? (I don't mind that it is US …”
   • [community] “Only available in the US.”
   • [community] “guessing this doesn't work with Canada”

   proof ↗⚑ flag

   Teller~partialcommunity3/10

   Teller publishes a single aggregate figure ("more than 7,000 financial institutions") but no breakdown by geography, no searchable list of supported institutions, and no way for a founder to verify coverage against their specific user base. The old community thread references only a handful of UK banks, but this appears to be from an earlier version of the product and is not directly comparable to the current 7,000+ claim. missing for 10: geographic breakdown, institution-name list/coverage tool, independent verification of the 7,000 figure.

   • [claimed-docs] “Connect instantly with more than 7,000 financial institutions and fall back to same-day ACH microdeposit verification for everyone else.”
   • [community] “Teller is available today for Santander UK, Barclays, Natwest, Nationwide, RBS, Isle of Man Bank, and Ulster Bank.”

   proof ↗⚑ flag

Status

1. ops leadPer-institution health is visible — documented institution statuses, outage or degradation signals, and error codes that distinguish a bank problem from my problem

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections~partialclaimed3/10

   Docs show webhook events for refresh completions (balance, ownership, transaction) and a relink API for inactive accounts, which provide some signal that an account/connection has degraded, but there is no documented institution status page, no outage/degradation signal feed, and no error-code taxonomy that distinguishes a bank-side problem from an integration-side problem. Missing for 10: institution health/status dashboard, explicit outage signals, and documented error codes separating bank vs. merchant-side failures.

   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “Use the relink API to help your user reconnect their inactive account.”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”

   proof ↗⚑ flag

   Teller—none0/10

   No evidence of a status page, per-institution outage/degradation signals, or documented error codes distinguishing bank-side failures from client-side errors. Webhooks are mentioned for enrollment/data change events, but nothing ties to institution health visibility or error taxonomy.

   ⚑ flag

Multi product

1. developerOne link session can power multiple data products — auth, balances, transactions, identity — without forcing the user through separate connection flows per product

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections✓fullcommunity8/10

   Docs confirm one Financial Connections session/client_secret lets a user link an account and expose auth, balances, ownership/identity, and transactions data together (docs-1, docs-8/9/10, docs-2/3/4), and a community integrator confirms using the same link for verification, ACH fraud signal, and adjacent Stripe products (comm-6). missing for 10: no explicit first-party statement that all four data products are requested/returned in a single session without re-prompting the user, and one community report notes transactions/other data products were 'coming soon' at beta (comm-8), leaving some ambiguity about full simultaneous availability.

   • [claimed-docs] “You can use one integration to instantly verify bank accounts for ACH payments, reduce underwriting risk with balances data, mitigate fraud …”
   • [claimed-docs] “Access an account’s current and available balances.”
   • [claimed-docs] “Access account owners’ names and mailing addresses.”
   • [claimed-docs] “Access an account’s transaction history.”
   • [claimed-docs] “Collect a bank account for ACH Direct Debit payments while using account data, including balances.”
   • [claimed-docs] “Collect a bank account to use for Connect payouts, and use account data, such as ownership details, with your integration.”
   • [claimed-docs] “Collect user accounts and gain access to account data to build more complex integrations, such as personal finance apps.”
   • [community] “I work at one of the companies that integrated Financial Connections during its beta, moving from Plaid Auth. We use the link to bank accoun…”
   • [community] “By clicking 'Start Now', I try to visit dashboard.stripe.com/financial-connections/application and it redirects to the test dashboard. A lot…”

   proof ↗⚑ flag

   Teller✓fullclaimed7/10

   Teller's architecture centers on a single enrollment/access-token granted via one Connect flow, which then powers balances, transactions, identity, and account-details APIs (teller-docs-1, teller-docs-4/19 note identity covers 'all accounts the end-user granted access authorization', teller-docs-13 defines an enrollment as one bank login with multiple accounts). This implies a single link session unlocks multiple data products without repeated connect flows. missing for 10: an explicit statement confirming no re-authentication is needed per product, and independent/hands-on developer corroboration of this multi-product single-session behavior.

   • [claimed-docs] “Teller lets users connect their accounts in seconds, and you verify account ownership, ACH details, balances, and transactions with ease.”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “**100 enrollment limit** — An enrollment represents one bank login, which may include multiple accounts”
   • [claimed-docs] “The account balances API provides your application with live, real-time account balances.”
   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”

   proof ↗⚑ flag

Quickstart

1. developerGo from signup to my first linked sandbox account fast — self-serve API keys, a runnable quickstart, and client libraries in my language

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections~partialprobed6/10

   Docs show a testable sandbox flow (test institutions requiring no real credentials, client_secret-based auth via collectFinancialConnectionsAccounts) and an official CLI, indicating a runnable quickstart path to a first linked sandbox account. However, the pack lacks explicit evidence of self-serve API key issuance or language-specific client library listings for Financial Connections. missing for 10: explicit self-serve API key/dashboard signup evidence, explicit client library/SDK language coverage, and independent hands-on confirmation of quickstart speed.

   • [claimed-docs] “the authentication flow exclusively shows a selection of test institutions managed by Stripe. The client can link accounts from any of these…”
   • [claimed-docs] “Use collectFinancialConnectionsAccounts to launch the authentication flow from your client using the client_secret returned by your server”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [community] “By clicking 'Start Now', I try to visit dashboard.stripe.com/financial-connections/application and it redirects to the test dashboard. A lot…”

   proof ↗⚑ flag

   Teller~partialclaimed5/10

   Docs confirm a quickstart guide that ends with linking a first sandbox account, a dedicated sandbox environment with simulated data and OTP test flows, and at least one client library (React hook/component) for Teller Connect. However, authentication requires mTLS with client certificates rather than a simple self-serve API key (raising integration friction), and there's no evidence of client libraries beyond React or of a fast self-serve signup process for keys/certs. Missing for 10: explicit self-serve API-key/signup flow, additional-language client libraries (Node/Python/etc.), independent hands-on confirmation of speed from quickstart to first linked sandbox account.

   • [claimed-docs] “finish up by linking your first financial accounts to Teller.”
   • [claimed-docs] “The sandbox environment uses simulated data and never connects to real financial institutions.”
   • [claimed-docs] “`otp` () - Will follow an OTP MFA flow whereby the user will be asked to select a contact to send an OTP code. The correct code is `0000`”
   • [claimed-docs] “The Teller API uses mTLS to authenticate the API caller. Teller issues client certificates that you use to connect to the Teller API.”
   • [github] “React hook and component for integrating with Teller Connect”

   proof ↗⚑ flag

Sandbox

1. developerA sandbox with test institutions and documented test credentials lets me exercise linking, data retrieval, and error states end-to-end before touching a real bank account

   weight 3 · round to Teller
   Stripe Financial Connections✓fullclaimed7/10

   Docs explicitly describe a dedicated testing mode where the authentication flow shows only Stripe-managed test institutions that can be linked without credentials, enabling end-to-end exercise of the linking flow before touching real banks. However, evidence doesn't detail documented test credentials for specific error-state scenarios (e.g., forced failures, specific test account numbers for different data states) or confirm sandbox coverage of balances/transactions/ownership retrieval scenarios. Missing for 10: documented specific test credentials/account numbers for triggering distinct error states, and explicit confirmation that data retrieval (balances/transactions) can be exercised in test mode with corroborating independent developer accounts.

   • [claimed-docs] “the authentication flow exclusively shows a selection of test institutions managed by Stripe. The client can link accounts from any of these…”
   • [claimed-docs] “The client can link accounts from any of these institutions without providing credentials.”

   proof ↗⚑ flag

   Teller✓fullclaimed8/10

   Docs confirm a sandbox environment with simulated data that never touches real institutions, plus documented test credentials/flows (e.g., OTP MFA code '0000'), and full documented APIs for linking, balances, transactions, identity, and payments that can be exercised in sandbox. Missing for 10: independent/hands-on developer accounts specifically validating the sandbox test-credential workflow and documented error-state simulation beyond MFA.

   • [claimed-docs] “The sandbox environment uses simulated data and never connects to real financial institutions.”
   • [claimed-docs] “`otp` () - Will follow an OTP MFA flow whereby the user will be asked to select a contact to send an OTP code. The correct code is `0000`”
   • [claimed-docs] “The account balances API provides your application with live, real-time account balances.”
   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”
   • [claimed-docs] “**100 enrollment limit** — An enrollment represents one bank login, which may include multiple accounts”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Financial Connections~partialprobed5/10

   Most Financial Connections operations (creating sessions, retrieving balances/ownership/transactions, webhooks, relink) are documented as pure server-side API calls, and Stripe also exposes an MCP server and CLI for agent-driven interaction with the API (docs-11, docs-18, probe-4, probe-5). However, the actual account-linking/authentication step inherently requires the client-side `collectFinancialConnectionsAccounts` hosted flow (docs-6, docs-7) — a consumer-facing UI that cannot be bypassed via pure API calls, so an AI-native user cannot complete the core linking action through API alone. Missing for 10: evidence of a pure-API path to complete bank authentication/consent without the client SDK, and confirmation that all Dashboard-configurable settings are also API-exposed.

   • [claimed-docs] “Use collectFinancialConnectionsAccounts to launch the authentication flow from your client using the client_secret returned by your server”
   • [claimed-docs] “Users select their bank from frequently chosen institutions or by searching more than 12,000 supported banks.”
   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s kno…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Use the relink API to help your user reconnect their inactive account.”

   proof ↗⚑ flag

   Teller~partialclaimed5/10

   Teller exposes rich API endpoints for balances, transactions, identity, payments, and account details (teller-docs-2,3,4,5,6), suggesting most financial data operations are API-driven, but account linking is done through the Teller Connect UI widget and webhook registration is explicitly described as being configured 'from the Teller Dashboard' rather than via an API endpoint (teller-docs-7), indicating some UI-only actions lack documented API equivalents. Missing for 10: an API endpoint for webhook/enrollment management equivalent to Dashboard actions, explicit documentation confirming full API/UI parity, and independent confirmation of no UI-exclusive features.

   • [claimed-docs] “The account balances API provides your application with live, real-time account balances.”
   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”
   • [claimed-docs] “The payments resource allows you to send payments to yourself or a 3rd party on behalf of the end-user from their account. Currently the onl…”
   • [claimed-docs] “To access account details from these institutions, you can implement the 'Verify Account Details via Microdeposit' flow.”
   • [claimed-docs] “To register a new webhook, you need to have a URL in your app that Teller can call. You can configure a new webhook from the Teller Dashboar…”
   • [claimed-docs] “Learn about Teller Connect and how to integrate and customize it for you application.”

   proof ↗⚑ flag

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

   weight 3 · round to Teller
   Stripe Financial Connections—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

   Teller~partialcommunity3/10

   Teller exposes account balances/transactions/identity via JSON API (open format), and a community member built a third-party script exporting Teller data to CSV/QIF, showing data can be extracted. However there is no first-party 'export all my data and leave' feature, no bulk data-export or account-deletion tooling, and no documentation of full data portability for end users. Missing for 10: official bulk export/download-all-data feature, documented account closure/data portability process, and independent confirmation beyond one hobbyist script.

   • [community] “I built a little script to export my accounts to CSV/QIF. Super easy to use API! https://github.com/scottrobertson/teller-export”
   • [claimed-docs] “The account balances API provides your application with live, real-time account balances.”
   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”
   • [claimed-docs] “Identity provides you with all of the accounts the end-user granted your application access authorization along with beneficial owner identi…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Stripe Financial Connections—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

   Teller—none0/10

   Teller is a closed, proprietary financial API/service; the only open-source artifact found is a client-side React SDK wrapper (teller-connect-react), not the product's core source. A community comment explicitly wishes Teller were open source, implying it is not, and no license or source-availability claims appear in vendor docs.

   • [github] “React hook and component for integrating with Teller Connect”
   • [community] “I'd much prefer that this were just open source so I don't have to share my bank credentials.”

   proof ↗⚑ flag

Pay by bank

1. developerInitiate a bank payment from a connected account — a documented pay-by-bank or payment-initiation product with its live geographies stated honestly

   weight 2 · round to Teller
   Stripe Financial Connections~partialcommunity4/10

   Financial Connections lets a linked bank account be used to collect ACH Direct Debit payments (docs-8, docs-16, docs-17, docs-27-29), which is a debit-based bank payment initiation flow, but this is not a full 'pay-by-bank' push-payment product, and there is no documented statement of live geographies — the only geography signal comes from community reports that it is US-only (comm-9, comm-11, comm-12), not honest first-party docs. Missing for 10: explicit documented geography/coverage list, and evidence of true push-payment (real-time transfer) initiation rather than just ACH debit collection.

   • [claimed-docs] “Collect a bank account for ACH Direct Debit payments while using account data, including balances.”
   • [claimed-docs] “instant | Financial Connections only, with no manual entry and microdeposit fallback”
   • [claimed-docs] “Reduce your payment failure rate from closed or inactive accounts - Improve payments conversion by keeping users on session, instead of forc…”
   • [claimed-docs] “Reduce your payment failure rate from closed or inactive accounts”
   • [claimed-docs] “Improve payments conversion by keeping users on session, instead of forcing them to leave your payments flow to locate their accounts and ro…”
   • [claimed-docs] “Save development time by eliminating the need to create a custom bank account collection form”
   • [community] “Curious that they translated it to German based on my phone settings for a product that only supports US banks? (I don't mind that it is US …”
   • [community] “Only available in the US.”
   • [community] “guessing this doesn't work with Canada”

   proof ↗⚑ flag

   Teller~partialclaimed5/10

   Teller docs confirm a payments API that lets a developer send a payment from a connected account to self or a third party, with idempotency support (teller-docs-5, teller-docs-18, teller-docs-20), and separately state broad institution coverage (7,000+ US institutions) for account connectivity (teller-docs-11). However, the payments API explicitly supports only the Zelle scheme currently, not general ACH/bank-transfer payment initiation, and there is no explicit geography statement scoped to the payments product itself (vs. the broader account-linking coverage claim). Missing for 10: multi-rail payment initiation beyond Zelle, an explicit payments-specific geography/eligibility statement, and independent/hands-on confirmation that payment initiation works live in production.

   • [claimed-docs] “The payments resource allows you to send payments to yourself or a 3rd party on behalf of the end-user from their account. Currently the onl…”
   • [claimed-docs] “The payments resource allows you to send payments to yourself or a 3rd party on behalf of the end-user from their account.”
   • [claimed-docs] “This endpoint supports idempotent requests.”
   • [claimed-docs] “Connect instantly with more than 7,000 financial institutions and fall back to same-day ACH microdeposit verification for everyone else.”
   • [claimed-docs] “**100 enrollment limit** — An enrollment represents one bank login, which may include multiple accounts”

   proof ↗⚑ flag

Recurring

1. developerRecurring bank payments are supported — variable recurring payments, standing consents, or documented recurring debit flows built on the connection

   weight 2 · round to Stripe Financial Connections
   Stripe Financial Connections~partialcommunity4/10

   Financial Connections explicitly supports collecting a bank account for ACH Direct Debit payments (docs-8, docs-16, docs-17), and ACH Direct Debit mandates are inherently reusable for repeat debits, but the evidence never documents a specific recurring/subscription debit flow, standing consent, or variable recurring payment (VRP) mechanism built on top of the connection. Missing for 10: explicit documentation of mandate reuse for recurring charges, standing consent/authorization language, and any VRP-style flow or recurring-debit API guidance.

   • [claimed-docs] “Collect a bank account for ACH Direct Debit payments while using account data, including balances.”
   • [claimed-docs] “instant | Financial Connections only, with no manual entry and microdeposit fallback”
   • [claimed-docs] “Reduce your payment failure rate from closed or inactive accounts - Improve payments conversion by keeping users on session, instead of forc…”
   • [community] “I work at one of the companies that integrated Financial Connections during its beta, moving from Plaid Auth. We use the link to bank accoun…”

   proof ↗⚑ flag

   Teller—none0/10

   Teller's payments resource only supports Zelle-based payments to self or third parties; there is no mention of variable recurring payments, standing consents, or documented recurring debit flows.

   • [claimed-docs] “The payments resource allows you to send payments to yourself or a 3rd party on behalf of the end-user from their account. Currently the onl…”
   • [claimed-docs] “The payments resource allows you to send payments to yourself or a 3rd party on behalf of the end-user from their account.”
   • [claimed-docs] “This endpoint supports idempotent requests.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   No evidence in the pack mentions data residency, regional storage options, or user/customer choice of data location for Financial Connections; comments even note it's US-only, which suggests no regional selection capability. Missing for 10: any documentation of region/residency configuration, data localization options, or EU/other data center choices.

   • [community] “Only available in the US.”
   • [community] “guessing this doesn't work with Canada”

   proof ↗⚑ flag

   Teller—none0/10

   No evidence of any data residency/region selection controls in Teller's docs or community discussion; the pack covers account linking, payments, mTLS auth, and webhooks but nothing about data storage location choice.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   No evidence in the pack addresses data retention controls, deletion APIs/mechanisms, or configurable data lifecycle policies for Financial Connections data; docs describe data access (balances, transactions, ownership) and webhooks but not retention/deletion controls for AI-native users. Missing for 10: any documentation of data retention settings, account/data deletion endpoints, or user-controlled data lifecycle management.

   ⚑ flag

   Teller—none0/10

   No evidence anywhere in the pack addresses data retention policies, deletion controls, or data lifecycle management for end-user financial data; docs cover connectivity, API resources, auth, and webhooks but nothing on retention/deletion controls.

   ⚑ flag

Cashflow

1. finance leadThe platform derives income and cash-flow signals from connected accounts — recurring streams, payroll detection, or documented income verification products built on the same data

   weight 2 · round drawn
   Stripe Financial Connections—none0/10

   Financial Connections documents raw data access (balances, transactions, ownership) and encourages building 'fintech products with transactions data' or 'personal finance apps,' but there is no evidence of Stripe itself deriving income/cash-flow signals — no recurring-stream detection, payroll identification, or documented income-verification product built on this data. Community discussion also focuses on account linking reliability and pricing, not income analytics.

   • [claimed-docs] “Access an account’s transaction history.”
   • [claimed-docs] “Collect user accounts and gain access to account data to build more complex integrations, such as personal finance apps.”
   • [claimed-docs] “build new fintech products with transactions data”

   proof ↗⚑ flag

   Teller—none0/10

   Teller's docs cover balances, transactions, categorization, and identity, but no evidence describes recurring-stream detection, payroll detection, or an income-verification product built on the transaction data — this is a fair axis for an account-aggregation platform but unaddressed in the evidence pack.

   ⚑ flag

Enrichment

1. developerRaw bank transactions come back enriched — cleaned merchant names, categories, and logos — documented as a capability of the platform, not left as an exercise for me

   weight 2 · round to Teller
   Stripe Financial Connections—none0/10

   The docs describe raw transaction history access (docs-4) but never mention any enrichment layer — no cleaned/normalized merchant names, spending categories, or merchant logos are documented anywhere in the evidence pack. Community threads even note the transactions product was still 'Coming Soon' at one point, with no follow-up confirming enrichment features shipped.

   • [claimed-docs] “Access an account’s transaction history.”
   • [claimed-docs] “Collect user accounts and gain access to account data to build more complex integrations, such as personal finance apps.”
   • [community] “By clicking 'Start Now', I try to visit dashboard.stripe.com/financial-connections/application and it redirects to the test dashboard. A lot…”

   proof ↗⚑ flag

   Teller~partialclaimed4/10

   Docs confirm the transactions API includes categorization of transactions (teller-docs-16, teller-docs-3), but there is no documented evidence of merchant name cleaning/normalization or merchant logos as a platform capability. missing for 10: documented merchant-name cleaning, logo enrichment, independent corroboration of enrichment quality.

   • [claimed-docs] “the category that the transaction belongs to. Teller uses the following values for categorization”
   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”

   proof ↗⚑ flag

Transactions

1. developerPull transaction history for a connected account through the API — paginated, with documented history depth and a sync pattern for fetching only what changed

   weight 3 · round to Teller
   Stripe Financial Connections~partialcommunity5/10

   Docs confirm access to an account's transaction history (docs-4) and a webhook-driven refresh model (transaction refresh completed events, docs-25) that lets a client know when to pull new data, and community evidence confirms documented depth/cadence limits (180 days history, daily pulls) as a real sync pattern. However, there is no explicit documentation in the pack of the transactions list endpoint's pagination parameters (cursor/starting_after) or a formal delta/sync-token mechanism for fetching only changed transactions. Missing for 10: explicit API pagination documentation for the transactions list endpoint, and a documented incremental-sync/cursor mechanism beyond the refresh webhook.

   • [claimed-docs] “Access an account’s transaction history.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”
   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [community] “The limit to only daily pulls and up to 180 days of historical data is pretty disappointing. Would expect Stripe to push the envelope here..…”

   proof ↗⚑ flag

   Teller~partialcommunity6/10

   Docs confirm a transactions API with pagination support and category enrichment, plus webhooks that fire on data changes (a plausible 'fetch only what changed' mechanism), and a community report of successfully exporting transaction history via the API. However, there's no documented statement of how far back transaction history extends, and no explicit incremental-sync/cursor endpoint beyond generic webhook notifications. Missing for 10: documented history depth/lookback window, an explicit delta-sync or cursor-based endpoint (not just webhooks) for changed transactions.

   • [claimed-docs] “The transactions API exposes the ledger transactions of a financial account.”
   • [claimed-docs] “the transactions list endpoint supports pagination controls.”
   • [claimed-docs] “the category that the transaction belongs to. Teller uses the following values for categorization”
   • [claimed-docs] “Teller sends webhook events when specific conditions or changes are detected in user enrollments or their financial data.”
   • [claimed-docs] “To register a new webhook, you need to have a URL in your app that Teller can call. You can configure a new webhook from the Teller Dashboar…”
   • [community] “I built a little script to export my accounts to CSV/QIF. Super easy to use API! https://github.com/scottrobertson/teller-export”

   proof ↗⚑ flag