Stripe Financial Connections vs MX

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 drawn
   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

   MX✓fullclaimed8/10

   MX docs describe the Connect Widget as a ready-made, embeddable UI that prompts end users to authenticate with their institution credentials, paired with the Platform API for server-side session/member creation, matching the drop-in hosted flow with no custom institution UI needed. Webhooks and member/account tokens (e.g., guid-based member connections) round out the server-to-client flow. missing for 10: explicit mention of a 'connect token' generation endpoint and independent/third-party confirmation of the end-to-end session-create-then-widget-open flow.

   • [claimed-docs] “MX's ready-made UI that can be embedded in your application to aggregate users' account data by prompting end users to connect to their fina…”
   • [claimed-docs] “Use the Connect Widget and Platform API to let end users connect to their accounts.”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice.”
   • [claimed-docs] “To test OAuth in the Connect Widget when it's embedded in a WebView, you must load the financial institution's OAuth window in the device's …”
   • [claimed-docs] “MX automatically aggregates each `member` approximately every 24 hours.”

   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

   MX—none0/10

   Evidence shows MX supports OAuth in its Connect Widget (mx-docs-23) but there is no documentation of overall OAuth coverage across institutions or any stated plan for retiring legacy credential-based (screen-scraped) connections, which is the core of this story.

   • [claimed-docs] “To test OAuth in the Connect Widget when it's embedded in a WebView, you must load the financial institution's OAuth window in the device's …”

   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

   MX—none0/10

   The evidence pack covers MX's connectivity products (aggregation, IAV, AOI, microdeposits, webhooks) but never documents connection/member status codes (e.g., expired, revoked, challenged) or a dedicated re-authentication/update flow that lets users fix a broken link without re-onboarding. This is a plausible and expected capability for an account-aggregation platform, but nothing in the pack substantiates it.

   ⚑ flag

