Stripe Financial Connections vs Yapily

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

   Yapily✓fullclaimed7/10

   Yapily Connect is explicitly documented as a ready-built, white-label hosted UI for AIS/PIS flows with pre-built institution selection and consent screens, no frontend engineering required, automatic SCA/redirect handling, and customizable branding — matching the drop-in widget story closely. Missing for 10: explicit documentation of the server-side 'create session' API call and the exact token/consent-object returned to the backend after widget completion, plus independent/hands-on corroboration beyond vendor docs.

   • [claimed-docs] “Yapily Connect provides a ready-built, white-label open banking UI for AIS and PIS flows. Reduce development effort with pre-built instituti…”
   • [claimed-docs] “No frontend engineering required for consent and authorisation flows”
   • [claimed-docs] “Handles Strong Customer Authentication (SCA) and bank redirects automatically”
   • [claimed-docs] “Customisable branding (logo and colours)”
   • [claimed-docs] “UX design guidelines for Yapily Connect AIS flows. Best practices for institution selection, consent screens, and account selection for data…”

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

   Yapily~partialclaimed4/10

   Yapily's docs describe bank redirect and SCA-based consent flows (docs-9, docs-10) which imply OAuth-style bank-hosted authentication rather than screen-scraping, but no evidence explicitly uses the term 'OAuth,' documents OAuth coverage across institutions, or discusses retirement of legacy credential-scraping flows. Missing for 10: explicit OAuth terminology/documentation, institution-by-institution OAuth coverage stats, and any statement about phasing out screen-scraped credential flows.

   • [claimed-docs] “No frontend engineering required for consent and authorisation flows”
   • [claimed-docs] “Handles Strong Customer Authentication (SCA) and bank redirects automatically”

   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

   Yapily—none0/10

   The evidence pack covers payments, data retrieval, webhooks, and Yapily Connect UI, but nothing documents how expired/revoked consent links surface as statuses or how users re-authenticate via an update flow without restarting the linking process — missing for 10: documented consent-expiry/revocation status codes, and an explicit re-auth/update flow that preserves prior linkage.

   ⚑ flag

