Marketplace & Platform Payments Arena
Adyen for Platforms vs Rainforest
Adyen for Platforms
Adyen N.V.
Adyen for Platforms wins · 24–2 (15 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to Adyen for PlatformsA 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”
A probe confirms a live llms.txt file at docs.rainforestpay.com/llms.txt (HTTP 200) that explicitly documents the docs and notes pages can be fetched as .md, and multiple doc pages are indeed available with .md suffixes as referenced elsewhere in the pack. Missing for 10: no independent/third-party confirmation of agent usage with this llms.txt, and no evidence of a broader agent-oriented docs structure beyond the single llms.txt file.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.rainforestpay.com/llms.txt # Rainforest Docs Documentation > Documentation for Rainforest Docs Ap…”
- [claimed-docs] “Integrate Rainforest's low-code embeddable component into your platform, allowing me”
- [claimed-docs] “Create a merchant with an initial merchant application.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to Adyen for PlatformsAdyen 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”
Rainforestnone0/10Rainforest exposes REST APIs and webhooks, which theoretically could be scripted, but there is no evidence of a CLI, headless mode, or CI-integration tooling — the docs focus on merchant onboarding, payment components, and pricing, not automation/agentic workflows. missing for 10: CLI or SDK for automation, explicit CI/headless usage examples, any agent/automation-oriented tooling.
- [claimed-docs] “Create a merchant with an initial merchant application.”
- [claimed-docs] “You can subscribe to events for the following resources”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.rainforestpay.com/openapi.json, https://docs.rainforestpay.com/swagger.json, https://do…”
ai-native userConnect an agent via an official MCP server
weight 3 · round to Adyen for PlatformsAdyen 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/”
ai-native userUse an official CLI
weight 2 · round drawnAdyen for Platformsnone0/10Evidence 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.”
ai-native userDrive the product through a documented public API
weight 3 · round to Adyen for PlatformsAdyen 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…”
Rainforest ships an extensive documented REST API (create/update merchant, webhooks, deposits, amount splits) with a reference doc site and an llms.txt for machine-readable docs access, showing a genuine public API surface. However, a probe for standard machine-discoverable API specs (OpenAPI/Swagger) returned 404s across all candidate paths, meaning there's no verified formal schema for automated/agentic API consumption. Missing for 10: a discoverable OpenAPI/Swagger spec, SDK/client library evidence, and explicit agent-tooling integration guidance.
- [claimed-docs] “Create a merchant with an initial merchant application.”
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
- [claimed-docs] “You can subscribe to events for the following resources”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.rainforestpay.com/llms.txt # Rainforest Docs Documentation > Documentation for Rainforest Docs Ap…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.rainforestpay.com/openapi.json, https://docs.rainforestpay.com/swagger.json, https://do…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnAdyen for Platformsnone0/10No evidence in the pack addresses issuing scoped or least-privilege API credentials for an AI agent; the docs cover onboarding, payouts, fraud monitoring, webhooks, and an MCP server, but nothing about API key/credential scoping or permission granularity for agents.
ai-native userBuild against official SDKs
weight 2 · round drawnAdyen for Platformsnone0/10The 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.”
Rainforestnone0/10Evidence only shows REST API reference docs, webhooks, and embeddable components, with no mention of official client SDKs in any language; the OpenAPI probe even returned 404s for spec endpoints. Missing for 10: any documented SDK (e.g., Node/Python/Java client libraries), package registry listing, or SDK quickstart guide.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.rainforestpay.com/openapi.json, https://docs.rainforestpay.com/swagger.json, https://do…”
- [claimed-docs] “Create a merchant with an initial merchant application.”
- [claimed-docs] “Detailed guides and walkthroughs, full end-to-end sandbox testing, realtime API logs, and more.”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnAdyen 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”
Rainforest's docs explicitly describe a webhooks/notifications system where you can subscribe to events for a list of resources, directly matching the story. missing for 10: no independent/hands-on corroboration or details on payload signing/retry semantics beyond the doc listing.
- [claimed-docs] “You can subscribe to events for the following resources”
Agentic features
ai-native userSet up automations that run autonomously in the background
weight 2 · round to Adyen for PlatformsAdyen 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/”
ai-native userOperate the product with natural-language commands
weight 2 · round to Adyen for PlatformsAdyen 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/”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnAdyen for Platformsnone0/10The 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.
Rainforestnone0/10The evidence pack shows conventional API reference pages (e.g., create_merchant.md) and general docs, but nothing describes an interactive, runnable API console or live code execution; the OpenAPI/swagger probe returned 404s, suggesting no standard interactive spec is exposed. missing for 10: evidence of a 'try it' console, runnable code samples, or OpenAPI-based interactive explorer.
- [claimed-docs] “Create a merchant with an initial merchant application.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.rainforestpay.com/openapi.json, https://docs.rainforestpay.com/swagger.json, https://do…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnAdyen for Platformsnone0/10The 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.
Rainforestnone0/10Rainforest exposes a documentation site with reference pages for its API, but a direct probe for standard OpenAPI/Swagger spec locations (openapi.json, swagger.json, etc.) returned 404 across all candidates, and no other evidence shows a downloadable machine-readable spec (only an llms.txt for markdown docs).
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.rainforestpay.com/openapi.json, https://docs.rainforestpay.com/swagger.json, https://do…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.rainforestpay.com/llms.txt # Rainforest Docs Documentation > Documentation for Rainforest Docs Ap…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnDocs 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”
Rainforest explicitly documents a sandbox environment for testing payments with dedicated test cards/accounts that don't touch production, plus 'full end-to-end sandbox testing' mentioned as a platform feature. Missing for 10: independent/hands-on corroboration of sandbox fidelity, and more detail on data isolation guarantees beyond card-decline behavior.
- [claimed-docs] “Any card number *not* included in any list below will result in a generic **Declined** payment in the sandbox environment.”
- [claimed-docs] “Detailed guides and walkthroughs, full end-to-end sandbox testing, realtime API logs, and more.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnAdyen for Platformsnone0/10No 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…”
Rainforestnone0/10No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probes returned 404s and docs only cover functional payment integration topics, not API lifecycle/versioning commitments.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.rainforestpay.com/openapi.json, https://docs.rainforestpay.com/swagger.json, https://do…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnAdyen for Platformsnone0/10Evidence 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.
Rainforestnone0/10Rainforest is a payments processing API/platform; evidence covers merchant onboarding, payments, deposits, webhooks, and pricing, but nothing describes bulk operations across many items (e.g., batch payment processing, bulk merchant creation, or batch API endpoints). No evidence of any bulk/batch capability.
- [claimed-docs] “Create a merchant with an initial merchant application.”
- [claimed-docs] “Process online payments”
- [claimed-docs] “You can subscribe to events for the following resources”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to Adyen for PlatformsAdyen 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”
Rainforest offers webhook subscriptions for resource events (e.g., merchant, payment status changes), which provides a basic event-trigger mechanism, but there is no documented rules engine or conditional 'if event X then action Y' automation layer for defining custom logic. missing for 10: rule/condition definition syntax, built-in action execution (not just external webhook delivery), examples of automated workflows triggered by rules.
- [claimed-docs] “You can subscribe to events for the following resources”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to Adyen for PlatformsAdyen 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.”
Embedded experience — stories about embedded experience in this arenaEmbedded experience
Stories about embedded experience in this arena
Embedded components
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 drawnAdyen 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”
Rainforest explicitly offers pre-built embeddable components for payments, reporting, chargebacks, and merchant onboarding, plus a 'payment component studio' for designing branded embedded components for platform integration, supporting white-labeled seller-facing surfaces like transaction/payment history [rainforest-docs-15, rainforest-docs-4, rainforest-docs-11]. However, deposits/payouts are only exposed via API endpoints (e.g., updating deposit frequency) with no explicit mention of a dedicated embeddable balances or payouts UI component, and no evidence of granular white-label branding controls beyond the component studio. Missing for 10: explicit embeddable balance/payout UI components, documented white-label branding/customization API for these surfaces, and independent/hands-on confirmation of branding flexibility.
- [claimed-docs] “Start processing payments in days, not months. Reduce development time and get to revenue faster with our pre-built, embeddable components f…”
- [claimed-docs] “Integrate Rainforest's low-code embeddable component into your platform, allowing me”
- [claimed-docs] “Head over to the [payment component studio] to start designing the embedded payment component for your platform integration.”
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
Omnichannel
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 RainforestThe 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”
Rainforest documents both online payments and 'Process payments with a device' (terminal-style in-person processing) under the same merchant/API model, implying shared merchant balances and reporting infrastructure (deposits, webhooks). However, there is no explicit documentation of a tap-to-pay SDK or an explicit statement confirming that in-person device payments settle into the exact same balance/reporting pipeline as online payments. missing for 10: explicit tap-to-pay SDK support, explicit confirmation that device/terminal payments unify with online payments in settlement and reporting, independent corroboration of in-person hardware integration.
- [claimed-docs] “Process payments with a device”
- [claimed-docs] “Process online payments”
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
- [claimed-docs] “You can subscribe to events for the following resources”
Seller reporting
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 PlatformsAdyen 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.”
Rainforest advertises a pre-built embeddable 'reporting' component alongside payments, chargebacks, and onboarding, implying some seller-facing financial visibility, but the docs pack contains no specifics on per-seller statements, payout reconciliation reports, or bookkeeper-ready exports. Missing for 10: documentation of statement generation, reconciliation report format/fields, and export capabilities (CSV/PDF) for bookkeepers.
- [claimed-docs] “Start processing payments in days, not months. Reduce development time and get to revenue faster with our pre-built, embeddable components f…”
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
Funds routing — stories about funds routing in this arenaFunds routing
Stories about funds routing in this arena
Holds release
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 PlatformsAdyen 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.”
Rainforestnone0/10The evidence covers payment processing, deposits/payout frequency, amount splits, and webhooks, but nothing describes holding seller funds in escrow until delivery or dispute windows pass, nor programmable release triggers or documented limits for such a mechanism — missing for 10: escrow/hold-funds primitive, delivery/dispute-window release logic, and documented limits on hold duration or amounts.
- [claimed-docs] “You can implement amount splits in three steps”
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
- [claimed-docs] “You can subscribe to events for the following resources”
Negative balances
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 PlatformsDocs 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”
Rainforestnone0/10The pack only shows a generic mention of a 'chargebacks' component (rainforest-docs-15) among Rainforest's embeddable features, but there is no documentation describing automatic debits against future earnings, bank account debits for negative balances, or a documented liability order for recovering losses. Missing for 10: any doc on negative-balance recovery mechanics, reserve/liability sequencing, or bank-account debit process.
- [claimed-docs] “Start processing payments in days, not months. Reduce development time and get to revenue faster with our pre-built, embeddable components f…”
Splits
developerSplit one charge among any set of parties — route funds to multiple sellers, take my cut, and reverse or adjust the split later, all as first-class API objects
weight 3 · round to Adyen for PlatformsDocs 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.”
Rainforest documents an 'amount splits' feature implemented via API steps (rainforest-docs-6), supporting the core idea of routing a charge across parties, but there is no evidence of split objects being adjustable or reversible after the fact, no detail on how many parties can be split among, and no confirmation these splits are exposed as standalone first-class API objects rather than a payment-creation parameter. Missing for 10: adjustable/reversible split objects, multi-party routing detail, explicit object model documentation, and independent corroboration.
- [claimed-docs] “You can implement amount splits in three steps”
Marketplace disputes — stories about marketplace disputes in this arenaMarketplace disputes
Stories about marketplace disputes in this arena
Dispute handling
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 PlatformsDocs 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”
Rainforest advertises a pre-built 'chargebacks' component alongside merchant onboarding and payments, implying dispute handling exists in a submerchant-based platform, but the evidence never details per-seller/sub-merchant dispute routing, API-based evidence submission, or automatic balance reconciliation of outcomes. missing for 10: documentation on chargeback-to-submerchant assignment, evidence submission API/dashboard specifics, and how dispute outcomes update seller balances.
- [claimed-docs] “Start processing payments in days, not months. Reduce development time and get to revenue faster with our pre-built, embeddable components f…”
Portfolio risk
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 PlatformsDocs 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”
Marketplace payouts — stories about marketplace payouts in this arenaMarketplace payouts
Stories about marketplace payouts in this arena
Cross border
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 PlatformsDocs 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.”
Rainforestnone0/10Rainforest's docs describe US-centric payment processing, merchant onboarding, deposits, and payouts, but there is no mention of multi-currency support, FX handling, local-currency payouts, or settlement to local bank rails in other countries — the product appears scoped to US card/ACH processing only.
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
- [claimed-docs] “Facilitate payments from users to your customers via card, PayPal, Venmo, PayPal Pay Later, ACH, and Apple Pay.”
- [claimed-docs] “Start processing payments in days, not months. Reduce development time and get to revenue faster with our pre-built, embeddable components f…”
Payout schedules
ops userPayouts run on the schedule each seller needs — daily, weekly, monthly, or manual, plus instant payouts to cards or real-time rails where supported, configurable per seller
weight 3 · round to Adyen for PlatformsAdyen 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.”
Docs confirm per-merchant deposit frequency can be configured and updated via the API (rainforest-docs-7), supporting scheduled payouts per seller, but there is no evidence of instant/real-time payouts to cards or push-to-card rails, nor explicit mention of daily/weekly/monthly/manual options as distinct settings. missing for 10: instant payouts to cards or real-time rails, explicit enumeration of daily/weekly/monthly/manual schedule options, and any confirmation of per-seller instant payout support.
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to Adyen for PlatformsDocs 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…”
Rainforest's docs show a broad set of API endpoints (create/update merchant, deposits, splits, webhooks, payments) covering most core functionality, and it is fundamentally API-first with embeddable UI components layered on top rather than a separate full UI. However, there is no explicit statement or evidence mapping every UI capability (e.g., the payment component studio design flow) to an equivalent API call, so full parity is unconfirmed. Missing for 10: explicit parity documentation or changelog confirming API/UI feature equivalence, and evidence that studio/dashboard-only actions can be performed purely via API.
- [claimed-docs] “Create a merchant with an initial merchant application.”
- [claimed-docs] “You can implement amount splits in three steps”
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
- [claimed-docs] “You can subscribe to events for the following resources”
- [claimed-docs] “Head over to the [payment component studio] to start designing the embedded payment component for your platform integration.”
Payfac liability — stories about payfac liability in this arenaPayfac liability
Stories about payfac liability in this arena
Graduation path
founderThere's a path up the stack — start on the managed model and graduate toward registered payment facilitation with more economics and control, without replatforming
weight 2 · round to Adyen for PlatformsAdyen 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.”
Rainforestnone0/10Evidence describes Rainforest's managed payfac model, pricing control, and onboarding components, but there is no mention of a defined path or product mechanism to graduate from Rainforest's managed platform toward becoming a registered/independent PayFac without replatforming. missing for 10: any documentation of a registered-PayFac graduation path, migration tooling, or sponsor-bank transition process.
- [claimed-docs] “We lead with a buy-rate, interchange-plus pricing model, and have no revenue split. See how much money you could save versus a flat rate mod…”
- [claimed-docs] “Yes! You totally control how much you bill your merchants. And with our buy-rate model, any optimization to pricing or interchange costs goe…”
- [claimed-docs] “Start processing payments in days, not months. Reduce development time and get to revenue faster with our pre-built, embeddable components f…”
Responsibility split
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 drawnAdyen for Platformsnone0/10The 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.”
Tax forms
finance leadSeller tax reporting is handled — 1099-K thresholds tracked, forms generated, delivered, and filed, with the data corrections workflow documented
weight 2 · round drawnAdyen for Platformsnone0/10The 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.
Platform agent access — stories about platform agent access in this arenaPlatform agent access
Stories about platform agent access in this arena
Agent money ops
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 Adyen for PlatformsAdyen 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/”
Rainforest documents merchant, deposit and webhook APIs (e.g. deposit frequency, event subscriptions) that touch payout mechanics, and its docs are markdown-fetchable via llms.txt for agent consumption, but there is no documented endpoint for reading balances, investigating a missing payout, or drafting dispute/chargeback evidence, and the probe found no OpenAPI spec for structured agent access. missing for 10: explicit balance/payout read endpoints, dispute-evidence drafting API, and a machine-readable OpenAPI spec.
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
- [claimed-docs] “You can subscribe to events for the following resources”
- [claimed-docs] “Create a merchant with an initial merchant application.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.rainforestpay.com/llms.txt # Rainforest Docs Documentation > Documentation for Rainforest Docs Ap…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.rainforestpay.com/openapi.json, https://docs.rainforestpay.com/swagger.json, https://do…”
Agent onboarding
ai-native userAn agent can run seller operations — create accounts, drive onboarding to completion, and answer requirements-due states through the API or an MCP surface with scoped credentials
weight 3 · round to Adyen for PlatformsAdyen 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/”
Rainforest exposes a REST API for creating merchant accounts, driving onboarding via embeddable components, and webhook notifications for status/requirements changes (rainforest-docs-5, rainforest-docs-4, rainforest-docs-8, rainforest-docs-10), which could plausibly be driven by an agent. However there is no evidence of an MCP server/surface, no mention of scoped or agent-specific credentials, and the openapi probe returned 404s suggesting no discoverable machine-readable API spec for agent tooling. missing for 10: MCP server/tool surface, scoped/agent-specific API credentials, explicit agent-orchestration documentation, discoverable OpenAPI spec.
- [claimed-docs] “Create a merchant with an initial merchant application.”
- [claimed-docs] “Integrate Rainforest's low-code embeddable component into your platform, allowing me”
- [claimed-docs] “You can subscribe to events for the following resources”
- [claimed-docs] “Your Rainforest integration includes three primary phases.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.rainforestpay.com/openapi.json, https://docs.rainforestpay.com/swagger.json, https://do…”
Platform ledger — stories about platform ledger in this arenaPlatform ledger
Stories about platform ledger in this arena
Funds custody
finance leadPlatform funds have a home — clarity on where in-flight and held funds sit, whether balances earn yield, and how money is segregated from the provider's own accounts
weight 2 · round to Adyen for PlatformsDocs 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”
Rainforestnone0/10The evidence covers merchant onboarding, payment processing, and deposit frequency settings, but nothing addresses where in-flight/held funds are custodied, whether balances earn yield, or how funds are segregated from Rainforest's own accounts. This is a fair question for a payments/payfac platform, so the axis applies, but no evidence supports it.
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
Ledger visibility
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 Adyen for PlatformsDocs 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”
Rainforest documents amount splits, payout/deposit scheduling, merchant creation, and webhooks for payment-lifecycle events, plus a generic 'reporting' embeddable component, which together imply some traceability from charge to payout. However there is no explicit documentation of a ledger, seller-level balance views, fee-account tracking, or penny-level reconciliation tooling. Missing for 10: dedicated ledger/balance reporting docs, explicit reconciliation guarantees, fee-account balance visibility, and any independent confirmation of reconciliation accuracy.
- [claimed-docs] “You can implement amount splits in three steps”
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
- [claimed-docs] “You can subscribe to events for the following resources”
- [claimed-docs] “Start processing payments in days, not months. Reduce development time and get to revenue faster with our pre-built, embeddable components f…”
Recon exports
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 PlatformsAdyen 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.”
Rainforest mentions a pre-built 'reporting' embeddable component and webhooks/events for merchant and payment resources, plus deposit frequency settings per merchant, which are adjacent to reconciliation, but there is no explicit documentation of settlement/balance reports per seller and rolled up, nor of scheduled file or API delivery for a finance stack. missing for 10: dedicated settlement/balance report docs, per-seller and rollup reconciliation reports, scheduled file exports, finance-system API integration details.
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
- [claimed-docs] “You can subscribe to events for the following resources”
- [claimed-docs] “Start processing payments in days, not months. Reduce development time and get to revenue faster with our pre-built, embeddable components f…”
Platform monetization — stories about platform monetization in this arenaPlatform monetization
Stories about platform monetization in this arena
Application fees
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 drawnAdyen 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”
Rainforest supports buy-rate/interchange-plus pricing with full control over what founders bill merchants, meaning markup/margin capture is real and per-merchant pricing is possible (rainforest-docs-12, rainforest-docs-13), and amount splits let platforms take a fee on each transaction (rainforest-docs-6). However, evidence does not show a dedicated 'platform revenue' reporting view that separates markup/application-fee revenue from underlying processing costs — reporting docs focus on merchant/transaction data, not platform P&L separation. missing for 10: explicit per-seller/per-merchant custom pricing configuration UI or API field, and a distinct revenue-vs-cost reporting/dashboard feature for the platform itself.
- [claimed-docs] “We lead with a buy-rate, interchange-plus pricing model, and have no revenue split. See how much money you could save versus a flat rate mod…”
- [claimed-docs] “Yes! You totally control how much you bill your merchants. And with our buy-rate model, any optimization to pricing or interchange costs goe…”
- [claimed-docs] “You can implement amount splits in three steps”
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
Buy rates
finance leadI control the economics — a documented buy rate from the provider and freedom to set the sell rate my sellers see, with interchange-level cost visibility to manage the spread
weight 2 · round to RainforestAdyen 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”
Vendor docs explicitly state a buy-rate, interchange-plus pricing model with no revenue split, and confirm platforms fully control the sell rate charged to merchants, with pricing optimizations flowing directly to the platform's margin. Missing for 10: independent/third-party corroboration of actual interchange-level cost breakdowns in the dashboard/API and real customer confirmation of spread visibility.
- [claimed-docs] “We lead with a buy-rate, interchange-plus pricing model, and have no revenue split. See how much money you could save versus a flat rate mod…”
- [claimed-docs] “Yes! You totally control how much you bill your merchants. And with our buy-rate model, any optimization to pricing or interchange costs goe…”
Seller onboarding — stories about seller onboarding in this arenaSeller onboarding
Stories about seller onboarding in this arena
Global coverage
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 drawnAdyen for Platformsnone0/10Evidence 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.”
Rainforestnone0/10The evidence pack shows Rainforest's payment methods (card, PayPal, Venmo, ACH, Apple Pay) and onboarding/merchant creation flows, but nothing documents a coverage map of supported onboarding countries, local payment methods per country, or local-currency settlement — ACH and the overall feature set suggest a US-centric product with no cross-border documentation provided.
- [claimed-docs] “Facilitate payments from users to your customers via card, PayPal, Venmo, PayPal Pay Later, ACH, and Apple Pay.”
- [claimed-docs] “Integrate Rainforest's low-code embeddable component into your platform, allowing me”
- [claimed-docs] “Create a merchant with an initial merchant application.”
Onboarding api
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 drawnDocs 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.”
Docs explicitly describe API-driven merchant creation (KYB/KYC via merchant application), embeddable low-code onboarding components, and pre-built components for merchant onboarding as an alternative to building forms; deposit/webhook docs suggest bank account linking is part of merchant setup. missing for 10: explicit mention of terms/e-sign acceptance flow and dedicated bank-linking API endpoint documentation, plus independent/hands-on corroboration.
- [claimed-docs] “Integrate Rainforest's low-code embeddable component into your platform, allowing me”
- [claimed-docs] “Create a merchant with an initial merchant application.”
- [claimed-docs] “Start processing payments in days, not months. Reduce development time and get to revenue faster with our pre-built, embeddable components f…”
- [claimed-docs] “Head over to the [payment component studio] to start designing the embedded payment component for your platform integration.”
- [claimed-docs] “For **Active** merchants, the deposit frequency can be updated by setting the new deposit frequency on the [Update merchant] endpoint.”
Progressive requirements
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 Adyen for PlatformsAdyen 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.”
Rainforestnone0/10Evidence covers merchant creation, onboarding components, and going-live phases, but nothing describes staged/tunable onboarding requirements, minimum-to-start thresholds, or per-seller 'requirements-due' states tied to payout limits.
- [claimed-docs] “Integrate Rainforest's low-code embeddable component into your platform, allowing me”
- [claimed-docs] “Create a merchant with an initial merchant application.”
- [claimed-docs] “Your Rainforest integration includes three primary phases.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableAdyen for Platformsn/aAdyen for Platforms is a payments/marketplace backend service, not an AI agent or assistant capable of consuming MCP servers as a client. The only MCP-related evidence shows Adyen exposing its own MCP server for others to connect to (the reverse role), which does not make the 'plug MCP servers into this product' client story applicable.
- [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/”
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · not comparableAdyen for Platformsnone0/10The evidence pack covers onboarding, payouts, fraud rules, reconciliation reports, and an MCP server for developer integration, but nothing describes AI-generated insights or suggestions surfaced to end users from their platform data. No dashboard AI features, analytics recommendations, or generative summaries are mentioned anywhere.
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableAdyen for Platformsn/aAdyen for Platforms is a payments infrastructure product, not an agentic assistant application; the evidence shows an MCP server for developer connectivity, not a built-in AI assistant users can delegate tasks to. This is a category mismatch — the axis of 'built-in AI assistant to delegate tasks to' does not apply to a payments platform API/dashboard product.
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableAdyen for Platformsn/aAdyen for Platforms is a payments/marketplace infrastructure product, not an automation/workflow tool with 'automations' that a user builds, versions, and rolls back — this axis is a category error for a payments API platform.
ai-native userExport all of my data in open formats and leave
weight 3 · not comparableAdyen for Platformsnone0/10No evidence of any data export/portability feature or open-format data dump capability; documentation covers onboarding, payouts, fraud, reporting, and API integration but never data export or account closure/portability. Reports (docs-5) are for bookkeeping, not full data export in open formats.
Rainforestn/aRainforest is a payments infrastructure/API platform, not a data-holding SaaS tool where users store personal content that would need bulk export in open formats to 'leave'; the story's premise (exporting all user data and leaving) is a category error for a payment processing API product.
ai-native userRead the product's source under an open license
weight 2 · not comparableAdyen for Platformsn/aAdyen for Platforms is a closed commercial payments/fintech SaaS product, not an open-source software project; source code availability under an open license is not an applicable axis for this kind of product.
ai-native userSelf-host the core product
weight 3 · not comparableAdyen for Platformsn/aAdyen for Platforms is a hosted, regulated payments/fintech SaaS platform; self-hosting is not a coherent capability for this category — it's a wrong-axis question, not an absent feature.
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 · not comparableAdyen for Platformsnone0/10Evidence 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.
Rainforestn/aRainforest is a payment-processing/merchant-of-record platform for embedding payments into a software platform, not a marketplace or agent framework offering agent-initiated checkout protocols or delegated payment credentials for AI agents; this axis is a category error for this product type.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableAdyen for Platformsnone0/10The 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.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableAdyen for Platformsn/aAdyen for Platforms is a payments/marketplace infrastructure product, not an AI model or data-processing service where 'AI training opt-out' is a meaningful axis; the evidence pack covers payment splitting, onboarding, payouts, and an MCP server for developer tooling, none of which relate to controlling AI training data usage.
ai-native userControl data retention and deletion
weight 2 · not comparableAdyen for Platformsnone0/10The evidence pack covers payment platform features (onboarding, payouts, splits, fraud, reporting, MCP server) but contains no mention of data retention policies, deletion controls, or privacy/data-lifecycle management for AI-native users.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableAdyen for Platformsn/aAdyen for Platforms is a payments/marketplace infrastructure product, not an AI assistant or developer tool with telemetry collection concerns relevant to an AI-native user's own usage data; opting out of telemetry/usage tracking is a category mismatch for this axis.