Stripe Connect vs Tilled

Agent access

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

   weight 2 · round to Stripe Connect
   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

   Tilled—none0/10

   No evidence of an llms.txt file, agent-oriented documentation, or any mention of AI agent-friendly docs; the evidence pack only shows standard developer documentation for payments/onboarding.

   ⚑ 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

   Tilled—none0/10

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

   ⚑ flag

3. ai-native 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

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

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

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

   Tilled~partialclaimed7/10

   Tilled documents a public API with API keys, a quick-start guide, sandbox/test environment, and webhooks for event-driven use, indicating the product can be driven programmatically (tilled-docs-1, tilled-docs-2, tilled-docs-3, tilled-docs-4). However, the evidence pack lacks a full API reference/spec, SDK details, or independent developer corroboration of building an integration end-to-end. Missing for 10: comprehensive API reference/OpenAPI docs, SDK examples, and third-party/hands-on confirmation of programmatic control.

   • [claimed-docs] “API keys are required to access API. To generate API keys through the Dashboard”
   • [claimed-docs] “Check out everything Tilled has to offer and get a little test-happy in our sandbox environment.”
   • [claimed-docs] “To simulate a decline, pass-through the respective amount when Creating a Payment Intent”
   • [claimed-docs] “Webhooks provide real-time notifications to your application about events occurring on platform.”

   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

   Tilled—none0/10

   The evidence pack covers API keys, sandbox testing, webhooks, merchant onboarding, and dashboard features, but contains no mention of official SDKs (e.g., language-specific libraries like Python, Node.js, Java) for developers to build against.

   ⚑ flag