Agent access

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

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

   Yapily✓fullprobed9/10

   Yapily explicitly documents an llms.txt file (confirmed live via probe returning HTTP 200) and dedicated agent-oriented docs describing how to connect Claude, Cursor, or other AI agents via MCP, llms.txt, or Agent Skills, directly matching the story. Missing for 10: independent third-party confirmation of an agent successfully consuming the docs end-to-end.

   • [claimed-docs] “Connect Claude, Cursor, or another AI coding agent directly to these docs via MCP, llms.txt, or Agent Skills.”
   • [claimed-docs] “Yapily Connect provides a ready-built, white-label open banking UI for AIS and PIS flows. Reduce development effort with pre-built instituti…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.yapily.com/llms.txt # Yapily API Documentation - [Welcome to Yapily Docs](https://docs.yapily.com/…”
   • [probe] “official MCP server documented at https://docs.yapily.com/resources/ai-agents”

   proof ↗⚑ flag

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

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

   Yapily~partialclaimed5/10

   Yapily is a REST/API-first platform (payments, data, webhooks) with a sandbox for testing and generated client libraries, implying it can be scripted/automated without a UI, but there is no explicit documentation of running it headlessly in a CI pipeline, no CLI tool, and no automation/testing-pipeline example. missing for 10: explicit CI/CD or headless automation documentation, a CLI or scriptable test harness, evidence of pipeline integration examples.

   • [claimed-docs] “A sandbox is a test environment that allows you to connect your application to a bank and access test accounts to simulate the real Open Ban…”
   • [claimed-docs] “Generate API client libraries for Yapily in your preferred language using the OpenAPI specification. Supports code generation for Java, Pyth…”
   • [claimed-docs] “Webhooks allows you to receive real-time HTTP notifications of changes happening in the Yapily Platform.”
   • [claimed-docs] “No frontend engineering required for consent and authorisation flows”

   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

   Yapily~partialprobed6/10

   Yapily documents an official MCP server for connecting AI agents (Claude, Cursor) to its docs, confirmed by both docs and a probe verifying the ai-agents.md resource, so the axis clearly applies and is addressed. However, the evidence only shows MCP access to documentation/context, not to Yapily's actual banking APIs (payments, data, AIS/PIS) as agent-callable tools, and there's no independent or hands-on confirmation of the MCP server's tool set in action. Missing for 10: evidence that the MCP server exposes real API operations (payments, account data) as agent tools, tool/resource list details, and independent corroboration beyond first-party docs.

   • [claimed-docs] “Connect Claude, Cursor, or another AI coding agent directly to these docs via MCP, llms.txt, or Agent Skills.”
   • [probe] “official MCP server documented at https://docs.yapily.com/resources/ai-agents”

   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

   Yapily—none0/10

   Yapily provides SDK/client library generation (yapily-docs-8) and AI-agent connectivity via MCP/llms.txt (yapily-docs-6), but there is no evidence of an official CLI tool for interacting with the Yapily platform or APIs.

   ⚑ flag

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

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

   Yapily✓fullprobed8/10

   Yapily is API-first: docs describe endpoints for payments, data, webhooks, and confirm OpenAPI-based client library generation, plus explicit AI-agent access via MCP/llms.txt (confirmed live by probe-1 and probe-3), directly matching the 'documented public API for AI-native use' story. Missing for 10: a verifiable OpenAPI spec file (probe-2 found all standard OpenAPI/swagger paths 404) and independent third-party confirmation of API completeness beyond first-party docs.

   • [claimed-docs] “Generate API client libraries for Yapily in your preferred language using the OpenAPI specification. Supports code generation for Java, Pyth…”
   • [claimed-docs] “Connect Claude, Cursor, or another AI coding agent directly to these docs via MCP, llms.txt, or Agent Skills.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.yapily.com/llms.txt # Yapily API Documentation - [Welcome to Yapily Docs](https://docs.yapily.com/…”
   • [probe] “official MCP server documented at https://docs.yapily.com/resources/ai-agents”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.yapily.com/openapi.json, https://docs.yapily.com/swagger.json, https://docs.yapily.com/…”
   • [claimed-docs] “You can initiate single, scheduled and periodic payments using Yapily's Payments API.”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”

   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

   Yapily—none0/10

   No evidence in the pack describes issuing scoped or least-privilege API credentials/keys for agent use; documentation covers payments, data access, consent flows, and AI-agent documentation connectivity (MCP/llms.txt) but not credential scoping mechanisms.

   ⚑ 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

   Yapily~partialprobed5/10

   Yapily documents generating client libraries from an OpenAPI spec for Java, Python, Node.js, etc., which supports the 'official SDK' story, but this is code generation rather than a maintained, first-party SDK repository, and the probe found no accessible OpenAPI spec file, undermining confidence in this claim. missing for 10: evidence of actual published/maintained SDK repos (GitHub links, versioning, install instructions), independent corroboration, and working OpenAPI spec access.

   • [claimed-docs] “Generate API client libraries for Yapily in your preferred language using the OpenAPI specification. Supports code generation for Java, Pyth…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.yapily.com/openapi.json, https://docs.yapily.com/swagger.json, https://docs.yapily.com/…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

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

   Yapily✓fullclaimed8/10

   Yapily documents a dedicated webhooks system delivering real-time HTTP notifications of platform events (e.g., payment status changes), directly matching the story. Missing for 10: independent/hands-on corroboration of webhook reliability and no detail on subscription filtering/event types.

   • [claimed-docs] “Webhooks allows you to receive real-time HTTP notifications of changes happening in the Yapily Platform.”
   • [claimed-docs] “You can track the status of each payment via [Webhooks](/tools-and-services/webhooks/get-started) from the Yapily API for visibility of the …”

   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

   Yapily—none0/10

   Yapily's data API supports transaction categorisation and spending insights (yapily-docs-3), but this is not documented as AI-generated insights or suggestions surfaced within a Yapily product interface; the only AI-related evidence concerns connecting coding agents to its docs via MCP, not AI-driven analysis of user data.

   • [claimed-docs] “Categorise and analyse transaction data with merchant detection and spending insights.”
   • [claimed-docs] “Connect Claude, Cursor, or another AI coding agent directly to these docs via MCP, llms.txt, or Agent Skills.”

   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

   Yapily~partialclaimed4/10

   Yapily's Payments API supports scheduled and recurring/variable-recurring payments that execute autonomously without re-authorisation, and webhooks provide background event notifications — both are forms of autonomous background automation. However, there's no evidence of an AI-agent-specific automation-setup flow (e.g., an agent configuring or monitoring these jobs), just generic API-level scheduling. Missing for 10: explicit AI-agent-driven automation setup, agent monitoring/adjusting of scheduled tasks, and independent confirmation of reliability of unattended runs.

   • [claimed-docs] “Initiate bank-to-bank payments directly from your customer's account. Single, scheduled, or recurring.”
   • [claimed-docs] “Collect variable recurring payments without re-authorisation each time.”
   • [claimed-docs] “You can initiate single, scheduled and periodic payments using Yapily's Payments API.”
   • [claimed-docs] “Webhooks allows you to receive real-time HTTP notifications of changes happening in the Yapily Platform.”
   • [claimed-docs] “You can track the status of each payment via [Webhooks](/tools-and-services/webhooks/get-started) from the Yapily API for visibility of the …”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Yapily—none0/10

   Yapily's evidence covers a developer API/SDKs and an MCP-served documentation assistant for coding agents (yapily-docs-6, yapily-probe-3), but there is no evidence that end users can issue natural-language commands to actually operate Yapily's core functions (payments, account data retrieval, etc.). The MCP/llms.txt integration is for helping coding agents navigate docs, not a natural-language control interface for the product's operations.

   • [claimed-docs] “Connect Claude, Cursor, or another AI coding agent directly to these docs via MCP, llms.txt, or Agent Skills.”
   • [probe] “official MCP server documented at https://docs.yapily.com/resources/ai-agents”

   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

   Yapily—none0/10

   No evidence of an interactive API reference or runnable code examples; the OpenAPI spec probe returned 404s and docs only mention static content, code-gen libraries, and AI-agent integration (MCP/llms.txt), not an interactive playground with runnable examples.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.yapily.com/openapi.json, https://docs.yapily.com/swagger.json, https://docs.yapily.com/…”
   • [claimed-docs] “Generate API client libraries for Yapily in your preferred language using the OpenAPI specification. Supports code generation for Java, Pyth…”
   • [claimed-docs] “Connect Claude, Cursor, or another AI coding agent directly to these docs via MCP, llms.txt, or Agent Skills.”

   proof ↗⚑ flag

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

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

   Yapily!disputedcontradicted4/10

   Docs reference an OpenAPI specification used to generate client libraries (yapily-docs-8), implying a machine-readable spec exists, but a direct probe for standard OpenAPI/Swagger file locations returned 404 everywhere (yapily-probe-2), meaning no publicly downloadable spec could be located. missing for 10: a working public URL/download link for the OpenAPI/Swagger file, confirmation of its format and completeness, and independent corroboration that it can actually be fetched.

   • [claimed-docs] “Generate API client libraries for Yapily in your preferred language using the OpenAPI specification. Supports code generation for Java, Pyth…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.yapily.com/openapi.json, https://docs.yapily.com/swagger.json, https://docs.yapily.com/…”

   proof ↗⚑ flag

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

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

   Yapily✓fullclaimed8/10

   Yapily explicitly documents a sandbox environment that simulates real Open Banking flows with test accounts/banks so developers can test without touching production data (yapily-docs-12), supported by webhook and API docs for testing flows. Missing for 10: independent/hands-on confirmation of sandbox behavior and explicit detail on data isolation guarantees beyond the doc description.

   • [claimed-docs] “A sandbox is a test environment that allows you to connect your application to a bank and access test accounts to simulate the real Open Ban…”
   • [claimed-docs] “Webhooks allows you to receive real-time HTTP notifications of changes happening in the Yapily Platform.”

   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

   Yapily—none0/10

   No evidence pack items mention API versioning scheme or a documented deprecation policy; docs reference API capabilities, sandbox, webhooks, and client library generation but nothing about version lifecycle or deprecation commitments. missing for 10: versioning scheme documentation, deprecation policy/notice process, changelog or migration guides.

   ⚑ flag

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

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

   Yapily~partialclaimed4/10

   Yapily's docs mention 'bulk' as a supported payment type alongside scheduled/periodic/international payments, indicating some batch-processing capability, but there is no detailed documentation of bulk API semantics (batch size limits, bulk data retrieval, bulk consent management, etc.) beyond this one-line reference. missing for 10: dedicated bulk API endpoint documentation, batch limits/pagination for data retrieval, examples of bulk operations in practice.

   • [claimed-docs] “Choose this when you need payment types Hosted does not yet support (bulk, scheduled, periodic, international)”
   • [claimed-docs] “You can initiate single, scheduled and periodic payments using Yapily's Payments API.”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Yapily—none0/10

   Yapily documents webhooks for real-time event notifications, but there is no evidence of a rules engine or mechanism letting users define conditional triggers that automatically execute actions based on events — webhooks only notify, they don't let a user configure 'if X then do Y' automation.

   • [claimed-docs] “Webhooks allows you to receive real-time HTTP notifications of changes happening in the Yapily Platform.”
   • [claimed-docs] “You can track the status of each payment via [Webhooks](/tools-and-services/webhooks/get-started) from the Yapily API for visibility of the …”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

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

   Yapily~partialclaimed5/10

   Yapily's Payments API explicitly supports scheduled and recurring (periodic/variable recurring) payment initiation, which is a concrete recurring-job capability exposed via API and webhooks for status tracking. However, this is domain-specific (payments only) rather than a general-purpose job/workflow scheduler or automation engine that an AI agent could use to orchestrate arbitrary recurring tasks. Missing for 10: evidence of a generic scheduling/orchestration API or cron-like trigger system beyond payment initiation, and no independent corroboration of this working end-to-end.

   • [claimed-docs] “Initiate bank-to-bank payments directly from your customer's account. Single, scheduled, or recurring.”
   • [claimed-docs] “Collect variable recurring payments without re-authorisation each time.”
   • [claimed-docs] “You can initiate single, scheduled and periodic payments using Yapily's Payments API.”
   • [claimed-docs] “Choose this when you need payment types Hosted does not yet support (bulk, scheduled, periodic, international)”
   • [claimed-docs] “You can track the status of each payment via [Webhooks](/tools-and-services/webhooks/get-started) from the Yapily API for visibility of the …”
   • [claimed-docs] “Payments are made via local payment rails including Faster Payments in the UK and SEPA in Europe for fast settlement”

   proof ↗⚑ flag

