OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
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.
Structured read interface for the declared product and resources
Subscriptions ↗
Structured read interface for the declared product and resources · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
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.
Tutorial Step 4; GET subscriptions list
Custom customer portal tutorials: create API token ↗
Tutorial Step 4; GET subscriptions list · Checked 2026-10-16
Query expressiveness 7.5/10
Fixed object or report retrieval
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.
Subscription-specific lookup; broader filter expressiveness not established
Subscriptions ↗
Subscription-specific lookup; broader filter expressiveness not established · Checked 2026-10-16
Access cost barrier -
-
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.
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved
Custom customer portal tutorials: create API token ↗
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
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.
Partner application requires acceptance into the Agency or Technology Partner Program; OAuth authorization code flow
Creating a partner app ↗
Partner application requires acceptance into the Agency or Technology Partner Program; OAuth authorization code flow · Checked 2026-10-16
Downstream permission -
-
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.
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established
Custom customer portal tutorials: create API token ↗
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
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.
PUT /subscriptions/{subscription_id}; frequency/product update
Build a custom customer portal with the Recharge API ↗
PUT /subscriptions/{subscription_id}; frequency/product update · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
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.
Approved applications use the documented fixed API interfaces
Creating a partner app ↗
Approved applications use the documented fixed API interfaces · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
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.
Subscription created/updated/deleted webhooks
Webhook examples 2021-11 ↗
Subscription created/updated/deleted webhooks · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
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.
40-call bucket, two calls/second leak rate; rate-limit handling
API rate limits ↗
40-call bucket, two calls/second leak rate; rate-limit handling · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
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.
subscription/updated and subscription/deleted; cancellation distinct
Webhook examples 2021-11 ↗
subscription/updated and subscription/deleted; cancellation distinct · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
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.
Up to twenty deliveries over 48 hours; duplicate handling required
Using webhooks ↗
Up to twenty deliveries over 48 hours; duplicate handling required · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
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.
Customer-held structured API records within the declared resource scope
Subscriptions ↗
Customer-held structured API records within the declared resource scope · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
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.
Applicable post-cancellation retrieval clause not established by reviewed technical documentation
Custom customer portal tutorials: create API token ↗
Applicable post-cancellation retrieval clause not established by reviewed technical documentation · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
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.
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified
Subscriptions ↗
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
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.
Customer integration code can run outside the provider; native workflow authoring not established
Custom customer portal tutorials: create API token ↗
Customer integration code can run outside the provider; native workflow authoring not established · Checked 2026-10-16
Rights to custom logic -
-
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.
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved
Custom customer portal tutorials: create API token ↗
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Merchants create API tokens with selected scopes. A partner application requires acceptance into the Agency or Technology Partner Program and uses customer-approved OAuth scopes. Certain add-on or Pro scopes require additional approval.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
The customer-portal tutorial lists subscriptions and retrieves individual records. API version must be pinned; subscription cancellation leaves lifecycle state and differs from deletion. Customer and address relationships require separate retrieval.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Recharge scoped API access | OAuth 2.0 | Integration provider | Yes | Partner approval | 2026-10-16 |
| Recharge customer-owned application | API key | Customer | No | Customer-supplied credentials | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Minimum-plan API eligibility, production entitlement and fixed access fees remain unresolved. API token creation instructions do not establish a fee-free route.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
PUT /subscriptions/{id} changes product or delivery frequency. Updates can regenerate charges and remove upcoming skips or reschedule charges, so a record edit can affect future billing.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Subscription webhooks include created, updated and deleted events. Failed deliveries can retry 20 times over 48 hours, with duplicates possible; this is a redelivery policy rather than durable consumer replay.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesRecharge 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. subscription/updated and subscription/deleted; cancellation distinct | Webhook examples 2021-11 ↗subscription/updated and subscription/deleted; cancellation distinctChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointRecharge 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. Up to twenty deliveries over 48 hours; duplicate handling required | Using webhooks ↗Up to twenty deliveries over 48 hours; duplicate handling requiredChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Subscription JSON can be copied before cancellation, with customer/address relations retrieved separately. Vault credentials, historical versions and all native settings remain unverified; merchant-account cancellation rights are distinct from cancelling a buyer subscription.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
External applications can build customer portals and apply subscription rules through API operations. Native workflow rights and independent execution remain unresolved (a subscription schedule is not the entire recurring billing runtime).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeRecharge 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. Structured read interface for the declared product and resources | Subscriptions ↗Structured read interface for the declared product and resourcesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsRecharge 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. Tutorial Step 4; GET subscriptions list | Custom customer portal tutorials: create API token ↗Tutorial Step 4; GET subscriptions listChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Fixed object or report retrievalRecharge 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. Subscription-specific lookup; broader filter expressiveness not established | Subscriptions ↗Subscription-specific lookup; broader filter expressiveness not establishedChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredRecharge 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. Partner application requires acceptance into the Agency or Technology Partner Program; OAuth authorization code flow | Creating a partner app ↗Partner application requires acceptance into the Agency or Technology Partner Program; OAuth authorization code flowChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -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. Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved | Custom customer portal tutorials: create API token ↗Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -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. Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established | Custom customer portal tutorials: create API token ↗Reviewed access documentation; applicable downstream processing, AI and redistribution terms not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainRecharge 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. PUT /subscriptions/{subscription_id}; frequency/product update | Build a custom customer portal with the Recharge API ↗PUT /subscriptions/{subscription_id}; frequency/product updateChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesRecharge 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. Approved applications use the documented fixed API interfaces | Creating a partner app ↗Approved applications use the documented fixed API interfacesChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksRecharge 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. Subscription created/updated/deleted webhooks | Webhook examples 2021-11 ↗Subscription created/updated/deleted webhooksChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsRecharge 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. 40-call bucket, two calls/second leak rate; rate-limit handling | API rate limits ↗40-call bucket, two calls/second leak rate; rate-limit handlingChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsRecharge 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. Customer-held structured API records within the declared resource scope | Subscriptions ↗Customer-held structured API records within the declared resource scopeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -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. Applicable post-cancellation retrieval clause not established by reviewed technical documentation | Custom customer portal tutorials: create API token ↗Applicable post-cancellation retrieval clause not established by reviewed technical documentationChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedRecharge 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. Customer integration code can run outside the provider; native workflow authoring not established | Custom customer portal tutorials: create API token ↗Customer integration code can run outside the provider; native workflow authoring not establishedChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -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. Ownership and reusable export or independent execution of native workflow artifacts remain unresolved | Custom customer portal tutorials: create API token ↗Ownership and reusable export or independent execution of native workflow artifacts remain unresolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedRecharge 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. Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified | Subscriptions ↗Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverifiedChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest eligible plan and fixed API access fees
- Applicable downstream-use and customer cancellation terms
- Complete file, history and configuration recovery
- Native workflow artifact ownership and independent execution
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.