7. ai-native userSubscribe to events via webhooks

   weight 2 · round to Stripe Connect
   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

   Tilled~partialclaimed5/10

   Tilled documents webhooks that provide real-time event notifications, confirming basic webhook subscription support, but there is no evidence of event type filtering, subscription management API, signature verification, or retry/delivery configuration details. missing for 10: documented list of subscribable event types, webhook management/configuration API, signature verification details, independent/hands-on confirmation.

   • [claimed-docs] “Webhooks provide real-time notifications to your application about events occurring on platform.”

   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

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

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

   Tilled—none0/10

   Evidence shows standard docs (quick-start, webhooks, testing, onboarding) but no mention of an interactive API reference or runnable code examples/sandbox console embedded in docs.

   ⚑ 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

   Tilled—none0/10

   No evidence pack item mentions an OpenAPI spec, Swagger file, or any downloadable machine-readable API specification; docs only describe API concepts and dashboard features.

   ⚑ flag

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

   weight 1 · round to Tilled
   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

   Tilled✓fullclaimed7/10

   Tilled explicitly offers a sandbox environment for testing, including simulating declines and mock card-present/terminal testing, without touching production data. Missing for 10: independent/hands-on corroboration beyond vendor docs, and no explicit mention of automated/agentic test workflows or CI integration.

   • [claimed-docs] “Check out everything Tilled has to offer and get a little test-happy in our sandbox environment.”
   • [claimed-docs] “To simulate a decline, pass-through the respective amount when Creating a Payment Intent”
   • [claimed-docs] “A mock card present provider, which allows for terminal creation and testing”

   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

   Tilled—none0/10

   No evidence pack items mention API versioning, version numbers, or a deprecation policy for Tilled's API; documentation covers keys, webhooks, onboarding, and dashboard features but not lifecycle/versioning practices.

   ⚑ 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

   Tilled—none0/10

   Tilled's evidence pack covers payments API, onboarding, disputes, payouts, and webhooks, but there is no mention of bulk/batch operations across many items (e.g., bulk payment creation, bulk merchant updates, batch API endpoints for multiple resources at once). The only 'batch' reference concerns settlement batch closing for a single store's transactions, not bulk operations across many items.

   ⚑ 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

   Tilled—none0/10

   Tilled offers webhooks for event notifications (tilled-docs-4) but there is no evidence of a rules engine or conditional trigger system that lets users define automated actions based on those events.

   • [claimed-docs] “Webhooks provide real-time notifications to your application about events occurring on platform.”

   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

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

   Tilled~partialclaimed6/10

   Tilled explicitly offers white-labeling of API, onboarding, and reporting console under a partner's own domain, and documents building custom UIs on top of its API (payouts, disputes, subscriptions data are accessible via Dashboard/API). This supports embeddable seller-facing surfaces but the evidence doesn't detail specific pre-built components for balances/transaction history or give independent proof of embedding fidelity. Missing for 10: dedicated embeddable balance/transaction-history widget docs, explicit component-level white-label UI examples, and independent/hands-on confirmation of the white-label experience.

   • [claimed-docs] “Enterprise partners have the ability to host their API, merchant onboarding, and reporting console experiences on a domain that reflects the…”
   • [claimed-docs] “Customize and build your own UI”
   • [claimed-docs] “To view a merchant’s payout speed in the Dashboard”
   • [claimed-docs] “Merchants can manage disputes through the Dashboard.”
   • [claimed-docs] “Merchants and ISVs can now view and manage all of their subscriptions within their Dashboard.”

   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 Tilled
   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

   Tilled~partialclaimed5/10

   Tilled docs mention card-present terminal creation/testing and batch closing so in-person transactions settle at shift end, implying integration with the same merchant account, but there's no explicit tap-to-pay SDK or documentation showing unified balance/reporting dashboards combining online and in-person payments. Missing for 10: tap-to-pay SDK details, explicit unified reporting/balance evidence combining online and card-present transactions, and independent corroboration of terminal hardware support.

   • [claimed-docs] “By closing a batch via API, a store can ensure their transactions are settled at time of close or end of shift”
   • [claimed-docs] “A mock card present provider, which allows for terminal creation and testing”

   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 Tilled
   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

   Tilled~partialclaimed3/10

   Tilled's docs show merchants can view payout speed in a Dashboard (tilled-docs-10) and enterprise partners can white-label a 'reporting console' (tilled-docs-14), suggesting some self-serve payout visibility, but there is no evidence of per-seller statements, payout reconciliation reports, or bookkeeper-ready exports. missing for 10: per-seller statement generation, payout reconciliation report format/detail, CSV/export functionality for bookkeepers.

   • [claimed-docs] “To view a merchant’s payout speed in the Dashboard”
   • [claimed-docs] “Enterprise partners have the ability to host their API, merchant onboarding, and reporting console experiences on a domain that reflects the…”

   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

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

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

   Tilled—none0/10

   Evidence only mentions that merchants can 'manage disputes' through the Dashboard, with no documentation of negative balance recovery, automatic debits against future earnings, bank account debits, or liability ordering for refunds/chargebacks exceeding balance.

   • [claimed-docs] “Merchants can manage disputes through the Dashboard.”

   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

   Tilled—none0/10

   The evidence pack covers merchant onboarding, pricing templates, payouts, disputes, and webhooks, but nothing describes splitting a single charge across multiple parties, taking a platform cut, or reversing/adjusting such splits as API objects. Tilled's evidence centers on single-merchant payment processing and ISV platform fee/pricing templates, not multi-party charge splitting. Missing for 10: any mention of split payments, multi-party charge routing, application fees, or transfer/reversal objects for splits.

   • [claimed-docs] “Merchant pricing is managed using pricing templates, which serve as a repository of pricing information for a specific payment method.”
   • [claimed-docs] “To view a merchant’s payout speed in the Dashboard”

   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

   Tilled~partialclaimed3/10

   Only one doc snippet confirms merchants can manage disputes via the Dashboard, implying per-merchant (sub-merchant) dispute handling, but there's no evidence of API-based evidence submission, explicit chargeback routing logic, or automatic reconciliation of outcomes into seller balances. missing for 10: API-based dispute evidence submission, explicit per-seller chargeback routing details, automatic balance reconciliation after dispute outcome.

   • [claimed-docs] “Merchants can manage disputes through the Dashboard.”

   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

   Tilled—none0/10

   The evidence pack covers onboarding, payouts, disputes management, webhooks, and API testing, but contains no mention of fraud/credit-risk scoring per sub-merchant, anomaly alerts, or tools to pause payouts/offboard risky sellers.

   ⚑ 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

   Tilled—none0/10

   The evidence pack covers merchant onboarding, payouts speed settings, disputes, and dashboard features, but contains no mention of international sellers, multi-currency support, FX handling, or local bank rail settlement outside the US. Tilled appears to be a US-focused payment facilitator platform with no documented cross-border/local-currency payout capability.

   ⚑ 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

   Tilled~partialclaimed3/10

   Only one thin reference confirms that Tilled lets ops view a merchant's 'payout speed' in the Dashboard, implying some per-merchant payout timing configuration, but there is no documentation of specific schedule options (daily/weekly/monthly/manual) or instant payouts to cards/real-time rails. Missing for 10: explicit schedule types (daily/weekly/monthly/manual), instant payout to card support, real-time rails support, and confirmation that these are configurable per seller.

   • [claimed-docs] “To view a merchant’s payout speed in the Dashboard”

   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

   Tilled~partialclaimed4/10

   Tilled offers API access for core payment operations (payments, webhooks, batches, testing) but several UI-only functions like dispute management and payout speed viewing are explicitly documented as Dashboard-only, and merchant onboarding has a no-code Dashboard option alongside API options, suggesting UI and API are not fully at parity. missing for 10: evidence that disputes, payout configuration, and subscription management can be fully performed via API rather than only through the Dashboard, plus independent confirmation of full API/UI parity.

   • [claimed-docs] “To view a merchant’s payout speed in the Dashboard”
   • [claimed-docs] “Merchants can manage disputes through the Dashboard.”
   • [claimed-docs] “Merchants and ISVs can now view and manage all of their subscriptions within their Dashboard.”
   • [claimed-docs] “No-code option for software platforms to onboard a merchant.”
   • [claimed-docs] “By closing a batch via API, a store can ensure their transactions are settled at time of close or end of shift”

   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

   Tilled—none0/10

   The evidence pack covers Tilled's managed PayFac features (onboarding, pricing templates, webhooks, dashboards, white-labeling) but contains no mention of a graduation path toward registered payment facilitation, economics changes, or control transitions without replatforming. Missing for 10: any documentation of a registered-PayFac upgrade path, economics/revenue-share changes at that tier, or migration mechanics that avoid replatforming.

   ⚑ 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

   Tilled—none0/10

   The evidence pack contains only integration, onboarding, testing, and dashboard feature docs; none of it addresses an explicit documented split of liability for KYC/AML, card-network compliance, fraud losses, or seller misconduct between Tilled 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

   Tilled—none0/10

   No evidence anywhere in the pack mentions 1099-K threshold tracking, tax form generation, delivery, filing, or a data-corrections workflow; the pack covers onboarding, payments, payouts, disputes, and dashboards but is silent on tax reporting entirely.

   ⚑ 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

   Tilled~partialclaimed3/10

   Docs confirm a general API with keys and webhooks for real-time events, and payout speed/dispute management are documented, but they are explicitly described as Dashboard-based features rather than agent-callable API endpoints for reading balances, investigating payouts, or drafting dispute evidence. Missing for 10: explicit API endpoints/schemas for balances, payout investigation, and dispute evidence submission usable by an autonomous agent, plus any agent/automation-specific tooling or examples.

   • [claimed-docs] “To view a merchant’s payout speed in the Dashboard”
   • [claimed-docs] “Merchants can manage disputes through the Dashboard.”
   • [claimed-docs] “Webhooks provide real-time notifications to your application about events occurring on platform.”
   • [claimed-docs] “API keys are required to access API. To generate API keys through the Dashboard”

   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

   Tilled~partialclaimed4/10

   Tilled's docs show API-driven merchant onboarding (create, pre-fill, and edit applications in `created`/`started` status) and dashboard progress tracking of onboarding steps, which supports part of the 'agent drives onboarding' story. However, there is no evidence of an MCP surface, no mention of scoped/restricted API credentials for agent use, and no explicit handling of 'requirements-due' states via API. missing for 10: MCP server/tool surface, scoped credential model for agents, explicit requirements-due state API.

   • [claimed-docs] “No-code option for software platforms to onboard a merchant.”
   • [claimed-docs] “Merchant applications with the `created` or `started` status can be pre-filled and edited on behalf of the merchant.”
   • [claimed-docs] “ISVs can see their progress item by item - creating API keys, submitting a merchant application, collecting a first payment, and more - righ…”
   • [claimed-docs] “API keys are required to access API. To generate API keys through the Dashboard”

   proof ↗⚑ flag