Ach details

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

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

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

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

   Yapily✓fullclaimed7/10

   Yapily's Data API explicitly documents retrieving account balances (via AIS/Open Banking) alongside accounts and transactions, which is the core capability needed for pre-payment balance checks. Missing for 10: explicit 'real-time' latency guarantees and explicit framing of the endpoint for NSF/risk-check use cases.

   • [claimed-docs] “Retrieve accounts, balances, and transactions with user consent.”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”

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

   Yapily✓fullclaimed7/10

   Yapily explicitly documents confirming account ownership and retrieving customer details, plus broader Data API access to account details/balances for identity matching purposes. Missing for 10: no explicit breakdown of which fields (name, address, contact) are returned, and no independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “Confirm account ownership and customer details instantly.”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”
   • [claimed-docs] “Retrieve accounts, balances, and transactions with user consent.”

   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

   Yapily—none0/10

   Yapily's docs describe account verification and payment initiation via its own Payments/Data APIs, but there is no evidence of documented integrations or token-exchange mechanisms that hand verified account credentials to third-party payment processors or platforms.

   ⚑ flag

Agent data

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

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

   Yapily~partialprobed5/10

   Docs show enrichment (merchant detection, spending insights) and a Data API returning structured account/transaction/balance data, plus OpenAPI-based client generation implying documented schemas (yapily-docs-3, yapily-docs-2, yapily-docs-8, yapily-docs-15). However, a probe found the openapi.json/swagger.json spec not resolvable at standard paths, casting doubt on how discoverable the machine-readable schema actually is, and no evidence pack item shows an actual JSON response sample or schema definition. Missing for 10: concrete JSON response examples/schema snippets, confirmation of a publicly resolvable OpenAPI spec, and explicit statement that enrichment fields are machine-parseable without heuristics.

   • [claimed-docs] “Retrieve accounts, balances, and transactions with user consent.”
   • [claimed-docs] “Categorise and analyse transaction data with merchant detection and spending insights.”
   • [claimed-docs] “Generate API client libraries for Yapily in your preferred language using the OpenAPI specification. Supports code generation for Java, Pyth…”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.yapily.com/openapi.json, https://docs.yapily.com/swagger.json, https://docs.yapily.com/…”

   proof ↗⚑ flag

