Adyen for Platforms vs Finix

Agent access

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

   weight 2 · round drawn
   Adyen for Platforms✓fullprobed9/10

   A probe confirms llms.txt returns HTTP 200 at docs.adyen.com/llms.txt with a description of the docs corpus, and individual docs pages are also available as .md files (e.g. platforms.md, onboard-users.md), directly supporting agent-oriented consumption. Missing for 10: no independent/community confirmation of an agent successfully using llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.adyen.com/llms.txt # Adyen Docs > Developer and merchant documentation for Adyen payments, Adyen f…”
   • [claimed-docs] “onboard sellers, service providers, or contractors on to your platform, and let Adyen verify them before paying out”

   proof ↗⚑ flag

   Finix✓fullprobed9/10

   Finix has a confirmed llms.txt endpoint returning HTTP 200 with a description of the docs, plus documented agent-oriented resources including an official MCP server for AI agents to query the API. This directly satisfies the story of pointing an agent at llms.txt or agent-oriented docs. Missing for 10: independent/community corroboration of actual agent usage against llms.txt or MCP server in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.finix.com/llms.txt # Finix Docs > Explore our documentation, guides, and APIs to start building yo…”
   • [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
   • [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”

   proof ↗⚑ flag

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

   weight 2 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed5/10

   Adyen for Platforms is API-first and offers a full REST API for onboarding, legal entity management, balance accounts, and split payments, plus webhooks for async status checks instead of polling — these are usable headlessly/in CI. However, there is no explicit CI/CD example, no CLI tool, and part of the onboarding flow relies on Adyen-hosted UI pages rather than pure headless flow. missing for 10: explicit CI/automation pipeline examples, a CLI or SDK automation guide, confirmation that all onboarding steps (not just hosted-page flow) can run fully headless without human/UI interaction.

   • [claimed-docs] “Build your own UI and collect required user data. You make API requests to create resources and submit the user data to Adyen.”
   • [claimed-docs] “Direct your users to a page hosted by Adyen, where Adyen manages the onboarding flow and user interface (UI).”
   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “Test the different types of transactions with Adyen that your integration handles using test credentials”

   proof ↗⚑ flag

   Finix—none0/10

   Finix is a payments infrastructure API with developer docs, sandbox environments, and an MCP server for querying API docs, but there is no evidence of a CLI, SDK automation tool, or headless mode designed for CI/automation pipelines. missing for 10: CLI tool, CI/CD integration examples, headless automation documentation, evidence of running Finix operations in scripted/automated pipelines.

   ⚑ flag

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

   weight 3 · round to Finix
   Adyen for Platforms~partialprobed6/10

   Adyen documents an official MCP server enabling natural-language connections to build on Adyen's platform, which is directly on-topic and applicable since Adyen is a payments platform, not an agent itself. However, evidence is limited to a single doc-page reference and generic description without detail on setup, scope of coverage for Platforms-specific APIs, or independent/hands-on confirmation. Missing for 10: detailed docs on MCP server capabilities/tools exposed, confirmation it covers Platforms-specific endpoints, and independent corroboration of real-world usage.

   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”
   • [probe] “official MCP server documented at https://docs.adyen.com/development-resources/mcp-server/”

   proof ↗⚑ flag

   Finix✓fullprobed7/10

   Finix documents an official MCP server allowing AI agents to query the Finix API for accurate answers, confirmed by both docs and a probe hit on the dedicated mcp-server page. Missing for 10: no independent/hands-on corroboration of the MCP server working, and no detail on setup, transport, or tool coverage beyond the brief description.

   • [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
   • [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   Evidence shows API docs, webhooks, and an MCP server for natural-language integration, but no mention of an official CLI tool for Adyen for Platforms; the openapi/CLI probes came back 404. missing for 10: any documentation of an official CLI, its install/usage, or command reference.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”
   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”

   proof ↗⚑ flag

   Finix—none0/10

   No evidence of an official CLI tool; Finix's docs cover APIs, Dashboard, and an MCP server but nothing about a command-line interface for developers.

   ⚑ flag

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

   weight 3 · round drawn
   Adyen for Platforms✓fullprobed8/10

   Adyen for Platforms is driven entirely through documented REST APIs (Legal Entity Management, Configuration API, Balance Accounts, split transactions), webhooks for async events, and even an official MCP server for natural-language/agentic access. Missing for 10: a discoverable OpenAPI/swagger spec (probe found 404s) and independent third-party corroboration of API completeness beyond vendor docs.

   • [claimed-docs] “Build your own UI and collect required user data. You make API requests to create resources and submit the user data to Adyen.”
   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”
   • [probe] “official MCP server documented at https://docs.adyen.com/development-resources/mcp-server/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”

   proof ↗⚑ flag

   Finix✓fullprobed8/10

   Finix provides extensive documented public APIs for onboarding, payouts, disputes, subscriptions, and webhooks, plus a sandbox environment and an llms.txt discovery file for AI agents, showing clear support for programmatic/API-driven use. missing for 10: independent third-party hands-on confirmation of API usability, and more detail on API completeness/versioning beyond docs listing.

   • [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
   • [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “Webhooks let you receive notifications programmatically when your API resources are created or updated.”
   • [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.finix.com/llms.txt # Finix Docs > Explore our documentation, guides, and APIs to start building yo…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   No evidence in the pack addresses issuing scoped or least-privilege API credentials for an AI agent; the docs cover onboarding, payouts, fraud monitoring, webhooks, and an MCP server, but nothing about API key/credential scoping or permission granularity for agents.

   ⚑ flag

   Finix—none0/10

   Finix docs mention separate Sandbox/Live API credentials but give no evidence of scoped or least-privilege credential issuance (e.g., role-based keys, permission scopes) for agent use cases; the MCP server doc is about querying API docs, not credential scoping.

   • [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
   • [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   The evidence pack only documents API endpoints (Legal Entity Management API, Configuration API, Checkout/webhooks) and an MCP server for natural-language access, but never mentions official client SDKs or language-specific libraries for building against Adyen for Platforms. Missing for 10: any citation of an official SDK, its languages, or GitHub repo/package documentation.

   • [claimed-docs] “Build your own UI and collect required user data. You make API requests to create resources and submit the user data to Adyen.”
   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”

   proof ↗⚑ flag

   Finix—none0/10

   The evidence pack repeatedly references Finix's APIs, dashboard, and an MCP server for AI agents to query documentation, but never mentions official SDKs (e.g., Python, Node, Java client libraries) for developers to build against. Missing for 10: any mention of official SDKs, supported languages, or SDK documentation/repos.

   • [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
   • [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
   • [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
   • [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Adyen for Platforms✓fullclaimed7/10

   Adyen documents a dedicated webhooks system for asynchronous event notifications, explicitly framed as an alternative to polling, which aligns well with an AI-agent-driven subscribe-to-events workflow. Missing for 10: no details on webhook subscription management API, event type catalog, or independent/hands-on corroboration of reliability.

   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”

   proof ↗⚑ flag

   Finix✓fullclaimed7/10

   Finix has documented webhook support for programmatic notifications when API resources are created/updated, matching the core subscribe-to-events story. missing for 10: no detail on payload schema/signature verification, no independent/hands-on corroboration of webhook reliability, and no explicit AI-agent-specific webhook consumption examples.

   • [claimed-docs] “Webhooks let you receive notifications programmatically when your API resources are created or updated.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   The evidence pack covers onboarding, payouts, fraud rules, reconciliation reports, and an MCP server for developer integration, but nothing describes AI-generated insights or suggestions surfaced to end users from their platform data. No dashboard AI features, analytics recommendations, or generative summaries are mentioned anywhere.

   ⚑ flag

   Finix—none0/10

   No evidence of AI-generated insights or suggestions surfaced from user data within Finix's dashboard or product; the MCP server evidence only supports asking an AI agent questions about the API, not in-product data insights.

   ⚑ flag

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

   weight 2 · round to Adyen for Platforms
   Adyen for Platforms~partialprobed4/10

   Adyen for Platforms documents background automation mechanics well suited to autonomous operation — managed payout schedules that run without manual intervention (docs-12), webhooks to avoid polling for async status changes (docs-13), and automated fraud/risk monitoring rules (docs-4, docs-18) — plus an MCP server that lets AI agents connect via natural language (docs-14, probe-4). However, there's no evidence tying these into an AI-agent-orchestrated 'set it up once and it runs autonomously' workflow specifically for AI-native users. Missing for 10: documentation of AI agents configuring/scheduling these automations via the MCP server end-to-end, evidence of persistent agent-driven task execution, and any hands-on/independent confirmation of autonomous agent use.

   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “identify fraudulent behavior, stop suspicious payouts, and flag unusual user activities.”
   • [claimed-docs] “Outsource financial user risk management to Adyen or use Adyen's custom tools to configure your own monitoring rules and mitigations”
   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”
   • [probe] “official MCP server documented at https://docs.adyen.com/development-resources/mcp-server/”

   proof ↗⚑ flag

   Finix—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 userOperate the product with natural-language commands

   weight 2 · round drawn
   Adyen for Platforms~partialprobed5/10

   Adyen documents an official MCP server explicitly designed to let developers 'use natural language to connect with Adyen's platform more easily and build new payment solutions faster,' which is direct evidence of natural-language operability. However, this is scoped to developer/build-time use rather than full operational control (onboarding, payouts, fraud monitoring, reconciliation are still driven via traditional REST APIs and dashboards per the rest of the pack). Missing for 10: evidence that end-to-end platform operations (onboarding, payouts, dispute handling, reporting) can be driven via natural language, and independent/hands-on confirmation of the MCP server's real-world coverage and reliability.

   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”
   • [probe] “official MCP server documented at https://docs.adyen.com/development-resources/mcp-server/”

   proof ↗⚑ flag

   Finix~partialprobed5/10

   Finix documents an official MCP server that lets an AI agent 'ask questions about the Finix API to get accurate, current answers' (finix-docs-21, finix-probe-2), showing some agentic/natural-language interface exists, but the evidence describes it as a Q&A/documentation lookup tool rather than a way to actually issue commands (e.g., create payouts, onboard sellers) via natural language. Missing for 10: evidence that natural-language commands can trigger real API actions (payouts, onboarding, disputes) rather than just answer questions, and any independent confirmation of this working end-to-end.

   • [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
   • [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   The evidence pack shows only static docs pages and confirms openapi/swagger endpoints return 404, with no mention of an interactive API reference or runnable code examples/try-it console.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.adyen.com/platforms/.md”

   proof ↗⚑ flag

   Finix—none0/10

   Evidence shows Finix has documentation, sandbox/live environments, and an MCP server, but nothing describes an interactive API reference with runnable/executable examples (e.g., no mention of embedded code sandboxes, 'try it' consoles, or in-docs request execution). Missing for 10: evidence of an interactive/runnable API reference tool, any 'try it' console feature, or runnable code snippets in docs.

   • [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.finix.com/llms.txt # Finix Docs > Explore our documentation, guides, and APIs to start building yo…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   The evidence pack shows explicit probes for OpenAPI/Swagger spec files at all standard candidate paths returning 404, and no other citation confirms a downloadable machine-readable API spec for Adyen for Platforms. While Adyen is an API-first product where this axis clearly applies, there is no evidence in the pack that a machine-readable spec is actually published or downloadable.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.adyen.com/platforms/.md”

   proof ↗⚑ flag

   Finix—none0/10

   No evidence of a downloadable OpenAPI spec or machine-readable API schema; docs mention guides, an llms.txt file, and an MCP server, but nothing about an OpenAPI/Swagger spec download.

   ⚑ flag

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

   weight 1 · round to Finix
   Adyen for Platforms✓fullclaimed7/10

   Docs explicitly describe using test credentials to test different transaction types against Adyen's integration before going live, which is a standard sandbox-vs-production separation for API-driven platforms. Missing for 10: no explicit mention of isolated sandbox data reset/cleanup tools, no independent/hands-on corroboration of sandbox fidelity, and no detail on how sandbox test data is kept separate from production records.

   • [claimed-docs] “Test the different types of transactions with Adyen that your integration handles using test credentials”

   proof ↗⚑ flag

   Finix✓fullclaimed8/10

   Finix explicitly documents separate Sandbox and Live accounts with distinct API credentials, and a dedicated test environment that simulates live payments (test cards, fee schemas, payout schedules) without touching production data. missing for 10: independent/hands-on confirmation from a developer using the sandbox, and explicit detail on data isolation guarantees between sandbox and production.

   • [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
   • [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   No evidence in the pack references API versioning, version numbers, or a deprecation policy/timeline for Adyen's APIs; probes for OpenAPI specs returned 404. This is a fair axis for a payments API platform, but nothing documents a versioning or deprecation policy, so it counts as none.

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

   proof ↗⚑ flag

   Finix—none0/10

   No evidence pack item mentions API versioning scheme or a documented deprecation policy; docs cover product features, sandbox/live environments, webhooks, and an MCP server but nothing about version lifecycle or deprecation commitments.

   ⚑ flag

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

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   Evidence shows per-resource API operations (create legal entities, balance accounts, split payments) but nothing about batch/bulk endpoints for processing many items in a single call, nor bulk import/export tooling for AI-native workflows.

   ⚑ flag

   Finix—none0/10

   Finix's evidence covers payments/payouts/onboarding APIs and an MCP server for querying API docs, but there is no mention of bulk operations, batch endpoints, or multi-item processing capabilities for AI-native automation.

   ⚑ flag

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

   weight 3 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed5/10

   Adyen for Platforms supports event-driven automation via webhooks (avoiding polling) and lets platforms 'configure your own monitoring rules and mitigations' for fraud/risk, plus custom payout schedules and split-payment instructions triggered by transaction events, but this is limited to a few pre-defined domains (payouts, risk, chargebacks) rather than a general-purpose rules engine for arbitrary events/actions. Missing for 10: a documented general rules/automation engine covering diverse event types and custom actions, and independent evidence of real-world automation workflows built on these primitives.

   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “Outsource financial user risk management to Adyen or use Adyen's custom tools to configure your own monitoring rules and mitigations”
   • [claimed-docs] “identify fraudulent behavior, stop suspicious payouts, and flag unusual user activities.”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”
   • [claimed-docs] “you can provide instructions to split payments and chargebacks when you make calls to the following endpoints”

   proof ↗⚑ flag

   Finix—none0/10

   Finix offers webhooks to receive event notifications, but there is no evidence of a rules engine or automation layer that lets users define conditional triggers/actions on those events—webhooks only push data, requiring external logic to act on it.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Adyen for Platforms~partialclaimed4/10

   Adyen for Platforms supports one specific recurring scheduling feature — managed payout schedules that recur based on location/currency for balance accounts — but this is a narrow payments-domain feature, not a general-purpose recurring job/workflow scheduler for AI-native automation use cases. Missing for 10: evidence of a general workflow/job scheduling API or automation framework beyond payout timing, no support for scheduling arbitrary recurring API workflows, and no AI-native orchestration hooks tied to scheduling.

   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”
   • [claimed-docs] “Control when and how users get paid, with a customizable or fully automated solution.”
   • [claimed-docs] “Set custom settlement and payout times. Combine with CashOut to unlock instant access to funds.”

   proof ↗⚑ flag

   Finix~partialclaimed4/10

   Finix documents recurring billing via Subscriptions and configurable payout schedules in its test environment, which are forms of recurring financial jobs, but there is no evidence of a general-purpose workflow/automation scheduler, cron-like triggers, or AI-agent-driven recurring task orchestration beyond these payment-specific features. Missing for 10: generic recurring workflow/automation engine, scheduling API beyond payouts/subscriptions, AI-agent orchestration of recurring tasks.

   • [claimed-docs] “Bill your customers and buyers using Finix's Subscriptions.”
   • [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”
   • [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”

   proof ↗⚑ flag

Embedded components

1. developerSeller-facing surfaces are embeddable — white-label components or APIs for balances, payouts, and transaction history that live inside my product under my brand

   weight 2 · round drawn
   Adyen for Platforms~partialclaimed6/10

   Adyen provides APIs to build your own UI for onboarding, balances, and transaction data (docs-6, docs-9, docs-8), and split payments/payouts data can be surfaced in a platform's own UI under its brand, satisfying the core embeddable/white-label ask via API-first approach. However, evidence does not show pre-built embeddable UI components (like white-label widgets) specifically for balances, payouts, or transaction history — only raw APIs plus an Adyen-hosted onboarding page (docs-7), which is not white-labeled inside the platform's own product. Missing for 10: dedicated white-label UI components/SDKs for balance/payout/transaction display, documentation of embeddable widgets, and independent/hands-on confirmation of branding customization depth.

   • [claimed-docs] “Build your own UI and collect required user data. You make API requests to create resources and submit the user data to Adyen.”
   • [claimed-docs] “Direct your users to a page hosted by Adyen, where Adyen manages the onboarding flow and user interface (UI).”
   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “you can provide instructions to split payments and chargebacks when you make calls to the following endpoints”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”

   proof ↗⚑ flag

   Finix~partialclaimed6/10

   Finix documents APIs to build custom onboarding, payout, and dispute experiences under the platform's own brand (finix-docs-9, finix-docs-10, finix-docs-12, finix-docs-17) plus dashboard-based reporting (finix-docs-24), suggesting sellers' financial data/actions can be surfaced via API in a host product. However, there is no explicit mention of pre-built white-label UI components/widgets (e.g., embeddable balance or transaction-history widgets) — only APIs and Finix's own hosted Dashboard/forms are described. missing for 10: explicit embeddable/white-label UI component library for balances/transaction history, evidence of branding customization on hosted components, independent confirmation of embedding experience.

   • [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
   • [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
   • [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
   • [claimed-docs] “Save time onboarding sellers by using our Onboarding Forms.”

   proof ↗⚑ flag

Omnichannel

1. founder with offline sellersIn-person works on the same stack — terminals or tap-to-pay SDKs that settle into the same seller balances and reporting as online payments

   weight 2 · round to Adyen for Platforms
   Adyen for Platforms~partialprobed2/10

   The evidence pack for Adyen for Platforms is entirely about online split payments, payouts, balance accounts, and onboarding — it never explicitly documents terminals or tap-to-pay SDKs settling into the same seller balance accounts. The only hint is a generic mention that Adyen's docs cover 'point-of-sale' alongside Platforms, which is not tied to unified balance/reporting for in-person sales. Missing for 10: explicit documentation of terminal/tap-to-pay SDK integration, confirmation that in-person transactions post to the same balance accounts and split-payment/reporting pipeline as online payments, and any hands-on or independent corroboration of this unified flow.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.adyen.com/llms.txt # Adyen Docs > Developer and merchant documentation for Adyen payments, Adyen f…”
   • [claimed-docs] “You can split the payments between one or more users, deduct costs as needed, and hold funds until payout.”
   • [claimed-docs] “use Adyen-generated reports for your bookkeeping and reconciliation processes to ensure accurate accounting of funds within your platform”

   proof ↗⚑ flag

   Finix—none0/10

   The evidence pack covers Finix's online payments, payouts, onboarding, disputes, and reporting APIs, but there is no mention of in-person/card-present capabilities such as terminals, tap-to-pay SDKs, or POS hardware integrations that settle into the same seller balances as online payments. Without any documentation of card-present/terminal support, this applicable capability is unevidenced.

   ⚑ flag

Seller reporting

1. ops userSellers can self-serve their money questions — per-seller statements, payout reconciliation reports, and exports that let their bookkeeper close the month without contacting me

   weight 2 · round drawn
   Adyen for Platforms~partialclaimed4/10

   Adyen provides platform-level reconciliation reports and managed payouts (docs-5, docs-12) that the operator can use, but there is no evidence of a seller-facing self-serve portal, per-seller statements, or bookkeeper-ready exports that sellers can access directly without going through the ops user. missing for 10: seller-facing statement/export UI, evidence of self-serve access for sub-merchants, bookkeeper-specific export formats.

   • [claimed-docs] “use Adyen-generated reports for your bookkeeping and reconciliation processes to ensure accurate accounting of funds within your platform”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”
   • [claimed-docs] “Control fees and use payments as a competitive edge, all managed in your Adyen Dashboard.”

   proof ↗⚑ flag

   Finix~partialclaimed4/10

   Finix documents a Payouts Dashboard and >10 automated report types (transactions, disputes, fees) plus seller-payout management tools, which could support reconciliation and reporting, but there's no explicit evidence of a seller-facing self-serve statement/export portal that sellers or their bookkeepers can access directly without going through the platform's ops team. Missing for 10: seller-facing self-serve statement/export UI, explicit reconciliation report for bookkeeper close-out, and any confirmation that sellers (not just the platform) can pull these reports themselves.

   • [claimed-docs] “Learn how to manage your payout activity using the Payouts Dashboard.”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
   • [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”

   proof ↗⚑ flag

Holds release

1. developerFunds can wait — hold seller funds in a balance until delivery or dispute windows pass, release on my schedule or trigger, with the escrow-like mechanics and their limits documented

   weight 2 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed6/10

   Adyen for Platforms lets you hold funds in balance accounts and split/deduct amounts until payout (docs-2, docs-9), and gives full control over payout timing via custom payouts or managed payout schedules triggered on your own schedule (docs-3, docs-12, docs-17, docs-20). This covers the core 'hold until release' mechanic, but there is no explicit escrow terminology, no documented dispute-window integration, and no stated limits (max hold duration, balance caps) governing the hold — missing for 10: explicit escrow/dispute-window semantics, documented hold-duration or balance limits, independent confirmation of behavior at scale.

   • [claimed-docs] “You can split the payments between one or more users, deduct costs as needed, and hold funds until payout.”
   • [claimed-docs] “decide when and how your users are paid, either utilizing our managed payouts solution, or exercising full control over timing with custom p…”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”
   • [claimed-docs] “Control when and how users get paid, with a customizable or fully automated solution.”
   • [claimed-docs] “Set custom settlement and payout times. Combine with CashOut to unlock instant access to funds.”

   proof ↗⚑ flag

   Finix~partialclaimed5/10

   Finix documents controlling seller payouts on your own schedule via Dashboard or API and topping up/holding a platform balance before disbursing funds (finix-docs-12, finix-docs-13, finix-docs-15), which supports delaying seller payouts, and it has dispute-handling workflows (finix-docs-17, finix-docs-18). But there is no dedicated 'escrow' feature description — no documented hold-until-delivery mechanism, dispute-window-linked release triggers, or stated limits on how long funds can be held. Missing for 10: explicit escrow/hold-fund mechanics tied to delivery or dispute windows, documented release triggers/automation, and stated limits or edge cases of such holds.

   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
   • [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
   • [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
   • [claimed-docs] “Upload evidence and submit a response to challenge a Dispute.”

   proof ↗⚑ flag

Negative balances

1. finance leadRefunds and chargebacks that exceed a seller's balance are recoverable — automatic debits against future earnings or their bank account, with the liability order documented

   weight 2 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed6/10

   Docs confirm split-chargeback handling with multiple configurable liability options (docs-11), split/deduct instructions for chargebacks (docs-10), and general balance/payout controls, implying negative balances can be recovered via future earnings splits. However, there is no explicit documentation of automatic debit against a seller's bank account or a clearly documented 'liability order' sequence (e.g., balance → future earnings → bank debit) as a finance-lead would need. Missing for 10: explicit bank-account debit/recovery mechanism for negative balances, documented liability/waterfall order, and independent confirmation of this recovery flow working in practice.

   • [claimed-docs] “you can provide instructions to split payments and chargebacks when you make calls to the following endpoints”
   • [claimed-docs] “You can choose between three different ways to handle potential chargeback events”
   • [claimed-docs] “You can split the payments between one or more users, deduct costs as needed, and hold funds until payout.”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”

   proof ↗⚑ flag

   Finix—none0/10

   Evidence covers disputes monitoring/response, payouts, and balance top-ups, but nothing describes automatic debiting of a seller's future earnings or bank account to recover chargeback/refund losses, nor any documented liability waterfall/order. missing for 10: documentation of automatic negative-balance recovery, debit reversal against future payouts or linked bank account, and liability order documentation.

   • [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
   • [claimed-docs] “Upload evidence and submit a response to challenge a Dispute.”
   • [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
   • [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”

   proof ↗⚑ flag

Splits

1. developerSplit one charge among any set of parties — route funds to multiple sellers, take my cut, and reverse or adjust the split later, all as first-class API objects

   weight 3 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed7/10

   Docs confirm split payments as first-class API objects — splitting funds among multiple sellers/parties, deducting platform fees, and even split-chargeback handling with three configurable methods for reversing/adjusting after the fact. However, there's no explicit evidence of later adjusting/modifying a split after settlement outside of chargebacks, nor independent/hands-on corroboration of the split-transaction API's flexibility. Missing for 10: evidence of post-settlement split adjustment beyond chargebacks, independent verification/hands-on API examples.

   • [claimed-docs] “You can split the payments between one or more users, deduct costs as needed, and hold funds until payout.”
   • [claimed-docs] “you can provide instructions to split payments and chargebacks when you make calls to the following endpoints”
   • [claimed-docs] “You can choose between three different ways to handle potential chargeback events”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”

   proof ↗⚑ flag

   Finix~partialclaimed5/10

   Finix's platform-payments docs show sellers can be onboarded and paid out, and platforms can 'monetize' payments and customize fees, which implies a split between seller and platform, but no evidence describes a first-class 'split' object spanning multiple sellers on one charge, nor mechanisms to reverse or adjust splits after the fact. missing for 10: explicit multi-party split/transfer API object, ability to route one charge to several sellers simultaneously, and reversal/adjustment of splits post-charge.

   • [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
   • [claimed-docs] “Finix allows you to easily monetize your payments. We offer out of the box customizability, efficiency, and revenue growth tools.”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “Some of the fee customizations available are: International charges, Transaction volume discounts, Applying fees per payment method, Acceler…”

   proof ↗⚑ flag

Dispute handling

1. ops userDisputes are managed per seller — chargebacks land against the right sub-merchant, evidence is submitted via API or dashboard, and outcomes flow back into seller balances automatically

   weight 3 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed6/10

   Docs confirm per-transaction chargeback splitting instructions tied to sub-merchants (docs-10) and three configurable ways to handle chargebacks (docs-11), plus webhooks for async status updates (docs-13) that could feed balance updates. However, there's no explicit evidence of a dedicated dispute-evidence submission workflow (API or dashboard) or confirmation that dispute outcomes automatically flow back into seller balances beyond generic split/chargeback allocation. Missing for 10: explicit evidence-submission API/dashboard flow for disputes, documented automatic balance reconciliation post-dispute-outcome, and independent/hands-on confirmation of per-seller dispute routing.

   • [claimed-docs] “you can provide instructions to split payments and chargebacks when you make calls to the following endpoints”
   • [claimed-docs] “You can choose between three different ways to handle potential chargeback events”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”

   proof ↗⚑ flag

   Finix~partialclaimed5/10

   Finix documents general dispute management (monitor/act via Dashboard or API, upload evidence, submit response) and separately documents platform/seller-based architecture (onboarding sellers, seller payouts, sub-merchant balances), implying disputes could be tied to sub-merchants, but no docs explicitly confirm chargebacks are routed per-seller or that outcomes automatically adjust seller balances. missing for 10: explicit documentation of chargebacks landing against the correct sub-merchant, and automatic balance reconciliation after dispute resolution.

   • [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
   • [claimed-docs] “Upload evidence and submit a response to challenge a Dispute.”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”

   proof ↗⚑ flag

Portfolio risk

1. ops userWatch risk across my seller portfolio — fraud and credit-risk signals per sub-merchant, alerts on anomalous sellers, and tools to pause payouts or offboard bad actors

   weight 2 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed6/10

   Docs confirm fraud/risk monitoring capabilities ("identify fraudulent behavior, stop suspicious payouts, and flag unusual user activities") and configurable monitoring rules/mitigations, plus ability to pause/control payouts and manage users. However, there is no evidence of a dedicated portfolio-wide dashboard view per sub-merchant, specific anomaly-alerting mechanics, or explicit offboarding tooling described in detail. Missing for 10: per-seller risk dashboard/scoring UI, alert configuration details, explicit offboarding workflow documentation, and independent/hands-on validation of these fraud tools in practice.

   • [claimed-docs] “identify fraudulent behavior, stop suspicious payouts, and flag unusual user activities.”
   • [claimed-docs] “Outsource financial user risk management to Adyen or use Adyen's custom tools to configure your own monitoring rules and mitigations”
   • [claimed-docs] “decide when and how your users are paid, either utilizing our managed payouts solution, or exercising full control over timing with custom p…”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”

   proof ↗⚑ flag

   Finix~partialclaimed4/10

   Finix documents dispute monitoring/response tools, payout dashboards, and automated reports covering transactions/disputes/fees, which partially support portfolio oversight and dispute handling. However there is no evidence of fraud or credit-risk scoring per sub-merchant, anomaly alerts on sellers, or explicit tools to pause payouts or offboard bad actors. missing for 10: fraud/credit-risk signal scoring per sub-merchant, anomaly detection alerts, explicit payout-pause/offboarding controls, independent validation of these risk tools.

   • [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
   • [claimed-docs] “Upload evidence and submit a response to challenge a Dispute.”
   • [claimed-docs] “Dispute Management Tools”
   • [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
   • [claimed-docs] “Learn how to manage your payout activity using the Payouts Dashboard.”

   proof ↗⚑ flag

Cross border

1. finance leadInternational sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wires

   weight 2 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed4/10

   Docs show global seller onboarding, managed/custom payout scheduling, and balance accounts tied to a single currency and location, implying some local-currency payout capability, but there's no explicit documentation of FX conversion mechanics, published FX rates/markups, or confirmation that payouts settle via local bank rails rather than wires. missing for 10: explicit FX handling/rate documentation, confirmation of local bank rail settlement vs wire transfers, multi-currency payout examples, independent verification of cost savings.

   • [claimed-docs] “Onboard global sellers with one integration while Adyen handles verification and payouts.”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “Control when and how users get paid, with a customizable or fully automated solution.”
   • [claimed-docs] “Set custom settlement and payout times. Combine with CashOut to unlock instant access to funds.”

   proof ↗⚑ flag

   Finix—none0/10

   Finix's documented payouts focus on US rails (ACH, wire, card, real-time bank payouts) and its only international-related mention is a fee customization for 'International charges' (finix-docs-25), not multi-currency payout support, FX handling, or local settlement rails. No evidence describes local-currency payouts to international sellers or settlement via local bank networks.

   • [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
   • [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
   • [claimed-docs] “Some of the fee customizations available are: International charges, Transaction volume discounts, Applying fees per payment method, Acceler…”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”

   proof ↗⚑ flag

Payout schedules

1. ops userPayouts run on the schedule each seller needs — daily, weekly, monthly, or manual, plus instant payouts to cards or real-time rails where supported, configurable per seller

   weight 3 · round to Adyen for Platforms
   Adyen for Platforms✓fullclaimed6/10

   Adyen documents managed payout schedules applied to balance accounts (daily/weekly/monthly cadence) as well as custom payout timing via API, plus CashOut for instant access to funds, directly matching the story's scheduling and instant-payout needs. However, the evidence doesn't spell out per-seller granularity (schedules are applied per location/currency group) or specifics on instant payouts to cards/real-time rails. Missing for 10: explicit per-seller schedule configuration detail, instant-to-card/real-time-rail specifics, and independent confirmation beyond vendor docs.

   • [claimed-docs] “decide when and how your users are paid, either utilizing our managed payouts solution, or exercising full control over timing with custom p…”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”
   • [claimed-docs] “Control when and how users get paid, with a customizable or fully automated solution.”
   • [claimed-docs] “Set custom settlement and payout times. Combine with CashOut to unlock instant access to funds.”

   proof ↗⚑ flag

   Finix~partialclaimed6/10

   Finix docs confirm real-time payouts to bank accounts or cards, payout links, top-up via ACH/wire, and a test environment where you can 'set payout schedules,' plus per-seller payout management via Dashboard or API. However, there's no explicit documentation of configurable daily/weekly/monthly/manual cadence options per seller or instant-payout-to-real-time-rails distinctions beyond cards. missing for 10: explicit per-seller schedule configuration UI/API (daily/weekly/monthly/manual options), documentation of real-time rail support beyond cards, and independent/hands-on confirmation of scheduling flexibility.

   • [claimed-docs] “Make a payout to a recipient's credit or debit card.”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
   • [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
   • [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Adyen for Platforms~partialprobed6/10

   Docs show extensive API coverage for platform operations (Legal Entity Management API for onboarding, Configuration API for balance accounts, split payments/chargebacks endpoints, webhooks instead of polling), and users can 'build your own UI' entirely via API rather than using Adyen-hosted pages. However, some controls like fee configuration are explicitly described as 'managed in your Adyen Dashboard', and no consolidated OpenAPI spec was discoverable (404s), so full UI/API parity isn't clearly evidenced. Missing for 10: explicit confirmation that dashboard-only features (fee control, monitoring rule configuration) have API equivalents, and a discoverable complete API reference/spec proving full parity.

   • [claimed-docs] “Build your own UI and collect required user data. You make API requests to create resources and submit the user data to Adyen.”
   • [claimed-docs] “Direct your users to a page hosted by Adyen, where Adyen manages the onboarding flow and user interface (UI).”
   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “you can provide instructions to split payments and chargebacks when you make calls to the following endpoints”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “Control fees and use payments as a competitive edge, all managed in your Adyen Dashboard.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”

   proof ↗⚑ flag

   Finix~partialclaimed6/10

   Docs repeatedly note dual access via 'Dashboard or API' for payouts, seller payouts, disputes, and onboarding (finix-docs-6,7,8,12,17), indicating most core operations are API-accessible, and a Sandbox/Live environment plus webhooks support programmatic workflows (finix-docs-19,20). However, some UI-only surfaces like reporting/dashboard analytics and pricing/fee customization tools are described only in dashboard terms (finix-docs-22,24,25) without explicit API parity confirmation. Missing for 10: explicit API equivalents for dashboard reporting/analytics and fee-customization UI, and independent/hands-on confirmation that no UI action is API-inaccessible.

   • [claimed-docs] “Learn how to onboard your sellers with Finix's APIs.”
   • [claimed-docs] “Make a payout to a recipient's credit or debit card.”
   • [claimed-docs] “Learn how to create payout links on the Finix Dashboard and via API”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
   • [claimed-docs] “Webhooks let you receive notifications programmatically when your API resources are created or updated.”
   • [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
   • [claimed-docs] “Dispute Management Tools”
   • [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Adyen for Platforms—none0/10

   No evidence of any data export/portability feature or open-format data dump capability; documentation covers onboarding, payouts, fraud, reporting, and API integration but never data export or account closure/portability. Reports (docs-5) are for bookkeeping, not full data export in open formats.

   ⚑ flag

   Finix—none0/10

   No evidence describes an ability to export all account/transaction data in open formats or facilitate leaving the platform; only dashboard reporting features are mentioned, not full data export/portability. Missing for 10: documented bulk data export, open format guarantees (CSV/JSON), or data portability/exit tooling.

   ⚑ flag

Graduation path

1. founderThere's a path up the stack — start on the managed model and graduate toward registered payment facilitation with more economics and control, without replatforming

   weight 2 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed4/10

   Adyen for Platforms documents a spectrum of control (managed vs. custom payouts, outsourced vs. self-configured risk, fee control) within the same platform, which implies increasing control without switching providers, but there is no explicit documentation of a formal path to registered PayFac status or licensing progression with more economics/control retained by the founder. missing for 10: explicit registered-PayFac graduation path, documentation of economics/liability shift, evidence of no-replatform migration mechanics.

   • [claimed-docs] “decide when and how your users are paid, either utilizing our managed payouts solution, or exercising full control over timing with custom p…”
   • [claimed-docs] “Control fees and use payments as a competitive edge, all managed in your Adyen Dashboard.”
   • [claimed-docs] “Control when and how users get paid, with a customizable or fully automated solution.”
   • [claimed-docs] “Outsource financial user risk management to Adyen or use Adyen's custom tools to configure your own monitoring rules and mitigations”
   • [claimed-docs] “Set custom settlement and payout times. Combine with CashOut to unlock instant access to funds.”

   proof ↗⚑ flag

   Finix—none0/10

   Evidence shows Finix's platform-payments features (seller onboarding, payouts, monetization, disputes) but nowhere describes a staged path from a managed/PayFac-as-a-service model to full registered payment facilitation, nor any assurance that such a transition avoids replatforming. This specific payfac-liability graduation story is unaddressed in the pack.

   ⚑ flag

Responsibility split

1. ops userThe responsibility split is explicit — who owns KYC/AML, card-network compliance, fraud losses, and seller misconduct between me and the provider, in the docs rather than the contract's fine print

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   The evidence describes onboarding, verification, fraud monitoring, payouts, and split-payment mechanics, but nowhere is there an explicit statement of which party (Adyen vs. platform) bears legal/financial responsibility for KYC/AML compliance, card-network rule adherence, fraud losses, or seller misconduct. Docs describe capabilities ('Adyen verifies', 'outsource risk management to Adyen') but do not delineate a liability/ownership split in plain-language documentation as the story requires. Missing for 10: explicit liability-allocation documentation, a dedicated responsibility-matrix or compliance-ownership page, statements on who absorbs fraud/chargeback losses or seller misconduct liability.

   • [claimed-docs] “onboard sellers, service providers, or contractors on to your platform, and let Adyen verify them before paying out”
   • [claimed-docs] “identify fraudulent behavior, stop suspicious payouts, and flag unusual user activities.”
   • [claimed-docs] “You can choose between three different ways to handle potential chargeback events”
   • [claimed-docs] “Outsource financial user risk management to Adyen or use Adyen's custom tools to configure your own monitoring rules and mitigations”
   • [claimed-docs] “Onboard global sellers with one integration while Adyen handles verification and payouts.”

   proof ↗⚑ flag

   Finix—none0/10

   Evidence pack shows only feature-level docs (onboarding, payouts, disputes, tokenization) with no explicit documentation splitting liability for KYC/AML, card-network compliance, fraud losses, or seller misconduct between Finix and the platform/ops user. Community items are unrelated commentary about branding/positioning, not liability allocation.

   ⚑ flag

Tax forms

1. finance leadSeller tax reporting is handled — 1099-K thresholds tracked, forms generated, delivered, and filed, with the data corrections workflow documented

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   The evidence pack covers onboarding, payouts, splits, chargebacks, reconciliation reports, and fraud monitoring, but contains no mention of 1099-K threshold tracking, tax form generation/delivery/filing, or a data corrections workflow for tax reporting.

   ⚑ flag

   Finix—none0/10

   No evidence in the pack mentions 1099-K thresholds, tax form generation/filing, delivery to sellers, or any data-correction workflow for tax reporting; coverage is limited to payouts, onboarding, disputes, and reporting on transactions/fees.

   ⚑ flag

Agent money ops

1. ai-native userAn agent can work the money side — read balances and payouts, investigate a seller's missing payout, draft dispute evidence — against documented, agent-usable surfaces

   weight 2 · round drawn
   Adyen for Platforms~partialprobed6/10

   Adyen for Platforms exposes documented APIs for balances, payouts, legal entities, and split/chargeback handling (docs-8,9,10,11,12), webhooks for async status changes (docs-13), and even a first-party MCP server for natural-language integration (docs-14, probe-4), which supports an agent-native access pattern. However, there is no direct evidence of an endpoint or workflow specifically for 'investigating a missing payout' or 'drafting dispute evidence' — only general chargeback-handling docs — and the openapi probe returned 404s, suggesting no single machine-readable spec for full API discovery. Missing for 10: explicit payout-investigation workflow docs, dispute-evidence drafting API/docs, and a discoverable OpenAPI/machine-readable schema confirming full agent tool coverage.

   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “you can provide instructions to split payments and chargebacks when you make calls to the following endpoints”
   • [claimed-docs] “You can choose between three different ways to handle potential chargeback events”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”
   • [probe] “official MCP server documented at https://docs.adyen.com/development-resources/mcp-server/”

   proof ↗⚑ flag

   Finix~partialprobed6/10

   Finix documents API/dashboard surfaces for reading payouts, diagnosing failed payouts, and uploading dispute evidence (finix-docs-7,12,13,16,17,18), and it ships an official MCP server so agents can query API documentation (finix-docs-21, finix-probe-2). However, the MCP server is explicitly for answering questions about the API, not for performing agent actions like reading live balances or drafting/submitting dispute evidence directly — that still requires building against the REST API. Missing for 10: evidence of an agent actually executing balance/payout reads or dispute-evidence actions via the MCP server or an agent SDK, and independent/hands-on confirmation of agent usability.

   • [claimed-docs] “Make a payout to a recipient's credit or debit card.”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
   • [claimed-docs] “Diagnose and resolve payouts that fail before funds reach the recipient.”
   • [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
   • [claimed-docs] “Upload evidence and submit a response to challenge a Dispute.”
   • [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
   • [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”

   proof ↗⚑ flag

Agent onboarding

1. ai-native userAn agent can run seller operations — create accounts, drive onboarding to completion, and answer requirements-due states through the API or an MCP surface with scoped credentials

   weight 3 · round to Adyen for Platforms
   Adyen for Platforms~partialprobed5/10

   Adyen for Platforms exposes API-driven seller onboarding (create legal entities, balance accounts, submit KYC data) via docs-6/8/9, and Adyen documents a first-party MCP server for natural-language interaction with its platform (docs-14, probe-4), which together make agent-driven account creation and onboarding plausible. However, there is no evidence the MCP server specifically exposes onboarding/requirements-due workflows, no documentation of scoped/limited credentials for agent use, and no explicit mention of programmatically checking or resolving 'requirements due' verification states. Missing for 10: MCP server tool list/scope confirming onboarding operations, scoped-credential/permission model for agent access, and explicit API/MCP support for querying and resolving requirements-due status.

   • [claimed-docs] “Build your own UI and collect required user data. You make API requests to create resources and submit the user data to Adyen.”
   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”
   • [probe] “official MCP server documented at https://docs.adyen.com/development-resources/mcp-server/”

   proof ↗⚑ flag

   Finix~partialprobed4/10

   Finix has API-based seller onboarding (create accounts, onboarding forms, API onboarding flows) and an official MCP server for the docs/API, but the MCP server is documented as a Q&A assistant ('ask an AI agent questions about the Finix API') rather than an actionable surface for agents to create accounts, drive onboarding, or query/answer requirements-due states. No evidence of scoped credentials for agent-driven actions or of onboarding-status/requirements-due endpoints being exposed via MCP. missing for 10: evidence that the MCP server supports actionable operations (account creation, onboarding progression) rather than just Q&A, documentation of requirements-due/onboarding-status API endpoints, and evidence of scoped/agent-specific credentialing.

   • [claimed-docs] “Learn how to onboard your sellers with Finix's APIs.”
   • [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
   • [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
   • [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
   • [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
   • [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”

   proof ↗⚑ flag

Agentic commerce

1. developerThe platform is ready for agent buyers — documented support for agent-initiated checkout on marketplace transactions (agentic-commerce protocols, delegated payment credentials) that works with split funds flows

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   Evidence covers split payments, onboarding, payouts, and even an MCP server for developer tooling, but nothing addresses agent-initiated checkout, agentic-commerce protocols, or delegated payment credentials for AI agent buyers on marketplace transactions. No mention of agent commerce standards (e.g., Agentic Commerce Protocol, delegated tokens) exists in the pack.

   ⚑ flag

   Finix—none0/10

   No evidence of agent-initiated checkout support, agentic-commerce protocols, or delegated payment credentials tied to marketplace split-funds flows; docs only cover standard onboarding, payouts, disputes, and an MCP server for asking questions about the API, not enabling agent-driven purchases.

   • [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
   • [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
   • [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”

   proof ↗⚑ flag

Funds custody

1. finance leadPlatform funds have a home — clarity on where in-flight and held funds sit, whether balances earn yield, and how money is segregated from the provider's own accounts

   weight 2 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed4/10

   Docs confirm balance accounts hold/segregate funds per user and describe payout timing, splits, and reconciliation reports, giving some visibility into where in-flight and held funds sit. However, there is no mention of whether balances earn yield/interest, and no explicit statement on legal/regulatory segregation of platform funds from Adyen's own corporate accounts (safeguarding, e-money regulations, etc.). missing for 10: yield/interest treatment on balances, explicit fund-segregation/safeguarding disclosures, independent audit or regulatory confirmation of asset protection.

   • [claimed-docs] “You can split the payments between one or more users, deduct costs as needed, and hold funds until payout.”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “use Adyen-generated reports for your bookkeeping and reconciliation processes to ensure accurate accounting of funds within your platform”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”

   proof ↗⚑ flag

   Finix—none0/10

   The evidence pack covers payouts, onboarding, disputes, and dashboard reporting, but contains no mention of where held/in-flight funds are custodied, whether balances earn yield, or how platform funds are segregated from Finix's own accounts — a standard and expected disclosure for a payments/platform-ledger product. missing for 10: any documentation of fund custody/segregation structure, statements on yield/interest on held balances, and disclosure of banking partner or FBO account arrangements.

   • [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
   • [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”

   proof ↗⚑ flag

Ledger visibility

1. finance leadThe platform's money is legible — balances by seller and by my own fee accounts, every movement traceable from charge through split to payout, reconcilable to the penny

   weight 3 · round drawn
   Adyen for Platforms~partialclaimed6/10

   Docs confirm balance accounts per seller/platform, split payments with fee deduction, chargeback splitting, managed/custom payouts, and Adyen-generated reports for bookkeeping/reconciliation, which directly supports per-seller and per-fee-account balance visibility and reconciliation. However, there's no concrete evidence of penny-level traceability from charge through split to payout (e.g., detailed report schemas, transaction-level audit trail examples, or reconciliation report samples) or independent/hands-on validation of reconciliation accuracy. Missing for 10: sample reconciliation reports/schemas showing charge-to-payout linkage, evidence of penny-accurate reconciliation, and independent/third-party confirmation of ledger accuracy.

   • [claimed-docs] “You can split the payments between one or more users, deduct costs as needed, and hold funds until payout.”
   • [claimed-docs] “use Adyen-generated reports for your bookkeeping and reconciliation processes to ensure accurate accounting of funds within your platform”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “you can provide instructions to split payments and chargebacks when you make calls to the following endpoints”
   • [claimed-docs] “You can choose between three different ways to handle potential chargeback events”
   • [claimed-docs] “you can create a managed payout schedule for your balance platform and apply it to balance accounts with the same location and currency”

   proof ↗⚑ flag

   Finix~partialclaimed6/10

   Finix provides fee/monetization tooling, a Payouts Dashboard, 10+ automated report types (transactions, disputes, fees), sandbox/live environments and webhooks for tracking resource state changes, which together support financial visibility and reconciliation workflows. However, there is no explicit documentation of a unified ledger view showing per-seller balances alongside platform fee-account balances, or a single traceable charge→split→payout audit trail guaranteed to reconcile to the penny. Missing for 10: dedicated seller-balance/fee-account balance dashboard, explicit charge-to-payout traceability/audit-trail documentation, penny-level reconciliation guarantees or tooling.

   • [claimed-docs] “Learn how to manage your payout activity using the Payouts Dashboard.”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
   • [claimed-docs] “Webhooks let you receive notifications programmatically when your API resources are created or updated.”
   • [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
   • [claimed-docs] “Some of the fee customizations available are: International charges, Transaction volume discounts, Applying fees per payment method, Acceler…”
   • [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”

   proof ↗⚑ flag

Recon exports

1. developerReconciliation is automatable — settlement and balance reports per seller and rolled up, delivered as files or APIs my finance stack consumes on schedule

   weight 2 · round to Adyen for Platforms
   Adyen for Platforms~partialclaimed6/10

   Adyen documents Adyen-generated reports for bookkeeping/reconciliation, webhooks for async status updates instead of polling, and APIs for balance accounts, legal entities, and split transactions that support per-seller and rolled-up reconciliation data. However, evidence doesn't detail scheduled file delivery formats, per-seller vs platform-rolled-up report structures, or specifics on how finance stacks consume these on a schedule. missing for 10: documented report scheduling/delivery mechanics (SFTP/file cadence), explicit per-seller vs aggregate report examples, third-party finance-tool integration evidence.

   • [claimed-docs] “use Adyen-generated reports for your bookkeeping and reconciliation processes to ensure accurate accounting of funds within your platform”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “you can provide instructions to split payments and chargebacks when you make calls to the following endpoints”
   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”

   proof ↗⚑ flag

   Finix~partialclaimed5/10

   Finix docs mention automated dashboard reports (10+ report types covering transactions, disputes, fees) and webhooks for programmatic event notifications, plus seller payout management via API, which together support some reconciliation workflows. However, there is no explicit documentation of scheduled file delivery, per-seller vs rolled-up settlement/balance report APIs, or a dedicated reconciliation/reporting API for finance-stack consumption. Missing for 10: explicit scheduled report export (files/API), per-seller vs aggregate balance reconciliation endpoints, and confirmation of finance-stack integration patterns.

   • [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
   • [claimed-docs] “Webhooks let you receive notifications programmatically when your API resources are created or updated.”
   • [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”

   proof ↗⚑ flag

Application fees

1. founderPayments are a revenue line — take an application fee or markup on every transaction, set per-seller pricing, and see my payments revenue reported distinctly from processing costs

   weight 3 · round to Finix
   Adyen for Platforms~partialclaimed6/10

   Adyen for Platforms explicitly supports splitting payments and deducting costs/fees per transaction via the Split Transactions API, and markets 'control fees and use payments as a competitive edge' plus bookkeeping/reconciliation reports (docs-2, docs-10, docs-16, docs-5). However, there's no explicit documentation of per-seller custom fee/pricing configuration or a dedicated report that separates platform monetization revenue from underlying processing costs. Missing for 10: explicit per-seller pricing/fee-schedule configuration, dedicated revenue-vs-cost reporting or dashboard view distinguishing platform fee income from interchange/processing costs.

   • [claimed-docs] “You can split the payments between one or more users, deduct costs as needed, and hold funds until payout.”
   • [claimed-docs] “you can provide instructions to split payments and chargebacks when you make calls to the following endpoints”
   • [claimed-docs] “Control fees and use payments as a competitive edge, all managed in your Adyen Dashboard.”
   • [claimed-docs] “use Adyen-generated reports for your bookkeeping and reconciliation processes to ensure accurate accounting of funds within your platform”
   • [claimed-docs] “You can choose between three different ways to handle potential chargeback events”

   proof ↗⚑ flag

   Finix✓fullclaimed8/10

   Finix explicitly documents platform monetization: per-seller fee customization (international charges, volume discounts, per-method fees), a dedicated 'Monetizing Payments' guide, and dashboard reporting that separates transactions, disputes, and fees across 10+ automated report types. This directly supports application fees/markup, per-seller pricing, and distinct revenue reporting. Missing for 10: no independent/hands-on verification of the revenue-vs-cost reporting split or real-world confirmation that markup fees appear as distinct line items in the dashboard.

   • [claimed-docs] “Finix allows you to easily monetize your payments. We offer out of the box customizability, efficiency, and revenue growth tools.”
   • [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
   • [claimed-docs] “Some of the fee customizations available are: International charges, Transaction volume discounts, Applying fees per payment method, Acceler…”
   • [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”
   • [claimed-docs] “Dispute Management Tools”

   proof ↗⚑ flag

Buy rates

1. finance leadI control the economics — a documented buy rate from the provider and freedom to set the sell rate my sellers see, with interchange-level cost visibility to manage the spread

   weight 2 · round to Finix
   Adyen for Platforms~partialclaimed4/10

   Adyen documents that platforms can control fees/sell rates (docs-16), split payments and deduct costs (docs-2), and use Adyen-generated reports for reconciliation (docs-5), which supports sell-rate freedom and some cost visibility. However, there is no explicit documentation of a defined 'buy rate' from Adyen or interchange-level cost breakdowns to manage the spread precisely. Missing for 10: documented buy-rate/cost basis from Adyen, interchange-level fee transparency in reporting, explicit spread-management guidance.

   • [claimed-docs] “Control fees and use payments as a competitive edge, all managed in your Adyen Dashboard.”
   • [claimed-docs] “You can split the payments between one or more users, deduct costs as needed, and hold funds until payout.”
   • [claimed-docs] “use Adyen-generated reports for your bookkeeping and reconciliation processes to ensure accurate accounting of funds within your platform”

   proof ↗⚑ flag

   Finix~partialclaimed5/10

   Finix documents platform monetization tools — fee customization (international charges, volume discounts, per-payment-method fees), configurable fee schemas in test/sandbox, and dashboard reports covering transactions, disputes, and fees — which supports setting a sell rate and viewing cost data. However there is no explicit documentation of a 'buy rate' contract from Finix itself or interchange-level cost breakdowns for spread management. Missing for 10: documented buy rate/cost-plus pricing terms, interchange-level line-item visibility, and independent confirmation of spread transparency.

   • [claimed-docs] “Finix allows you to easily monetize your payments. We offer out of the box customizability, efficiency, and revenue growth tools.”
   • [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
   • [claimed-docs] “Some of the fee customizations available are: International charges, Transaction volume discounts, Applying fees per payment method, Acceler…”
   • [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   The evidence pack covers platform payments features (onboarding, payouts, splits, fraud, MCP server) but contains no mention of data residency, regional data storage options, or configurable geographic data controls.

   ⚑ flag

   Finix—none0/10

   No evidence anywhere in the pack of data residency/region selection controls, storage location options, or compliance-region certifications; Finix's documentation is entirely about payments/payouts/onboarding functionality with no mention of data residency choices.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   The evidence pack covers payment platform features (onboarding, payouts, splits, fraud, reporting, MCP server) but contains no mention of data retention policies, deletion controls, or privacy/data-lifecycle management for AI-native users.

   ⚑ flag

   Finix—none0/10

   No evidence pack items address data retention policies, deletion controls, or privacy/data lifecycle management for Finix; docs focus entirely on payments, payouts, onboarding, and disputes.

   ⚑ flag

Global coverage

1. founderSellers can join from where they are — supported onboarding countries, local payment methods, and local-currency settlement documented as a coverage map, not discovered ticket by ticket

   weight 2 · round drawn
   Adyen for Platforms—none0/10

   Evidence only shows generic marketing claims like 'onboard global sellers with one integration' (docs-19) and generic onboarding/legal-entity API docs, but no documented coverage map listing supported onboarding countries, local payment methods, or local-currency settlement per market — the exact ticket-by-ticket problem the story flags. Missing for 10: a published country/payment-method/currency coverage map or matrix, evidence of self-serve discovery of local rails per country.

   • [claimed-docs] “Onboard global sellers with one integration while Adyen handles verification and payouts.”
   • [claimed-docs] “Build your own UI and collect required user data. You make API requests to create resources and submit the user data to Adyen.”
   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”

   proof ↗⚑ flag

   Finix—none0/10

   Evidence covers merchant onboarding mechanics (forms, APIs) but there is no documented coverage map of supported onboarding countries, local payment methods, or local-currency settlement — nothing resembling a country/currency/payment-method matrix appears anywhere in the pack.

   ⚑ flag

Onboarding api

1. developerOnboard a seller through the API — KYB and KYC, bank account linking, and terms acceptance — with hosted flows and embeddable components when I don't want to build the forms

   weight 3 · round to Adyen for Platforms
   Adyen for Platforms✓fullclaimed8/10

   Docs explicitly cover both API-driven onboarding (build your own UI, submit user data via API) and hosted onboarding pages managed by Adyen, plus Legal Entity Management API for KYB/KYC and balance account/bank linking. Terms acceptance and hosted flow are directly referenced in onboard-users.md and platforms.md. missing for 10: no explicit mention of embeddable/drop-in onboarding components (only 'build your own UI' vs 'hosted page'), and no independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “onboard sellers, service providers, or contractors on to your platform, and let Adyen verify them before paying out”
   • [claimed-docs] “Build your own UI and collect required user data. You make API requests to create resources and submit the user data to Adyen.”
   • [claimed-docs] “Direct your users to a page hosted by Adyen, where Adyen manages the onboarding flow and user interface (UI).”
   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”
   • [claimed-docs] “You can create balance accounts manually using the Configuration API.”
   • [claimed-docs] “Onboard global sellers with one integration while Adyen handles verification and payouts.”

   proof ↗⚑ flag

   Finix~partialclaimed6/10

   Finix docs clearly describe API-based seller onboarding (finix-docs-6, finix-docs-9, finix-docs-10) and hosted 'Onboarding Forms' to save developers from building UI (finix-docs-5), plus general merchant onboarding guidance (finix-docs-4). However, the evidence pack never explicitly details KYC/KYB data collection, bank account linking, or terms-of-service acceptance steps, nor confirms an embeddable (non-hosted-redirect) component distinct from the hosted forms. Missing for 10: explicit KYC/KYB field documentation, bank-account-linking flow details, terms-acceptance step, and confirmation of embeddable UI components (vs. only hosted forms).

   • [claimed-docs] “If you are a platform, you can quickly onboard merchants to Finix.”
   • [claimed-docs] “Save time onboarding sellers by using our Onboarding Forms.”
   • [claimed-docs] “Learn how to onboard your sellers with Finix's APIs.”
   • [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
   • [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”

   proof ↗⚑ flag

Progressive requirements

1. ops userOnboarding friction is tunable — collect the minimum to start selling and gather the rest before payout thresholds, with clear requirements-due states per seller

   weight 2 · round to Finix
   Adyen for Platforms~partialclaimed4/10

   Adyen for Platforms clearly supports onboarding via API or hosted UI and states verification happens 'before paying out' (docs-1, docs-6, docs-7), implying some ability to sell before full KYC is complete, and Legal Entity Management API (docs-8) suggests granular data collection. However there is no explicit documentation of configurable onboarding thresholds, a 'requirements-due' status per seller, or tunable minimum-data-to-start-selling flows. Missing for 10: explicit docs on per-seller requirement/due states, configurable minimum-onboarding-to-payout thresholds, and any hands-on/independent confirmation of this tunability.

   • [claimed-docs] “onboard sellers, service providers, or contractors on to your platform, and let Adyen verify them before paying out”
   • [claimed-docs] “Build your own UI and collect required user data. You make API requests to create resources and submit the user data to Adyen.”
   • [claimed-docs] “Direct your users to a page hosted by Adyen, where Adyen manages the onboarding flow and user interface (UI).”
   • [claimed-docs] “To manage legal entities, use the Legal Entity Management API.”

   proof ↗⚑ flag

   Finix~partialclaimed5/10

   Finix docs show onboarding forms and APIs for onboarding sellers, plus dashboard/API controls for seller payouts, implying some flexibility in what's collected before payout, but there's no explicit documentation of a tunable 'minimum to start selling then collect more before payout thresholds' workflow or explicit per-seller requirements-due states. missing for 10: explicit documentation of configurable onboarding requirement tiers, requirements-due state tracking per seller, and evidence of payout-threshold gating tied to progressive data collection.

   • [claimed-docs] “Save time onboarding sellers by using our Onboarding Forms.”
   • [claimed-docs] “Learn how to onboard your sellers with Finix's APIs.”
   • [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
   • [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
   • [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”

   proof ↗⚑ flag