Where the reviewed products stand
Compare documented control across the named products and routes. Open a review for its plan, region and agreement (this is a selected sample).
0–10 on both axes · Higher and further right means more documented control
Exact scores & review links (7)
| Vendor | Data access & portability | Build & act |
|---|---|---|
| Chargebee ↗ | 4.7* | 3.6* |
| Paddle ↗ | 4.7* | 3.8* |
| Recharge ↗ | 6.1* | 4.3* |
| Zuora ↗ | 4.7* | 2.7* |
| Recurly ↗ | 4.7* | 5.4* |
| Maxio Advanced Billing ↗ | 5.3* | 5.6* |
| Permute ↗Publisher self-assessment | 8.0* | 7.1* |
Axes average three dimensions each: access, third-party access and exit horizontally; action, continuity and business logic vertically. Fixed 0–10 scale, midlines at 5 (overall grades use separate weights). * Some evidence is unresolved. Marker colors identify companies, not score bands. How to read the map ↗
Permute is included as a reference (it owns this site and is a publisher self-assessment). Its score is excluded from sample averages. Read the Permute review ↗
Reviews distinguish subscription state, billing events and documented mutations. Portable records do not establish payment credentials or full configuration portability.
Compare the six dimensions
| Overall control | |
|---|---|
| Data access | |
| Third-party accessibility | |
| External action | |
| Continuity | |
| Data exit | |
| Business logic and customization | |
Product scopes, dates & reviews
Chargebee
Billing · Checked 2026-10-16
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Read findings and sources ↗Paddle
Billing · Checked 2026-10-16
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Read findings and sources ↗| Customer control | Chargebee ↗ | Paddle ↗ | Recharge ↗ | Zuora ↗ | Recurly ↗ | Maxio Advanced Billing ↗ | Permute ↗ |
|---|---|---|---|---|---|---|---|
| Category | Billing | Billing | Billing | Billing | Billing | Billing | Databases and data platforms |
| Overall control | |||||||
| Data access | |||||||
| Third-party accessibility | |||||||
| External action | |||||||
| Continuity | |||||||
| Data exit | |||||||
| Business logic and customization | |||||||
| Assessment scope | Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. | Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. | Recharge API 2021-11 / subscription records, updates and lifecycle webhooks; accepted partner OAuth and merchant-owned API tokens are distinct routes, separate from storefront tokens and payment vaults. | Zuora Billing REST / tenant-scoped OAuth, subscription object queries and subscription creation; Revenue and separately entitled Data Query/AQuA exports are not combined. | Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate. | Maxio Advanced Billing, formerly Chargify: subscription list/create/update and customer-managed API keys; Maxio Core has separate credentials and is not combined with this assessment. | Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. |
| Assessment checked | 2026-10-16 | 2026-10-16 | 2026-10-16 | 2026-10-16 | 2026-10-16 | 2026-10-16 | 2026-10-12 |
| Read the findings | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ |
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
Who can connect?
Yes No- Unknown
| Connection method | Customer credentials | Integrator credentials | Provider approval required |
|---|---|---|---|
| Chargebee ↗ | |||
| Chargebee scoped API access ↗ | - | ||
| Paddle ↗ | |||
| Paddle scoped API access ↗ | - | ||
| Recharge ↗ | |||
| Recharge scoped API access ↗ | |||
| Recharge customer-owned application ↗ | |||
| Zuora ↗ | |||
| Zuora scoped API access ↗ | - | ||
| Recurly ↗ | |||
| Recurly customer API ↗ | - | ||
| Maxio Advanced Billing ↗ | |||
| Maxio Advanced Billing customer API ↗ | - | ||
| Permute ↗ | |||
| Scoped customer REST / TypeScript SDK ↗ | |||
| Permissioned end-user MCP ↗ | |||
A check means the column applies to that route (customer credentials can still require provider approval). Report exports use the customer account without separate API credentials. Open a connection method for its authentication, requirements and last review date.
What each review covers
Chargebee ↗
Chargebee supports customer lists, customer creation and lifecycle events. Event IDs and resource versions help reconcile duplicates and ordering, while contractual reuse and complete replay retention remain unresolved.
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Paddle ↗
Paddle Billing exposes structured customers and a 90-day event stream. That window supports bounded gap recovery, while API credentials and event delivery do not establish complete service migration rights.
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Recharge ↗
Recharge exposes subscription updates and delete events through merchant tokens or approved partner OAuth. Failed webhook delivery can retry for 48 hours; missed history still needs current-state reconciliation.
Recharge API 2021-11 / subscription records, updates and lifecycle webhooks; accepted partner OAuth and merchant-owned API tokens are distinct routes, separate from storefront tokens and payment vaults.
Zuora ↗
Zuora exposes subscription records and creation operations through tenant OAuth. Query limits, API versions and entity boundaries require explicit choices; separate export products do not automatically establish one migration entitlement.
Zuora Billing REST / tenant-scoped OAuth, subscription object queries and subscription creation; Revenue and separately entitled Data Query/AQuA exports are not combined.
Recurly ↗
Recurly offers account and subscription APIs plus richer nightly export files. API keys are available across plans but grant full account access; Automated Exports has a separate upgrade condition and a limited file-retention window.
Recurly Subscriptions V3 account reads/create-update, subscription listing and optional nightly Automated Exports; standalone Revenue Recognition and other Recurly products are separate.
Maxio Advanced Billing ↗
Maxio Advanced Billing includes API access on all plans without an API charge. Subscription filters, webhooks and explicit reconciliation guidance support external copies, while cancellation blocks API requests and native workflow portability remains unestablished.
Maxio Advanced Billing, formerly Chargify: subscription list/create/update and customer-managed API keys; Maxio Core has separate credentials and is not combined with this assessment.
Permute ↗
Scoped APIs expose SQL reads, managed records and customer-authored operation code. Customer-built apps are supported, while complete workspace recovery, outbound CDC and minimum-plan access terms remain unresolved.
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.