Stripe Financial Connections vs Mastercard Open Finance (Finicity)

Hosted flows

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

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

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

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

   proof ↗⚑ flag

   Mastercard Open Finance (Finicity)~partialclaimed3/10

   The evidence only briefly references a 'Connect' mechanism for linking accounts ('link them to at least one account via Connect') but provides no detail on a hosted, drop-in widget, server-side session creation, or token retrieval flow that a developer would use to avoid building institution UI. Missing for 10: documentation of Connect widget UI, session token generation API, and end-to-end token exchange after linking.

   • [claimed-docs] “link them to at least one account via Connect”

   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

   Mastercard Open Finance (Finicity)—none0/10

   The evidence pack covers Connect/account-linking, webhooks, and API products but never mentions OAuth-based bank authentication coverage, connectivity method mix, or a documented plan/status for retiring screen-scraped credential flows. Without explicit documentation of OAuth coverage vs. legacy scraping, this specific developer-facing transparency claim is unevidenced.

   • [claimed-docs] “link them to at least one account via Connect”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”

   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

   Mastercard Open Finance (Finicity)—none0/10

   The evidence pack covers account data products, webhooks, onboarding, and testing personas, but nothing documents connection health statuses (expired/revoked), a re-authentication or 'update mode' flow, or any repair-without-restart mechanism for broken links. Missing for 10: documented connection status states (e.g., expired/revoked/error), an update/re-auth flow API or UI, and any evidence of preserving existing account links during re-auth.

   • [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
   • [claimed-docs] “link them to at least one account via Connect”

   proof ↗⚑ flag

Agent access

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

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

   Mastercard Open Finance (Finicity)✓fullprobed8/10

   A probe confirms llms.txt is live at developer.mastercard.com/llms.txt (HTTP 200), and Mastercard also documents an agent-oriented MCP toolkit with dynamic code generation for agents. Missing for 10: no independent third-party confirmation that agents actually consume this llms.txt effectively, and no explicit doc listing Open Finance-specific sections within it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.mastercard.com/llms.txt # Mastercard Developers Mastercard Developers is a comprehensive API p…”
   • [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
   • [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
   • [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”

   proof ↗⚑ flag

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

   weight 2 · round to Mastercard Open Finance (Finicity)
   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

   Mastercard Open Finance (Finicity)~partialclaimed6/10

   As a pure REST API platform, Open Finance is inherently headless — it uses PartnerID/secret token auth (docs-10, docs-23), an OpenAPI spec with generated client libraries (mastercard-open-finance-gh-1), and a non-billable 'Test Drive' sandbox with scripted test personas (docs-24, docs-25) suitable for automated/CI testing. Missing for 10: no explicit CI/CD pipeline examples, no documented headless SDK/CLI runner, and no first-party guidance on automating the flow end-to-end in a build pipeline.

   • [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
   • [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
   • [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
   • [claimed-docs] “we provide you with a set of testing personas. Each persona represents an example of a user who might use your app.”
   • [github] “The test project generates an API client library from the API specification like you would do in a real application”

   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

   Mastercard Open Finance (Finicity)✓fullprobed7/10

   Mastercard documents an official Agent Toolkit MCP server (mcp-overview) that includes dynamic code generation and an example use case directly referencing Open Finance verification and balance checks, confirming AI agents can connect via this official MCP server to access Open Finance APIs. Missing for 10: independent/hands-on corroboration of the MCP server working with Open Finance endpoints, and detailed API-to-tool mapping documentation.

   • [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
   • [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”
   • [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”

   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

   Mastercard Open Finance (Finicity)—none0/10

   No evidence of an official CLI tool; evidence covers APIs, webhooks, MCP server, and SDK/test client generation but nothing describing a command-line interface for AI-native workflows. Missing for 10: any mention of an official CLI, its installation, or its use in agentic/AI workflows.

   ⚑ flag

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

   weight 3 · round to Mastercard Open Finance (Finicity)
   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

   Mastercard Open Finance (Finicity)✓fullprobed8/10

   Mastercard Open Finance exposes a well-documented public REST API (accounts, balances, transactions, ownership verification, webhooks) with OpenAPI spec, token-based auth, sandbox/test-drive access, and even an llms.txt plus official MCP toolkit for agent-driven access. missing for 10: independent third-party developer confirmation of API usability/reliability beyond vendor docs.

   • [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
   • [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
   • [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
   • [github] “The test project generates an API client library from the API specification like you would do in a real application”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.mastercard.com/llms.txt # Mastercard Developers Mastercard Developers is a comprehensive API p…”
   • [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
   • [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”

   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

   Mastercard Open Finance (Finicity)—none0/10

   Evidence shows PartnerID/secret/appKey token generation for API access (docs-10, docs-23) but no mention of scoped, least-privilege, or per-agent credential issuance — auth appears to be a single partner-level secret rather than granular scoped tokens for agents. Missing for 10: any documentation of scoped/limited-permission API keys, per-agent credential issuance, or role-based access control for agent use.

   • [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
   • [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

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

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

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

   proof ↗⚑ flag

   Mastercard Open Finance (Finicity)~partialclaimed3/10

   The only relevant evidence is a GitHub repo showing an OpenAPI-generated client library used for testing, not a fully documented, officially published SDK across languages. Missing for 10: dedicated official SDK repositories/packages (e.g., npm, PyPI, Maven), SDK version support docs, and independent developer confirmation of SDK usability.

   • [github] “The test project generates an API client library from the API specification like you would do in a real application”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

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

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

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

   proof ↗⚑ flag

   Mastercard Open Finance (Finicity)✓fullclaimed7/10

   Docs explicitly describe webhook support for real-time event notifications (avoiding polling) and a subscription-based OBWMS API letting developers subscribe to specific events. Missing for 10: concrete webhook payload/setup examples, independent/hands-on confirmation, and detail on programmatic subscription management via API/SDK.

   • [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
   • [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”

   proof ↗⚑ flag

Agentic features

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

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

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

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

   proof ↗⚑ flag

   Mastercard Open Finance (Finicity)—none0/10

   The evidence shows Mastercard Open Finance exposes categorized financial data (transaction types, recurring transactions, spending, loan payments) via APIs, and a separate MCP agent toolkit for developers to generate code, but there is no evidence of AI-generated insights or suggestions surfaced to an end-user inside the product itself.

   • [claimed-docs] “Insights into: * [Transaction types] * [Recurring transactions] * [Consumer spending] * [Loan payments]”
   • [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
   • [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”

   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

   Mastercard Open Finance (Finicity)—none0/10

   Evidence shows webhooks for event notifications and an MCP toolkit for code generation, but nothing about scheduling or configuring autonomous background automations/workflows that run without user intervention. Missing for 10: any documentation of scheduled/triggered automation setup, autonomous workflow orchestration, or agentic task execution running independently in the background.

   • [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
   • [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”
   • [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”

   proof ↗⚑ flag

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

   weight 2 · round to Mastercard Open Finance (Finicity)
   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

   Mastercard Open Finance (Finicity)~partialprobed5/10

   Mastercard offers an official Agent Toolkit/MCP server with dynamic code generation and natural-language-friendly API access (e.g., 'I need to integrate Open Finance to verify account ownership and check balances'), which supports operating the platform via AI-native/natural-language workflows. However, this is a developer-integration tool rather than end-user natural-language command execution over the product's core financial functions. missing for 10: evidence of an end-user-facing natural-language interface, broader coverage of MCP tool capabilities beyond code generation, and independent/hands-on validation of the MCP server's reliability.

   • [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
   • [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”
   • [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”

   proof ↗⚑ flag

Api quality

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

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

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

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

   proof ↗⚑ flag

   Mastercard Open Finance (Finicity)—none0/10

   The evidence shows extensive product/API documentation, an OpenAPI spec-driven test client, and a 'Test Drive' sandbox plan, but nothing describes an interactive API reference (e.g., Swagger/Postman-style try-it console) with runnable code examples in the docs portal itself.

   • [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
   • [github] “The test project generates an API client library from the API specification like you would do in a real application”
   • [claimed-docs] “we provide you with a set of testing personas”

   proof ↗⚑ flag

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

   weight 2 · round to Mastercard Open Finance (Finicity)
   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

   Mastercard Open Finance (Finicity)✓fullprobed8/10

   A GitHub repo (open-banking-us-openapi) explicitly generates an API client library from a published OpenAPI specification, confirming a machine-readable spec is downloadable/usable, and Mastercard also exposes an llms.txt and MCP toolkit for machine-consumable API access. Missing for 10: no direct link/documentation showing a single canonical spec file download page or version history, and no independent third-party confirmation of spec completeness.

   • [github] “The test project generates an API client library from the API specification like you would do in a real application”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.mastercard.com/llms.txt # Mastercard Developers Mastercard Developers is a comprehensive API p…”
   • [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
   • [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”

   proof ↗⚑ flag

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

   weight 1 · round to Mastercard Open Finance (Finicity)
   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

   Mastercard Open Finance (Finicity)✓fullclaimed8/10

   Mastercard provides a dedicated non-billable 'Test Drive' plan with unlimited access to all Open Finance API endpoints plus documented testing personas representing example users, explicitly for sandbox-style integration testing without production data, and a GitHub sample project generating a client from the API spec for testing. missing for 10: independent/hands-on confirmation of full production-data isolation and details on sandbox data realism or limitations.

   • [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
   • [claimed-docs] “we provide you with a set of testing personas”
   • [claimed-docs] “we provide you with a set of testing personas. Each persona represents an example of a user who might use your app.”
   • [github] “The test project generates an API client library from the API specification like you would do in a real application”

   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

   Mastercard Open Finance (Finicity)—none0/10

   No evidence pack items mention API versioning scheme or a documented deprecation policy; docs reference endpoints, onboarding, testing, and webhooks but not version lifecycle management.

   ⚑ 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

   Mastercard Open Finance (Finicity)—none0/10

   No evidence describes batch/bulk endpoints or multi-item operations (e.g., submitting many account IDs or requests in a single call); documented APIs appear per-account/per-transaction oriented, and webhooks only address real-time single-event notifications, not bulk processing.

   ⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Mastercard Open Finance (Finicity)—none0/10

   Webhooks provide event notifications but there is no evidence of user-definable rules or automated triggered actions based on those events; missing for 10: rule-definition engine, conditional logic, automated action execution tied to events.

   • [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
   • [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”

   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

   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

Ach details

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

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

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

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

   proof ↗⚑ flag

   Mastercard Open Finance (Finicity)~partialclaimed6/10

   Mastercard's docs list dedicated 'Get ACH details' and 'Validate account details' products alongside account-ownership verification and balance checks, which together match the story of retrieving account/routing data and validating funding source without micro-deposits. However, the evidence pack only shows product titles/index links rather than detailed descriptions of the actual data returned (e.g., explicit account/routing number fields, tokenization format, or confirmation that validation replaces micro-deposits). Missing for 10: detailed API schema/response showing routing+account numbers or tokens, explicit statement that validation eliminates micro-deposit verification, and independent developer confirmation of real-world usage.

   • [claimed-docs] “Get ACH details”
   • [claimed-docs] “Get [ACH details]”
   • [claimed-docs] “Validate account details”
   • [claimed-docs] “Validate [account details]”
   • [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
   • [claimed-docs] “you can send customer data to our match account ownership details endpoint to receive confidence scores comparing the provided data and the …”

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

   Mastercard Open Finance (Finicity)✓fullclaimed7/10

   Docs explicitly describe an Account Balance service returning real-time or cached balance data from the connected FI, matching the NSF/risk-check use case, and MCP overview references verifying ownership and checking balances as a supported integration flow. Missing for 10: explicit request/response schema examples, independent/hands-on confirmation of real-time latency, and no direct mention of pre-payment NSF workflow tying balance check to payment initiation.

   • [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
   • [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”

   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

   Mastercard Open Finance (Finicity)✓fullclaimed8/10

   Docs explicitly describe an Account Owner Verification service retrieving name, address, email and phone from the connected FI account, and a match-account-ownership endpoint that compares provided customer data against the bank's on-file details with confidence scores — directly matching the ops matching workflow. Missing for 10: independent/hands-on corroboration beyond vendor docs and more detail on data completeness/edge cases across FIs.

   • [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
   • [claimed-docs] “you can send customer data to our match account ownership details endpoint to receive confidence scores comparing the provided data and the …”
   • [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”

   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

   Mastercard Open Finance (Finicity)~partialclaimed5/10

   Mastercard Open Finance provides account ownership verification, balance, ACH details, and account aggregation APIs accessible via token-based auth (PartnerID/secret) that developers can integrate into payment processing flows, and it supports Connect for account linking. However, the evidence does not document specific third-party payment processor/platform integration partnerships or an explicit token-exchange handoff mechanism to hand verified credentials to external processors — the story implies pre-built plug-and-play integrations rather than raw APIs a developer must wire up themselves. missing for 10: named third-party processor/platform integration partners, explicit token-exchange-to-processor handoff documentation, independent confirmation of such integrations working in production.

   • [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
   • [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
   • [claimed-docs] “Get ACH details”
   • [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
   • [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
   • [claimed-docs] “link them to at least one account via Connect”

   proof ↗⚑ flag

Agent data

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

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

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

   • [claimed-docs] “Access an account’s current and available balances.”
   • [claimed-docs] “Access account owners’ names and mailing addresses.”
   • [claimed-docs] “Access an account’s transaction history.”
   • [claimed-docs] “Financial insights for agents | - Agent-powered spending analysis - Balance and transaction monitoring | Link CLI”
   • [claimed-docs] “Sent when a customer links a new account. If they link multiple accounts, it emits multiple events (one per account).”
   • [claimed-docs] “Sent after a balance refresh is complete.”
   • [claimed-docs] “Sent after an ownership refresh is complete.”
   • [claimed-docs] “Sent after a transaction refresh is complete.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   Mastercard Open Finance (Finicity)~partialprobed6/10

   Mastercard Open Finance provides structured JSON APIs with documented schemas for account, transaction, balance, and enrichment data (transaction categorization, recurring transactions, spending insights), an OpenAPI spec with generated client libraries, and even an official MCP/agent-toolkit for AI consumption. However, evidence doesn't show explicit example JSON payloads or schema definitions in the pack, nor confirmation that enrichment fields are agent-optimized (e.g., no heuristic parsing needed) versus requiring developer interpretation. missing for 10: concrete JSON schema examples/response samples, explicit confirmation that enrichment output avoids downstream heuristic parsing, independent developer corroboration of agent-readiness.

   • [claimed-docs] “The Transaction Data Services provide account transaction data.”
   • [claimed-docs] “The account and transaction data elements returned from Account Aggregation and Transaction Data vary depending on the account type.”
   • [claimed-docs] “Insights into: * [Transaction types] * [Recurring transactions] * [Consumer spending] * [Loan payments]”
   • [github] “The test project generates an API client library from the API specification like you would do in a real application”
   • [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
   • [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”

   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

   Mastercard Open Finance (Finicity)~partialprobed6/10

   Mastercard's Open Finance APIs clearly support the core actions an agent would need — creating link sessions via Connect, retrieving balances (Account Balance service), pulling transactions (Transaction Data), and managing connections/webhooks — all gated by PartnerID/secret/appKey OAuth tokens that function as scoped credentials. There is also a documented official MCP surface (agent-toolkit/mcp-overview) explicitly referencing Open Finance use cases like verifying ownership and checking balances, but its documented function is 'dynamic code generation' for developers rather than confirmed direct agentic execution of live account operations. missing for 10: evidence the MCP server itself executes link-session/balance/transaction calls (vs. just generating code samples), and independent/hands-on confirmation of an agent operating end-to-end with scoped MCP credentials.

   • [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
   • [claimed-docs] “The Transaction Data Services provide account transaction data.”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
   • [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
   • [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
   • [claimed-docs] “link them to at least one account via Connect”
   • [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
   • [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”
   • [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”

   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

   Mastercard Open Finance (Finicity)—none0/10

   Evidence pack covers data retrieval, verification, transaction data, webhooks, onboarding tokens, and testing personas, but nowhere documents an end-user-facing consent management portal, dashboard, or revocation mechanism for shared bank-data access. No mention of a consent surface for users to view or revoke connected apps' access.

   ⚑ 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

   Mastercard Open Finance (Finicity)—none0/10

   No evidence pack item documents a delete/disconnect endpoint, user data purge process, or data retention/deletion policy for connections or held account data; coverage is limited to data retrieval, verification, and onboarding APIs.

   ⚑ 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

   Mastercard Open Finance (Finicity)~partialclaimed4/10

   The docs show a product-based API structure (separate endpoints for account ownership, balance, transactions, ACH, etc.), which implicitly allows requesting only specific data products rather than a single blob, but there is no explicit documentation of scoped consent tokens, granular permission grants, or data-minimization controls presented to developers. missing for 10: explicit consent-scoping API/parameters, documentation of minimal-data-grant mechanisms, evidence of per-scope authorization tokens, and any independent confirmation of data-minimization enforcement.

   • [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
   • [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
   • [claimed-docs] “The Transaction Data Services provide account transaction data.”
   • [claimed-docs] “The account and transaction data elements returned from Account Aggregation and Transaction Data vary depending on the account type.”
   • [claimed-docs] “[Account] and [transaction] details”

   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

   Mastercard Open Finance (Finicity)—none0/10

   Evidence shows account balance can be 'real-time or cached' and webhooks provide event notifications, but there is no documented API endpoint or explicit refresh semantics (e.g., a force-refresh trigger, freshness guarantees, or polling-for-refresh-status flow) for triggering an on-demand data refresh. Missing for 10: an explicit refresh/force-update endpoint, documented refresh semantics (sync vs async, staleness thresholds), and any independent confirmation of on-demand refresh behavior.

   • [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
   • [claimed-docs] “The Transaction Data Services provide account transaction data.”

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

   Mastercard Open Finance (Finicity)~partialclaimed6/10

   Docs confirm webhooks exist for real-time event notifications instead of polling, and OBWMS lets you subscribe to specific events; transaction/notification-type docs exist too. However, there's no evidence of webhook payload signing/verification, and no explicit documentation enumerating events like balance updates or connection-state changes with delivery guarantees. Missing for 10: signature verification mechanism, explicit event-type catalog (transactions/balances/connection state), delivery retry/reliability details.

   • [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
   • [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”
   • [claimed-docs] “[Transaction notifications]”

   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

   Mastercard Open Finance (Finicity)—none0/10

   The evidence pack covers API capabilities (verification, balances, transaction data, webhooks, onboarding) but contains no published institution-coverage numbers, geographic breakdowns, or bank-reach statistics that 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

   Mastercard Open Finance (Finicity)—none0/10

   The evidence pack covers API products (balance, ownership, transaction data, webhooks, onboarding) but contains no mention of institution status dashboards, outage/degradation signals, or error codes distinguishing bank-side vs integration-side issues.

   ⚑ 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

   Mastercard Open Finance (Finicity)—none0/10

   The evidence lists multiple separate data products (account ownership, balances, transactions) and mentions a generic 'Connect' linking step, but nothing describes a single link/Connect session simultaneously provisioning auth, balances, transactions, and identity without repeated connection flows per product.

   ⚑ 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

   Mastercard Open Finance (Finicity)~partialclaimed5/10

   Docs show a self-serve-ish onboarding path (PartnerID/secret/appKey token generation, a non-billable unlimited 'Test Drive' plan, and test personas for sandbox account linking) and a GitHub OpenAPI spec that can generate a client library, but there's no explicit runnable quickstart tutorial or multi-language official client libraries beyond the one generated test project. Missing for 10: an explicit step-by-step quickstart guide, published official SDKs in multiple languages, and clear evidence of instant self-serve API key issuance without a sales/partner approval step.

   • [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
   • [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
   • [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
   • [claimed-docs] “we provide you with a set of testing personas. Each persona represents an example of a user who might use your app.”
   • [github] “The test project generates an API client library from the API specification like you would do in a real application”

   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

   Mastercard Open Finance (Finicity)~partialclaimed6/10

   Docs confirm a dedicated Test Drive sandbox with unlimited access to all endpoints, testing personas representing different user scenarios, and a GitHub sample project generating a real API client for end-to-end testing — covering linking, data retrieval, and onboarding tokens. However, there is no explicit documentation of error-state simulation or a catalog of documented test credentials/institutions with specific failure scenarios. Missing for 10: explicit documented test credentials list, coverage of error/failure state simulation, and independent/hands-on confirmation of the sandbox experience.

   • [claimed-docs] “we provide you with a set of testing personas”
   • [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
   • [claimed-docs] “we provide you with a set of testing personas. Each persona represents an example of a user who might use your app.”
   • [github] “The test project generates an API client library from the API specification like you would do in a real application”
   • [claimed-docs] “link them to at least one account via Connect”

   proof ↗⚑ flag

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

   weight 2 · round to Mastercard Open Finance (Finicity)
   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

   Mastercard Open Finance (Finicity)~partialclaimed6/10

   As an API-first data platform, virtually all core functions (account verification, balances, transactions, ACH details, webhooks/event management, token generation) are exposed directly via documented REST APIs rather than gated behind a UI, and even administrative functions like webhook subscriptions and token creation are API-driven (docs-9, docs-23, docs-26). However, the 'Connect' account-linking flow is a hosted widget/UI experience (docs-27) whose full API-equivalence isn't evidenced, and there's no explicit confirmation that all developer-portal/dashboard actions (billing, partner management) have API parity. Missing for 10: explicit API equivalents for the Connect linking UI, and confirmation that portal/dashboard admin tasks are fully scriptable.

   • [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
   • [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
   • [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”
   • [claimed-docs] “link them to at least one account via Connect”
   • [claimed-docs] “The Transaction Data Services provide account transaction data.”
   • [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”

   proof ↗⚑ flag

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

   weight 3 · 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

   Mastercard Open Finance (Finicity)—none0/10

   This is a B2B financial data API platform, not a consumer product with user-owned data to export; the evidence shows no data export/portability feature for end users to take their data out in open formats and leave. No mention of any account/data export or account deletion/portability capability anywhere in the docs.

   ⚑ 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

   Mastercard Open Finance (Finicity)—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

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

   Mastercard Open Finance (Finicity)—none0/10

   The evidence pack describes the 'Pay' product family only as verification (account ownership, balance, ACH details, match), fraud/success prediction, and switching services — none of the docs describe an actual payment-initiation endpoint that moves funds from a connected account, nor any stated live geographies for such a capability. Without a documented API to actually initiate a bank payment, this axis is unmet.

   • [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
   • [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
   • [claimed-docs] “you can send customer data to our match account ownership details endpoint to receive confidence scores comparing the provided data and the …”
   • [claimed-docs] “Predict [payment success]”
   • [claimed-docs] “Switch [deposits and bill payments]”
   • [claimed-docs] “Get ACH details”

   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

   Mastercard Open Finance (Finicity)—none0/10

   Evidence covers account data (balances, ownership, transactions), ACH details, and 'switch deposits and bill payments' but nothing documents variable recurring payments, standing consents, or a recurring debit/payment-initiation flow — this product's Pay APIs appear focused on verification (account owner, balance, ACH details) rather than initiating recurring debits.

   ⚑ 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

   Mastercard Open Finance (Finicity)—none0/10

   No evidence anywhere in the pack discusses data residency, regional storage options, or geographic controls for where customer data is stored/processed. This is an applicable axis for a financial data platform handling sensitive PII, but nothing addresses it.

   ⚑ 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

   Mastercard Open Finance (Finicity)—none0/10

   The evidence pack covers API products (account data, verification, transactions, webhooks, onboarding) but contains no mention of data retention policies, deletion controls, or user-facing privacy/data-lifecycle management tools. Missing for 10: any documentation of data retention periods, deletion/erasure APIs, or consumer-facing controls over stored financial data.

   ⚑ 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 to Mastercard Open Finance (Finicity)
   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

   Mastercard Open Finance (Finicity)~partialclaimed6/10

   Docs confirm transaction data services with insights into recurring transactions, transaction types, consumer spending, and loan payments, plus credit-decisioning report APIs — directly supporting cash-flow/recurring-stream signals. However, there's no explicit mention of payroll detection or a dedicated income-verification product built on this data. missing for 10: explicit payroll/income detection feature, named income-verification product, independent validation of accuracy.

   • [claimed-docs] “The Transaction Data Services provide account transaction data.”
   • [claimed-docs] “Insights into: * [Transaction types] * [Recurring transactions] * [Consumer spending] * [Loan payments]”
   • [claimed-docs] “APIs for credit decisioning [reports]”
   • [claimed-docs] “The account and transaction data elements returned from Account Aggregation and Transaction Data vary depending on the account type.”

   proof ↗⚑ flag

Enrichment

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

   weight 2 · round to Mastercard Open Finance (Finicity)
   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

   Mastercard Open Finance (Finicity)~partialclaimed4/10

   Docs confirm Transaction Data Services return categorized insights (transaction types, recurring transactions, consumer spending, loan payments), which implies some enrichment/categorization layer, but nothing explicitly documents merchant-name cleansing or logo attachment as a first-class capability. Missing for 10: explicit documentation of merchant name normalization/cleanup and logo enrichment fields in the transaction schema.

   • [claimed-docs] “The Transaction Data Services provide account transaction data.”
   • [claimed-docs] “The account and transaction data elements returned from Account Aggregation and Transaction Data vary depending on the account type.”
   • [claimed-docs] “Insights into: * [Transaction types] * [Recurring transactions] * [Consumer spending] * [Loan payments]”

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

   Mastercard Open Finance (Finicity)~partialclaimed5/10

   Evidence confirms a dedicated Transaction Data Services API that returns account/transaction details and varies by account type, plus a webhook/notification system explicitly framed as eliminating constant polling, which implies a change-based sync pattern. However, no evidence documents pagination mechanics or a specific stated history depth (e.g., days/months of transactions) for the transaction endpoint. missing for 10: explicit pagination documentation, stated transaction history depth/lookback window, explicit delta/cursor sync pattern for transactions specifically (webhooks reference is generic, not transaction-specific).

   • [claimed-docs] “The Transaction Data Services provide account transaction data.”
   • [claimed-docs] “The account and transaction data elements returned from Account Aggregation and Transaction Data vary depending on the account type.”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
   • [claimed-docs] “[Account] and [transaction] details”
   • [claimed-docs] “Insights into: * [Transaction types] * [Recurring transactions] * [Consumer spending] * [Loan payments]”
   • [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”

   proof ↗⚑ flag