Agent access

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

   weight 2 · round to MX
   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

   MX✓fullprobed9/10

   MX hosts a working llms.txt at docs.mx.com/llms.txt (confirmed HTTP 200 with structured doc links) and also documents an official MCP server, both explicitly agent-oriented entry points into their docs. Missing for 10: independent third-party confirmation of an AI agent successfully consuming these resources end-to-end.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mx.com/llms.txt # MX Documentation - [Welcome to the MX Documentation](https://docs.mx.com/index.m…”
   • [probe] “official MCP server documented at https://docs.mx.com/mcp”

   proof ↗⚑ flag

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

   weight 2 · round to MX
   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

   MX~partialclaimed5/10

   MX is an API-first platform with a documented REST/OpenAPI spec (mx-gh-1, mx-docs-12/26) and webhooks (mx-docs-7/22) that could be driven headlessly from CI, but there is no explicit evidence of a CLI, headless SDK mode, or documented CI/automation workflow — the Connect Widget appears UI-embedded (mx-docs-9, mx-docs-21) which cuts against pure headless use. missing for 10: explicit CI/headless usage docs, a CLI or automation-focused SDK, confirmation that Connect flows can run without embedded UI.

   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”
   • [claimed-docs] “MX's ready-made UI that can be embedded in your application to aggregate users' account data by prompting end users to connect to their fina…”
   • [claimed-docs] “Use the Connect Widget and Platform API to let end users connect to their accounts.”

   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

   MX✓fullprobed7/10

   MX documents an official MCP server at docs.mx.com/mcp, confirmed via probe, indicating a first-party MCP integration point. Missing for 10: detailed setup/config docs excerpt, independent/hands-on confirmation of the MCP server working, and specifics on tool coverage exposed via MCP.

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

   proof ↗⚑ 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

   MX—none0/10

   MX is a financial data API/SDK platform; no evidence of an official CLI tool for developers or AI-native workflows appears in the evidence pack — only API specs, webhooks, and a widget/UI. Evidence exists of an MCP server and OpenAPI spec, but no CLI is documented.

   ⚑ flag

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

   weight 3 · round to MX
   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

   MX✓fullprobed8/10

   MX exposes a documented Platform API with OpenAPI spec (available via GitHub and Postman import), REST endpoints across account verification, aggregation, statements, and webhooks, plus llms.txt and an MCP endpoint enabling AI-native access. Missing for 10: the official openapi.json isn't directly hosted at expected docs.mx.com paths (probe 404s), and there's no independent third-party corroboration of API robustness beyond MX's own docs.

   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mx.com/llms.txt # MX Documentation - [Welcome to the MX Documentation](https://docs.mx.com/index.m…”
   • [probe] “official MCP server documented at https://docs.mx.com/mcp”
   • [claimed-docs] “Use the Connect Widget and Platform API to let end users connect to their accounts.”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”

   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

   MX—none0/10

   No evidence of scoped/least-privilege API credential issuance for agents—docs cover data connectivity, webhooks, OpenAPI spec, and even an MCP server reference, but nothing about issuing restricted-scope API keys/tokens for AI agent use.

   ⚑ 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

   MX~partialclaimed4/10

   MX publishes an official OpenAPI specification (mx-gh-1) and supports importing it into Postman for API exploration (mx-docs-12/26), which enables building typed/generated clients, but there is no evidence of dedicated first-party SDK libraries (e.g., Python, JS, Java) or SDK-specific documentation/examples. missing for 10: named official SDK packages/libraries, language-specific SDK docs, and independent confirmation of SDK usage.

   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to MX
   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

   MX✓fullclaimed8/10

   MX documents a webhooks system that sends HTTPS POST callbacks so developers can subscribe to specific events, clearly supporting webhook-based event subscription. Missing for 10: an exhaustive list of supported event types and independent/hands-on confirmation beyond first-party docs.

   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to MX
   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

   MX~partialclaimed5/10

   MX's marketing pages describe personalized financial guidance and a conversational 'ask about your money' experience generated from each consumer's data (mx-docs-14, mx-docs-27), which matches the AI-insights story, and mx-docs-13 references 'data-driven intelligence.' However, these are thin, high-level marketing snippets rather than detailed product docs, and there is no independent/hands-on corroboration or technical documentation of the underlying AI model or insight-generation pipeline. Missing for 10: dedicated technical documentation of the AI/insights feature, concrete examples of generated insights, and independent verification of the claim.

   • [claimed-docs] “Use data-driven intelligence about your customers”
   • [claimed-docs] “Personalized financial guidance generated from each consumer's financial data, surfaced in a relevant and timely experience”
   • [claimed-docs] “Provide an experience where consumers can ask about their money in plain language and act on the answer, with every figure pulled from real …”
   • [claimed-docs] “Access account and transaction history all in one view. Use the data to increase multi-product adoption, and build trust.”

   proof ↗⚑ 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

   MX~partialprobed3/10

   MX documents autonomous background behavior — automatic re-aggregation of accounts roughly every 24 hours and webhook callbacks for events — which could underpin background automations, and an MCP endpoint is referenced. However there's no evidence of a user-facing automation/workflow builder or agent-orchestration framework for setting up custom autonomous tasks. Missing for 10: explicit automation/workflow configuration tooling, evidence of AI-agent-driven autonomous task execution beyond scheduled sync, and independent confirmation of the MCP server's automation capabilities.

   • [claimed-docs] “MX automatically aggregates each `member` approximately every 24 hours.”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice.”
   • [probe] “official MCP server documented at https://docs.mx.com/mcp”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

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

   Evidence shows Stripe's MCP server lets external AI agents call the Stripe API and a customer use-case of building agent-powered spending analysis apps, but there is no evidence of a built-in AI assistant inside Financial Connections itself that a user can delegate tasks to.

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

   MX—none0/10

   The evidence shows MX enabling data connectivity and hints at conversational/personalized finance experiences (mx-docs-27, mx-docs-13/14) that MX's customers could build for their end-users, but there is no evidence of a built-in AI assistant inside the MX product itself that an AI-native user could delegate tasks to.

   ⚑ flag

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

   weight 2 · round to MX
   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

   MX~partialprobed6/10

   MX documents an official MCP server (mx-probe-3) that would let AI agents issue natural-language commands against the platform, and marketing copy (mx-docs-27) describes enabling plain-language financial queries. However, there is no detailed documentation of the NL command set, limits, or hands-on confirmation of how well it works. Missing for 10: detailed MCP tool/command documentation, independent verification of NL command execution, and coverage of edge cases/limitations.

   • [probe] “official MCP server documented at https://docs.mx.com/mcp”
   • [claimed-docs] “Provide an experience where consumers can ask about their money in plain language and act on the answer, with every figure pulled from real …”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to MX
   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

   MX~partialprobed5/10

   MX publishes an OpenAPI spec (mx-gh-1) that users can import into Postman to explore requests/responses (mx-docs-12, mx-docs-26), and provides a sandbox test-platform with test institutions (mx-docs-8). However, there is no evidence of an embedded, in-docs interactive API reference with directly runnable examples (e.g., a Swagger/Redoc-style try-it-now console) — probes for a hosted openapi.json on the docs site 404 (mx-probe-2), meaning users must leave the docs and use an external tool like Postman to run calls. Missing for 10: an in-browser interactive explorer with click-to-run examples, and confirmation the OpenAPI spec is directly hosted/interactive on docs.mx.com rather than requiring external import.

   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”
   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [claimed-docs] “We offer four test institutions that you can use”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mx.com/openapi.json, https://docs.mx.com/swagger.json, https://docs.mx.com/api/openapi.…”

   proof ↗⚑ flag

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

   weight 2 · round to MX
   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

   MX✓fullprobed9/10

   MX explicitly documents downloading its OpenAPI Specification for import into Postman, and a dedicated GitHub repo (mxenabled/openapi) hosts the machine-readable spec. Missing for 10: no evidence of a standard hosted openapi.json endpoint (probe found 404s at common paths), so discovery relies on docs/GitHub rather than a canonical URL.

   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”
   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mx.com/openapi.json, https://docs.mx.com/swagger.json, https://docs.mx.com/api/openapi.…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   MX✓fullclaimed7/10

   MX explicitly documents a test platform with four test institutions and OpenAPI spec/Postman import for exercising the API without touching real production financial data, plus dedicated guidance for testing the Connect Widget/OAuth flows. missing for 10: no explicit statement distinguishing a separate 'sandbox' credential set or environment isolation guarantee, and no independent/hands-on confirmation that test data never touches production systems.

   • [claimed-docs] “We offer four test institutions that you can use”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”
   • [claimed-docs] “To test OAuth in the Connect Widget when it's embedded in a WebView, you must load the financial institution's OAuth window in the device's …”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”

   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

   MX—none0/10

   Evidence confirms MX publishes an OpenAPI spec (mx-gh-1, mx-docs-12/26) but nowhere documents API versioning conventions or a formal deprecation policy for breaking changes. Missing for 10: documented version numbering scheme, deprecation timeline/notice policy, changelog of breaking changes.

   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”

   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

   MX—none0/10

   The evidence describes per-user/per-account connectivity, aggregation, and identity verification features, but nothing documents bulk or batch operations across many items/accounts/users at once. Missing for 10: any batch API endpoints, bulk data export/import operations, or documentation of multi-item processing at scale.

   ⚑ flag

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

   weight 3 · round to MX
   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

   MX~partialclaimed4/10

   MX provides webhooks that let subscribers receive event notifications (e.g., aggregation completion) which developers can use to trigger their own downstream actions, but there is no evidence of a native rules/automation engine where users define conditional trigger-action logic within MX itself. missing for 10: a documented rules/automation builder or conditional trigger-action configuration UI, evidence of built-in actions (not just external webhook consumption).

   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice.”
   • [claimed-docs] “MX automatically aggregates each `member` approximately every 24 hours.”

   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

   MX—none0/10

   MX's aggregation happens automatically on a fixed ~24-hour cycle (mx-docs-25) and webhooks push events, but there is no evidence of user-defined recurring job/workflow scheduling, cron-like configuration, or workflow orchestration for AI-native users. missing for 10: user-configurable schedule/frequency controls, workflow/orchestration engine, any AI-native automation scheduling feature.

   • [claimed-docs] “MX automatically aggregates each `member` approximately every 24 hours.”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”

   proof ↗⚑ 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 MX
   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

   MX✓fullclaimed9/10

   MX's Instant Account Verification explicitly retrieves account and routing numbers for demand deposit accounts without micro-deposits, and Tokenized Account Numbers (TANs) provide a secure tokenized alternative for ACH money movement, both documented as distinct from the separate microdeposits verification method. missing for 10: independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “you can connect to an end user's financial institution and retrieve account and routing numbers for their demand deposit accounts”
   • [claimed-docs] “With Instant Account Verification, you can connect to an end user's financial institution and retrieve account and routing numbers for their…”
   • [claimed-docs] “Tokenized Account Numbers (TANs) are substitute account numbers used for secure ACH money movement.”
   • [claimed-docs] “Microdeposits is different—it provides an alternate method for verifying account ownership by making small test deposits to an account.”

   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 Stripe Financial Connections
   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

   MX~partialclaimed6/10

   MX documents a balance product ('Get the available balance for an end user's financial accounts') confirming real-time balance retrieval for connected accounts, which aligns with the story's core ask. However, there is no explicit mention of NSF/risk-check use case, no documented latency/real-time SLA, and no dedicated endpoint spec or code sample shown in evidence. missing for 10: explicit NSF/risk-check framing, real-time performance guarantees, concrete endpoint/request-response example.

   • [claimed-docs] “Get the available balance for an end user’s financial accounts”
   • [claimed-docs] “Get the available balance for an end user's financial accounts”

   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

   MX✓fullclaimed8/10

   MX's Account Owner Identification product explicitly retrieves name and address data tied to a financial account, directly enabling ops to match account holder identity against a customer record; this is well documented with first-party docs. Missing for 10: independent/hands-on corroboration beyond MX's own docs, and no explicit mention of retrieving full contact data (phone/email) alongside name/address.

   • [claimed-docs] “you can connect to an end user's financial account to retrieve information such as their name and address”
   • [claimed-docs] “With Account Owner Identification, you can connect to an end user's financial account to retrieve information such as their name and address…”

   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

   MX~partialclaimed6/10

   MX provides Instant Account Verification (account/routing numbers) and Tokenized Account Numbers (TANs) explicitly described as 'substitute account numbers used for secure ACH money movement,' which supports handing verified account credentials to processors for payment initiation, plus a Connect Widget/Platform API for linking accounts. However, evidence does not show explicit named integrations or token-exchange flows with specific third-party payment processors (e.g., Stripe, Plaid-style processor partnerships) beyond MX's own ACH/TAN mechanism. missing for 10: documented named processor/platform integrations or partner list, explicit token-exchange API examples handing credentials to a specific external processor, independent confirmation of processor handoff working in production.

   • [claimed-docs] “you can connect to an end user's financial institution and retrieve account and routing numbers for their demand deposit accounts”
   • [claimed-docs] “With Instant Account Verification, you can connect to an end user's financial institution and retrieve account and routing numbers for their…”
   • [claimed-docs] “Tokenized Account Numbers (TANs) are substitute account numbers used for secure ACH money movement.”
   • [claimed-docs] “Use the Connect Widget and Platform API to let end users connect to their accounts.”
   • [github] “This repository contains the OpenAPI specification for the MX Platform API”

   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 to MX
   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

   MX✓fullprobed8/10

   MX publishes a full OpenAPI specification (mx-gh-1, mx-docs-12/26) covering structured request/response payloads across accounts, transactions, balances, identity, and verification endpoints, plus webhooks for event-driven consumption (mx-docs-7/22) and even an official MCP server for agent access (mx-probe-3), directly supporting machine-consumable, schema-documented data for automated workflows. Missing for 10: concrete sample JSON response bodies in the evidence pack and independent third-party corroboration that the schemas are agent-friendly without extra parsing.

   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”
   • [probe] “official MCP server documented at https://docs.mx.com/mcp”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mx.com/llms.txt # MX Documentation - [Welcome to the MX Documentation](https://docs.mx.com/index.m…”

   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 drawn
   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

   MX~partialprobed6/10

   MX exposes a full Platform API (with OpenAPI spec) covering balances, transactions, account aggregation, connect sessions/members, and webhooks, and there is a documented MCP surface at docs.mx.com/mcp confirming an MCP entry point exists. However, the evidence pack lacks detail on MCP tool scoping, credential/permission scoping for agent use, or hands-on confirmation of agent-driven session creation and connection management via MCP. missing for 10: documented MCP tool list/schema, evidence of scoped credentials for agent access, independent/hands-on validation of the MCP surface in agentic workflows.

   • [probe] “official MCP server documented at https://docs.mx.com/mcp”
   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [claimed-docs] “Get the available balance for an end user’s financial accounts”
   • [claimed-docs] “connect to end users' financial institutions and retrieve 90 days of data for their accounts and transactions”
   • [claimed-docs] “Use the Connect Widget and Platform API to let end users connect to their accounts.”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice.”

   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

   MX—none0/10

   The evidence pack covers MX's data connectivity products (account verification, aggregation, transaction history) and webhooks, but contains no mention of any end-user-facing consent dashboard, permissions center, or revocation portal where users can view/manage which apps hold access to their bank data. missing for 10: documented consent/permissions portal, revocation flow, any UI or API for end users to view/manage connected app access.

   • [claimed-docs] “MX's ready-made UI that can be embedded in your application to aggregate users' account data by prompting end users to connect to their fina…”
   • [claimed-docs] “Use the Connect Widget and Platform API to let end users connect to their accounts.”
   • [claimed-docs] “Share your held data with an FDX open finance platform”

   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

   MX—none0/10

   The evidence pack covers connectivity, aggregation, webhooks, and API testing but contains no documentation of a delete/disconnect flow for members or users, nor any statement about MX stopping data collection or purging held data upon request. This is a fair question for a financial data aggregator handling sensitive consumer data, but no supporting evidence exists.

   ⚑ 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

   MX~partialclaimed4/10

   MX splits data access into distinct products (Instant Account Verification, Account Owner Identification, Account Aggregation, Extended Transaction History, Balance), which implies a developer could integrate only the specific product/data type needed rather than one monolithic grant. However, there is no explicit documentation of a consent-scoping mechanism, a permission UI showing only requested scopes to end users, or stated data-minimization principles/controls. Missing for 10: explicit consent/scope management docs, evidence of end-user-facing scope selection in Connect Widget, and any stated data-minimization policy.

   • [claimed-docs] “you can connect to an end user's financial institution and retrieve account and routing numbers for their demand deposit accounts”
   • [claimed-docs] “you can connect to an end user's financial account to retrieve information such as their name and address”
   • [claimed-docs] “connect to end users' financial institutions and retrieve 90 days of data for their accounts and transactions”
   • [claimed-docs] “you can connect to an end user's financial institution and retrieve up to 24 months of data for their accounts and transactions”
   • [claimed-docs] “Get the available balance for an end user’s financial accounts”
   • [claimed-docs] “Use the Connect Widget and Platform API to let end users connect to their accounts.”

   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

   MX—none0/10

   The evidence only shows MX automatically aggregates accounts on a ~24-hour cycle (mx-docs-25) and describes webhooks for event notifications, but there is no documented API endpoint or semantics for a developer-triggered on-demand refresh of a connected account's data.

   • [claimed-docs] “MX automatically aggregates each `member` approximately every 24 hours.”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”

   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 MX
   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

   MX✓fullclaimed8/10

   MX docs confirm webhooks with HTTPS POST callbacks for subscribing to events like transaction/balance/connection changes, and note that account aggregation runs automatically (~every 24h) with webhook notification rather than requiring polling. Missing for 10: explicit documentation of webhook payload signing/verification mechanism and a full enumerated list of event types, plus independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice.”
   • [claimed-docs] “MX automatically aggregates each `member` approximately every 24 hours.”

   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

   MX—none0/10

   The evidence pack covers MX's connectivity products, APIs, and webhooks but contains no published figures on number of institutions reached, geographic coverage, or any coverage map/list a founder could check against their users' banks.

   ⚑ 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

   MX—none0/10

   Evidence covers connectivity, aggregation, webhooks, and test institutions, but there is no documented institution status dashboard, outage/degradation signal, or error-code taxonomy distinguishing bank-side failures from client-side issues. Missing for 10: institution health/status page, outage or degradation indicators, and documented error codes for bank vs integration failure.

   ⚑ 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

   MX✓fullclaimed7/10

   MX's Connect Widget/Platform API model uses a single connection (member) per institution that then exposes multiple products—verification, identity, balances, aggregation, extended history—via the same member without re-prompting the user (mx-docs-21, mx-docs-9, mx-docs-15/16/18/19/20). Webhooks and the 24-hour auto-aggregation cycle (mx-docs-25, mx-docs-7) further support a single persistent connection powering ongoing multi-product data access. missing for 10: no explicit documentation or hands-on confirmation that a single Connect session activates all products simultaneously without separate per-product entitlement/config steps, and no independent developer account of this exact flow.

   • [claimed-docs] “Use the Connect Widget and Platform API to let end users connect to their accounts.”
   • [claimed-docs] “MX's ready-made UI that can be embedded in your application to aggregate users' account data by prompting end users to connect to their fina…”
   • [claimed-docs] “With Instant Account Verification, you can connect to an end user's financial institution and retrieve account and routing numbers for their…”
   • [claimed-docs] “With Account Owner Identification, you can connect to an end user's financial account to retrieve information such as their name and address…”
   • [claimed-docs] “Get the available balance for an end user's financial accounts”
   • [claimed-docs] “With Account Aggregation, connect to end users' financial institutions and retrieve 90 days of data for their accounts and transactions.”
   • [claimed-docs] “With Extended Transaction History, you can connect to an end user's financial institution and retrieve up to 24 months of data for their acc…”
   • [claimed-docs] “MX automatically aggregates each `member` approximately every 24 hours.”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”

   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

   MX~partialprobed4/10

   MX provides developer-facing artifacts like a downloadable OpenAPI spec (importable into Postman), a public GitHub OpenAPI repo, and a test platform with sandbox test institutions, which support quick experimentation. However there's no evidence of a self-serve API key signup flow, a step-by-step quickstart guide, or officially maintained client libraries/SDKs in specific languages. missing for 10: self-serve API key/account signup flow, official quickstart tutorial, language-specific client libraries/SDKs.

   • [claimed-docs] “We offer four test institutions that you can use”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”
   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mx.com/openapi.json, https://docs.mx.com/swagger.json, https://docs.mx.com/api/openapi.…”

   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 Stripe Financial Connections
   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

   MX~partialclaimed7/10

   MX documents a dedicated test platform with four test institutions and an OpenAPI spec importable into Postman, plus guidance on testing the Connect Widget's OAuth flow end-to-end — directly supporting sandbox-based linking/testing before production use. However, the evidence does not show explicit documented test credentials for each test institution or guidance on simulating specific error states. Missing for 10: documented test credentials per institution, explicit error-state/failure simulation guidance.

   • [claimed-docs] “We offer four test institutions that you can use”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”
   • [claimed-docs] “To test OAuth in the Connect Widget when it's embedded in a WebView, you must load the financial institution's OAuth window in the device's …”

   proof ↗⚑ flag

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

   weight 2 · round to MX
   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

   MX~partialprobed6/10

   MX exposes a full Platform API (with public OpenAPI spec and even an MCP server) covering the same core capabilities as its Connect Widget UI—account verification, aggregation, balances, transaction history, webhooks—so most end-user and data flows are API-accessible. However, there is no explicit documentation confirming full parity between the API and MX's dashboard/admin UI (e.g., configuration, analytics, or account-management screens), so some UI-only functions may not be exposed. Missing for 10: explicit parity statement, evidence covering dashboard/admin functions via API, independent confirmation of no UI-only features.

   • [claimed-docs] “Use the Connect Widget and Platform API to let end users connect to their accounts.”
   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [probe] “official MCP server documented at https://docs.mx.com/mcp”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”

   proof ↗⚑ flag

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

   weight 3 · round to MX
   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

   MX~partialclaimed3/10

   MX supports sharing held data with an FDX open finance platform and exposes an OpenAPI spec, suggesting some open-format data portability for the businesses that integrate with it, but there is no evidence of an end-user-facing 'export all my data and leave' feature or documented full data export/deletion workflow. missing for 10: end-user self-service export tool, documentation of full data export scope/format, evidence of account closure/data portability workflow, independent confirmation of FDX export usage.

   • [claimed-docs] “Share your held data with an FDX open finance platform”
   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API and its request and response payloads.”

   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

   MX—none0/10

   MX is a closed commercial fintech API/SaaS product; the only public GitHub repo (mx-gh-1) contains an OpenAPI specification for documentation/integration purposes, not the actual application source code, and no license grants access to MX's implementation source.

   • [github] “This repository contains the OpenAPI specification for the MX Platform API”

   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 Stripe Financial Connections
   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

   MX—none0/10

   MX's evidence covers account verification, aggregation, balance, transaction history, and identity data, plus 'Tokenized Account Numbers... for secure ACH money movement' (mx-docs-24), but there is no documented payment-initiation API/product, no description of initiating a bank payment/transfer, and no stated live geographies for such a capability.

   • [claimed-docs] “Tokenized Account Numbers (TANs) are substitute account numbers used for secure ACH money movement.”
   • [claimed-docs] “With Instant Account Verification, you can connect to an end user's financial institution and retrieve account and routing numbers for their…”
   • [claimed-docs] “With Account Aggregation, connect to end users' financial institutions and retrieve 90 days of data for their accounts and transactions.”

   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

   MX—none0/10

   MX's evidence covers account aggregation, identity/verification, balances, transaction history and ACH microdeposit verification, plus tokenized account numbers for ACH money movement — but there is no mention of variable recurring payments, standing consents, or any recurring/scheduled debit payment-initiation flow.

   ⚑ 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

   MX—none0/10

   No evidence in the pack addresses data residency, region selection, or storage location controls for MX's data; all citations concern connectivity, aggregation, and API/testing features. missing for 10: any mention of data residency/region options, compliance certifications tied to geographic storage, or configuration for where data is stored.

   ⚑ 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

   MX—none0/10

   The evidence pack contains no mention of data retention periods, deletion policies, or user/data-controller controls over stored financial data; all citations relate to connectivity, aggregation, and API features rather than privacy/data lifecycle 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

   MX—none0/10

   MX's evidence covers account aggregation, balances, identity/ownership verification, and general 'data intelligence' or 'personalized guidance' claims, but nothing documents a specific income/cash-flow signal product — no mention of recurring-income detection, payroll detection, or a named income verification offering built on transaction data.

   ⚑ 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 drawn
   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

   MX—none0/10

   The evidence pack covers connectivity, verification, aggregation, webhooks, and testing tools, but never documents transaction enrichment specifics like cleaned merchant names, categorization, or logos — only vague references to 'data-driven intelligence' and 'account and transaction history in one view.' Since enrichment is a fair and expected capability for a financial-data-aggregation platform, but no concrete documentation of merchant cleansing/categories/logos appears, this is 'none' rather than 'na'.

   • [claimed-docs] “Use data-driven intelligence about your customers”
   • [claimed-docs] “Access account and transaction history all in one view. Use the data to increase multi-product adoption, and build trust.”
   • [claimed-docs] “connect to end users' financial institutions and retrieve 90 days of data for their accounts and transactions”
   • [claimed-docs] “With Account Aggregation, connect to end users' financial institutions and retrieve 90 days of data for their accounts and transactions.”

   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 MX
   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

   MX~partialclaimed7/10

   MX clearly documents transaction history depth (90 days standard via Account Aggregation, up to 24 months via Extended Transaction History) and provides a sync mechanism via webhooks plus automatic ~24hr re-aggregation of connected accounts, backed by a public OpenAPI spec for the Platform API. However, the evidence never explicitly documents pagination parameters/behavior for the transactions endpoint itself, and the webhook-based sync isn't described as an incremental 'only what changed' diff pattern (e.g., no mention of delta/cursor tokens). Missing for 10: explicit pagination documentation for transaction list endpoints, explicit incremental/delta sync mechanism beyond generic webhooks/24h refresh.

   • [claimed-docs] “connect to end users' financial institutions and retrieve 90 days of data for their accounts and transactions”
   • [claimed-docs] “you can connect to an end user's financial institution and retrieve up to 24 months of data for their accounts and transactions”
   • [claimed-docs] “With Account Aggregation, connect to end users' financial institutions and retrieve 90 days of data for their accounts and transactions.”
   • [claimed-docs] “With Extended Transaction History, you can connect to an end user's financial institution and retrieve up to 24 months of data for their acc…”
   • [claimed-docs] “MX automatically aggregates each `member` approximately every 24 hours.”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice. This enables you to subscribe to certain events”
   • [claimed-docs] “MX provides webhooks that send HTTPS POST callback requests to the URL of your choice.”
   • [github] “This repository contains the OpenAPI specification for the MX Platform API”
   • [claimed-docs] “You can download our OpenAPI Specification and import it into Postman to learn more about our API”

   proof ↗⚑ flag