Stripe Connect vs Rainforest

Agent access

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

   weight 2 · round drawn
   Stripe Connect✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 userBuild against official SDKs

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

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

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

   proof ↗⚑ flag

   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

7. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Stripe Connect✓fullcommunity7/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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