Agent operations

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

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

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

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

   proof ↗⚑ flag

   Yapily~partialprobed4/10

   Yapily's API clearly supports creating consent/link sessions, retrieving balances/transactions, and managing connections (yapily-docs-2, -7, -9, -15), and there is an MCP surface (yapily-docs-6, yapily-probe-3) — but that MCP is documented as connecting coding agents (Claude/Cursor) to the documentation, not as an operational interface for agents to actually invoke banking actions with scoped credentials. Missing for 10: evidence of an MCP tool surface that performs live API calls (link sessions, balance/transaction retrieval) rather than just docs access, and explicit scoped-credential/agent-auth model for such calls.

   • [claimed-docs] “Retrieve accounts, balances, and transactions with user consent.”
   • [claimed-docs] “Yapily Connect provides a ready-built, white-label open banking UI for AIS and PIS flows. Reduce development effort with pre-built instituti…”
   • [claimed-docs] “No frontend engineering required for consent and authorisation flows”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”
   • [claimed-docs] “Connect Claude, Cursor, or another AI coding agent directly to these docs via MCP, llms.txt, or Agent Skills.”
   • [probe] “official MCP server documented at https://docs.yapily.com/resources/ai-agents”

   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

   Yapily—none0/10

   Evidence shows Yapily Connect provides consent screens for initiating AIS/PIS authorization (docs-7, docs-20) but nothing about a portal or surface where end users can view all apps/connections and actively revoke previously granted consent to their bank data.

   ⚑ 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

   Yapily—none0/10

   No evidence describes a documented deletion/revocation flow for connections or users, nor confirmation that data collection stops and held data is purged; docs only mention consent collection, sandbox, webhooks, and data retrieval, not consent revocation or data deletion/purge.

   ⚑ 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

   Yapily~partialclaimed5/10

   Yapily separates its offerings into distinct products (Data API for AIS, Payments API for PIS, account confirmation, VRP) each with its own consent screen, implying developers only request the product-specific consent they need rather than a single blanket grant (yapily-docs-2, -15, -16, -20). However, there is no explicit documentation of fine-grained data-minimization controls within a product (e.g., requesting balances only vs. full transaction history) or scope parameters in the API reference. missing for 10: granular in-product scope/field-level consent documentation, explicit data-minimization API parameters, independent confirmation of scope enforcement.

   • [claimed-docs] “Retrieve accounts, balances, and transactions with user consent.”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”
   • [claimed-docs] “You can initiate single, scheduled and periodic payments using Yapily's Payments API.”
   • [claimed-docs] “UX design guidelines for Yapily Connect AIS flows. Best practices for institution selection, consent screens, and account selection for data…”

   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

   Yapily—none0/10

   Evidence covers account data retrieval, webhooks for real-time notifications, and payments, but nothing describes an on-demand refresh endpoint/parameter or documents refresh semantics (e.g., how often data updates or how to force a refresh). Missing for 10: any mention of a refresh API/endpoint, refresh frequency/rate limits, or documented semantics for on-demand data freshness.

   • [claimed-docs] “Retrieve accounts, balances, and transactions with user consent.”
   • [claimed-docs] “Webhooks allows you to receive real-time HTTP notifications of changes happening in the Yapily Platform.”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”

   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

   Yapily~partialclaimed6/10

   Yapily documents webhooks for real-time HTTP notifications of platform changes, explicitly used for payment status tracking, supporting event-driven updates instead of polling. However, the evidence never confirms webhook payloads are cryptographically signed, nor details specific coverage for new transactions/balance updates/connection state changes as separate event types. Missing for 10: signature/verification mechanism documentation, explicit event types for transactions/balances/connection state, and independent confirmation of reliability.

   • [claimed-docs] “Webhooks allows you to receive real-time HTTP notifications of changes happening in the Yapily Platform.”
   • [claimed-docs] “You can track the status of each payment via [Webhooks](/tools-and-services/webhooks/get-started) from the Yapily API for visibility of the …”

   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

   Yapily—none0/10

   The evidence pack contains no published institution counts, geographic coverage lists, or bank-name directories that a founder could check against their users' banks—only product/API feature descriptions.

   ⚑ 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

   Yapily—none0/10

   No evidence of a documented institution status page, outage/degradation signals, or error-code taxonomy distinguishing bank-side failures from client-side issues; only generic webhook and payment-status mentions are present. Missing for 10: institution status/availability page, degradation/outage signals, and documented bank-vs-integration error code distinctions.

   • [claimed-docs] “You can track the status of each payment via [Webhooks](/tools-and-services/webhooks/get-started) from the Yapily API for visibility of the …”
   • [claimed-docs] “Webhooks allows you to receive real-time HTTP notifications of changes happening in the Yapily Platform.”

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

   Yapily~partialclaimed6/10

   Yapily's Data API and consent flow (via Yapily Connect) grant access to accounts, balances, transactions, and identity data under a single AIS consent/session (yapily-docs-2, yapily-docs-4, yapily-docs-15, yapily-docs-20), and Yapily Connect explicitly reduces repeated consent screens across flows (yapily-docs-7, yapily-docs-9). However, payments (PIS) are documented as a separate initiation flow/API from data access (AIS), and no evidence explicitly confirms a single link/consent session spans both AIS and PIS products without re-authentication. missing for 10: explicit confirmation that one consent/session token covers both payments and data products together, and independent/hands-on evidence of a true single multi-product session rather than per-product consent screens.

   • [claimed-docs] “Retrieve accounts, balances, and transactions with user consent.”
   • [claimed-docs] “Confirm account ownership and customer details instantly.”
   • [claimed-docs] “Yapily Connect provides a ready-built, white-label open banking UI for AIS and PIS flows. Reduce development effort with pre-built instituti…”
   • [claimed-docs] “No frontend engineering required for consent and authorisation flows”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”
   • [claimed-docs] “UX design guidelines for Yapily Connect AIS flows. Best practices for institution selection, consent screens, and account selection for data…”
   • [claimed-docs] “You can initiate single, scheduled and periodic payments using Yapily's Payments API.”

   proof ↗⚑ flag

