INTEGRATIONS
Maxio
How to connect Maxio to NoChurn: what to paste, what NoChurn does in Maxio and what it reads.
Connect
In NoChurn, test mode first, open Integrations, pick Maxio and paste the fields below (or send them to POST /v1/billing_connections with provider: "maxio"). Use the provider’s test or sandbox credentials in test mode. Secrets are stored encrypted and never returned by the API.
| Field | Where to find it |
|---|---|
subdomain | The part before .chargify.com, or the full address of an EU site (acme.ebilling.maxio.com). A site in test mode in Test mode |
api_keySECRET | Config › Integrations › API keys |
site_shared_keySECRET | Config › Settings › Site shared key: signs the webhooks |
The connection returns a webhook_url. Point Maxio’s webhook to it: Maxio signs its webhooks with the keys connected here, so there is no webhook secret to paste.
What NoChurn does
| Retries | Maxio retries the payment (its own retry settings). NoChurn sends the recovery emails. |
|---|---|
| Card update | The recovery emails link to Maxio’s own page where the customer updates the payment method. |
| Cancel flow offers | Applied in Maxio: discount. An offer the provider cannot apply reaches your backend as a billing.*_requested webhook. |
| Cancellation | A cancellation requested in the cancel flow is carried out in Maxio. |
| Disputes | Maxio handles disputes. NoChurn shows them on the customer’s timeline. |
| Events | NoChurn follows Maxio’s webhooks. |
| Import | The last 12 months are imported when you connect (POST /v1/billing_connections/{id}/backfill imports again). |
What NoChurn reads
- Customers and subscriptions
- Invoices, payments and failures
- Payment profile type and expiry
- Coupons and products, to build offers
What stays with Maxio: invoicing, taxes and the charge itself; your payment gateway; your products and prices. More on the Maxio integration page.