Stripe Billing vs Orb
Stripe Billing
Stripe, Inc.
Stripe Billing wins · 20–12 (17 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnStripe hosts an llms.txt at docs.stripe.com/llms.txt (HTTP 200) and markdown-formatted docs (e.g. billing.md), confirming agent-friendly documentation is directly accessible. Missing for 10: independent/third-party confirmation that agents successfully consume these files in practice beyond the probe check.
A live probe confirms Orb serves a proper llms.txt at docs.withorb.com/llms.txt returning HTTP 200 with structured links to docs, directly satisfying the agent-oriented docs discovery story. Missing for 10: no independent third-party corroboration of agent usage/adoption beyond the probe itself.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.withorb.com/llms.txt # Orb - [Overview](https://docs.withorb.com/overview.md) - [What is Orb?](htt…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to Stripe BillingStripe Billing is fully accessible via API and has a documented CLI for building, testing, and managing integrations from the command line, both of which support headless/CI automation, and webhooks enable event-driven automation flows. Missing for 10: explicit CI pipeline examples (e.g., GitHub Actions) or documented headless-mode flags for the CLI, and independent confirmation of CI usage.
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
- [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
- [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
Orb is API-first for core actions (e.g., subscription creation, event ingestion, webhooks) which implies operations can be automated without the UI, but there is no evidence of a CLI, SDK, or explicit CI/pipeline integration story — the evidence never discusses running Orb 'headlessly' in an automation/CI context. missing for 10: CLI or SDK for automation, explicit CI/pipeline integration examples, documentation framing API use as headless/agentic automation.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Orb provides per-event idempotency through the API to guarantee that duplicates are never processed within the account grace period.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
ai-native userConnect an agent via an official MCP server
weight 3 · round to Stripe BillingStripe (parent product of Stripe Billing) documents an official MCP server that lets AI agents interact with the Stripe API, confirmed by both docs and probe evidence. Missing for 10: no independent/community hands-on validation of the MCP server specifically, and no detail on which Billing-specific endpoints/tools are exposed via MCP.
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
ai-native userUse an official CLI
weight 2 · round to Stripe BillingStripe documents an official Stripe CLI for building, testing, and managing Stripe integrations from the command line, confirmed by both docs and probe evidence. Missing for 10: independent hands-on community reports specifically about CLI usage/quality (community evidence here focuses on billing fees, not the CLI).
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
ai-native userDrive the product through a documented public API
weight 3 · round to Stripe BillingStripe Billing is fully drivable via the well-documented Subscriptions/Invoicing/Usage-based/Prorations APIs, with webhooks for events and even an official CLI and MCP server for agent-driven access. Missing for 10: no published OpenAPI spec discoverable at standard locations (404s on probe) and no independent hands-on confirmation of full API parity for AI-agent workflows.
- [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
- [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/billing.md # Billing Create and manage subscriptions, track usage, and issue invoices. …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
- [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
Orb's docs explicitly reference creating subscriptions via API, an api-reference error-responses page, per-event idempotency through the API, and a real-time webhooks system, indicating a documented public API spanning core billing operations. Missing for 10: a discoverable machine-readable OpenAPI/swagger spec (probe returned 404 on all candidates) and independent third-party corroboration of API usage.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “If you are processing an error programmatically, consider using the type URI along with the status code.”
- [claimed-docs] “Orb provides per-event idempotency through the API to guarantee that duplicates are never processed within the account grace period.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnStripe Billingnone0/10The evidence pack shows Stripe's MCP server and CLI for agent integration, but nothing documents scoped or least-privilege API credential issuance for agents (e.g., restricted API keys with granular permissions) — this specific capability is absent from the pack. Missing for 10: documentation of restricted/scoped API key creation, permission granularity controls, and any agent-specific credential-scoping workflow.
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
ai-native userBuild against official SDKs
weight 2 · round to Stripe BillingThe pack shows Stripe exposes a public API, an official CLI, and an MCP server for agent access, and the llms.txt note implies npm-published SDK packages, but there is no explicit documentation of official language SDKs (Node/Python/Ruby/etc.) or SDK-specific guides in the evidence pack. Missing for 10: explicit SDK reference docs/links, language coverage list, and any independent corroboration of SDK quality or agent usage with them.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
- [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
Orbnone0/10The evidence pack shows Orb has a REST API (endpoints, error responses, webhooks) but contains no mention of official language SDKs (e.g., Python, Node, Java client libraries), and the OpenAPI probe returned 404s, suggesting no public spec/SDK generation surface. Missing for 10: any documentation of official SDKs, client libraries, or language-specific packages for building AI-native integrations.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “If you are processing an error programmatically, consider using the type URI along with the status code.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnStripe's docs explicitly describe webhooks pushing real-time event data when things happen in the account, which is the standard mechanism for subscribing to billing-related events (e.g., subscription/invoice lifecycle). Missing for 10: no specifics on which billing event types are supported, no documentation of webhook endpoint management via API, and no agent-specific webhook subscription flow (e.g., via MCP) tying it to the 'AI-native' framing.
- [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
Orb documents a real-time webhooks system that issues calls to an endpoint for account events, directly enabling event subscription. Missing for 10: details on event payload schema, list of supported event types, signature verification/security, and independent/hands-on confirmation beyond docs.
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnStripe Billingnone0/10Evidence shows only standard analytics dashboards (docs-11) and an MCP server for external agents to call the API (docs-18), but nothing indicating the product itself generates AI-driven insights or suggestions from a merchant's billing data. missing for 10: any AI/ML-generated insights or recommendation features, in-product analysis narratives, or evidence of generative AI surfacing suggestions from billing/subscription data.
- [claimed-docs] “Monitor overall performance at a glance”
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
Orbnone0/10Orb is a billing/usage-metering platform; evidence covers forecasting, revenue recognition, invoicing, and pricing analytics, but none describes AI-generated insights or suggestions surfaced within the product itself. No mention of AI/ML features, copilots, or generative recommendations anywhere in the docs pack.
ai-native userSet up automations that run autonomously in the background
weight 2 · round to Stripe BillingStripe Billing ships genuine background automations that run autonomously without manual intervention — recurring subscription billing, smart retries for failed payments, and webhook-driven event automation — and it exposes an official MCP server letting AI agents interact with the Billing API, aligning with the AI-native automation story. However, there is no evidence of an AI-native automation/rules builder (e.g., agent-authored workflows, scheduled agent tasks) beyond the MCP connector and the native recurring-billing engine. Missing for 10: dedicated AI-agent workflow/automation builder, evidence of agents autonomously configuring or modifying billing automations, independent hands-on validation of MCP-driven autonomous operation.
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”
- [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
Orb has several autonomous background processes (auto dunning retries, automatic invoice issuance after grace periods, usage-threshold alerts, and real-time webhooks) that run without manual intervention, which partially satisfies 'automations that run in the background.' However there is no evidence of an AI-native automation builder, agent-configurable workflows, or general-purpose autonomous task orchestration beyond these fixed billing behaviors. Missing for 10: user-configurable automation/workflow engine, AI-agent-triggered automation setup, evidence of arbitrary background task scheduling beyond billing-specific triggers.
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
- [claimed-docs] “Trigger alerts at usage thresholds to power product-led growth.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnStripe Billingnone0/10The 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.)
ai-native userOperate the product with natural-language commands
weight 2 · round to Stripe BillingStripe documents an official MCP server that lets AI agents interact with the Stripe API (which includes Billing endpoints for subscriptions, invoices, etc.), enabling natural-language-driven operation via an AI agent layer. However, this is evidenced only via first-party docs at the general Stripe API level, not Billing-specific NL commands, and there's no independent/hands-on confirmation of it working well for Billing tasks. Missing for 10: Billing-specific natural-language examples, independent/hands-on validation of MCP-driven billing operations, and documented limitations/edge cases.
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
Orbnone0/10No evidence anywhere in the pack of a natural-language interface, chat/AI assistant, or NL-driven command execution for Orb; all documented interactions are via UI or REST/SQL APIs.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Build complex billing metrics with full SQL control.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnStripe Billingnone0/10The evidence pack contains no mention of an interactive API reference with runnable/executable code examples for Stripe Billing; it only covers docs, CLI, MCP server, and general billing features. Absence of evidence for this applicable capability yields 'none'.
Orbnone0/10Evidence only shows standard API reference docs (e.g., error-responses.md) but no mention of an interactive explorer or runnable code examples; the openapi spec probe returned 404s, suggesting no discoverable machine-readable spec to power such interactivity.
- [claimed-docs] “If you are processing an error programmatically, consider using the type URI along with the status code.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnStripe Billingnone0/10The evidence pack shows an explicit probe for OpenAPI/Swagger spec files at all standard paths returning 404, and no docs or community item mentions a downloadable OpenAPI/equivalent spec for Stripe Billing's API; only llms.txt and markdown docs endpoints are confirmed, which are not API specs.
- [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/billing.md # Billing Create and manage subscriptions, track usage, and issue invoices. …”
Orbnone0/10The evidence pack shows explicit probes for a machine-readable OpenAPI spec (openapi.json, swagger.json, etc.) all returning 404, and no docs page offers a downloadable API spec — only an llms.txt index and general API reference mentions. Missing for 10: any working OpenAPI/Swagger endpoint, a documented spec download link, or third-party confirmation of spec availability.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.withorb.com/llms.txt # Orb - [Overview](https://docs.withorb.com/overview.md) - [What is Orb?](htt…”
- [claimed-docs] “If you are processing an error programmatically, consider using the type URI along with the status code.”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnStripe Billingnone0/10The evidence pack never mentions a Stripe test mode, sandbox environment, or test API keys — only general docs on billing features, CLI ("build, test, and manage... from the command line"), and MCP server access, none of which document an explicit non-production sandbox for safely testing AI-driven billing workflows. Since sandbox/test-mode support is a mainstream, applicable expectation for a billing platform, its absence here yields 'none' rather than 'na'.
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
Orbnone0/10The axis applies since billing/API platforms commonly offer sandbox/test environments, but the evidence pack never mentions a distinct sandbox or test-mode environment isolated from production data — only 'testing pricing changes against historical usage' (orb-docs-1), which is backtesting, not a sandbox. missing for 10: explicit sandbox/test-mode environment, API keys or docs distinguishing test vs live data, confirmation that test data never touches production.
- [claimed-docs] “Test pricing changes against historical usage before deploying.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnStripe Billingnone0/10The evidence pack covers Billing features, pricing, fees, and community reactions but contains no mention of API versioning scheme, version pinning, or a documented deprecation policy for the Stripe API. Missing for 10: any documentation of API version headers, changelog/versioning policy, or deprecation timelines.
Orbnone0/10No evidence pack item documents API versioning scheme or a deprecation policy; only error-response handling and general docs are covered. Missing for 10: versioning scheme (e.g., date-based API versions), deprecation/sunset policy, changelog or migration guides for breaking changes.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnStripe Billing exposes a full REST API, CLI, and MCP server that could be scripted for bulk actions, and docs mention importing many existing subscriptions from third-party systems in bulk. However, there is no explicit documentation of batch/bulk endpoints, rate-limit-aware bulk workflows, or AI-agent-specific bulk operation support beyond general API access. Missing for 10: explicit bulk/batch API endpoints, documented bulk operation patterns via CLI/MCP, and independent evidence of successful large-scale bulk usage.
- [claimed-docs] “You can import existing subscriptions from third-party billing systems (such as Zuora, Recurly, Chargify, or Chargebee) into Stripe Billing.”
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
- [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
Orb documents high-throughput event ingestion (1M+ events/sec) and backfilling historical usage events, which are forms of bulk data operations, but there is no explicit documentation of a bulk/batch API for operations like mass-editing subscriptions, invoices, or other resources. missing for 10: explicit bulk/batch API endpoints for subscriptions, invoices, or other catalog items; UI or API support for multi-item batch edits.
- [claimed-docs] “Handle 1M+ billing events per second in production deployments.”
- [claimed-docs] “If you want Orb to generate accurate invoices or analytics based on prior usage data, you can backfill events.”
- [claimed-docs] “Orb provides per-event idempotency through the API to guarantee that duplicates are never processed within the account grace period.”
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round drawnStripe Billing ships built-in automations tied to events (Smart Retries triggers on failed payment events, entitlements auto grant/revoke access) and exposes webhooks so developers can build custom event-triggered actions, satisfying the spirit of 'rules trigger actions on events.' However, there's no documented no-code/rule-builder interface for defining arbitrary trigger-condition-action rules — webhooks require custom code to consume events. Missing for 10: a dedicated rules/automation engine or UI for defining conditional triggers, and evidence of AI-native/agent-configurable rule definition beyond raw webhooks.
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”
- [claimed-docs] “Determine when you can grant or revoke product feature access to customers.”
- [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
Orb offers usage-threshold alerts and a real-time webhooks system that fires on defined events, which functions as event-triggered automation, and dunning/invoice issuance include automatic rule-based actions (auto-retry, auto-issue). However, these are fixed, product-specific automations rather than a general user-defined rules/actions engine (no evidence of custom conditional logic, multi-step workflows, or arbitrary action definitions). Missing for 10: a general-purpose rule builder, evidence of custom conditional logic beyond thresholds, and support for arbitrary automated actions beyond alerts/webhooks/dunning.
- [claimed-docs] “Trigger alerts at usage thresholds to power product-led growth.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to Stripe BillingStripe Billing's core function is automating recurring billing workflows (subscriptions, trials, retries, prorations) and it exposes an API, CLI, and MCP server that let an AI-native user programmatically create/manage these recurring billing schedules. However, this is scoped to billing/subscription recurrence, not general-purpose job/workflow scheduling, and there's no explicit documentation of a 'subscription schedule' or cron-like workflow orchestration primitive beyond subscriptions/retries. missing for 10: dedicated subscription-schedule/workflow-scheduling docs, independent hands-on confirmation of AI-agent-driven recurring job setup via MCP/CLI.
- [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
- [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”
- [claimed-docs] “Use the Trial Offer API to manage both free and paid introductory periods for your subscriptions with a single API integration.”
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
- [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
Orb offers some built-in recurring automated processes—daily scheduled data exports, automatic dunning retries on fixed day intervals, and automatic invoice issuance after grace periods—which are recurring, schedule-driven jobs, but these are fixed billing-domain behaviors rather than a general-purpose scheduler or workflow engine that an AI-native user could configure for arbitrary recurring tasks. Missing for 10: a documented job/workflow scheduling API or UI, support for custom recurrence rules or triggers beyond billing events, and any evidence of user-defined automation workflows.
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
Billing agent access — stories about billing agent access in this arenaBilling agent access
Stories about billing agent access in this arena
Agent operations
ai-native userAn agent can operate my billing — create a subscription, apply a credit, change a plan — through a programmatic surface with scoped permissions
weight 3 · round to Stripe BillingStripe Billing exposes a full programmatic Subscriptions API (create, change plan, proration preview) and an official MCP server letting AI agents interact with the Stripe API, which supports the 'agent operates billing programmatically' story. However, the evidence never documents scoped/restricted permission controls for agent access, nor explicit 'apply a credit' functionality, so the scoped-permission and credit-specific parts of the story are unevidenced. Missing for 10: documented scoped/restricted API key or permission model for agent use, explicit credit-application API evidence, and independent corroboration of the MCP server's agent workflows.
- [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
- [claimed-docs] “You can preview a proration to view the amount before applying the changes.”
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
Orb documents a full programmatic surface for the core actions an agent would need: creating subscriptions via API (orb-docs-8), editing subscription pricing/config (orb-docs-10, orb-docs-11), and plan changes with automatic proration credit (orb-docs-16). However, there is no evidence of a scoped-permission or API-key-role model that would let an agent operate with restricted access rather than full account credentials — the error-handling doc (orb-docs-15) only covers error codes, not auth scopes, and the OpenAPI spec probe returned 404s (orb-probe-2), leaving the permission-scoping mechanism unverified. missing for 10: documented scoped API keys/OAuth roles for agent-level permissions, an official agent/MCP-style integration, independent confirmation that these endpoints support least-privilege access.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
Agent queries
ai-native userAn agent can answer questions about my billing state — MRR, delinquent accounts, upcoming renewals, a customer's invoices — by querying the platform directly
weight 2 · round to Stripe BillingStripe ships an official MCP server explicitly for AI agents to interact with the Stripe API (docs-18, probe-4), which would let an agent query subscriptions, invoices, and customer records directly; docs also show subscription/invoice/analytics APIs (docs-2, docs-8, docs-11) that could back such queries. However, there's no direct evidence the MCP/API surfaces higher-level billing-state metrics like MRR or delinquency status as first-class queryable objects, and analytics is described as dashboard-facing rather than agent-facing. Missing for 10: explicit MCP tool/API documentation for MRR aggregation, delinquent-account flags, and renewal-forecast queries, plus any hands-on agent demo confirming these questions can be answered end-to-end.
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
- [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
- [claimed-docs] “Create, customize, and send a Stripe-hosted invoice from the Dashboard, with no code required.”
- [claimed-docs] “Monitor overall performance at a glance”
Orbnone0/10Evidence covers billing mechanics (dunning, revenue recognition, invoice issuance, exports) but nothing shows an agent-facing query interface for aggregate billing state like MRR, delinquent-account lists, or renewal schedules — no MCP server, natural-language API, or reporting endpoint is documented, and the openapi probe returned 404s, undermining even basic API discoverability for an autonomous agent.
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
- [claimed-docs] “Orb automatically calculates recognized revenue in a way that accords with ASC606 guidelines.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
Billing math — stories about billing math in this arenaBilling math
Stories about billing math in this arena
Billing cycles
ops userControl billing anchors and cycles — calendar vs anniversary billing, alignment across a customer's subscriptions, custom invoice dates
weight 2 · round to OrbStripe Billingnone0/10The evidence pack covers subscriptions, usage-based pricing, prorations, trials, and invoicing generally, but nothing documents billing_cycle_anchor controls, calendar-vs-anniversary billing options, cross-subscription alignment, or custom invoice date setting. Missing for 10: any doc/community mention of billing cycle anchor parameters, alignment across subscriptions, or custom invoice date configuration.
Docs confirm subscriptions can be aligned to the creation date (anniversary billing) and that billing cycle alignment is configurable, but there's no explicit evidence of calendar-vs-anniversary toggle, cross-subscription cycle alignment for a single customer, or custom invoice date overrides. Missing for 10: explicit calendar billing option, multi-subscription alignment mechanics, custom invoice date configuration.
- [claimed-docs] “Orb also allows you to align the billing cycles with the date that the subscription was created.”
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
Proration
finance leadMid-cycle upgrades and downgrades are prorated with documented, auditable math — credits, partial periods, and invoice line items that reconcile to the penny
weight 3 · round to OrbStripe docs confirm proration is supported with a preview capability before applying changes, giving finance teams visibility into charges before invoicing, and invoices/line items are generated automatically. However, there is no documented detail on the exact proration math methodology (day-count conventions, rounding rules), no auditable reconciliation reports, and no independent/community evidence confirming penny-level accuracy in practice. missing for 10: detailed documented proration formula/rounding rules, audit trail/reconciliation reporting for finance teams, independent verification of penny-accurate reconciliation.
- [claimed-docs] “You can preview a proration to view the amount before applying the changes.”
- [claimed-docs] “Create, customize, and send a Stripe-hosted invoice from the Dashboard, with no code required.”
Orb documents day-based proration on plan changes, credits for unused time, a preview of billing/invoice impact before saving edits, and minimum/maximum charge handling — supporting the core proration and invoice line-item math. However, there is no explicit documentation of penny-level reconciliation guarantees, detailed audit trails, or worked examples showing exact credit/debit math across partial periods. missing for 10: worked/auditable proration examples, explicit 'reconciles to the penny' guarantee, audit-log/traceability documentation for finance review.
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Minimums: Ensures a minimum charge is applied. Maximums: Caps the charge at a certain amount.”
Dunning recovery — stories about dunning recovery in this arenaDunning recovery
Stories about dunning recovery in this arena
Card recovery
ops userExpiring or replaced cards update themselves — network account updater, backup payment methods, and hosted update-payment pages
weight 2 · round to Stripe BillingStripe's customer portal (docs-12, docs-13) provides hosted pages where customers can update payment methods, and Smart Retries (docs-5, docs-6) addresses failed payment recovery, but the evidence pack never mentions a network account updater service or backup/secondary payment methods functionality explicitly. missing for 10: explicit documentation of card network account updater, backup payment method fallback logic, and independent confirmation these auto-update cards without customer action.
- [claimed-docs] “Give your customers the ability to manage their account by setting up a customer portal.”
- [claimed-docs] “Use the Dashboard to activate the customer portal and optionally customize branding and prefill customer email addresses.”
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”
Orbnone0/10Evidence covers dunning retry scheduling (orb-docs-19) but there is no mention of network account updater, backup payment methods, or hosted update-payment pages anywhere in the pack, so the specific card-self-update capability is unevidenced.
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
Dunning comms
ops userConfigure automated dunning sequences — branded emails, in-app banners, grace periods, and final-state rules like cancel vs unpaid
weight 2 · round drawnStripe Billing docs confirm automated Smart Retries to recover failed payments, which is the core of dunning automation, but the evidence pack lacks any mention of branded dunning emails, in-app banners, configurable grace periods, or explicit final-state rules (cancel vs. mark-unpaid) that the story requires. missing for 10: branded email templates, in-app banner configuration, grace period settings, explicit cancel-vs-unpaid final state rules.
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”
Orb docs confirm basic dunning mechanics — automatic payment retries at 1/4/9 days (orb-docs-19) and automatic vs manual invoice issuance after grace periods (orb-docs-21) — but there is no evidence of branded/customizable dunning emails, in-app banners, or configurable final-state rules like cancel vs unpaid. missing for 10: branded email templates, in-app banner/notification configuration, customizable grace period settings beyond fixed retry schedule, and explicit cancel-vs-unpaid final state logic.
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
Smart retries
finance leadFailed renewal payments are retried automatically on an ML- or schedule-optimized cadence that measurably recovers involuntary churn
weight 3 · round to Stripe BillingStripe Billing documents Smart Retries, an automated system that retries failed subscription/invoice payments to reduce involuntary churn, directly matching the story's core ask (docs-5, docs-6). However, evidence doesn't detail ML- or schedule-optimization mechanics, retry cadence customization, or quantified recovery metrics, and community evidence focuses on pricing/fees rather than corroborating recovery effectiveness. Missing for 10: independent/hands-on evidence of measurable churn recovery impact, specifics on the ML/schedule optimization logic, and customer-facing proof of recovered revenue rates.
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”
Orb documents automatic dunning retries on a fixed schedule (1, 4, and 9 days after failed payment) via its 'essential-dunning' feature, which addresses the schedule-optimized retry cadence for involuntary churn recovery. However, there is no evidence of ML-based optimization of retry timing, nor any documented metrics or case studies showing measurable churn recovery impact. Missing for 10: ML-driven retry optimization, evidence of measured recovery rates/churn reduction, configurability of retry cadence per customer segment.
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
Entitlements — stories about entitlements in this arenaEntitlements
Stories about entitlements in this arena
Entitlement checks
developerFeatures and limits are modeled as entitlements attached to plans, and my application can check a customer's entitlements at runtime via API or SDK
weight 3 · round to Stripe BillingStripe explicitly documents an Entitlements feature for granting/revoking product feature access to customers, matching the story's core idea of feature entitlements tied to products/plans, but the evidence pack gives only a single high-level doc link with no detail on the runtime API/SDK check flow or independent corroboration. missing for 10: specifics on the Entitlements API/SDK call for runtime checks, code examples, and community or hands-on validation of the feature.
- [claimed-docs] “Determine when you can grant or revoke product feature access to customers.”
Orbnone0/10The evidence pack covers subscriptions, plans, usage metrics, invoicing, and revenue recognition, but nowhere mentions entitlements, feature-level access modeling, or an API/SDK for checking a customer's entitlements at runtime. Since billing platforms plausibly could offer such a feature, the axis applies, but there is no supporting evidence.
Plan versioning
ops userChange pricing without breaking existing subscribers — versioned plans, grandfathering, and bulk migration tools for moving cohorts to new prices
weight 2 · round to OrbStripe docs show proration previews for subscription changes and a tool for importing subscriptions from third-party billing systems, which touch on the mechanics of adjusting pricing without immediately breaking billing, but there is no documentation of explicit 'versioned prices' grandfathering existing subscribers, nor a dedicated bulk cohort-migration tool for moving groups of subscribers to new prices. Missing for 10: explicit grandfathering/versioned-plan documentation, a bulk cohort price-migration API/tool, and independent evidence that ops teams use it this way.
- [claimed-docs] “You can preview a proration to view the amount before applying the changes.”
- [claimed-docs] “You can import existing subscriptions from third-party billing systems (such as Zuora, Recurly, Chargify, or Chargebee) into Stripe Billing.”
- [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
- [claimed-docs] “Determine when you can grant or revoke product feature access to customers.”
Orb documents subscription-level pricing edits with pre-save impact previews, proration on plan changes, and a Stripe migration path with usage backfill — enabling controlled repricing without breaking existing invoices. But there is no explicit documentation of plan versioning, formal grandfathering mechanisms, or a bulk cohort-migration tool for moving many subscribers to new prices at once. missing for 10: explicit plan-versioning/grandfathering feature, bulk cohort migration tooling beyond one-off Stripe import, evidence of moving existing subscriber cohorts to a new plan version at scale.
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [claimed-docs] “Orb supports a seamless migration from Stripe Billing, whether you're using flat-rate subscriptions, usage-based pricing, pricing on seats, …”
- [claimed-docs] “If you want Orb to generate accurate invoices or analytics based on prior usage data, you can backfill events.”
- [claimed-docs] “Test pricing changes against historical usage before deploying.”
Invoicing tax — stories about invoicing tax in this arenaInvoicing tax
Stories about invoicing tax in this arena
Invoices
ops userThe platform generates compliant invoices, credit notes, and receipts — sequential numbering, custom fields, memos — delivered to customers automatically
weight 2 · round to OrbDocs confirm Stripe Billing/Invoicing can create, customize, and automatically send hosted invoices from the Dashboard (stripe-billing-docs-8), but the evidence never explicitly documents sequential invoice numbering, credit notes, receipts, or memo/custom-field compliance details, and a community comment even claims Stripe historically lacked easy 'email invoicing' compared to competitors (stripe-billing-comm-6). missing for 10: explicit documentation of sequential numbering, credit note generation, receipt issuance, and memo/custom field support with independent corroboration that these are compliant and automated end-to-end.
- [claimed-docs] “Create, customize, and send a Stripe-hosted invoice from the Dashboard, with no code required.”
- [community] “A team said they were 'writing code to move from stripe to recurly/adyen' citing that 'the analytics/easy plan mgmt and email invoicing in r…”
- [community] “Confusion among users about what Stripe Billing actually includes: 'I thought Stripe Billing referred to the Customer Portal functionality a…”
Orb documents automatic invoice issuance, proration/minimums/maximums calculations, and revenue recognition, indicating invoices are generated and delivered automatically, but there is no explicit evidence of sequential invoice numbering, credit note generation, receipts, or custom fields/memos on invoices. missing for 10: sequential numbering guarantees, credit note issuance, receipt generation, custom fields/memo support on invoices, and independent confirmation of compliance formatting.
- [claimed-docs] “Minimums: Ensures a minimum charge is applied. Maximums: Caps the charge at a certain amount.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
- [claimed-docs] “Orb automatically calculates recognized revenue in a way that accords with ASC606 guidelines.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
Multi currency
finance leadBill customers in their local currency with per-currency price points and consolidated reporting in my home currency
weight 2 · round to Stripe BillingStripe Billing supports subscriptions and analytics, but a Stripe PM confirmed that multi-currency pricing currently requires creating a separate plan per currency rather than a single price point with per-currency variants, and reporting/analytics is mentioned only generically without evidence of home-currency consolidation across currencies. missing for 10: native single-price multi-currency price points (not per-currency plan duplication), documented consolidated/rollup reporting in home currency across multiple billing currencies, independent confirmation of this workflow.
- [community] “For multi-currency subscriptions, Stripe PM confirmed you currently need to create a separate plan per currency (e.g. bronze_plan:eur), sinc…”
- [claimed-docs] “Monitor overall performance at a glance”
- [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
Tax
finance leadSales tax, VAT, and GST are calculated on every invoice — natively or through a first-class tax integration — with the right registrations and rates
weight 2 · round to Stripe BillingStripe Tax is documented as a native, first-class feature that automates sales tax, VAT, and GST compliance directly within the Stripe ecosystem (stripe-billing-docs-15), aligning with Stripe Billing's invoicing flow. Missing for 10: independent/hands-on corroboration of tax calculation accuracy and detail on how registrations/rates are managed across multiple jurisdictions beyond the single doc reference.
- [claimed-docs] “Automate sales tax, VAT, and GST compliance on all your transactions.”
- [claimed-docs] “Create, customize, and send a Stripe-hosted invoice from the Dashboard, with no code required.”
Orbnone0/10The evidence pack covers billing, metering, revenue recognition, dunning, and invoicing calculations but contains no mention of sales tax, VAT, GST calculation, tax registrations, or a first-class tax integration (e.g., Avalara, Stripe Tax). This is a fair axis for a billing/invoicing platform, so absent evidence yields 'none' rather than 'na'.
Migration portability — stories about migration portability in this arenaMigration portability
Stories about migration portability in this arena
Export
finance leadExport every subscription, invoice, and usage record — and port stored payment methods out to another provider — if I choose to leave
weight 2 · round to OrbStripe Billingnone0/10Evidence only documents importing subscriptions *into* Stripe from other providers (Zuora, Recurly, etc.) and migrating customer/payment data *to* Stripe — the reverse direction (exporting subscriptions/invoices/usage and porting stored payment methods to another provider) is never documented. Community evidence even shows a team having to 'write code to move from stripe to recurly/adyen' themselves, implying no built-in export/portability tool exists.
- [claimed-docs] “You can import existing subscriptions from third-party billing systems (such as Zuora, Recurly, Chargify, or Chargebee) into Stripe Billing.”
- [claimed-docs] “Migrating your customer and payments data to Stripe is a multi-step process.”
- [community] “A team said they were 'writing code to move from stripe to recurly/adyen' citing that 'the analytics/easy plan mgmt and email invoicing in r…”
Orb documents managed daily data exports of resource types to any destination (orb-docs-12) and revenue/financial exports (orb-docs-7), which could cover subscriptions/invoices/usage, but there is no evidence describing exporting stored payment methods or any outbound migration path — the only migration content covers importing customers *into* Orb from Stripe (orb-docs-13, orb-docs-14), not leaving Orb for another provider. Missing for 10: explicit payment-method export/portability, confirmation that exports cover all three record types comprehensively, and documentation of an outbound/offboarding migration process.
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
- [claimed-docs] “Track recognized and deferred revenue with exports for financial systems.”
- [claimed-docs] “Orb supports a seamless migration from Stripe Billing, whether you're using flat-rate subscriptions, usage-based pricing, pricing on seats, …”
- [claimed-docs] “If you want Orb to generate accurate invoices or analytics based on prior usage data, you can backfill events.”
Import
ops userMigrate live subscriptions in from a spreadsheet or a competing platform — including PCI-compliant card data transfer — without customers noticing
weight 3 · round to Stripe BillingDocs explicitly cover importing subscriptions from competing platforms like Zuora, Recurly, Chargify, and Chargebee (docs-10) and a general 'multi-step' customer/payments data migration guide (docs-17), which supports the platform-migration part of the story. However there is no evidence of spreadsheet-based import, no detail on PCI-compliant card data transfer mechanics, and no confirmation that migrated subscriptions continue billing seamlessly without customer-visible disruption. Missing for 10: spreadsheet import support, explicit PCI-compliant card token transfer process, and evidence/testimony that migration is invisible to end customers.
- [claimed-docs] “You can import existing subscriptions from third-party billing systems (such as Zuora, Recurly, Chargify, or Chargebee) into Stripe Billing.”
- [claimed-docs] “Migrating your customer and payments data to Stripe is a multi-step process.”
Orb documents migration from Stripe Billing (including flat-rate, usage-based, seat pricing) and backfilling historical usage events for accurate invoicing, which supports competing-platform migration. However there is no evidence of spreadsheet-based import tooling, PCI-compliant card/payment-method data transfer, or explicit assurances that migration is seamless enough that customers won't notice. Missing for 10: spreadsheet import support, PCI-compliant card data transfer mechanism, and documentation/testimony of zero customer disruption during migration.
- [claimed-docs] “Orb supports a seamless migration from Stripe Billing, whether you're using flat-rate subscriptions, usage-based pricing, pricing on seats, …”
- [claimed-docs] “If you want Orb to generate accurate invoices or analytics based on prior usage data, you can backfill events.”
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnStripe's API covers most Billing operations (subscriptions, usage-based pricing, prorations, trials, entitlements, invoicing) and there's also a CLI and MCP server for programmatic/agent access, but some UI-only features are explicitly dashboard-driven with no-code framing (e.g., hosted invoice creation, customer portal branding/activation), and community comments note gaps like easy plan management/analytics parity versus competitors. missing for 10: confirmation that customer portal setup/branding and dashboard-only analytics views are fully API-configurable, independent verification of full UI/API parity, and evidence addressing feature gaps raised by users (e.g., portal customization, analytics).
- [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
- [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
- [claimed-docs] “You can preview a proration to view the amount before applying the changes.”
- [claimed-docs] “Determine when you can grant or revoke product feature access to customers.”
- [claimed-docs] “Use the Dashboard to activate the customer portal and optionally customize branding and prefill customer email addresses.”
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [community] “A team said they were 'writing code to move from stripe to recurly/adyen' citing that 'the analytics/easy plan mgmt and email invoicing in r…”
- [community] “Confusion among users about what Stripe Billing actually includes: 'I thought Stripe Billing referred to the Customer Portal functionality a…”
Docs show many UI actions—creating subscriptions, editing subscriptions, configuring billing metrics, exports, webhooks—are explicitly available via API endpoints (orb-docs-8, orb-docs-10, orb-docs-12, orb-doces-18, orb-docs-23), suggesting strong UI/API parity for core billing workflows. However there is no explicit blanket claim that 'everything in the UI is possible via API,' and a probe for a public OpenAPI/swagger spec returned 404s, weakening confidence in full documented API surface coverage. missing for 10: an explicit parity statement, a discoverable full API reference/OpenAPI spec, and confirmation that dashboard-only features (e.g., invoice approval UI, analytics dashboards) have full API equivalents.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
- [claimed-docs] “A billable metric consists of event filters as well as an aggregation clause.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to OrbStripe Billingnone0/10Evidence covers importing/migrating data INTO Stripe Billing (from Zuora, Recurly, etc.) but nothing about exporting a merchant's own subscription/invoice/customer data out in open formats to leave the platform. No documentation of a data export or portability tool for departing customers.
- [claimed-docs] “You can import existing subscriptions from third-party billing systems (such as Zuora, Recurly, Chargify, or Chargebee) into Stripe Billing.”
- [claimed-docs] “Migrating your customer and payments data to Stripe is a multi-step process.”
Orb supports managed daily exports of resource types to a destination of choice and revenue/financial exports, which gives data portability, but this is billing-data export for downstream systems rather than a full account-level open-format export-and-leave capability aimed at an AI-native user. missing for 10: explicit full account/data export (all entities, configs, historical events) in open formats, documented data portability/deletion workflow for leaving the platform, and independent confirmation of export completeness.
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
- [claimed-docs] “Track recognized and deferred revenue with exports for financial systems.”
ai-native userRead the product's source under an open license
weight 2 · round drawnStripe Billingnone0/10Stripe Billing is a closed-source SaaS product; there is no evidence of any open-licensed source code being available for inspection. Documentation, CLI, and MCP server are all provided, but none imply open-source availability of the underlying product code.
ai-native userSelf-host the core product
weight 3 · round drawnStripe Billingnone0/10The 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.)
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnStripe Billingnone0/10No evidence in the pack discusses data residency, regional storage options, or data sovereignty controls for Stripe Billing; the axis applies to a payments/data platform like Stripe but is unaddressed here.
ai-native userControl data retention and deletion
weight 2 · round drawnStripe Billingnone0/10The evidence pack covers subscriptions, invoicing, tax, portal, MCP/CLI tooling, and pricing complaints, but nothing addresses data retention policies, deletion controls, or privacy/data lifecycle management for AI-native users. Missing for 10: any documentation on data retention settings, deletion/erasure APIs, or privacy controls for customer/usage data.
Orbnone0/10The evidence pack covers billing, invoicing, revenue recognition, and data exports, but contains no mention of customer data retention policies, deletion APIs, or privacy controls for AI-native users. This is an applicable axis for any SaaS handling customer data, but there is no evidence Orb provides retention/deletion controls.
Revenue recognition — stories about revenue recognition in this arenaRevenue recognition
Stories about revenue recognition in this arena
Analytics
founderI get MRR, churn, cohort retention, and LTV analytics computed from the billing source of truth, not a bolted-on BI export
weight 2 · round to OrbStripe Billingdisputedcontradicted4/10Stripe's docs only vaguely reference subscription analytics ('Monitor overall performance at a glance') with no explicit mention of MRR, churn, cohort retention, or LTV computation, and community evidence directly contradicts the claim that Stripe provides adequate built-in analytics, with one team citing lack of analytics as a reason for migrating away from Stripe Billing to Recurly. missing for 10: explicit documentation of MRR/churn/cohort/LTV dashboards, independent confirmation that these metrics are computed natively rather than requiring external BI tools.
- [claimed-docs] “Monitor overall performance at a glance”
- [community] “A team said they were 'writing code to move from stripe to recurly/adyen' citing that 'the analytics/easy plan mgmt and email invoicing in r…”
Orb documents revenue-related metrics computed from billing data itself (accrued revenue, recognized/deferred revenue per ASC606, expansion forecasting) rather than a bolted-on BI export, and supports data exports/SQL for custom analytics. However, there is no explicit mention of MRR, churn, cohort retention, or LTV dashboards as native analytics features — these appear to require building via SQL/export rather than being out-of-the-box computed metrics. missing for 10: explicit MRR/churn/cohort retention/LTV dashboards or reports, evidence these are native computed analytics rather than DIY SQL queries, independent confirmation of accuracy/usability.
- [claimed-docs] “Track accrued revenue before invoices. Forecast and spot expansion.”
- [claimed-docs] “Build complex billing metrics with full SQL control.”
- [claimed-docs] “Track recognized and deferred revenue with exports for financial systems.”
- [claimed-docs] “Orb automatically calculates recognized revenue in a way that accords with ASC606 guidelines.”
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
Gl sync
finance leadInvoices, payments, and recognition entries sync to my general ledger or ERP — QuickBooks, Xero, NetSuite — so the close doesn't need CSV surgery
weight 2 · round to OrbStripe Billingnone0/10The evidence pack shows Stripe Billing's revenue recognition module (docs-7) and webhooks (docs-16) but contains no mention of native or documented sync to QuickBooks, Xero, NetSuite, or any ERP/GL system — only generic webhook/API primitives that a team would need to build custom integration on top of. Missing for 10: documented native connectors or partner integrations for QuickBooks/Xero/NetSuite, evidence of automated invoice/payment/rev-rec entry sync to a GL, and any customer account of eliminating manual CSV reconciliation.
- [claimed-docs] “Simplify your revenue recognition with automated support for global accounting standards”
- [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
- [claimed-docs] “Migrating your customer and payments data to Stripe is a multi-step process.”
Orb documents ASC606-compliant revenue recognition tracking and generic data exports 'for financial systems' to 'a data destination of your choice,' which could feed a GL, but no evidence names a native QuickBooks, Xero, or NetSuite connector or a no-CSV sync path — buyers would need to build the export pipeline themselves. Missing for 10: named ERP/accounting-system integrations, automated invoice/payment sync (not just data exports), and confirmation that no manual CSV mapping is required.
- [claimed-docs] “Track recognized and deferred revenue with exports for financial systems.”
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
- [claimed-docs] “Orb automatically calculates recognized revenue in a way that accords with ASC606 guidelines.”
Revrec reports
finance leadRevenue is recognized on an ASC 606 / IFRS 15 basis — deferred revenue schedules and audit-ready recognition reports straight from billing data
weight 3 · round to OrbStripe has a dedicated Revenue Recognition product that automates deferred revenue schedules per global accounting standards, directly matching the story's core intent, but the evidence pack gives only a single thin doc snippet with no mention of ASC 606/IFRS 15 specifically, no detail on audit-ready reporting outputs, and no independent/community corroboration of its use for finance audits. missing for 10: explicit ASC606/IFRS15 standard mapping, description of audit-ready report generation, independent or hands-on validation of the recognition reports.
- [claimed-docs] “Simplify your revenue recognition with automated support for global accounting standards”
Orb explicitly automates ASC606-compliant recognized/deferred revenue calculation (orb-docs-22), tracks accrued revenue before invoicing (orb-docs-4), and supports exporting recognized/deferred revenue data for financial systems (orb-docs-7), plus general data exports to downstream destinations (orb-docs-12). This covers the core finance-lead need of ASC606 deferred revenue schedules and exportable recognition data. missing for 10: no explicit mention of IFRS 15 compliance, no detail on audit-ready report formatting/controls, and no independent/hands-on corroboration beyond vendor docs.
- [claimed-docs] “Orb automatically calculates recognized revenue in a way that accords with ASC606 guidelines.”
- [claimed-docs] “Track accrued revenue before invoices. Forecast and spot expansion.”
- [claimed-docs] “Track recognized and deferred revenue with exports for financial systems.”
- [claimed-docs] “Orb supports managed, daily exports of resource types to your data destination of your choice.”
Subscription lifecycle — stories about subscription lifecycle in this arenaSubscription lifecycle
Stories about subscription lifecycle in this arena
Lifecycle api
developerCreate, update, pause, and cancel subscriptions through a documented API — the full lifecycle without touching a dashboard
weight 3 · round to Stripe BillingDocs confirm subscriptions can be created and updated via the Subscriptions API (including proration previews for changes) and trials/usage-based pricing are API-configurable, plus CLI/webhooks support programmatic workflows without the dashboard. However, explicit documentation of 'pause' and 'cancel' endpoints isn't present in the evidence pack, only implied by general subscription management docs. missing for 10: explicit doc citation for pause-subscription and cancel-subscription API endpoints, independent hands-on confirmation of full lifecycle via API only.
- [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
- [claimed-docs] “You can preview a proration to view the amount before applying the changes.”
- [claimed-docs] “Use the Trial Offer API to manage both free and paid introductory periods for your subscriptions with a single API integration.”
- [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/billing.md # Billing Create and manage subscriptions, track usage, and issue invoices. …”
- [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
Docs confirm subscription creation via API (orb-docs-8), billing cycle alignment (orb-docs-9), and editing subscription pricing with preview of impact (orb-docs-10, orb-docs-11), plus plan-change proration logic (orb-docs-16) — covering create/update well. However, no explicit documentation of 'pause' or 'cancel' subscription API endpoints appears in the evidence pack, and no OpenAPI/spec confirmation was found (orb-probe-2 shows 404s for spec files), so full lifecycle coverage is unverified via API alone. Missing for 10: explicit pause/cancel endpoint documentation, confirmed OpenAPI spec listing all lifecycle operations, independent/hands-on verification of API-only workflow.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Orb also allows you to align the billing cycles with the date that the subscription was created.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.withorb.com/openapi.json, https://docs.withorb.com/swagger.json, https://docs.withorb.c…”
Lifecycle events
developerEvery subscription state change — renewal, upgrade, payment failure, cancellation — emits a webhook or event my systems can act on reliably
weight 2 · round to Stripe BillingDocs confirm Stripe pushes real-time webhook events for account changes (stripe-billing-docs-16) and describe automated retry logic for failed payments (stripe-billing-docs-5/6), supporting reliable notification of key lifecycle changes like renewals and payment failures. However, the pack lacks explicit documentation enumerating specific event types for upgrades/downgrades/cancellations or delivery-guarantee details (retries, signing, idempotency) tied directly to subscription state transitions. Missing for 10: explicit list of subscription-lifecycle event types (e.g., customer.subscription.updated/deleted), and evidence of webhook delivery reliability guarantees.
- [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Stripe Billing can automatically retry failed subscription and invoice payments for you.”
Orb documents a real-time webhooks system for triggering calls on event occurrence, and related lifecycle mechanics (dunning retries, proration on plan change, invoice issuance) exist, implying underlying state changes are trackable. However, the evidence never enumerates which specific lifecycle events (renewal, upgrade, cancellation, payment failure) fire webhooks, nor details delivery guarantees like retries/signing for reliability. Missing for 10: explicit list of webhook event types covering renewal/upgrade/cancellation/payment failure, documentation of delivery reliability guarantees (retries, at-least-once delivery, signature verification), and independent/hands-on confirmation of webhook reliability.
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
- [claimed-docs] “Orb will automatically retry the charge after 1, 4, and 9 days from the initial payment attempt.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [claimed-docs] “Automatic Issuance ... Invoices auto-issue after grace periods and buffers ... Manual Issuance ... All invoices require manual approval befo…”
Self serve
founderMy customers can upgrade, downgrade, or cancel themselves through a hosted portal or embeddable components, without a support ticket
weight 2 · round to Stripe BillingStripe docs explicitly describe a hosted Customer Portal that lets customers manage their own accounts (upgrade/downgrade/cancel) with Dashboard-based activation and branding, directly addressing self-service without support tickets. Community evidence corroborates the portal exists though notes some confusion over what's included and general pricing/product complaints unrelated to portal functionality itself. Missing for 10: independent hands-on report specifically confirming self-serve upgrade/downgrade/cancel flows work smoothly in production, and no mention of embeddable pricing-table/components for the same use case.
- [claimed-docs] “Give your customers the ability to manage their account by setting up a customer portal.”
- [claimed-docs] “Use the Dashboard to activate the customer portal and optionally customize branding and prefill customer email addresses.”
- [community] “Confusion among users about what Stripe Billing actually includes: 'I thought Stripe Billing referred to the Customer Portal functionality a…”
Orbnone0/10The evidence pack details subscription creation, edits, plan changes, and proration via the Orb UI or API, but nowhere mentions a hosted customer-facing portal or embeddable self-serve components that end customers could use to upgrade/downgrade/cancel without a support ticket. Missing for 10: any mention of a hosted billing portal, embeddable UI components, or self-serve customer-facing flows.
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Orb also allows you to align the billing cycles with the date that the subscription was created.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
Trials promos
ops userRun free trials, coupons, and promotion codes with automatic conversion to paid — including trial-end notifications required by card-network rules
weight 2 · round to Stripe BillingDocs confirm a Trial Offer API for free/paid trial periods and subscription automation (stripe-billing-docs-14, stripe-billing-docs-2), and community notes that Stripe emails (e.g., card update notices) are off by default and merchants can use webhooks instead (stripe-billing-comm-7), implying trial-end reminders aren't automatic out-of-the-box. No evidence pack items mention coupons or promotion codes specifically, nor explicit trial-end notification features required by card-network rules. missing for 10: coupon/promotion-code documentation, explicit trial-end notification/reminder feature docs, evidence of automatic trial-to-paid conversion flow, and confirmation of card-network compliance requirements being met.
- [claimed-docs] “Use the Trial Offer API to manage both free and paid introductory periods for your subscriptions with a single API integration.”
- [claimed-docs] “Create a new subscription in the Dashboard or with the Subscriptions API.”
- [community] “Stripe Billing PM stated all customer emails (like credit card update notices) are off by default, matching behavior of other Stripe emails,…”
Orbnone0/10The evidence pack covers subscriptions, proration, dunning, invoicing, and revenue recognition, but contains no mention of free trials, coupon/promotion codes, automatic trial-to-paid conversion, or trial-end notifications required by card-network rules. Since Orb is a subscription billing platform, this axis is a fair question, but there is no supporting evidence for these specific capabilities.
Usage metering — stories about usage metering in this arenaUsage metering
Stories about usage metering in this arena
Event ingestion
developerStream high-volume usage events — API calls, tokens, compute-seconds — into a metering pipeline with idempotent ingestion and backdating support
weight 3 · round to OrbThe evidence only shows generic usage-based subscription pricing support (stripe-billing-docs-3) with no documentation of a dedicated meter/usage-events API, idempotency keys, backdating of events, or high-volume streaming ingestion mechanics. Missing for 10: explicit meter events API docs, idempotent ingestion mechanism details, backdating/timestamp support evidence, high-volume throughput claims or benchmarks.
- [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
Orb's docs directly support high-volume streaming ingestion (1M+ events/sec), per-event idempotency guarantees, and backdating/backfill support for historical usage recalculation and invoice adjustment. missing for 10: independent/hands-on benchmarks corroborating the 1M+ events/sec claim, and more detail on the exact idempotency key mechanism/grace period edge cases.
- [claimed-docs] “Handle 1M+ billing events per second in production deployments.”
- [claimed-docs] “Orb provides per-event idempotency through the API to guarantee that duplicates are never processed within the account grace period.”
- [claimed-docs] “Late data handled safely. Orb recalculates affected invoices automatically.”
- [claimed-docs] “If you want Orb to generate accurate invoices or analytics based on prior usage data, you can backfill events.”
- [claimed-docs] “Test pricing changes against historical usage before deploying.”
Pricing models
finance leadPrice with tiered, volume, graduated, per-unit, and hybrid subscription-plus-usage models — including credits, commitments, and overage — without custom code
weight 3 · round to OrbDocs confirm Stripe Billing supports usage-based subscription pricing and custom pricing plans without code (stripe-billing-docs-1, stripe-billing-docs-3), and community corroborates per-user/per-usage/per-tier models (stripe-billing-comm-1). However, the evidence never explicitly documents tiered, volume, graduated, or per-unit pricing structures, nor credits, commitments, or overage billing mechanics as named capabilities. Missing for 10: explicit documentation of tiered/volume/graduated/per-unit price types, credits and commitment/overage billing constructs, and any hands-on confirmation these can be combined without custom code.
- [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
- [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
- [community] “Stripe Billing supports per-user, per-usage, and per-tier subscription models in an automated recurring billing fashion, covering the 3 stan…”
Orb's docs cover billable metrics with flexible aggregation/SQL (orb-docs-5, orb-docs-18), subscription edits and plan changes with proration (orb-docs-10, orb-docs-16), minimums/maximums for commitments and overage (orb-docs-20), and subscription/plan configuration via UI or API — collectively supporting tiered, volume, graduated, per-unit, and hybrid subscription+usage pricing without custom code. missing for 10: explicit named documentation pages for each pricing model (tiered/volume/graduated) and credits/prepaid commitment mechanics, plus independent (non-vendor) confirmation of these pricing structures in production use.
- [claimed-docs] “Build complex billing metrics with full SQL control.”
- [claimed-docs] “A billable metric consists of event filters as well as an aggregation clause.”
- [claimed-docs] “Subscription Edits let you change a single subscription's pricing configuration ... without changing the plan itself.”
- [claimed-docs] “Preview the billing and invoice impact before you save, so you can confirm how charges and invoices will look.”
- [claimed-docs] “Orb will credit the customer an amount corresponding to the portion of the time period that was left unused using day-based proration.”
- [claimed-docs] “Minimums: Ensures a minimum charge is applied. Maximums: Caps the charge at a certain amount.”
- [claimed-docs] “You can create a subscription either from the Orb UI or via the subscription creation API endpoint.”
- [claimed-docs] “Orb also allows you to align the billing cycles with the date that the subscription was created.”
Usage visibility
ops userCustomers and my team can see current-cycle usage and accrued cost in real time, with thresholds and alerts before an invoice surprises anyone
weight 2 · round to OrbStripe Billingnone0/10Evidence covers usage-based pricing setup, proration previews, and subscription analytics, but there is no mention of real-time usage dashboards for customers/team, configurable usage thresholds, or proactive alerts before invoicing. missing for 10: real-time usage/cost visibility for customers and team, threshold configuration, proactive alerting before invoice generation.
- [claimed-docs] “you can set up and integrate different types of usage-based pricing models with your SaaS product.”
- [claimed-docs] “Monitor overall performance at a glance”
Orb docs confirm accrued cost/revenue tracking before invoicing (orb-docs-4), configurable usage-threshold alerts for product-led growth (orb-docs-6), and real-time webhooks for event notifications (orb-docs-23), covering the core alerting/real-time-visibility ask. missing for 10: explicit evidence of a customer-facing self-serve usage dashboard and independent/hands-on confirmation that alerts reliably fire before invoice generation.
- [claimed-docs] “Track accrued revenue before invoices. Forecast and spot expansion.”
- [claimed-docs] “Trigger alerts at usage thresholds to power product-led growth.”
- [claimed-docs] “Orb provides a powerful, real-time webhooks system that can issue calls to an endpoint of your choosing when certain events take place.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableStripe Billingn/aStripe Billing is a SaaS billing/subscriptions platform, not an AI agent or assistant that would consume external MCP servers as tools; the evidence only shows Stripe exposing an MCP server for other agents to call into Stripe (docs-18, probe-4), which is the reverse direction. There is no product surface in Stripe Billing designed to plug in and use third-party MCP tools, making this axis a category error for this product type.
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableStripe Billingn/aStripe Billing is a billing/subscription management product, not an automation/workflow-building tool with version control of 'automations'; there is no concept of versioning, reviewing, or rolling back automations in this product's domain. This axis is a category error for a billing platform.
Orbn/aOrb is a usage-based billing and revenue platform, not an automation-building tool; it has no concept of 'automations' to version, review, or roll back. The evidence pack covers billing metrics, subscriptions, invoicing, and revenue recognition, none of which relate to versioning/rollback of automations, so this axis is a category mismatch for Orb's product type.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableStripe Billingn/aStripe Billing is a subscription/invoicing management product, not an AI model provider or data-processing service that trains AI models on user data; controlling AI training data usage is not an applicable axis for this product category.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableStripe Billingnone0/10Stripe Billing is a payments/subscription platform, not a developer tool with telemetry collection concerns, but no evidence addresses any telemetry/usage-tracking opt-out mechanism for AI-native users interacting with its API, CLI, or MCP server; the evidence pack contains no mention of telemetry at all.
Orbn/aOrb is a billing/revenue platform, not an AI agent or tool with telemetry collected from AI-native usage; the evidence pack contains no telemetry/analytics-opt-out feature relevant to an 'AI-native user's own tool usage tracking. This axis is a category mismatch for a billing infrastructure product.