Mastercard Open Finance (Finicity) vs TrueLayer

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 Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)~partialclaimed3/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   The evidence pack describes TrueLayer's Data API for reading account/identity/transaction info and lists supported providers, but nowhere documents a drop-in hosted widget with a server-side session creation and token retrieval flow for account-linking (the closest analog, 'payment links', applies only to payments, not data/account linking). Missing for 10: hosted account-linking widget SDK/UI docs, session-creation endpoint for linking, and evidence of a returned account-link token from a widget flow.

   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”
   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”
   • [claimed-docs] “Query the providers endpoint to see which banks are supported in each European country and segment.”

   proof ↗⚑ flag

Oauth

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

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   The evidence pack covers TrueLayer's Payments, Data, and Verification APIs, SDKs, and a providers endpoint listing supported banks per country, but nothing explicitly documents that connections use bank-hosted OAuth versus screen-scraping, nor any statement about retiring legacy credential-based flows. Without that specific documentation, this axis is unsupported.

   • [claimed-docs] “Query the providers endpoint to see which banks are supported in each European country and segment.”
   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”

   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 drawn
   Mastercard Open Finance (Finicity)—none0/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   TrueLayer's docs cover consent, mandates, and webhooks for payment status but nowhere document how expired/revoked account-links surface as distinct statuses or how a user re-authenticates via an update flow without restarting; the evidence pack has no reference to reconnection/re-auth UX for broken links.

   ⚑ flag