Agentic commerce

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

   weight 2 · round drawn
   Stripe Connect—none0/10

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

   ⚑ flag

   Tilled—none0/10

   No evidence of agentic-commerce protocol support, delegated payment credentials, or agent-initiated checkout anywhere in the pack; documentation covers standard payment platform features (API keys, webhooks, merchant onboarding, payouts) with no mention of AI agent buyers or agent checkout flows.

   ⚑ 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

   Tilled—none0/10

   No evidence pack items address fund segregation, custody of in-flight/held balances, yield on balances, or safeguarding from provider's own accounts; documentation covers API keys, payouts speed, disputes, and onboarding only. missing for 10: any mention of fund segregation/custody model, held-balance yield policy, or safeguarding disclosures.

   ⚑ 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

   Tilled~partialclaimed4/10

   Docs show payout speed settings, merchant pricing templates, and dispute management, implying some money-tracking infrastructure, but there is no explicit documentation of per-seller balance views, platform fee account tracking, or charge-to-split-to-payout traceability/reconciliation. Missing for 10: explicit balance-by-seller/fee-account reporting, transaction-level traceability from charge through split to payout, and reconciliation tooling or statements.

   • [claimed-docs] “Merchant pricing is managed using pricing templates, which serve as a repository of pricing information for a specific payment method.”
   • [claimed-docs] “To view a merchant’s payout speed in the Dashboard”
   • [claimed-docs] “Merchants can manage disputes through the Dashboard.”

   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

   Tilled~partialclaimed3/10

   Evidence shows settlement-related building blocks (batch closing/settlement per docs-5, payout visibility per docs-10, webhooks for event notifications per docs-4, and a hosted reporting console per docs-14) but nothing documents automated per-seller and rolled-up reconciliation reports, scheduled delivery, or finance-stack-consumable file/API exports. missing for 10: explicit reconciliation/settlement report generation, per-seller vs rolled-up aggregation, scheduled file exports or dedicated reporting API endpoints for finance systems.

   • [claimed-docs] “By closing a batch via API, a store can ensure their transactions are settled at time of close or end of shift”
   • [claimed-docs] “To view a merchant’s payout speed in the Dashboard”
   • [claimed-docs] “Webhooks provide real-time notifications to your application about events occurring on platform.”
   • [claimed-docs] “Enterprise partners have the ability to host their API, merchant onboarding, and reporting console experiences on a domain that reflects the…”

   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 Stripe Connect
   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

   Tilled~partialclaimed4/10

   Tilled documents per-seller pricing via merchant pricing templates (tilled-docs-9), which supports setting per-seller pricing, but there is no evidence of an application-fee/markup mechanism on transactions or of a dashboard/report that separates platform revenue from underlying processing costs. Missing for 10: explicit application fee or markup configuration per transaction, and a revenue-vs-processing-cost reporting view.

   • [claimed-docs] “Merchant pricing is managed using pricing templates, which serve as a repository of pricing information for a specific payment method.”

   proof ↗⚑ flag

