Mangopay vs Rainforest

Agent access

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

   weight 2 · round to Mangopay
   Mangopay✓fullprobed9/10

   Mangopay provides a confirmed llms.txt (HTTP 200) explicitly instructing AI agents on retrieving clean Markdown docs, plus a documented OpenAPI spec and even an MCP server endpoint, directly enabling an agent to be pointed at agent-oriented docs. Missing for 10: independent/community confirmation of actual agent usage against these endpoints.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://docs.mangopay.com/_mcp/server”
   • [claimed-docs] “Send custom text to appear on the user's bank statement for a payment on your platform.”

   proof ↗⚑ flag

   Rainforest✓fullprobed8/10

   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.”

   proof ↗⚑ flag

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

   weight 2 · round to Mangopay
   Mangopay~partialprobed6/10

   Mangopay is a REST API/SDK payments platform with a documented OpenAPI spec, sandbox, and multi-language SDKs, which naturally supports headless/CI automation (scripted API calls, no UI required). However, there is no explicit evidence of CI-specific tooling, CLI, test automation examples, or hands-on confirmation of running it in a CI pipeline. missing for 10: dedicated CLI or CI/CD integration guide, hands-on CI pipeline examples, independent confirmation of headless automation workflows.

   • [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
   • [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Rainforest—none0/10

   Rainforest 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…”

   proof ↗⚑ flag

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

   weight 3 · round to Mangopay
   Mangopay✓fullprobed7/10

   Mangopay is a payments API platform (not an agent itself), so publishing an official MCP server is a valid axis; evidence shows a documented official MCP server endpoint at docs.mangopay.com/_mcp/server alongside llms.txt and OpenAPI probes confirming AI-native tooling support. Missing for 10: no independent/hands-on confirmation of connecting an agent to this MCP server, and no detail on its tool coverage or setup docs beyond the endpoint existing.

   • [probe] “official MCP server documented at https://docs.mangopay.com/_mcp/server”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

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

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Mangopay—none0/10

   No evidence of an official CLI tool; only SDKs in multiple languages, docs, and an MCP server are mentioned, none of which constitute a CLI.

   ⚑ flag

   Rainforest—none0/10

   No evidence of an official CLI tool anywhere in the docs or probes; the pack only covers REST API endpoints, webhooks, and embeddable components. Missing for 10: any mention of a CLI, its installation, or command reference.

   ⚑ flag

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

   weight 3 · round to Mangopay
   Mangopay✓fullprobed9/10

   Mangopay provides a documented public REST API with OpenAPI spec, SDKs in multiple languages, sandbox environment, and confirmed live openapi.json endpoint, clearly supporting programmatic/AI-driven use. Missing for 10: independent third-party confirmation of AI-agent usage in production beyond vendor docs/probes.

   • [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
   • [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”

   proof ↗⚑ flag

   Rainforest~partialprobed6/10

   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…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Mangopay—none0/10

   No evidence of scoped or least-privilege API key/credential issuance for agents — docs cover wallets, payouts, webhooks, FX, disputes, but nothing about API key scoping, permission granularity, or credential minting for automated/agent use.

   ⚑ flag

   Rainforest—none0/10

   Rainforest is a payments-processing platform; evidence covers merchant onboarding, payments, webhooks, and pricing but no mention of scoped or least-privilege API credential issuance for agents, API key management, or permission scoping.

   ⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Mangopay
   Mangopay✓fullprobed8/10

   Mangopay documents official SDKs across Node.js, PHP, Python, .NET, Java, and Ruby, plus a public OpenAPI spec, giving AI-native users concrete language-specific starting points and machine-readable API definitions to build against. Missing for 10: independent/hands-on developer corroboration of SDK quality or GitHub repo activity beyond docs claims.

   • [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”

   proof ↗⚑ flag

   Rainforest—none0/10

   Evidence 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.”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Mangopay
   Mangopay✓fullprobed8/10

   Mangopay documents a clear webhook subscription system for event notifications on API objects, configurable via Dashboard or API, which supports agentic/automated integration patterns; docs are also machine-readable (llms.txt, OpenAPI, MCP server) aiding AI-native consumption. Missing for 10: explicit documentation of programmatic webhook creation via API (only Dashboard flow shown) and no independent/hands-on confirmation of webhook reliability.

   • [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
   • [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Rainforest✓fullclaimed7/10

   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”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Mangopay
   Mangopay~partialclaimed4/10

   Mangopay offers webhooks for event-driven notifications and an API/SDKs that could be used to build background automations like automated payouts and fraud checks, but there is no evidence of a native scheduling, workflow, or agentic automation framework that runs autonomously without external orchestration. missing for 10: no first-party automation/scheduler product, no evidence of autonomous background job execution, no documented agent/automation orchestration layer beyond webhooks and API calls.

   • [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
   • [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
   • [claimed-docs] “Automate order processing and payouts for your Mirakl marketplace”
   • [claimed-docs] “Define custom logic to detect and mitigate fraud attempts on your platform”

   proof ↗⚑ flag

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

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

   weight 2 · round to Mangopay
   Mangopay~partialprobed5/10

   Mangopay documents an official MCP server (mangopay-probe-3) and an llms.txt with agent-oriented instructions (mangopay-probe-1), which enables AI agents to invoke Mangopay's API via natural-language-mediated tool calls rather than raw SDK code. However there is no direct evidence of a natural-language command interface, chat-based operation, or hands-on confirmation that this works end-to-end. Missing for 10: evidence of actual NL command usage/testing, documentation of specific MCP tools exposed, and any user-facing chat/agent interface beyond the MCP endpoint declaration.

   • [probe] “official MCP server documented at https://docs.mangopay.com/_mcp/server”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”
   • [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”

   proof ↗⚑ flag

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

Api quality

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

   weight 2 · round to Mangopay
   Mangopay~partialprobed6/10

   Mangopay provides sandbox API access, a documented OpenAPI spec, and multi-language getting-started guides, indicating a functional API reference; there's no explicit evidence of an interactive 'try it now' console with runnable examples embedded in the docs UI. missing for 10: explicit interactive try-it-now console evidence, independent hands-on confirmation of runnable examples in the reference itself.

   • [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
   • [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”

   proof ↗⚑ flag

   Rainforest—none0/10

   The 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…”

   proof ↗⚑ flag

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

   weight 2 · round to Mangopay
   Mangopay✓fullprobed9/10

   A live probe confirms an OpenAPI JSON spec is served at https://docs.mangopay.com/openapi.json returning HTTP 200 with an "openapi" key, directly satisfying the machine-readable spec requirement. Missing for 10: independent third-party confirmation or documentation explicitly advertising the OpenAPI download link in the docs UI.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Rainforest—none0/10

   Rainforest 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…”

   proof ↗⚑ flag

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

   weight 1 · round to Mangopay
   Mangopay✓fullclaimed8/10

   Mangopay docs explicitly describe a dedicated Sandbox API with simulated test payments, test payment methods (e.g., 3DS2 test cards), and accept/refuse payin simulation flows, allowing full testing without touching production data. Missing for 10: no independent/hands-on confirmation of sandbox-to-production parity or explicit data isolation guarantees beyond docs.

   • [claimed-docs] “Simulate a test payment to get funds on a Mangopay wallet”
   • [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
   • [claimed-docs] “The following card triggers a 3DS2 challenge flow, where SCA is required.”
   • [claimed-docs] “Select ***Accept the payin*** (or ***Refuse the payin***) and click ***Submit***.”

   proof ↗⚑ flag

   Rainforest✓fullclaimed7/10

   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.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Mangopay—none0/10

   Evidence shows an OpenAPI spec and sandbox API docs, but there is no mention of API versioning scheme or a documented deprecation policy anywhere in the pack. missing for 10: explicit API version numbering/headers, changelog of breaking changes, documented deprecation timeline/policy.

   ⚑ flag

   Rainforest—none0/10

   No 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…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Mangopay—none0/10

   Evidence covers individual API operations (wallets, payouts, disputes, webhooks) but no documentation of batch/bulk endpoints, multi-item transaction processing, or bulk automation tooling for AI-native workflows. Absence of evidence for this applicable capability yields none. missing for 10: bulk/batch API endpoints, batch payout or transfer operations, evidence of processing many items in a single call.

   ⚑ flag

   Rainforest—none0/10

   Rainforest 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”

   proof ↗⚑ flag

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

   weight 3 · round to Mangopay
   Mangopay~partialclaimed5/10

   Mangopay provides webhooks that notify external systems on API object events, and documents 'custom logic to detect and mitigate fraud attempts', plus automatic fee/dispute deductions, showing some event-driven automation. However, there's no evidence of a native rules-definition interface or workflow engine letting users declare 'if event X then action Y' logic within Mangopay itself—automation is limited to webhook notifications that require external code to act. Missing for 10: a documented rules/workflow builder, conditional trigger-action configuration UI, and evidence of built-in automated actions beyond webhooks and fee/dispute processing.

   • [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
   • [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
   • [claimed-docs] “Define custom logic to detect and mitigate fraud attempts on your platform”
   • [claimed-docs] “Your fees are automatically wired to your bank account every month.”
   • [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”

   proof ↗⚑ flag

   Rainforest~partialclaimed3/10

   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”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Mangopay—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

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

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

   Mangopay provides robust wallet, payout, and transaction APIs (docs-5, docs-6, docs-11, docs-18/19) that let developers build branded balance/payout/history experiences, plus webhooks for real-time updates (docs-14/15) — satisfying the 'APIs' half of the story. However, there is no evidence of prebuilt white-label UI components/widgets for embedding these surfaces directly, only raw API access and a dashboard for the platform itself. Missing for 10: documented drop-in UI components/widgets for balances/payouts/history, evidence of front-end SDKs for seller-facing embedding, and independent confirmation of embedding in production.

   • [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
   • [claimed-docs] “Send funds locally and internationally in 24+ currencies”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
   • [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
   • [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
   • [claimed-docs] “Mangopay always attempts to use the domestic rail if the currency and country correspond.”
   • [claimed-docs] “Mangopay applies a smart routing logic to always use the domestic rail if a local currency is sent, thereby optimizing routing costs and spe…”

   proof ↗⚑ flag

   Rainforest~partialclaimed6/10

   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.”

   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 Rainforest
   Mangopay—none0/10

   Evidence pack covers wallets, payouts, FX, disputes, webhooks, and online payin testing, but there is no mention of physical POS terminals or tap-to-pay/in-person SDKs that settle into the same wallet/balance system as online payments. Missing for 10: any documentation of terminal hardware, in-person card-present SDKs, or unified online/offline settlement flows.

   ⚑ flag

   Rainforest~partialclaimed5/10

   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”

   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 Rainforest
   Mangopay—none0/10

   The evidence pack covers wallets, payouts, disputes, webhooks, and FX/routing infrastructure, but contains no mention of seller-facing statements, payout reconciliation reports, or bookkeeper-ready exports that would let sellers self-serve without contacting ops. This is a fair axis for a marketplace payments platform, but no supporting documentation or feature reference exists in the pack.

   ⚑ flag

   Rainforest~partialclaimed3/10

   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.”

   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 Mangopay
   Mangopay~partialclaimed7/10

   Mangopay's wallet infrastructure explicitly supports holding funds indefinitely ('as long as needed') and releasing them via API/webhook-triggered events, with dispute/chargeback mechanics documented separately, which together give escrow-like fund-holding and release-on-trigger behavior. However the evidence doesn't show a dedicated 'escrow' product or documented limits (max hold duration, fees for holding, delivery-window-specific triggers) as a unified concept. Missing for 10: explicit escrow/hold-duration limits documentation, a named delivery/dispute-window release mechanism, and independent verification of this workflow in practice.

   • [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
   • [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
   • [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
   • [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”

   proof ↗⚑ flag

   Rainforest—none0/10

   The 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”

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

   Mangopay's dispute/e-wallet docs confirm that chargebacks trigger automatic fund deduction from the wallet and create a contestable dispute settled with Mangopay, showing some liability handling ([mangopay-docs-12], [mangopay-docs-13]). However, there is no documented mechanism for recovering shortfalls beyond wallet balance via automatic debits against future earnings or the seller's linked bank account, nor an explicit documented liability order/waterfall for such recovery. Missing for 10: explicit negative-balance recovery via future payouts, bank debit/clawback mechanics, and a documented liability order beyond the basic dispute-contest flow.

   • [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
   • [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
   • [claimed-docs] “Your fees are automatically wired to your bank account every month.”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”

   proof ↗⚑ flag

   Rainforest—none0/10

   The 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…”

   proof ↗⚑ flag

Splits

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

   weight 3 · round to Mangopay
   Mangopay~partialclaimed6/10

   Mangopay's wallet infrastructure explicitly supports receiving, holding, splitting and transferring funds across an unlimited number of wallets, with platform fees automatically routed to the platform's bank account, which enables multi-party fund routing and fee-taking (docs-5, docs-10, docs-11). However, evidence does not detail a first-class 'split payment' API object, nor explicit mechanisms to adjust or reverse a split after the fact beyond generic dispute/chargeback handling (docs-12, docs-13) which addresses refunds, not split adjustment. Missing for 10: explicit API object/documentation for defining a payment split across multiple recipients in one transaction, and documented reversal/adjustment of that split specifically (not just wallet transfers or chargebacks).

   • [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
   • [claimed-docs] “Your fees are automatically wired to your bank account every month.”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
   • [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
   • [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”

   proof ↗⚑ flag

   Rainforest~partialclaimed5/10

   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”

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

   Docs confirm that disputes/chargebacks are tied to a wallet's user (i.e., per-seller) and that funds are automatically deducted and can be contested with proof (mangopay-docs-12, mangopay-docs-13), and wallets are per-platform-user (mangopay-docs-11), implying per-sub-merchant handling. However, there is no explicit documentation of an API or dashboard workflow for submitting dispute evidence, nor confirmation that outcomes automatically reconcile back into seller balances beyond the initial deduction. Missing for 10: explicit evidence-submission API/dashboard flow, confirmation of sub-merchant-specific dispute routing, and automatic balance reconciliation after outcome.

   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
   • [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
   • [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”

   proof ↗⚑ flag

   Rainforest~partialclaimed3/10

   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…”

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

   Mangopay docs show custom fraud-detection logic, dispute/chargeback handling, and webhook event notifications that could support risk monitoring, but there is no evidence of a per-sub-merchant risk dashboard, anomaly alerts across a seller portfolio, or explicit tools to pause payouts/offboard bad actors. missing for 10: portfolio-level risk dashboard per sub-merchant, anomaly/alerting system for sellers, payout-pause or offboarding workflow.

   • [claimed-docs] “Define custom logic to detect and mitigate fraud attempts on your platform”
   • [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
   • [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
   • [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
   • [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”

   proof ↗⚑ flag

   Rainforest—none0/10

   Evidence covers merchant onboarding, payments processing, deposits, webhooks, and pricing, but nothing addresses fraud/credit-risk monitoring, anomaly alerts, or tools to pause payouts/offboard sellers as portfolio risk-management features for ops users.

   ⚑ 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 Mangopay
   Mangopay✓fullclaimed7/10

   Docs explicitly describe local-currency payouts via domestic bank rails (smart routing prioritizing domestic rail over wire), multi-currency sends in 24+ currencies, and embedded FX conversion for global markets, directly matching the finance-lead story. missing for 10: no explicit documented FX rate/markup transparency or fee schedule, and no independent/hands-on confirmation of settlement times or local rail coverage per country.

   • [claimed-docs] “Mangopay always attempts to use the domestic rail if the currency and country correspond.”
   • [claimed-docs] “Mangopay applies a smart routing logic to always use the domestic rail if a local currency is sent, thereby optimizing routing costs and spe…”
   • [claimed-docs] “Send funds locally and internationally in 24+ currencies”
   • [claimed-docs] “Reach global markets by seamlessly embedding FX conversions in your workflow”
   • [claimed-docs] “Your fees are automatically wired to your bank account every month.”

   proof ↗⚑ flag

   Rainforest—none0/10

   Rainforest'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…”

   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 Rainforest
   Mangopay—none0/10

   The evidence covers wallet infrastructure, payout routing rails (domestic vs cross-border), and platform fee wiring, but contains no mention of configurable payout schedules (daily/weekly/monthly/manual) per seller, nor instant payouts to cards or real-time rails. Missing for 10: any documentation of per-seller payout scheduling, manual vs automatic payout triggers, or instant/real-time payout options.

   • [claimed-docs] “Mangopay always attempts to use the domestic rail if the currency and country correspond.”
   • [claimed-docs] “Mangopay applies a smart routing logic to always use the domestic rail if a local currency is sent, thereby optimizing routing costs and spe…”
   • [claimed-docs] “Your fees are automatically wired to your bank account every month.”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”

   proof ↗⚑ flag

   Rainforest~partialclaimed5/10

   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.”

   proof ↗⚑ flag

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

   weight 2 · round to Mangopay
   Mangopay~partialprobed6/10

   Mangopay is API-first: docs show a full OpenAPI spec, sandbox API, and API-driven wallet, payout, dispute, and webhook management, suggesting broad functional parity. However, some flows (e.g., webhook setup, dispute proof submission) are documented via the Dashboard UI as an alternative path, and there is no explicit claim that all Dashboard actions are always mirrored in the API. Missing for 10: explicit statement of full UI/API parity, and evidence that dashboard-only admin actions (e.g., dispute contestation, account config) are fully API-accessible.

   • [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
   • [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
   • [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
   • [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”

   proof ↗⚑ flag

   Rainforest~partialclaimed4/10

   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.”

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

   No evidence describes a graduation path from managed/wallet model to registered payment-facilitator status with increased economics/control, nor any migration tooling or licensing tiers. Evidence only covers wallet infrastructure, payouts, disputes, and API onboarding — nothing about payfac-liability progression. Missing for 10: any mention of licensing tiers, BIN sponsorship, PF-of-record transition, or economics/control changes as platforms scale.

   ⚑ flag

   Rainforest—none0/10

   Evidence 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…”

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

   Docs mention compliance features (KYC guidance, fraud tooling, dispute/chargeback contestation) but nowhere is there an explicit ops-facing breakdown of who owns KYC/AML, card-network compliance, fraud losses, and seller misconduct versus Mangopay — it's scattered feature docs, not a liability-split reference.

   • [claimed-docs] “Manage your community of paying users in full compliance”
   • [claimed-docs] “Define custom logic to detect and mitigate fraud attempts on your platform”
   • [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
   • [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”

   proof ↗⚑ flag

   Rainforest—none0/10

   The evidence pack covers onboarding, payments, deposits, webhooks, and pricing docs, but nothing explicitly documents a liability/responsibility split for KYC/AML ownership, card-network compliance, fraud losses, or seller misconduct between Rainforest and the platform.

   ⚑ 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
   Mangopay—none0/10

   No evidence in the pack references 1099-K thresholds, tax form generation/filing, or a tax data correction workflow; the docs cover wallets, payouts, disputes, webhooks, and FX but nothing about US tax reporting compliance. missing for 10: 1099-K threshold tracking, form generation/delivery/filing, corrections workflow documentation.

   ⚑ flag

   Rainforest—none0/10

   No evidence in the pack addresses 1099-K threshold tracking, tax form generation/delivery/filing, or a data correction workflow; evidence only covers payments, onboarding, deposits, webhooks, and pricing.

   ⚑ 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 Mangopay
   Mangopay~partialprobed7/10

   Mangopay ships genuinely agent-usable surfaces: a documented OpenAPI spec, llms.txt agent instructions, and an official MCP server, plus docs on wallets/balances, payouts (with domestic-rail routing details useful for investigating a delayed payout), and disputes/chargebacks (including contesting with proof, which maps to 'draft dispute evidence'). However there's no explicit example or endpoint description for reading balances/payout status programmatically or a worked 'investigate missing payout' or 'draft dispute evidence' agent workflow — these are inferred from adjacent guides rather than directly documented. Missing for 10: explicit balance/payout-status API examples, a documented dispute-evidence submission workflow, and independent/hands-on confirmation the MCP server actually exposes these operations.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://docs.mangopay.com/_mcp/server”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
   • [claimed-docs] “Mangopay always attempts to use the domestic rail if the currency and country correspond.”
   • [claimed-docs] “Mangopay applies a smart routing logic to always use the domestic rail if a local currency is sent, thereby optimizing routing costs and spe…”
   • [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
   • [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
   • [claimed-docs] “Send custom text to appear on the user's bank statement for a payment on your platform.”

   proof ↗⚑ flag

   Rainforest~partialprobed4/10

   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…”

   proof ↗⚑ flag

Agent onboarding

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

   weight 3 · round to Mangopay
   Mangopay~partialprobed5/10

   Mangopay exposes a full API (with OpenAPI) and an official MCP server, plus docs on managing users/accounts in compliance, which supports agent-driven seller operations in principle. However, no evidence explicitly documents onboarding completion flows, KYC 'requirements-due' status handling, or scoped/limited credentials for agent use via the MCP surface. missing for 10: explicit onboarding-completion workflow docs, requirements-due state handling, scoped-credential/permission model for agent access.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://docs.mangopay.com/_mcp/server”
   • [claimed-docs] “Manage your community of paying users in full compliance”
   • [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”

   proof ↗⚑ flag

   Rainforest~partialprobed4/10

   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…”

   proof ↗⚑ flag

Funds custody

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

   weight 2 · round to Mangopay
   Mangopay~partialclaimed3/10

   Docs confirm Mangopay's wallet infrastructure lets platforms hold, split and transfer funds and that platform fees are wired out monthly (mangopay-docs-5, mangopay-docs-10, mangopay-docs-11), giving some sense of where funds sit, but there is no evidence addressing regulatory fund segregation from Mangopay's own accounts or whether held balances earn yield. missing for 10: explicit safeguarding/segregation-of-client-funds statement, disclosure of interest/yield policy on wallet balances, third-party or regulatory confirmation of fund protection.

   • [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
   • [claimed-docs] “Your fees are automatically wired to your bank account every month.”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”

   proof ↗⚑ flag

   Rainforest—none0/10

   The 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.”

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

   Docs confirm wallet infrastructure supporting per-seller and platform fee wallets, automatic fee payout to bank, webhooks for event tracking (charge/payin, split/transfer, payout), and dispute/chargeback handling — the building blocks for traceability and reconciliation. However there is no explicit documentation of a unified ledger/reporting view, reconciliation reports, or per-penny audit trail tooling that a finance lead would use directly. Missing for 10: dedicated reconciliation/reporting API or dashboard view showing full charge-to-payout trace, statement/ledger export functionality, and independent confirmation that balances reconcile to the penny in practice.

   • [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
   • [claimed-docs] “Your fees are automatically wired to your bank account every month.”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
   • [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
   • [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
   • [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
   • [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”

   proof ↗⚑ flag

   Rainforest~partialclaimed5/10

   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…”

   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 drawn
   Mangopay~partialclaimed3/10

   Mangopay's docs show wallet balances, automatic monthly fee wiring, and webhook event notifications that could feed a finance stack, but there is no explicit documentation of settlement/balance report files or scheduled per-seller reconciliation APIs. missing for 10: dedicated reconciliation/settlement report API or downloadable file exports, explicit per-seller rollup reporting, and evidence of scheduled delivery cadence.

   • [claimed-docs] “Your fees are automatically wired to your bank account every month.”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
   • [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
   • [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”

   proof ↗⚑ flag

   Rainforest~partialclaimed3/10

   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…”

   proof ↗⚑ flag

Application fees

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

   weight 3 · round to Rainforest
   Mangopay~partialclaimed5/10

   Mangopay's wallet infrastructure supports splitting funds and platforms have their fees automatically wired to their bank account monthly, which supports taking a fee/markup on transactions (mangopay-docs-5, mangopay-docs-10, mangopay-docs-11). However, there is no evidence of per-seller custom pricing configuration or of dashboard/reporting that separates fee revenue from processing costs. Missing for 10: per-seller/variable fee-setting documentation, dedicated revenue-vs-cost reporting/dashboard evidence, independent confirmation of fee mechanics in production.

   • [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
   • [claimed-docs] “Your fees are automatically wired to your bank account every month.”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”

   proof ↗⚑ flag

   Rainforest~partialclaimed6/10

   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.”

   proof ↗⚑ flag

Buy rates

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

   weight 2 · round to Rainforest
   Mangopay—none0/10

   The evidence shows only generic fee/wallet documentation (e.g., fees wired monthly, wallet infrastructure) but nothing about a documented buy rate, ability to set a sell rate, or interchange-level cost breakdown for spread management. Community comments merely speculate about overall pricing being surprisingly low, not about rate transparency or spread control tools.

   ⚑ flag

   Rainforest✓fullclaimed8/10

   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…”

   proof ↗⚑ 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 to Mangopay
   Mangopay~partialclaimed4/10

   Docs mention multi-currency payouts (24+ currencies), FX conversion, smart domestic-rail routing, and automated fee settlement, implying broad geographic/currency coverage, but there is no evidence of an explicit onboarding coverage map listing supported countries, KYC requirements per region, or local payment methods per market. Founders would still need to discover country-specific onboarding requirements piecemeal. missing for 10: a documented country/coverage map, list of supported local payment methods per country, explicit onboarding country list, independent confirmation of coverage claims.

   • [claimed-docs] “Send funds locally and internationally in 24+ currencies”
   • [claimed-docs] “Reach global markets by seamlessly embedding FX conversions in your workflow”
   • [claimed-docs] “Mangopay always attempts to use the domestic rail if the currency and country correspond.”
   • [claimed-docs] “Mangopay applies a smart routing logic to always use the domestic rail if a local currency is sent, thereby optimizing routing costs and spe…”
   • [claimed-docs] “Your fees are automatically wired to your bank account every month.”

   proof ↗⚑ flag

   Rainforest—none0/10

   The 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.”

   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 to Rainforest
   Mangopay—none0/10

   The evidence pack only vaguely references 'managing a community of paying users in full compliance' and wallet/payout infrastructure, but contains no documentation of KYB/KYC onboarding APIs, hosted onboarding flows, embeddable UI components, bank account linking, or terms-of-service acceptance mechanisms — the core elements of this story are entirely unevidenced.

   • [claimed-docs] “Manage your community of paying users in full compliance”

   proof ↗⚑ flag

   Rainforest✓fullclaimed8/10

   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.”

   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 drawn
   Mangopay—none0/10

   The evidence only shows generic compliance and wallet/payout docs (e.g., mangopay-docs-4, mangopay-docs-11) but nothing about tiered/progressive KYC, minimum-to-start onboarding, or explicit requirements-due states tied to payout thresholds. Missing for 10: documentation of staged KYC levels, seller onboarding status states, and payout gating tied to verification completeness.

   • [claimed-docs] “Manage your community of paying users in full compliance”
   • [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”

   proof ↗⚑ flag

   Rainforest—none0/10

   Evidence 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.”

   proof ↗⚑ flag