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
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.
The subscription API exposes structured subscription and related account/payment data.
Tips and Best Practices ↗
Subscription State; Synchronizing Your Database · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
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.
Subscription pages default to 20 and support up to 200 records.
Tips and Best Practices ↗
Synchronizing Your Database > page; per_page · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
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.
Subscription state and updated_at windows are documented.
Tips and Best Practices ↗
Synchronizing Your Database > date_field; state; start_date; end_date · Checked 2026-10-16
Access cost barrier 10.0/10
Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligible
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.
Advanced Billing API access is expressly included on all plans at no charge.
Tips and Best Practices ↗
Tips and Best Practices introduction · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
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.
Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
Advanced Billing API authentication ↗
API; HTTP Basic Authentication over TLS · Checked 2026-10-16
Downstream permission -
-
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.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
Advanced Billing API authentication ↗
API; HTTP Basic Authentication over TLS · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
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.
Create subscriptions; Update Subscription separately documents PUT /subscriptions/{subscription_id}.json.
Create Subscription ↗
Create Subscription > POST /subscriptions.json · Checked 2026-10-16
Update Subscription ↗
Update Subscription; PUT /subscriptions/{subscription_id}.json · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
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.
Customer-authored clients can communicate directly with Advanced Billing using API credentials.
Advanced Billing API authentication ↗
Authentication introduction; API · 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
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.
The provider documents webhooks and updated_at windows for subscription refresh.
Tips and Best Practices ↗
Getting Subscription States; Synchronizing Your Database · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
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.
Four concurrent calls per subdomain, 120-second timeouts and 429 slowdown/retry guidance are published.
Error Handling & Rate Limiting ↗
Rate-based Blocks; Concurrency; Timeout Limitation · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
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.
Subscription updates and cancellation states can be polled; hard-delete identity coverage is unestablished.
Tips and Best Practices ↗
Synchronizing Your Database > date_field=updated_at · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
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.
Overlap updated_at/start/end subscription filters to refetch changes since the prior sync. This supports current changed-record recovery, without durable event replay, deletion payloads or historical versions.
Tips and Best Practices ↗
Tips and Best Practices; filtering subscription changes · 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
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.
A locally cached copy and manual/API retrieval are explicitly supported.
Tips and Best Practices ↗
Getting Subscription States; Synchronizing Your Database · Checked 2026-10-16
Post-cancellation access Disclosure
Retrieval expressly prohibited at cancellation
Disclosure only; does not reduce planned-exit credit.
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.
API requests are blocked when the Advanced Billing subscription is cancelled; this finding concerns API access, not separate contractual assistance.
Error Handling & Rate Limiting ↗
API Access Limitations · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
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.
Portable current subscription records are documented; native configuration, gateway secrets and full historical completeness are unestablished.
Tips and Best Practices ↗
Subscription State; Synchronizing Your Database · 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
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.
External application code owns its local cache/reconciliation, without establishing native definition ownership.
Tips and Best Practices ↗
Getting Subscription States; Synchronizing Your Database · Checked 2026-10-16
Rights to custom logic -
-
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.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Advanced Billing API authentication ↗
API; HTTP Basic Authentication over TLS · 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
Customers manage site API keys under Config > Integrations with the integration-management permission. HTTP Basic uses the API key and a dummy password; these keys differ from the browser-side Maxio.js tokenization key pair and Maxio Core credentials.
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
Subscription lists support page/per_page (up to 200), state and updated_at date windows. The provider recommends maintaining a local copy, using webhooks and periodically reconciling subscriptions; ordinary list reads are not immutable history.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Maxio Advanced Billing customer API | HTTP Basic | Customer | Not confirmed | self service | 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
The current Advanced Billing guide says API access is included on all plans at no charge. This statement concerns the API access condition, not payment gateway fees, business subscription prices or separately scoped Maxio Core services.
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
Advanced Billing documents POST subscription creation and PUT subscription update. Mutations may initiate billing effects depending on fields and state; they need operation-specific validation and exact user approval, not an assumption that all edits are harmless metadata changes.
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
Use updated_at windows with overlap and periodic complete reconciliation as documented. Four concurrent API calls per subdomain are the stated limit; 429 responses require pausing and resuming more slowly, while hard-delete events and durable replay remain unestablished. Overlap updated_at/start/end subscription filters to refetch changes since the prior sync. This supports current changed-record recovery, without durable event replay, deletion payloads or historical versions.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedMaxio 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. Subscription updates and cancellation states can be polled; hard-delete identity coverage is unestablished. | Tips and Best Practices ↗Synchronizing Your Database > date_field=updated_atChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointMaxio 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. Overlap updated_at/start/end subscription filters to refetch changes since the prior sync. This supports current changed-record recovery, without durable event replay, deletion payloads or historical versions. | Tips and Best Practices ↗Tips and Best Practices; filtering subscription changesChecked 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 records can be retained externally before cancellation. The API guide explicitly blocks requests once the Advanced Billing subscription is cancelled, so an API-based exit copy must be obtained beforehand; this does not establish complete native configuration restore.
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
Customers can run external subscription-integration code (including their own state cache and reconciliation). The reviewed guides do not establish reusable ownership or independent execution of native billing workflow definitions.
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 scopeMaxio 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. The subscription API exposes structured subscription and related account/payment data. | Tips and Best Practices ↗Subscription State; Synchronizing Your DatabaseChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsMaxio 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. Subscription pages default to 20 and support up to 200 records. | Tips and Best Practices ↗Synchronizing Your Database > page; per_pageChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersMaxio 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. Subscription state and updated_at windows are documented. | Tips and Best Practices ↗Synchronizing Your Database > date_field; state; start_date; end_dateChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -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. Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved. | Advanced Billing API authentication ↗API; HTTP Basic Authentication over TLSChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligibleMaxio 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. Advanced Billing API access is expressly included on all plans at no charge. | Tips and Best Practices ↗Tips and Best Practices introductionChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -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. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | Advanced Billing API authentication ↗API; HTTP Basic Authentication over TLSChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainMaxio 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. Create subscriptions; Update Subscription separately documents PUT /subscriptions/{subscription_id}.json. | Create Subscription ↗Create Subscription > POST /subscriptions.jsonChecked 2026-10-16 Update Subscription ↗Update Subscription; PUT /subscriptions/{subscription_id}.jsonChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionMaxio 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. Customer-authored clients can communicate directly with Advanced Billing using API credentials. | Advanced Billing API authentication ↗Authentication introduction; APIChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksMaxio 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. The provider documents webhooks and updated_at windows for subscription refresh. | Tips and Best Practices ↗Getting Subscription States; Synchronizing Your DatabaseChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsMaxio 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. Four concurrent calls per subdomain, 120-second timeouts and 429 slowdown/retry guidance are published. | Error Handling & Rate Limiting ↗Rate-based Blocks; Concurrency; Timeout LimitationChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsMaxio 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. A locally cached copy and manual/API retrieval are explicitly supported. | Tips and Best Practices ↗Getting Subscription States; Synchronizing Your DatabaseChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | Retrieval expressly prohibited at cancellationMaxio 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. API requests are blocked when the Advanced Billing subscription is cancelled; this finding concerns API access, not separate contractual assistance. | Error Handling & Rate Limiting ↗API Access LimitationsChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedMaxio 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. External application code owns its local cache/reconciliation, without establishing native definition ownership. | Tips and Best Practices ↗Getting Subscription States; Synchronizing Your DatabaseChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -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. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | Advanced Billing API authentication ↗API; HTTP Basic Authentication over TLSChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedMaxio 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. Portable current subscription records are documented; native configuration, gateway secrets and full historical completeness are unestablished. | Tips and Best Practices ↗Subscription State; Synchronizing Your DatabaseChecked 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
- Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
- Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
- Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.