Stripe Connect vs Adyen for Platforms

Agent access

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

   weight 2 · round to Adyen for Platforms
   Stripe Connect✓fullprobed8/10

   Evidence confirms an llms.txt file is live at docs.stripe.com/llms.txt (HTTP 200) alongside markdown-formatted docs pages (e.g., connect.md) accessible for agent consumption, directly enabling an agent to be pointed at agent-oriented docs. Missing for 10: no explicit documentation describing llms.txt's intended use/structure for agents, and no independent third-party confirmation of agent usage beyond the probe.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/connect.md # Platforms and marketplaces with Stripe Connect Build a SaaS platform or mar…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Stripe Connect
   Stripe Connect~partialprobed6/10

   Stripe Connect is fundamentally API-driven (API onboarding, webhooks, testing docs) and ships an official CLI, both of which support headless/CI automation, but there is no explicit documentation or example of running it in a CI pipeline or scripted automation context. missing for 10: explicit CI/CD examples, automation-focused docs, independent evidence of CI usage.

   • [claimed-docs] “API onboarding: You use the Stripe API to build your own customized onboarding UI.”
   • [claimed-docs] “Before going live, test your Connect integration for account creation, identity verification, and payouts.”
   • [claimed-docs] “All Connect integrations should establish a webhook endpoint to listen for Connect events.”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Stripe Connect
   Stripe Connect✓fullprobed7/10

   Stripe documents an official MCP server at docs.stripe.com/mcp, confirming agents can connect via a first-party MCP endpoint; Stripe is a payments platform (not itself an agent), so the axis applies and is satisfied. Missing for 10: no detail on Connect-specific MCP tool coverage, no independent/hands-on corroboration of the MCP server working with Connect operations.

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

   proof ↗⚑ flag

   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

4. ai-native userUse an official CLI

   weight 2 · round to Stripe Connect
   Stripe Connect✓fullprobed7/10

   Stripe documents an official CLI (stripe-cli) that supports platform-wide API workflows including Connect, giving AI-native users a scriptable interface. missing for 10: no direct evidence the CLI has AI-native/agentic features (e.g., natural-language mode) or independent hands-on validation of CLI usage specifically for Connect workflows.

   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Stripe Connect✓fullprobed8/10

   Stripe Connect is fully driven through Stripe's documented public REST API (account creation, onboarding, charges, payouts, balances, webhooks) per docs, and probes confirm an official CLI and MCP server exist for programmatic/agentic access. missing for 10: no direct OpenAPI spec discovery (probe found 404s on standard OpenAPI paths) and no independent hands-on validation of AI-agent-driven API usage specifically.

   • [claimed-docs] “API onboarding: You use the Stripe API to build your own customized onboarding UI.”
   • [claimed-docs] “All Connect integrations should establish a webhook endpoint to listen for Connect events.”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   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

6. ai-native userBuild against official SDKs

   weight 2 · round to Stripe Connect
   Stripe Connect~partialprobed6/10

   Evidence shows Stripe Connect exposes a full API (docs-5, docs-6) and references official package distribution via npm (probe-1), plus AI-friendly docs (llms.txt) and an official MCP server/CLI (probe-4, probe-5), all of which support AI-native SDK-based development. However, the pack never explicitly documents a dedicated 'Official SDKs' page or lists supported languages, so the SDK claim is inferred rather than directly evidenced. missing for 10: explicit official SDK/library documentation page, multi-language SDK examples, independent developer confirmation of SDK usage for Connect specifically.

   • [claimed-docs] “API onboarding: You use the Stripe API to build your own customized onboarding UI.”
   • [claimed-docs] “Create a charge and split payments between your platform and your sellers or service providers.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   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

7. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Stripe Connect✓fullcommunity7/10

   Stripe Connect has documented webhook support explicitly for Connect events ('All Connect integrations should establish a webhook endpoint to listen for Connect events'), and community evidence confirms real-world usage ('The webhooks are great'). This covers the core subscribe-to-events capability. Missing for 10: explicit documentation of event types/payload schema in this pack, agentic/AI-native framing of webhook consumption, and independent verification of reliability at scale.

   • [claimed-docs] “All Connect integrations should establish a webhook endpoint to listen for Connect events.”
   • [community] “'I implemented stripe connect on donat.io and it is awesome! The webhooks are great and the oauth flow is super simple too.'”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round drawn
   Stripe Connect~partialprobed4/10

   Stripe Connect supports background, event-driven automation via scheduled automatic payouts and webhooks for Connect events, and an official MCP server exists for AI agent integration, but there is no documentation of end-users setting up autonomous AI-driven automations or agent workflows built on Connect. missing for 10: explicit AI-agent automation setup, orchestration/scheduling controls beyond payouts, evidence of autonomous background AI workflows using Connect.

   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “All Connect integrations should establish a webhook endpoint to listen for Connect events.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Stripe Connect~partialprobed5/10

   Stripe documents an official MCP server (docs.stripe.com/mcp) which would let AI agents interact with Stripe Connect via natural-language-driven tool calls, and also has an official CLI, but the evidence pack gives no detail on what Connect-specific actions are exposed via MCP or any hands-on confirmation of natural-language operation. missing for 10: details on MCP tool coverage for Connect operations, independent/hands-on validation of natural-language control, and confirmation beyond a bare 'documented at URL' probe.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Stripe Connect—none0/10

   The evidence pack contains only docs.stripe.com guide pages, an llms.txt probe, CLI/MCP mentions, and a failed openapi.json probe (404 on all candidate paths) — nothing documents an interactive API reference page or runnable/try-it code examples for Connect. Since this is a fair expectation for an API-first product, absence of evidence yields 'none' rather than 'na'.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/connect.md # Platforms and marketplaces with Stripe Connect Build a SaaS platform or mar…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Stripe Connect—none0/10

   The evidence pack shows a direct probe for OpenAPI/swagger spec files at all standard locations returning 404, and no other evidence item shows a downloadable machine-readable API spec (only markdown docs, an MCP server, and CLI are documented).

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

   proof ↗⚑ flag

   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

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

   weight 1 · round to Adyen for Platforms
   Stripe Connect~partialclaimed6/10

   Docs explicitly cover testing the Connect integration (account creation, identity verification, payouts) before going live, implying a sandbox/test-mode workflow, but there's no explicit description of a dedicated 'sandbox environment' distinct from production, no mention of test API keys/test clocks, or how AI agents would interact with it. missing for 10: explicit sandbox/test-mode documentation separate from production, test data isolation details, and independent/hands-on confirmation of sandbox usage.

   • [claimed-docs] “Before going live, test your Connect integration for account creation, identity verification, and payouts.”
   • [claimed-docs] “All Connect integrations should establish a webhook endpoint to listen for Connect events.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Stripe Connect—none0/10

   The evidence pack contains no mention of API versioning, version headers, or a documented deprecation policy for Stripe Connect's APIs; all citations describe product features (onboarding, payouts, disputes, etc.) rather than API lifecycle/versioning practices. Missing for 10: any documentation of API version pinning, deprecation notices, changelog, or migration guides.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Stripe Connect—none0/10

   Stripe Connect exposes per-resource APIs (accounts, payouts, balances) but nothing in the evidence pack describes bulk/batch operations across many connected accounts or transactions at once (e.g., batch create, bulk payout, multi-object update endpoints). Missing for 10: documented bulk/batch API endpoints, evidence of batch job or async bulk-processing tooling, and any AI-native automation examples operating on many items simultaneously.

   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”
   • [claimed-docs] “Manage connected accounts with the Dashboard: Review and take action on your connected accounts.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Stripe Connect~partialclaimed5/10

   Stripe Connect supports event-driven automation via webhooks (e.g. listening for account, payout, dispute events) and built-in automatic/scheduled payouts, but these require the platform to write custom webhook handlers rather than a declarative 'if-this-then-that' rules engine; the only no-code rule configuration mentioned is for pricing strategies, not general event-action automation. Missing for 10: a documented no-code/rules-based automation builder for arbitrary event-to-action mappings, and evidence of AI-native rule definition tooling.

   • [claimed-docs] “All Connect integrations should establish a webhook endpoint to listen for Connect events.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “Connect platforms and marketplaces can allow their connected accounts to access their balances immediately following a successful charge.”
   • [claimed-docs] “platforms can implement a range of pricing strategies for different payment processing use-cases, without the need to write any code”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Adyen for Platforms
   Stripe Connect—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

   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

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
   Stripe Connect~partialclaimed6/10

   Stripe Connect exposes APIs for connected-account balances, payout scheduling/management, and transaction data (docs-7, docs-13, docs-18), and documents an embeddable onboarding component that lives inside the platform's own app (docs-4), supporting the general idea of white-labeled seller surfaces. However, the evidence pack only shows an embedded UI component for onboarding, not for balances, payouts, or transaction history themselves — those are described as raw APIs the developer must build UI around, not turnkey embeddable components. missing for 10: explicit documentation of embeddable balance/payout/transaction-history components (vs. only onboarding), and independent confirmation these render fully white-labeled inside a host app.

   • [claimed-docs] “You embed the Account onboarding component directly in your application and your connected accounts go through the onboarding flow without l…”
   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [claimed-docs] “Manage connected accounts with the Dashboard: Review and take action on your connected accounts.”

   proof ↗⚑ flag

   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

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
   Stripe Connect—none0/10

   The evidence pack covers Connect's online payment splitting, onboarding, payouts, identity verification, and dashboard features, but contains no mention of Stripe Terminal, in-person/tap-to-pay hardware or SDKs, or how such in-person payments would settle into the same connected-account balances/reporting as online charges. This is an applicable axis for a payments platform (Stripe does offer Terminal separately), so absence of evidence here yields 'none' rather than 'na'.

   ⚑ flag

   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

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 to Adyen for Platforms
   Stripe Connect—none0/10

   The evidence only shows platform-level Dashboard management, balance API calls, and payout scheduling for connected accounts — all requiring developer/ops involvement, not self-serve seller statements, reconciliation reports, or bookkeeper-ready exports. No mention of an Express-style seller dashboard, downloadable statements, or export tooling that would let sellers or their bookkeepers close the books without contacting the platform ops team. Missing for 10: seller-facing statement/export UI, reconciliation report generation, bookkeeper self-serve documentation.

   • [claimed-docs] “Manage connected accounts with the Dashboard: Review and take action on your connected accounts.”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “You can view all disputes filed against your platform and connected accounts in your Dashboard.”

   proof ↗⚑ flag

   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

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
   Stripe Connect~partialcommunity5/10

   Stripe Connect docs confirm the underlying primitives needed for escrow-like fund holding — connected-account balances can be checked via API (docs-18), payout timing can be scheduled or set to manual (docs-13), and dispute visibility exists in the Dashboard (docs-17) — meaning a developer can technically hold funds until a trigger and then release a payout on demand. However, there is no dedicated 'escrow' feature or documentation describing dispute-window-specific holds, delivery-triggered releases, or the compliance limits of doing so; a community thread even raises unresolved compliance concerns about using transfer holds to delay payouts (stripe-connect-comm-13), which is a caveat rather than a proven failure. missing for 10: explicit escrow/hold-until-trigger documentation, dispute-window-specific release mechanics, and clarified compliance limits for manually delaying payouts.

   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [claimed-docs] “You can view all disputes filed against your platform and connected accounts in your Dashboard.”
   • [claimed-docs] “Connect platforms and marketplaces can allow their connected accounts to access their balances immediately following a successful charge.”
   • [community] “Compliance concern raised: using a 'Special Case Transfer' to let money sit before payout 'seems non-compliant', asking when charges could a…”

   proof ↗⚑ flag

   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

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
   Stripe Connect—none0/10

   The evidence pack shows Connect supports viewing disputes (docs-17) and checking connected-account balances (docs-18), but nothing documents automatic debiting of future earnings or a connected account's bank account to cover refunds/chargebacks that exceed balance, nor any documented liability ordering. missing for 10: negative balance recovery/debit mechanics, bank-account debit fallback, documented liability order between platform and seller.

   • [claimed-docs] “You can view all disputes filed against your platform and connected accounts in your Dashboard.”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”

   proof ↗⚑ flag

   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

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 drawn
   Stripe Connect~partialclaimed7/10

   Docs clearly show charges can be split between platform and connected accounts as first-class API objects (docs-6, docs-7), with balances and payouts manageable per account (docs-18, docs-13). However, the evidence pack lacks explicit documentation of reversing or adjusting a split after the fact (e.g., reversing transfers or partial refunds tied to application fees), only touching disputes generally (docs-17). missing for 10: explicit reversal/adjustment API documentation, independent hands-on confirmation of split modification.

   • [claimed-docs] “Create a charge and split payments between your platform and your sellers or service providers.”
   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “You can view all disputes filed against your platform and connected accounts in your Dashboard.”

   proof ↗⚑ flag

   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

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
   Stripe Connect~partialclaimed5/10

   Docs confirm disputes are tracked per connected account and viewable in the Dashboard for both platform and connected accounts, supporting the 'right sub-merchant' targeting (stripe-connect-docs-17), and connected-account balance retrieval exists (stripe-connect-docs-18). However, the evidence pack lacks explicit documentation of submitting dispute evidence via API/dashboard for connected accounts or confirmation that dispute outcomes automatically adjust seller balances. missing for 10: dedicated evidence-submission API/dashboard flow for connected-account disputes, and explicit description of automatic balance reconciliation post-dispute-resolution.

   • [claimed-docs] “You can view all disputes filed against your platform and connected accounts in your Dashboard.”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”

   proof ↗⚑ flag

   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

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
   Stripe Connect~partialclaimed4/10

   Docs confirm identity verification for risk reduction, a Dashboard to review/manage connected accounts and take action, and visibility into disputes across the platform — core building blocks for portfolio risk oversight. However there is no evidence of per-seller fraud/credit-risk scoring, automated anomaly alerts, or explicit payout-pause/offboarding workflows for bad actors. missing for 10: per-merchant fraud/credit-risk scoring, anomalous-seller alerting, explicit pause-payout/offboard tooling, independent evidence these risk tools work in practice.

   • [claimed-docs] “Use identity verification to reduce risk on your platform when using Connect.”
   • [claimed-docs] “You can view all disputes filed against your platform and connected accounts in your Dashboard.”
   • [claimed-docs] “Manage connected accounts with the Dashboard: Review and take action on your connected accounts.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”

   proof ↗⚑ flag

   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

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
   Stripe Connect~partialcommunity3/10

   Docs confirm platforms can pay out to connected accounts, schedule payouts, and check connected-account balances, and one community comment praises Stripe Connect for enabling international marketplace payouts, but the pack contains no explicit documentation of local-currency payout rails, FX conversion mechanics, or settlement to local bank rails versus wires. An older community complaint even flags lack of international support as a pain point. missing for 10: dedicated docs on multi-currency payouts, FX conversion/fee transparency, and local bank-rail settlement for connected accounts.

   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [community] “Frustration over lack of international support: 'I love Stripe. Really I do. But until I can accept users from around the world, it seems pr…”
   • [community] “'current balanced customer who is soon to be a stripe convert. very thrilled about this and being able to payout internationally as a market…”

   proof ↗⚑ flag

   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

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 Stripe Connect
   Stripe Connect✓fullclaimed8/10

   Docs explicitly cover configurable automatic payout scheduling per connected account (daily/weekly/monthly/manual) and instant payouts to cards/real-time rails where supported, matching the story's core requirements. Missing for 10: no explicit confirmation that schedule can be set independently per-seller at scale with concrete examples, and no independent/hands-on corroboration of the scheduling flexibility beyond docs.

   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “Connect platforms and marketplaces can allow their connected accounts to access their balances immediately following a successful charge.”
   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Stripe Connect
   Stripe Connect~partialprobed7/10

   Docs show Stripe Connect exposes nearly all platform operations (account creation, onboarding, charges, payouts, treasury, cards, balances, webhooks) via API, including an explicit 'API onboarding' path as an alternative to the embedded UI component (stripe-connect-docs-5), and CLI/MCP tooling further extend programmatic control (stripe-connect-probe-4, stripe-connect-probe-5). However, some capabilities like dispute review, account management, and no-code pricing tools are documented as Dashboard-centric (stripe-connect-docs-9, stripe-connect-docs-17, stripe-connect-docs-8) without explicit confirmation that every such action has a full API equivalent. Missing for 10: explicit documentation confirming 1:1 API parity for dispute resolution/dashboard review actions, and independent/hands-on confirmation that no UI-only feature exists.

   • [claimed-docs] “API onboarding: You use the Stripe API to build your own customized onboarding UI.”
   • [claimed-docs] “Manage connected accounts with the Dashboard: Review and take action on your connected accounts.”
   • [claimed-docs] “You can view all disputes filed against your platform and connected accounts in your Dashboard.”
   • [claimed-docs] “platforms can implement a range of pricing strategies for different payment processing use-cases, without the need to write any code”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   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

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 drawn
   Stripe Connect~partialclaimed4/10

   Docs show Connect offers a spectrum of control—managed onboarding vs. custom API onboarding, unified identity with multiple account configurations (merchant/customer), and platform-level control over payouts, pricing, and balances—implying a platform can grow from a lighter-touch managed setup toward more direct control without switching providers. However, there is no explicit documentation of a formal path to registered payment-facilitator (PayFac) status, its licensing/economics implications, or how liability shifts as a platform matures. missing for 10: explicit PayFac registration/graduation path, documentation on liability shift and licensing requirements, case studies of platforms moving from managed to PayFac model without replatforming.

   • [claimed-docs] “Create a unified identity to represent each of your platform's connected accounts with one or more configurations, such as merchant or custo…”
   • [claimed-docs] “You embed the Account onboarding component directly in your application and your connected accounts go through the onboarding flow without l…”
   • [claimed-docs] “API onboarding: You use the Stripe API to build your own customized onboarding UI.”
   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”
   • [claimed-docs] “Manage connected accounts with the Dashboard: Review and take action on your connected accounts.”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”

   proof ↗⚑ flag

   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

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
   Stripe Connect—none0/10

   The docs describe operational features (identity verification, dispute dashboards, payouts) but none explicitly lay out a responsibility matrix for who owns KYC/AML, card-network compliance, fraud losses, or seller misconduct — that allocation is left implicit or pushed to the underlying account agreement. Community evidence even shows a user unsure whether a specific payout pattern is compliant, underscoring the lack of a documented liability split.

   • [claimed-docs] “Use identity verification to reduce risk on your platform when using Connect.”
   • [claimed-docs] “You can view all disputes filed against your platform and connected accounts in your Dashboard.”
   • [community] “Compliance concern raised: using a 'Special Case Transfer' to let money sit before payout 'seems non-compliant', asking when charges could a…”

   proof ↗⚑ flag

   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

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
   Stripe Connect—none0/10

   The evidence pack covers onboarding, payments, payouts, disputes, identity verification, and treasury, but contains no mention of 1099-K tracking, tax form generation/delivery/filing, or a documented data corrections workflow for tax reporting.

   ⚑ flag

   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

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 to Stripe Connect
   Stripe Connect~partialprobed7/10

   Stripe publishes concrete API-level surfaces an agent could use: retrieving a connected account's balance (stripe-connect-docs-18), managing/scheduling payouts (stripe-connect-docs-7, docs-13), viewing disputes (stripe-connect-docs-17), webhooks for investigating events (stripe-connect-docs-15), plus an official MCP server (stripe-connect-probe-4) and CLI (stripe-connect-probe-5) that give agents a documented, tool-callable interface rather than just human docs. However, the evidence only shows dispute *viewing* in the Dashboard, not an API/MCP-exposed workflow for drafting/submitting dispute evidence, and there's no hands-on proof of an agent actually chaining balance+payout+dispute calls to 'investigate a missing payout.' Missing for 10: documented dispute-evidence submission surface usable by an agent, and independent/hands-on evidence of an agent performing the described investigate-and-draft workflow via MCP/API.

   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “You can view all disputes filed against your platform and connected accounts in your Dashboard.”
   • [claimed-docs] “All Connect integrations should establish a webhook endpoint to listen for Connect events.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   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

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 drawn
   Stripe Connect~partialprobed5/10

   Stripe Connect exposes full API surface for creating connected accounts, driving onboarding (embedded or API-based), and checking requirements via identity verification (docs-4, docs-5, docs-16), and Stripe documents an official MCP server (probe-4). However, there's no evidence the MCP server specifically exposes Connect account-creation/onboarding/requirements-due operations, nor any documentation of scoped credentials for agent-driven seller operations. Missing for 10: MCP tool list showing Connect account management functions, explicit scoped-credential/permission model for agents, and evidence of agents actually completing onboarding or resolving requirements-due states end-to-end.

   • [claimed-docs] “You embed the Account onboarding component directly in your application and your connected accounts go through the onboarding flow without l…”
   • [claimed-docs] “API onboarding: You use the Stripe API to build your own customized onboarding UI.”
   • [claimed-docs] “Use identity verification to reduce risk on your platform when using Connect.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   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

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
   Stripe Connect—none0/10

   Evidence covers standard Connect marketplace/split-payment functionality (charges, payouts, onboarding, balances) but contains no mention of agent-initiated checkout, agentic-commerce protocols, or delegated payment credentials for AI agent buyers. Missing for 10: any documentation of agent/AI buyer checkout support, delegated payment credential mechanisms, or agentic-commerce protocol integration with split funds.

   ⚑ flag

   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

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 drawn
   Stripe Connect~partialcommunity4/10

   Docs show connected-account balance visibility, payout scheduling/instant payouts, and Treasury for holding funds and cash-back, giving a finance lead partial insight into where funds sit and payout timing. However there is no explicit documentation on how platform funds are legally segregated from Stripe's own accounts, nor clear policy on whether held balances earn yield/interest, and a community thread raises unresolved compliance questions about funds sitting via 'Special Case Transfer' before payout. missing for 10: explicit fund-segregation/custody disclosures, yield/interest policy on held balances, clear compliance answer to the raised concern.

   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [claimed-docs] “Embed Treasury in your platform to allow your customers to hold funds, pay bills, earn cash back, and manage cashflow.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “Connect platforms and marketplaces can allow their connected accounts to access their balances immediately following a successful charge.”
   • [community] “Compliance concern raised: using a 'Special Case Transfer' to let money sit before payout 'seems non-compliant', asking when charges could a…”

   proof ↗⚑ flag

   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

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 to Stripe Connect
   Stripe Connect~partialcommunity7/10

   Docs show core building blocks for ledger legibility: per-connected-account balance retrieval, charge splitting between platform and sellers, payout scheduling/management, and webhook events for tracking money movement, plus dispute visibility. However there's no explicit evidence of a dedicated reconciliation/reporting API or penny-level ledger export, and community threads flag real confusion over fee 'double dipping' and payout timing/compliance that complicate exact traceability. missing for 10: explicit reconciliation/reporting tooling (e.g. balance transaction reports), documented penny-accurate audit trail from charge→split→payout, and independent confirmation that finance teams can fully reconcile without extra tooling.

   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [claimed-docs] “Create a charge and split payments between your platform and your sellers or service providers.”
   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “All Connect integrations should establish a webhook endpoint to listen for Connect events.”
   • [claimed-docs] “You can view all disputes filed against your platform and connected accounts in your Dashboard.”
   • [community] “User confusion over fee structure: 'If Stripe is charging 0.5% of funds paid out to managed accounts, does this mean you're "double dipping"…”
   • [community] “Compliance concern raised: using a 'Special Case Transfer' to let money sit before payout 'seems non-compliant', asking when charges could a…”

   proof ↗⚑ flag

   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

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
   Stripe Connect~partialclaimed4/10

   Docs show balance-per-account retrieval and payout scheduling APIs, which are building blocks for reconciliation, but there is no evidence of a dedicated reconciliation/reporting API, scheduled file exports, or rolled-up settlement reports designed for finance-stack consumption. Missing for 10: dedicated reporting/reconciliation API (e.g. Sigma or Reporting API), scheduled file delivery mechanism, explicit rolled-up multi-seller settlement report format, and any first-party or community evidence of automated reconciliation workflows.

   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [claimed-docs] “Schedule the frequency of automatic payouts”
   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”
   • [claimed-docs] “Manage connected accounts with the Dashboard: Review and take action on your connected accounts.”

   proof ↗⚑ flag

   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

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 drawn
   Stripe Connect~partialcommunity6/10

   Docs confirm the core mechanics of platform monetization: splitting charges to add an application fee (stripe-connect-docs-6), no-code pricing strategy tools for different sellers/use-cases (stripe-connect-docs-8), and balance/payout management per connected account (stripe-connect-docs-7, stripe-connect-docs-18). However, there is no explicit documentation of a dashboard or reporting view that separates platform application-fee revenue from Stripe's own processing costs, and community threads show real confusion over fee structure ('double dipping') rather than confirmation of clean revenue/cost separation. Missing for 10: explicit reporting/dashboard feature that isolates platform revenue vs. processing fees, and clearer documentation of per-seller custom pricing configuration beyond a general pricing-tools mention.

   • [claimed-docs] “Create a charge and split payments between your platform and your sellers or service providers.”
   • [claimed-docs] “platforms can implement a range of pricing strategies for different payment processing use-cases, without the need to write any code”
   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [community] “User confusion over fee structure: 'If Stripe is charging 0.5% of funds paid out to managed accounts, does this mean you're "double dipping"…”

   proof ↗⚑ flag

   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

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 drawn
   Stripe Connect~partialcommunity4/10

   Stripe Connect lets platforms split payments and set application/sell-side fees via 'platform pricing tools' and charge splitting, and Stripe's own processing rate is publicly documented, giving a documented buy rate and sell-rate freedom. However there is no evidence of interchange-level cost visibility or granular spread management — a community thread even shows confusion over Stripe's fee structure ('double dipping') rather than clear line-item interchange transparency. Missing for 10: interchange-level fee breakdown/reporting, documented spread/cost visibility tools, and evidence resolving the community confusion about fee stacking.

   • [claimed-docs] “Create a charge and split payments between your platform and your sellers or service providers.”
   • [claimed-docs] “platforms can implement a range of pricing strategies for different payment processing use-cases, without the need to write any code”
   • [claimed-docs] “To check the balance of a connected account, perform a retrieve balance call authenticated as the connected account.”
   • [community] “User confusion over fee structure: 'If Stripe is charging 0.5% of funds paid out to managed accounts, does this mean you're "double dipping"…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Stripe Connect—none0/10

   No evidence in the pack mentions data residency, regional data storage, or configurable data location for Stripe Connect; the axis applies (payments platforms commonly address data residency for compliance) but no supporting documentation is present.

   ⚑ flag

   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

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
   Stripe Connect—none0/10

   The evidence pack shows generic onboarding, identity-verification, and payout docs, but none of the citations reference a consolidated coverage map of supported onboarding countries, local payment methods, or local-currency settlement. In fact, community evidence points the other way: complaints about lack of international support and confusion between a blog post claiming broad country support and docs limiting it to US/Canada (comm-8, comm-10), suggesting coverage info is scattered rather than a single documented map. missing for 10: an explicit supported-countries list, a local-payment-methods matrix, and a local-currency settlement reference, plus confirmation these are unified rather than discovered piecemeal.

   • [community] “Frustration over lack of international support: 'I love Stripe. Really I do. But until I can accept users from around the world, it seems pr…”
   • [community] “Bug report: broken docs link for managed accounts showing 'An unexpected error occurred', and confusion between blog post saying managed acc…”

   proof ↗⚑ flag

   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

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 drawn
   Stripe Connect✓fullcommunity8/10

   Docs explicitly describe both hosted onboarding (embeddable Account onboarding component) and full API onboarding for custom UIs, plus identity verification, bank account/external account linking, and payouts — covering KYC/KYB and bank linking needs without building forms. Community quotes (OAuth flow, webhooks) corroborate ease of onboarding, though some complaints about seller-facing friction and international limits reflect UX rather than capability gaps. Missing for 10: explicit mention of terms-of-service acceptance step in onboarding flow and more recent independent hands-on validation of the embedded components.

   • [claimed-docs] “You embed the Account onboarding component directly in your application and your connected accounts go through the onboarding flow without l…”
   • [claimed-docs] “API onboarding: You use the Stripe API to build your own customized onboarding UI.”
   • [claimed-docs] “Use identity verification to reduce risk on your platform when using Connect.”
   • [claimed-docs] “Pay out to connected accounts: Manage payouts and external accounts for your connected accounts.”
   • [community] “'We've been using this for awhile for Zenbox... The implementation was straightforward, and it instantly made Stripe the easiest integration…”
   • [community] “'I implemented stripe connect on donat.io and it is awesome! The webhooks are great and the oauth flow is super simple too.'”

   proof ↗⚑ flag

   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

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 Stripe Connect
   Stripe Connect~partialclaimed5/10

   Docs confirm flexible onboarding (embedded component or custom API-driven UI) and identity verification to reduce risk, which implies staged data collection, but no evidence explicitly describes tunable minimum-to-start thresholds or discrete 'requirements-due' states per seller. Missing for 10: explicit documentation of progressive/staggered requirement collection tied to payout thresholds, and clear surfacing of per-seller requirements-due status in the dashboard or API.

   • [claimed-docs] “You embed the Account onboarding component directly in your application and your connected accounts go through the onboarding flow without l…”
   • [claimed-docs] “API onboarding: You use the Stripe API to build your own customized onboarding UI.”
   • [claimed-docs] “Use identity verification to reduce risk on your platform when using Connect.”
   • [claimed-docs] “Manage connected accounts with the Dashboard: Review and take action on your connected accounts.”

   proof ↗⚑ flag

   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