Quickstart

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

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

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

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

   proof ↗⚑ flag

   Yapily~partialprobed4/10

   Evidence confirms a sandbox test environment (yapily-docs-12) and client library generation via OpenAPI spec for Java, Python, Node.js, etc. (yapily-docs-8), but there is no evidence of a self-serve signup flow, API key issuance process, or a runnable quickstart guide. The openapi.json probe returned 404s across all candidate paths, casting doubt on how straightforward the client-library generation actually is in practice. missing for 10: self-serve signup/API-key evidence, an explicit quickstart walkthrough, working OpenAPI spec endpoint, independent corroboration of time-to-first-sandbox-account.

   • [claimed-docs] “A sandbox is a test environment that allows you to connect your application to a bank and access test accounts to simulate the real Open Ban…”
   • [claimed-docs] “Generate API client libraries for Yapily in your preferred language using the OpenAPI specification. Supports code generation for Java, Pyth…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.yapily.com/openapi.json, https://docs.yapily.com/swagger.json, https://docs.yapily.com/…”

   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

   Yapily~partialclaimed6/10

   Docs confirm a sandbox exists to connect to test banks and simulate the Open Banking experience, but the evidence pack doesn't detail documented test credentials, specific error-state simulation, or step-by-step end-to-end linking/retrieval walkthroughs. missing for 10: explicit test credentials list, error/edge-case simulation documentation, independent/hands-on confirmation of the sandbox experience.

   • [claimed-docs] “A sandbox is a test environment that allows you to connect your application to a bank and access test accounts to simulate the real Open Ban…”

   proof ↗⚑ flag

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

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

   Yapily~partialprobed6/10

   Yapily's UI (Yapily Connect) is explicitly described as a pre-built white-label layer for AIS/PIS flows that sits on top of the same Data and Payments APIs (docs-7, docs-9, docs-15, docs-16), implying most UI functionality is API-backed rather than API-exclusive. However, there is no explicit documentation stating full UI/API parity, and a probe found no discoverable OpenAPI spec at expected locations, raising doubt about complete self-service API coverage. Missing for 10: explicit parity statement enumerating any UI-only conveniences (e.g., branding, consent screen customization) and their API equivalents, and a working public OpenAPI spec confirming full endpoint coverage.

   • [claimed-docs] “Yapily Connect provides a ready-built, white-label open banking UI for AIS and PIS flows. Reduce development effort with pre-built instituti…”
   • [claimed-docs] “No frontend engineering required for consent and authorisation flows”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”
   • [claimed-docs] “You can initiate single, scheduled and periodic payments using Yapily's Payments API.”
   • [claimed-docs] “Generate API client libraries for Yapily in your preferred language using the OpenAPI specification. Supports code generation for Java, Pyth…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.yapily.com/openapi.json, https://docs.yapily.com/swagger.json, https://docs.yapily.com/…”

   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

   Yapily—none0/10

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

   ⚑ flag