Agent access

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

   weight 2 · round to TrueLayer
   Mastercard Open Finance (Finicity)✓fullprobed8/10

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

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

   proof ↗⚑ flag

   TrueLayer✓fullprobed9/10

   TrueLayer hosts a verified llms.txt at docs.truelayer.com/llms.txt (probe confirms HTTP 200) with a documented convention that any docs page can be appended with .md for markdown, directly enabling agent-oriented consumption; docs also explicitly cover an MCP integration for AI assistants, reinforcing agent-native design. Missing for 10: no independent third-party confirmation that agents reliably use this in practice beyond TrueLayer's own docs.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.truelayer.com/llms.txt # TrueLayer Documentation > TrueLayer Documentation Append .md to any docu…”
   • [claimed-docs] “Monitor payments and generate reports in Console.”
   • [claimed-docs] “By integrating the TrueLayer MCP server with this AI assistant, you'd empower Claude AI to perform a range of banking and payment operations…”
   • [probe] “official MCP server documented at https://docs.truelayer.com/docs/truelayer-mcp-integration-for-claude-ai”

   proof ↗⚑ flag

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

   weight 2 · round to Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)~partialclaimed6/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialclaimed5/10

   TrueLayer is API-first with SDKs (Node.js, Python, Java, .NET) and signing libraries, which are inherently usable in headless/automated/CI contexts since there is no GUI dependency for core payment/data operations. However, there is no explicit documentation about CI/CD integration, automated testing pipelines, or headless deployment guidance. Missing for 10: explicit CI/automation documentation, example CI pipeline configs, headless testing guidance, non-interactive auth flow docs for automated environments.

   • [claimed-docs] “SDKs for Node.js, Python, Java and .NET.”
   • [claimed-docs] “They simplify API calls with easy-to-use interfaces, type-hinted methods and abstractions. They also automate request signing for all Paymen…”
   • [github] “Convenient libraries to produce TrueLayer API requests signatures.”
   • [claimed-docs] “The Payments API v3 allows you to make and accept payments and payouts in the UK and EU.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Mastercard Open Finance (Finicity)✓fullprobed7/10

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

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

   proof ↗⚑ flag

   TrueLayer✓fullprobed7/10

   TrueLayer documents an official MCP server integration for Claude AI, exposing at least one concrete tool (create-truelayer-payment-link) that lets an agent perform banking/payment operations, and a probe confirms the doc page exists. Missing for 10: broader tool catalog beyond payment-link creation, independent/hands-on verification of the MCP server working, and details on setup/auth for non-Claude MCP clients.

   • [claimed-docs] “By integrating the TrueLayer MCP server with this AI assistant, you'd empower Claude AI to perform a range of banking and payment operations…”
   • [claimed-docs] “create-truelayer-payment-link` - Generate a new payment link for initiating a payment from a bank account to the TrueLayer merchant account”
   • [probe] “official MCP server documented at https://docs.truelayer.com/docs/truelayer-mcp-integration-for-claude-ai”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer—none0/10

   TrueLayer is a payments/banking API platform with SDKs, an MCP server for Claude, and signing libraries, but no evidence anywhere in the pack of an official CLI tool for developers or AI-native workflows.

   ⚑ flag

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

   weight 3 · round drawn
   Mastercard Open Finance (Finicity)✓fullprobed8/10

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

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

   proof ↗⚑ flag

   TrueLayer✓fullprobed8/10

   TrueLayer publishes extensive public API documentation covering Payments API v3, Data API, Verification API, webhooks, signing, and SDKs for Node.js/Python/Java/.NET, with a quickstart for making a test payment — clear evidence of a documented, programmatically drivable API for an AI-native or any developer user. Missing for 10: a discoverable machine-readable OpenAPI/Swagger spec (probe found only 404s), so full API surface must be inferred from prose docs rather than a formal schema.

   • [claimed-docs] “The Payments API v3 allows you to make and accept payments and payouts in the UK and EU.”
   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”
   • [claimed-docs] “SDKs for Node.js, Python, Java and .NET.”
   • [claimed-docs] “The Payments API v3 uses a pair of ECDSA keys in addition to a bearer token.”
   • [claimed-docs] “They simplify API calls with easy-to-use interfaces, type-hinted methods and abstractions. They also automate request signing for all Paymen…”
   • [claimed-docs] “you'll create a free UK merchant account and complete your first test payment with the Payments API v3”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.truelayer.com/llms.txt # TrueLayer Documentation > TrueLayer Documentation Append .md to any docu…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.truelayer.com/openapi.json, https://docs.truelayer.com/swagger.json, https://docs.truel…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   TrueLayer's docs describe standard API client credentials, OAuth-style bearer tokens plus ECDSA signing, and an MCP integration for Claude, but nothing describes issuing scoped or least-privilege credentials specifically for an AI agent (e.g., agent-specific API keys, granular permission tiers, or restricted scopes for automated/agentic use). Missing for 10: any mention of agent-specific credential scoping, permission tiers, or least-privilege key issuance beyond generic client_id/secret and bearer tokens.

   • [claimed-docs] “Invite users so they can retrieve your integration's client credentials, access the payments view, or issue refunds.”
   • [claimed-docs] “The Payments API v3 uses a pair of ECDSA keys in addition to a bearer token.”
   • [claimed-docs] “By integrating the TrueLayer MCP server with this AI assistant, you'd empower Claude AI to perform a range of banking and payment operations…”
   • [claimed-docs] “create-truelayer-payment-link` - Generate a new payment link for initiating a payment from a bank account to the TrueLayer merchant account”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to TrueLayer
   Mastercard Open Finance (Finicity)~partialclaimed3/10

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

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

   proof ↗⚑ flag

   TrueLayer✓fullclaimed7/10

   TrueLayer explicitly documents official SDKs for Node.js, Python, Java and .NET (truelayer-docs-11) that simplify API calls with typed interfaces and automate request signing (truelayer-docs-24), backed by a public GitHub signing library (truelayer-gh-1). Missing for 10: broader language coverage evidence, independent developer adoption signals (stars, community usage), and versioned changelog/release cadence proof.

   • [claimed-docs] “SDKs for Node.js, Python, Java and .NET.”
   • [claimed-docs] “They simplify API calls with easy-to-use interfaces, type-hinted methods and abstractions. They also automate request signing for all Paymen…”
   • [claimed-docs] “We offer signing libraries in these languages”
   • [github] “Convenient libraries to produce TrueLayer API requests signatures.”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to TrueLayer
   Mastercard Open Finance (Finicity)✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   TrueLayer✓fullclaimed8/10

   TrueLayer documents webhooks as JSON notifications for Payments API v3 events (e.g. payment status changes), configurable per-app via a webhook URI in Console, with signature verification (Tl-Signature) recommended via signing libraries. This gives a clear, documented subscribe-to-events-via-webhook mechanism usable programmatically by an AI-native integration. Missing for 10: no independent/hands-on corroboration of webhook reliability, and no evidence of webhook management via API (vs Console-only configuration) or filtering/subscription granularity.

   • [claimed-docs] “Webhooks are JSON-format notifications you receive when any event occurs within the Payments API v3.”
   • [claimed-docs] “webhooks inform you about: when a payment changes to a new status in the authorisation process”
   • [claimed-docs] “You must validate all incoming webhook requests through the `Tl-Signature` that accompanies the webhook.”
   • [claimed-docs] “Each of your apps in Console can have a single webhook URI, which the Payments API sends webhooks to.”
   • [claimed-docs] “We strongly recommend you use our signing libraries to verify the `Tl-Signature` of any webhooks you receive.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   TrueLayer's evidence covers Data/Payments APIs and an MCP integration letting Claude perform banking actions on a user's behalf, but nothing shows TrueLayer itself generating AI insights or suggestions from account/transaction data inside its Console or product surface.

   ⚑ flag

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

   weight 2 · round to TrueLayer
   Mastercard Open Finance (Finicity)—none0/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialprobed5/10

   TrueLayer supports payment mandates (VRPs/Direct Debits) that, once authorised, execute automatically in the background without further user authorisation, and webhooks provide event-driven automation; the MCP server integration also lets an AI agent (Claude) trigger banking/payment operations. However, there is no dedicated AI-native automation/scheduling framework—just mandate-based recurring payments plus generic webhooks and a single third-party MCP integration. Missing for 10: a first-party AI-agent automation/orchestration feature, evidence of persistent autonomous background agents beyond mandate execution, and broader multi-step automation tooling.

   • [claimed-docs] “Use the following steps to learn how to create a new payment mandate for your user. You'll need this mandate to set up recurring payments.”
   • [claimed-docs] “Once you create a payment on an authorised mandate, it executes immediately without requiring further user authorisation.”
   • [claimed-docs] “Payment mandates belong to one of three types: Sweeping VRPs... Wave 1 VRPs... Direct Debits”
   • [claimed-docs] “After you create a payment mandate and your user has authorised it, you can create a payment on the mandate... it executes immediately.”
   • [claimed-docs] “webhooks inform you about: when a payment changes to a new status in the authorisation process”
   • [claimed-docs] “By integrating the TrueLayer MCP server with this AI assistant, you'd empower Claude AI to perform a range of banking and payment operations…”
   • [claimed-docs] “create-truelayer-payment-link` - Generate a new payment link for initiating a payment from a bank account to the TrueLayer merchant account”
   • [probe] “official MCP server documented at https://docs.truelayer.com/docs/truelayer-mcp-integration-for-claude-ai”

   proof ↗⚑ flag

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

   weight 2 · round to TrueLayer
   Mastercard Open Finance (Finicity)~partialprobed5/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialprobed6/10

   TrueLayer documents an official MCP server integration with Claude AI that lets users invoke banking/payment operations (e.g., 'create-truelayer-payment-link') via natural language, directly enabling AI-native NL command usage. However, evidence only shows one example tool and a single AI assistant integration rather than a broad natural-language command surface across the full API. Missing for 10: evidence of broader NL command coverage across accounts/verification/mandates, independent hands-on confirmation of the MCP server's reliability, and support beyond Claude AI.

   • [claimed-docs] “By integrating the TrueLayer MCP server with this AI assistant, you'd empower Claude AI to perform a range of banking and payment operations…”
   • [claimed-docs] “create-truelayer-payment-link` - Generate a new payment link for initiating a payment from a bank account to the TrueLayer merchant account”
   • [probe] “official MCP server documented at https://docs.truelayer.com/docs/truelayer-mcp-integration-for-claude-ai”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   The evidence pack contains only static documentation descriptions (guides, webhook references, SDK mentions) with no mention of an interactive API reference or runnable code examples/try-it-out console. A direct probe for OpenAPI/Swagger specs at standard paths returned 404 across all candidates, indicating no discoverable interactive API explorer.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.truelayer.com/openapi.json, https://docs.truelayer.com/swagger.json, https://docs.truel…”
   • [claimed-docs] “SDKs for Node.js, Python, Java and .NET.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.truelayer.com/llms.txt # TrueLayer Documentation > TrueLayer Documentation Append .md to any docu…”

   proof ↗⚑ flag

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

   weight 2 · round to Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)✓fullprobed8/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   A direct probe for OpenAPI/Swagger spec files at common paths (openapi.json, swagger.json, etc.) returned 404 across the board, and no documentation item references a downloadable machine-readable API spec despite extensive API docs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.truelayer.com/openapi.json, https://docs.truelayer.com/swagger.json, https://docs.truel…”

   proof ↗⚑ flag

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

   weight 1 · round to Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialprobed5/10

   TrueLayer provides a free test/sandbox merchant account for making test payments (truelayer-docs-32, quickstart-make-a-test-payment), which lets a developer or AI agent exercise the Payments API without touching production data. However, there is no explicit documentation of a dedicated sandbox environment concept (separate sandbox base URLs, sandbox-specific credentials, or sandbox banks/test providers) distinct from a 'free account' used for a first test payment, and no confirmation the MCP integration itself can be pointed at a sandbox. Missing for 10: explicit sandbox environment documentation (test-mode endpoints, mock bank providers), confirmation that the MCP server/agent tooling can target sandbox vs production, and independent/hands-on verification of sandbox isolation.

   • [claimed-docs] “you'll create a free UK merchant account and complete your first test payment with the Payments API v3”
   • [claimed-docs] “By integrating the TrueLayer MCP server with this AI assistant, you'd empower Claude AI to perform a range of banking and payment operations…”
   • [probe] “official MCP server documented at https://docs.truelayer.com/docs/truelayer-mcp-integration-for-claude-ai”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer—none0/10

   Evidence confirms TrueLayer exposes a versioned API (Payments API v3) but nowhere documents a deprecation policy, versioning changelog, or sunset schedule for older API versions. Missing for 10: any versioning/deprecation policy page, changelog, migration guide, or sunset timeline evidence.

   • [claimed-docs] “The Payments API v3 allows you to make and accept payments and payouts in the UK and EU.”
   • [claimed-docs] “The Payments API v3 uses a pair of ECDSA keys in addition to a bearer token.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.truelayer.com/openapi.json, https://docs.truelayer.com/swagger.json, https://docs.truel…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer—none0/10

   The evidence pack covers single-payment, single-payout, and single-mandate creation flows, webhooks, and MCP tool for one-off payment links, but no documentation of any batch/bulk endpoint for processing many payments, payouts, or accounts in one call. Missing for 10: batch payment/payout creation endpoints, bulk data export or bulk verification APIs, any documented rate/volume-oriented bulk operation.

   • [claimed-docs] “The Payments API v3 allows you to make and accept payments and payouts in the UK and EU.”
   • [claimed-docs] “Send payments to bank accounts. Covers the API, beneficiary management and reconciliation.”
   • [claimed-docs] “Send payouts to bank accounts that have been verified against a user's identity.”
   • [claimed-docs] “Use the following steps to learn how to create a new payment mandate for your user. You'll need this mandate to set up recurring payments.”
   • [claimed-docs] “create-truelayer-payment-link` - Generate a new payment link for initiating a payment from a bank account to the TrueLayer merchant account”

   proof ↗⚑ flag

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

   weight 3 · round to TrueLayer
   Mastercard Open Finance (Finicity)—none0/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialclaimed4/10

   TrueLayer provides webhooks that notify external systems on payment status events, and payment mandates that execute automatically once authorised (e.g. VRPs, Direct Debits), giving building blocks for event-driven automation. However, there is no evidence of a native rules-engine or condition/action configuration UI where a user defines arbitrary 'if event X then do Y' automations within TrueLayer itself — the actual rule logic must be built by the developer's own system consuming the webhook. Missing for 10: a documented rules/automation engine, in-product trigger-action configuration, and any first-party or independent example of user-defined automation rules beyond webhooks and fixed mandate execution.

   • [claimed-docs] “Webhooks are JSON-format notifications you receive when any event occurs within the Payments API v3.”
   • [claimed-docs] “webhooks inform you about: when a payment changes to a new status in the authorisation process”
   • [claimed-docs] “Use the following steps to learn how to create a new payment mandate for your user. You'll need this mandate to set up recurring payments.”
   • [claimed-docs] “Once you create a payment on an authorised mandate, it executes immediately without requiring further user authorisation.”
   • [claimed-docs] “Payment mandates belong to one of three types: Sweeping VRPs... Wave 1 VRPs... Direct Debits”
   • [claimed-docs] “Each of your apps in Console can have a single webhook URI, which the Payments API sends webhooks to.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to TrueLayer
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer~partialclaimed5/10

   TrueLayer supports payment mandates (VRPs) that, once authorised, let a payment execute automatically and repeatedly without further user authorisation — a domain-specific form of recurring workflow (docs-15, docs-16, docs-30, docs-31). However there is no evidence of a general-purpose scheduler, cron-like triggers, or workflow orchestration beyond recurring payments themselves. missing for 10: general job/workflow scheduling primitives, evidence of scheduling cadence configuration (daily/weekly/custom), and any non-payment automation use case.

   • [claimed-docs] “Use the following steps to learn how to create a new payment mandate for your user. You'll need this mandate to set up recurring payments.”
   • [claimed-docs] “Once you create a payment on an authorised mandate, it executes immediately without requiring further user authorisation.”
   • [claimed-docs] “Payment mandates belong to one of three types: Sweeping VRPs... Wave 1 VRPs... Direct Debits”
   • [claimed-docs] “After you create a payment mandate and your user has authorised it, you can create a payment on the mandate... it executes immediately.”

   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 Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)~partialclaimed6/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   TrueLayer's documented Payments/Verification/Data APIs operate on UK/EU account identifiers (sort code/account number, IBAN, Direct Debit, Faster Payments, VRPs) and provide identity/name verification, not US-style ACH funding via account/routing numbers or tokenized ACH equivalents. No evidence pack item references ACH, routing numbers, or micro-deposit-free bank-debit tokenization.

   • [claimed-docs] “Verify that a bank account belongs to a given user.”
   • [claimed-docs] “Send payouts to bank accounts that have been verified against a user's identity.”
   • [claimed-docs] “We compare the identity data to the account holder's name for all the connected account(s) the user has given consent for.”
   • [claimed-docs] “Payment mandates belong to one of three types: Sweeping VRPs... Wave 1 VRPs... Direct Debits”
   • [claimed-docs] “Store bank account details for future payment initiation. Covers setup, consent and reuse.”

   proof ↗⚑ flag

Balances

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

   weight 3 · round to Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialclaimed5/10

   TrueLayer's Data API documents reading account balances (truelayer-docs-5, truelayer-docs-28), which could be used before initiating a payment, but there is no documented endpoint or guidance explicitly framed as a pre-payment real-time balance/NSF or risk check tied to the Payments API flow. missing for 10: explicit documentation of a balance-check step integrated into the payment initiation flow, real-time/NSF-specific balance endpoint framing, and independent confirmation of this workflow.

   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”
   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”
   • [claimed-docs] “The Payments API v3 allows you to make and accept payments and payouts in the UK and EU.”

   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 Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialclaimed5/10

   TrueLayer's Data API exposes 'identity' data alongside accounts/transactions/balances, and its Verification API explicitly compares identity data (name) against connected account holders — supporting name-based ownership matching. However, the evidence never confirms retrieval of addresses or contact details on file at the bank, only name matching. Missing for 10: explicit documentation of address/contact fields returned by the identity endpoint, and any hands-on confirmation of full account-holder profile retrieval.

   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”
   • [claimed-docs] “We compare the identity data to the account holder's name for all the connected account(s) the user has given consent for.”

   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 TrueLayer
   Mastercard Open Finance (Finicity)~partialclaimed5/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialclaimed6/10

   TrueLayer documents Data API/Verification API flows that verify account ownership and identity, plus Payments API mechanisms (mandates, webhooks, signed requests) that let merchants/platforms initiate verified payments to bank accounts — this covers the core 'linked accounts feed a payment processor' story. However, evidence is entirely first-party docs describing TrueLayer's own APIs as the processor, not clear documentation of handing verified credentials to a distinct third-party processor/platform via token exchange. missing for 10: independent/hands-on confirmation, explicit third-party processor handoff or OAuth token exchange spec, and real-world integration case studies beyond marketing snippets.

   • [claimed-docs] “Verify that a bank account belongs to a given user.”
   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”
   • [claimed-docs] “Store bank account details for future payment initiation. Covers setup, consent and reuse.”
   • [claimed-docs] “Send payouts to bank accounts that have been verified against a user's identity.”
   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”
   • [claimed-docs] “We compare the identity data to the account holder's name for all the connected account(s) the user has given consent for.”
   • [claimed-docs] “Use the following steps to learn how to create a new payment mandate for your user. You'll need this mandate to set up recurring payments.”
   • [claimed-docs] “After you create a payment mandate and your user has authorised it, you can create a payment on the mandate... it executes immediately.”
   • [claimed-docs] “Use TrueLayer for payments in your webshop with our plugins for WooCommerce, Shopify and Magento.”

   proof ↗⚑ flag

Agent data

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

   weight 2 · round to TrueLayer
   Mastercard Open Finance (Finicity)~partialprobed6/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialprobed7/10

   TrueLayer's Data API returns structured JSON (identity, accounts, transactions, balances) with a dedicated MCP server letting an AI assistant like Claude perform banking operations directly, and typed SDKs abstract the raw API surface — all strong signals of agent-consumable design. However, a probe found no discoverable OpenAPI/JSON schema (all candidate schema paths 404'd), and no evidence describes transaction enrichment (categorization, merchant normalization) that would let an agent reason without heuristic parsing. Missing for 10: published machine-readable schema/OpenAPI spec, documented data enrichment/categorization features, independent corroboration of agent consumption in practice.

   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”
   • [claimed-docs] “Webhooks are JSON-format notifications you receive when any event occurs within the Payments API v3.”
   • [claimed-docs] “SDKs for Node.js, Python, Java and .NET.”
   • [claimed-docs] “They simplify API calls with easy-to-use interfaces, type-hinted methods and abstractions. They also automate request signing for all Paymen…”
   • [claimed-docs] “By integrating the TrueLayer MCP server with this AI assistant, you'd empower Claude AI to perform a range of banking and payment operations…”
   • [claimed-docs] “create-truelayer-payment-link` - Generate a new payment link for initiating a payment from a bank account to the TrueLayer merchant account”
   • [probe] “official MCP server documented at https://docs.truelayer.com/docs/truelayer-mcp-integration-for-claude-ai”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.truelayer.com/openapi.json, https://docs.truelayer.com/swagger.json, https://docs.truel…”

   proof ↗⚑ flag

