Maxio
Connect your customers' Maxio Advanced Billing (formerly Chargify) sites so your product can manage subscriptions, read billing history, and update customer records without handling API key rotation yourself. The customer provides their API key once and Askel composes the Basic auth header on every request.
What you can do
Read subscriptions and their current state
Fetch subscriptions filtered by state (active, trialing, cancelled, past_due) along with product, customer, and billing details. Lets your product reflect real billing state without a separate webhook listener.
Create and update subscriptions
Provision a new subscription in the customer's Maxio site or upgrade and downgrade an existing one by changing the product handle. Covers proration settings and immediate versus next-renewal billing.
Manage subscription components and usage
Read component allocations and post metered usage events to quantity-based or metered billing components. Useful when your product drives usage that needs to be billed through Maxio.
Read and update customer records
Fetch customer profiles including email, billing address, and payment method status. Update email or address fields when they change in your product's CRM.
Create payment profiles
Add or update a credit card or ACH payment profile on a customer's account using Maxio's tokenized card handling, so your product can initiate billing setup without touching raw card data.
Pull invoices and billing events
Fetch issued invoices, credit notes, and billing event history for any subscription. Lets your product display accurate billing history without requiring direct Maxio portal access.
Syncing subscription activations from your marketplace to a customer's Maxio site
You sell a B2B marketplace platform. A customer, Halcyon Software Group, uses Maxio Advanced Billing as their subscription backend. When a new buyer activates a subscription through your marketplace, Halcyon wants a matching subscription created in their Maxio site immediately, so their billing team does not have to create it manually.
- 1
Customer provides the API key
Halcyon's billing admin logs into their Maxio site, copies the API key from Config and Integrations and API Keys, and pastes it into your product's connection form along with their Maxio subdomain (halcyon.chargify.com). Askel validates the credentials with a test call.
- 2
Product and component discovery
Askel reads Halcyon's Maxio product list and component catalog. Your product's setup wizard shows them and Halcyon maps each of your marketplace subscription tiers to the matching Maxio product handle.
- 3
Buyer activates on marketplace
A buyer completes checkout in your marketplace. Your product calls Askel to POST a subscription to Halcyon's Maxio site with the correct product handle, customer email, and billing details.
- 4
Usage events posted
If the subscription includes a metered component (for example, API calls), your product posts usage event records to Askel throughout the billing period. Askel forwards them to the matching component on the Maxio subscription.
- 5
Invoice fetched at period end
At the end of the billing period, your product reads the issued invoice from Askel and displays it in Halcyon's marketplace dashboard. Halcyon's billing team sees all invoices in both Maxio and your platform without manual reconciliation.
Basic auth
The customer provides their Maxio API key and subdomain (the part before .chargify.com). Askel composes a Basic auth header by base64-encoding the API key with the literal string x as the password field (the Maxio-standard format) on every request. The subdomain determines the per-customer host. Neither the API key nor the composed header ever reaches your servers.
How Askel sits between your product and the customer's system
FAQ for Maxio
Does this work with Maxio SaaS Metrics as well as Advanced Billing?+
How does the per-customer subdomain work?+
Can we operate in test mode using a Maxio sandbox site?+
What happens if the customer rotates their API key?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.