3. ai-native 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

   Yapily—none0/10

   Yapily is a closed commercial open banking API/SaaS platform; there is no evidence of any open-source license or public source repository for its core product. Documentation and OpenAPI probes exist but source code openness is not evidenced anywhere in the pack.

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

   Yapily~partialclaimed6/10

   Yapily's docs clearly describe payment initiation (single, scheduled, periodic, recurring/VRP) via its Payments API using local rails like UK Faster Payments and European SEPA, giving some geographic grounding, but there is no comprehensive, explicit list of supported countries/markets or independent confirmation of live coverage claims. missing for 10: full country/geography list, independent verification of live markets, and any hands-on confirmation of payment success rates.

   • [claimed-docs] “Initiate bank-to-bank payments directly from your customer's account. Single, scheduled, or recurring.”
   • [claimed-docs] “You can initiate single, scheduled and periodic payments using Yapily's Payments API.”
   • [claimed-docs] “Choose this when you need payment types Hosted does not yet support (bulk, scheduled, periodic, international)”
   • [claimed-docs] “Payments are made via local payment rails including Faster Payments in the UK and SEPA in Europe for fast settlement”
   • [claimed-docs] “You can track the status of each payment via [Webhooks](/tools-and-services/webhooks/get-started) from the Yapily API for visibility of the …”

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

   Yapily✓fullclaimed8/10

   Docs explicitly cover recurring/scheduled/periodic payments (yapily-docs-1, -16, -17) and dedicated variable recurring payment support without re-authorisation (yapily-docs-5), plus webhook-based status tracking and local rail settlement for recurring debits (yapily-docs-18, -21). Missing for 10: independent/hands-on confirmation of VRP flows in production and more detail on standing consent lifecycle management beyond docs claims.

   • [claimed-docs] “Initiate bank-to-bank payments directly from your customer's account. Single, scheduled, or recurring.”
   • [claimed-docs] “Collect variable recurring payments without re-authorisation each time.”
   • [claimed-docs] “You can initiate single, scheduled and periodic payments using Yapily's Payments API.”
   • [claimed-docs] “Choose this when you need payment types Hosted does not yet support (bulk, scheduled, periodic, international)”
   • [claimed-docs] “You can track the status of each payment via [Webhooks](/tools-and-services/webhooks/get-started) from the Yapily API for visibility of the …”
   • [claimed-docs] “Payments are made via local payment rails including Faster Payments in the UK and SEPA in Europe for fast settlement”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Yapily—none0/10

   No evidence in the pack addresses data residency, regional storage choice, or hosting location options for customer data; all docs focus on payments, data access APIs, and AI-agent connectivity.

   ⚑ 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

   Yapily—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or user-initiated data removal options for Yapily; the documentation covers data access, payments, and AI-agent integration but nothing about retention/deletion controls.

   ⚑ flag