Buy rates

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

   weight 2 · round drawn
   Stripe Connect~partialcommunity4/10

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

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

   proof ↗⚑ flag

   Tilled~partialclaimed4/10

   Tilled's docs mention merchant pricing templates that let platforms set pricing per payment method, implying sell-rate control (tilled-docs-9), but there is no documented buy rate from Tilled or interchange-level cost visibility described anywhere in the evidence pack. missing for 10: explicit buy rate disclosure, interchange-level cost breakdown/visibility tools, and spread-management reporting.

   • [claimed-docs] “Merchant pricing is managed using pricing templates, which serve as a repository of pricing information for a specific payment method.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Connect—none0/10

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

   ⚑ flag

   Tilled—none0/10

   No evidence in the pack mentions data residency, region selection, or geographic storage controls for Tilled's platform.

   ⚑ 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

   Tilled—none0/10

   No evidence pack item documents a coverage map of supported onboarding countries, local payment methods, or local-currency settlement; all citations relate to API/dashboard mechanics, merchant onboarding flow, and product journal updates rather than geographic/currency coverage. missing for 10: supported-country list, local payment method coverage, local-currency settlement documentation.

   ⚑ 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 Stripe Connect
   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

   Tilled~partialclaimed6/10

   Tilled's docs show a merchant onboarding API with multiple integration paths — a no-code hosted option and a fully custom API/UI option — plus white-labeled hosted onboarding for enterprise partners, matching the 'hosted flows and embeddable components' ask. However, the evidence never explicitly details KYC/KYB data collection, bank account linking steps, or terms-of-service acceptance as part of that flow. Missing for 10: explicit KYC/KYB field/process documentation, bank account linking API details, and terms acceptance mechanism.

   • [claimed-docs] “No-code option for software platforms to onboard a merchant.”
   • [claimed-docs] “Merchant applications with the `created` or `started` status can be pre-filled and edited on behalf of the merchant.”
   • [claimed-docs] “Customize and build your own UI”
   • [claimed-docs] “Enterprise partners have the ability to host their API, merchant onboarding, and reporting console experiences on a domain that reflects the…”

   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

   Tilled~partialclaimed4/10

   Tilled docs show merchant applications have progressive statuses (created/started) that can be pre-filled and edited over time, and ISVs get an item-by-item onboarding progress view in the Dashboard, suggesting some staged onboarding exists. However there is no explicit evidence of a tunable minimum-to-sell model gated by payout thresholds or clearly defined 'requirements-due' states per seller like a formal verification/eligibility system. Missing for 10: explicit documentation of minimum data required to start accepting payments, payout-threshold-triggered requirement escalation, and named per-seller requirements-due states.

   • [claimed-docs] “Merchant applications with the `created` or `started` status can be pre-filled and edited on behalf of the merchant.”
   • [claimed-docs] “ISVs can see their progress item by item - creating API keys, submitting a merchant application, collecting a first payment, and more - righ…”
   • [claimed-docs] “To view a merchant’s payout speed in the Dashboard”

   proof ↗⚑ flag