Agent operations

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

   weight 3 · round drawn
   Mastercard Open Finance (Finicity)~partialprobed6/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialprobed6/10

   TrueLayer ships an official MCP server for Claude AI (truelayer-docs-17, probe-3) with at least a documented `create-truelayer-payment-link` tool (truelayer-docs-27), and its APIs separately support account/balance/transaction retrieval (truelayer-docs-5, truelayer-docs-28) and connection management with scoped client credentials and ECDSA-signed requests (truelayer-docs-12, truelayer-docs-21). However, the MCP surface itself is only shown to expose link-session creation, not balance/transaction retrieval or connection management as MCP tools. Missing for 10: explicit MCP tools/endpoints for balance/transaction retrieval and connection management, and documentation of MCP-specific scoped credentials rather than general API auth.

   • [claimed-docs] “By integrating the TrueLayer MCP server with this AI assistant, you'd empower Claude AI to perform a range of banking and payment operations…”
   • [claimed-docs] “create-truelayer-payment-link` - Generate a new payment link for initiating a payment from a bank account to the TrueLayer merchant account”
   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”
   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”
   • [claimed-docs] “The Payments API v3 uses a pair of ECDSA keys in addition to a bearer token.”
   • [claimed-docs] “Invite users so they can retrieve your integration's client credentials, access the payments view, or issue refunds.”
   • [probe] “official MCP server documented at https://docs.truelayer.com/docs/truelayer-mcp-integration-for-claude-ai”

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

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

   ⚑ flag

   TrueLayer—none0/10

   No evidence of an end-user-facing consent dashboard or portal for viewing/revoking bank data access; documentation only covers developer-side consent creation (mandates, verification consent) and admin Console user management, not an end-user self-service revocation surface.

   ⚑ 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
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer—none0/10

   No evidence pack item documents a way to delete a connection/user, revoke consent, stop data collection, or purge held data; documentation covers payments, mandates, webhooks, and MCP integration but nothing about consent revocation or data deletion/erasure workflows.

   ⚑ 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 TrueLayer
   Mastercard Open Finance (Finicity)~partialclaimed4/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialclaimed5/10

   TrueLayer offers distinct product APIs (Payments, Data/Account Info, Verification, Payouts) that developers can integrate separately, implying some scoping by product, and Data API notes consent is tied to specific connected accounts a user has approved. However there is no explicit documentation of granular, developer-selectable OAuth scopes or a consent screen showing minimized data requests per call. missing for 10: explicit scope/permission parameters documented in API reference, evidence of a consent UI showing selectable data categories, and independent confirmation that unused scopes aren't granted by default.

   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”
   • [claimed-docs] “We compare the identity data to the account holder's name for all the connected account(s) the user has given consent for.”
   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”
   • [claimed-docs] “The Payments API v3 allows you to make and accept payments and payouts in the UK and EU.”
   • [claimed-docs] “Send payouts to bank accounts that have been verified against a user's identity.”

   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 drawn
   Mastercard Open Finance (Finicity)—none0/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   The evidence pack documents TrueLayer's Data API for reading account info, balances, and transactions, but contains no mention of an explicit on-demand refresh endpoint or documented refresh semantics (e.g., cache TTLs, force-refresh parameters, or freshness guarantees). This is a fair axis for an open banking data API, but no supporting evidence exists.

   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”
   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”

   proof ↗⚑ flag

Webhooks

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

   weight 2 · round to Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)~partialclaimed6/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialclaimed5/10

   TrueLayer documents signed webhooks (Tl-Signature validation) for the Payments API, notifying about payment status changes during authorisation — this covers signed delivery and payment state changes, but the evidence never shows webhooks for the Data API events explicitly named in the story (new transactions, balance updates, connection/consent state changes). Missing for 10: documented webhook events for transaction/balance/connection state changes on the Data/Accounts side, and any confirmation these are pushed rather than requiring polling of the Data API.

   • [claimed-docs] “We strongly recommend you use our signing libraries to verify the `Tl-Signature` of any webhooks you receive.”
   • [claimed-docs] “Webhooks are JSON-format notifications you receive when any event occurs within the Payments API v3.”
   • [claimed-docs] “webhooks inform you about: when a payment changes to a new status in the authorisation process”
   • [claimed-docs] “You must validate all incoming webhook requests through the `Tl-Signature` that accompanies the webhook.”
   • [claimed-docs] “Each of your apps in Console can have a single webhook URI, which the Payments API sends webhooks to.”
   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”

   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 TrueLayer
   Mastercard Open Finance (Finicity)—none0/10

   The evidence pack covers API capabilities (verification, balances, transaction data, webhooks, onboarding) but contains no published institution-coverage numbers, geographic breakdowns, or bank-reach statistics that a founder could check against their users' banks.

   ⚑ flag

   TrueLayer~partialclaimed5/10

   Docs state payments coverage spans UK and EU and provide a providers endpoint to query which banks are supported per country/segment, giving founders a way to check coverage against their user base. However, there's no published aggregate coverage numbers (e.g., total institutions reached) or a static geography breakdown document — only an API-based lookup. Missing for 10: published institution-count statistics, a documented list/table of supported countries and bank counts, and independent verification of coverage claims.

   • [claimed-docs] “The Payments API v3 allows you to make and accept payments and payouts in the UK and EU.”
   • [claimed-docs] “Query the providers endpoint to see which banks are supported in each European country and segment.”

   proof ↗⚑ flag

Status

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

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer—none0/10

   Evidence shows a providers endpoint for bank coverage/support by country (truelayer-docs-10) and generic webhook status events (truelayer-docs-33), but nothing documents per-institution health status, outage/degradation signals, or error codes that distinguish a bank-side failure from an integration-side one — missing for 10: institution status page/API, outage/degradation indicators, and error taxonomy separating bank vs merchant faults.

   • [claimed-docs] “Query the providers endpoint to see which banks are supported in each European country and segment.”
   • [claimed-docs] “webhooks inform you about: when a payment changes to a new status in the authorisation process”

   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 TrueLayer
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer✓fullclaimed7/10

   TrueLayer's Data API docs describe a single interface that covers identity, accounts, transactions and balance data across all integrated banks, implying one connection can serve multiple data products rather than separate flows per product ([truelayer-docs-28], [truelayer-docs-5]). Missing for 10: explicit description of the underlying consent/session mechanics (e.g., how one auth link's token scopes map to multiple product calls without re-prompting the user) and independent/hands-on confirmation that no re-authentication is required per product.

   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”
   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”
   • [claimed-docs] “Verify that a bank account belongs to a given user.”
   • [claimed-docs] “We compare the identity data to the account holder's name for all the connected account(s) the user has given consent for.”

   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 TrueLayer
   Mastercard Open Finance (Finicity)~partialclaimed5/10

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

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

   proof ↗⚑ flag

   TrueLayer✓fullclaimed7/10

   TrueLayer docs describe a self-serve quickstart that creates a free UK merchant account and completes a first test payment, plus SDKs for Node.js, Python, Java and .NET and dedicated signing libraries to speed integration. This directly matches the signup-to-first-linked-sandbox-account story, though all evidence is first-party docs with no independent/hands-on corroboration of actual time-to-first-success. Missing for 10: independent developer reports confirming ease/speed of the flow, explicit sandbox-environment terminology (vs 'test payment'), and confirmation that API key generation itself is fully self-serve without sales contact.

   • [claimed-docs] “you'll create a free UK merchant account and complete your first test payment with the Payments API v3”
   • [claimed-docs] “SDKs for Node.js, Python, Java and .NET.”
   • [claimed-docs] “They simplify API calls with easy-to-use interfaces, type-hinted methods and abstractions. They also automate request signing for all Paymen…”
   • [claimed-docs] “We offer signing libraries in these languages”
   • [github] “Convenient libraries to produce TrueLayer API requests signatures.”

   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 Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)~partialclaimed6/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialclaimed3/10

   Docs reference a quickstart that walks through creating a free account and completing a 'test payment' and a providers endpoint to see supported banks, implying some testing path exists, but there is no explicit mention of a sandbox environment, documented test institutions, or test credentials for exercising the Data API (linking/account retrieval) or specific error-state scenarios end-to-end. Missing for 10: explicit sandbox/test-bank credentials documentation, coverage of Data API linking and retrieval testing, and documented error-state simulation.

   • [claimed-docs] “you'll create a free UK merchant account and complete your first test payment with the Payments API v3”
   • [claimed-docs] “Query the providers endpoint to see which banks are supported in each European country and segment.”
   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)~partialclaimed6/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialprobed6/10

   TrueLayer is API-first: payments, payouts, mandates, data/account access, verification, webhooks and signing are all exposed as core API operations with SDKs, and Console (the UI) appears to largely mirror these merchant operations. However, some Console-only functions (inviting team users, MFA setup, account management, monitoring/reporting dashboards) are described as UI actions with no evidence of an equivalent API/endpoint, and no OpenAPI spec is discoverable (probe 404s), making full programmatic parity unverifiable. missing for 10: API-equivalents for Console user/team management and MFA setup, a public OpenAPI/schema confirming full endpoint parity, and independent confirmation that all UI actions have API counterparts.

   • [claimed-docs] “The Payments API v3 allows you to make and accept payments and payouts in the UK and EU.”
   • [claimed-docs] “Monitor payments and generate reports in Console.”
   • [claimed-docs] “Quickly see your merchant account balances, access balance reports, and configure sweeping.”
   • [claimed-docs] “Invite users so they can retrieve your integration's client credentials, access the payments view, or issue refunds.”
   • [claimed-docs] “After you create an account, add another layer of security with multi-factor authentication (MFA).”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.truelayer.com/openapi.json, https://docs.truelayer.com/swagger.json, https://docs.truel…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer—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 to TrueLayer
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer~partialclaimed2/10

   TrueLayer's core payments/banking product is a closed proprietary SaaS API with no evidence of full source availability, but one auxiliary component—the request-signing library—is published as open source on GitHub. missing for 10: no open license for the actual product/platform source, only a small signing helper library is open.

   • [github] “Convenient libraries to produce TrueLayer API requests signatures.”

   proof ↗⚑ flag

Pay by bank

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

   weight 2 · round to TrueLayer
   Mastercard Open Finance (Finicity)—none0/10

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

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

   proof ↗⚑ flag

   TrueLayer✓fullclaimed8/10

   TrueLayer's Payments API v3 is well documented for initiating pay-by-bank payments from a connected account, with a quickstart to create a test payment, payment links, mandates for recurring payments, and webhooks — and it explicitly states its live geographies as UK and EU (truelayer-docs-1, truelayer-docs-23, truelayer-docs-32, truelayer-docs-10). Missing for 10: independent/hands-on developer confirmation of the payment flow working end-to-end and a fully granular, country-by-country live-market breakdown beyond the UK/EU summary.

   • [claimed-docs] “The Payments API v3 allows you to make and accept payments and payouts in the UK and EU.”
   • [claimed-docs] “Accept Pay by Bank payments. Covers the API, authentication, webhooks and testing.”
   • [claimed-docs] “Generate payment links without a custom integration.”
   • [claimed-docs] “Use the following steps to learn how to create a new payment mandate for your user. You'll need this mandate to set up recurring payments.”
   • [claimed-docs] “you'll create a free UK merchant account and complete your first test payment with the Payments API v3”
   • [claimed-docs] “Query the providers endpoint to see which banks are supported in each European country and segment.”
   • [claimed-docs] “webhooks inform you about: when a payment changes to a new status in the authorisation process”

   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 TrueLayer
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer✓fullclaimed8/10

   TrueLayer documents payment mandates explicitly covering Sweeping VRPs, Wave 1 VRPs, and Direct Debits, with dedicated docs on creating a mandate and executing recurring payments on an authorised mandate without further user auth. This directly matches variable recurring payments, standing consents, and recurring debit flows built on the Payments API. Missing for 10: independent/hands-on corroboration beyond first-party docs, and more detail on standing consent lifecycle management (renewal/revocation).

   • [claimed-docs] “Use the following steps to learn how to create a new payment mandate for your user. You'll need this mandate to set up recurring payments.”
   • [claimed-docs] “Once you create a payment on an authorised mandate, it executes immediately without requiring further user authorisation.”
   • [claimed-docs] “Payment mandates belong to one of three types: Sweeping VRPs... Wave 1 VRPs... Direct Debits”
   • [claimed-docs] “After you create a payment mandate and your user has authorised it, you can create a payment on the mandate... it executes immediately.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer—none0/10

   TrueLayer's evidence covers UK/EU payments and data APIs but nowhere mentions user-selectable data residency or region storage controls; the mention of UK/EU scope reflects operational coverage, not a configurable data-residency choice. Missing for 10: any documentation of data residency options, region selection controls, or storage location configurability.

   • [claimed-docs] “The Payments API v3 allows you to make and accept payments and payouts in the UK and EU.”
   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”

   proof ↗⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

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

   ⚑ flag

   TrueLayer—none0/10

   No evidence of any data retention or deletion controls (e.g., data export, deletion API, retention policy settings) for AI-native users; evidence pack covers payments, data access APIs, webhooks, and MCP integration but nothing about controlling or deleting stored data.

   ⚑ flag

3. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Mastercard Open Finance (Finicity)—none0/10

   No evidence pack items mention telemetry, usage tracking, analytics collection, or any opt-out mechanism for AI-native or any users; this is an applicable axis for a developer platform but simply unevidenced.

   ⚑ flag

   TrueLayer—none0/10

   TrueLayer is a payments/banking API platform; no evidence in the pack addresses telemetry/usage-tracking opt-out settings for AI-native users interacting with its MCP integration or SDKs. This axis is plausible for a platform with SDKs and an MCP server, but no documentation or feature is cited, so it's 'none' rather than 'na'.

   ⚑ flag

Cashflow

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

   weight 2 · round to Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)~partialclaimed6/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   TrueLayer's Data API covers identity, accounts, balances and raw transaction history, but no evidence describes derived income/cash-flow signals such as recurring stream detection, payroll detection, or a dedicated income verification product built on the data.

   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”
   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”
   • [claimed-docs] “We compare the identity data to the account holder's name for all the connected account(s) the user has given consent for.”

   proof ↗⚑ flag

Enrichment

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

   weight 2 · round to Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)~partialclaimed4/10

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

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

   proof ↗⚑ flag

   TrueLayer—none0/10

   The Data API is documented as returning identity, accounts, transactions and balance data (truelayer-docs-28), but no evidence describes merchant name cleaning, categorization, or logo enrichment as a documented capability. Missing for 10: any mention of transaction enrichment, merchant name normalization, category tagging, or logo/icon data in the docs.

   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”

   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 Mastercard Open Finance (Finicity)
   Mastercard Open Finance (Finicity)~partialclaimed5/10

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

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

   proof ↗⚑ flag

   TrueLayer~partialclaimed3/10

   Docs confirm a Data API that reads account, balance and transaction history via a single interface (truelayer-docs-5, truelayer-docs-28), but there is no evidence of pagination mechanics, documented history depth/lookback window, or an incremental sync pattern (e.g., delta/cursor endpoints) for fetching only changed transactions. missing for 10: pagination details, documented transaction history depth/limits, incremental/delta sync mechanism.

   • [claimed-docs] “Read account information, balances and transaction history from a user's bank.”
   • [claimed-docs] “Access identity, accounts, transactions and balance data for all integrated banks with a single interface.”

   proof ↗⚑ flag