Cashflow

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

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

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

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

   proof ↗⚑ flag

   Yapily—none0/10

   Yapily's docs show transaction categorisation, merchant detection, and spending insights (yapily-docs-3), but there is no evidence of recurring income/payroll detection, cash-flow signal derivation, or income verification products built on the data.

   ⚑ flag

Enrichment

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

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

   Yapily~partialclaimed6/10

   Docs explicitly claim categorisation, merchant detection, and spending insights on transaction data (yapily-docs-3, yapily-docs-15), directly supporting enrichment as a documented platform capability rather than a DIY task. However, no evidence specifically documents merchant logo enrichment or detailed 'cleaned name' normalization, and there's no independent/hands-on confirmation of enrichment quality. Missing for 10: explicit logo enrichment documentation, detail on merchant name cleaning methodology, third-party/hands-on validation of enrichment accuracy.

   • [claimed-docs] “Categorise and analyse transaction data with merchant detection and spending insights.”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”

   proof ↗⚑ flag

Transactions

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

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

   Yapily~partialclaimed4/10

   Docs confirm transaction/account/balance retrieval via the Data API with consent (yapily-docs-2, yapily-docs-15) and webhooks for real-time change notifications (yapily-docs-13), which could support a sync pattern, but there is no documented pagination mechanism, no stated history depth/lookback window, and no explicit delta/incremental-fetch API for transactions. missing for 10: pagination details, documented transaction history depth, explicit changed-only/delta sync endpoint or pattern beyond generic webhooks.

   • [claimed-docs] “Retrieve accounts, balances, and transactions with user consent.”
   • [claimed-docs] “Using Yapily's Data API you can access your customers' financial data including account balances, transaction history and account details to…”
   • [claimed-docs] “Webhooks allows you to receive real-time HTTP notifications of changes happening in the Yapily Platform.”

   proof ↗⚑ flag