Maxio

Overview

Maxio (formerly Chargify and SaaSOptics, merged in 2022) is a subscription billing and revenue management platform built specifically for B2B SaaS companies. It combines subscription lifecycle management, automated billing, revenue recognition (ASC 606 / IFRS 15), and SaaS financial metrics (MRR, ARR, churn, LTV) into a single platform. When integrated into a website, Maxio provides the hosted checkout interfaces and self-service billing portals that subscribers use to sign up, upgrade, downgrade, and manage their accounts.

Maxio serves mid-market and growth-stage SaaS companies that need billing automation beyond what Stripe Billing or Chargebee offer out of the box — particularly around complex pricing models (usage-based, hybrid, custom contracts) and SaaS-specific revenue reporting.

What This Script Does

Maxio's client-side scripts render hosted billing UI directly on the merchant's website or application:

Hosted checkout pages: Maxio's checkout scripts (js.chargify.com — the legacy domain still in use — or Maxio-branded equivalents) render subscription plan selection, quantity configuration, and payment method collection within the merchant's checkout flow. For payment collection, card details are entered into PCI-compliant hosted fields that tokenize the card data within Maxio's certified environment before it ever touches the merchant's servers.

Self-service billing portal: Existing subscribers access a Maxio-powered billing management portal embedded in the merchant's application. Through this portal, the script enables customers to update their payment method, switch subscription plans, add or remove components (for usage-based billing), view invoice history, download invoices, and cancel or pause subscriptions. These are explicit user-initiated actions.

Payment method management: The script handles secure tokenization of new payment methods (credit cards, ACH bank accounts) through Maxio's PCI-DSS Level 1 certified hosted fields. Actual card numbers never pass through the merchant's application server.

Session state cookies: Session cookies maintain checkout state so that customers progressing through a multi-step checkout (plan selection → billing details → confirmation) do not lose their selections on navigation. These cookies are strictly functional, scoped to the duration of the checkout or portal session, and do not persist beyond the active session.

Subscription event webhooks: While not browser-side, Maxio fires server-side webhooks on subscription events (signup, renewal, upgrade, cancellation) to the merchant's application. These are server-to-server and involve no client-side data collection.

No behavioral analytics: Maxio does not deploy behavioral tracking, session replay, advertising pixels, or marketing analytics. Its scripts are scoped to transactional billing functionality.

Consent & Compliance

Maxio scripts serve a purely functional and transactional purpose:

• GDPR / ePrivacy: Under the ePrivacy Directive, cookies and scripts that are strictly necessary for a service explicitly requested by the user are exempt from prior consent requirements. Maxio's checkout and billing portal scripts — which process payments and manage subscriptions at the user's explicit request — fall squarely within this exemption. The lawful basis under GDPR is Article 6(1)(b): performance of a contract.
• PCI-DSS: Maxio is PCI-DSS Level 1 certified. Payment card data is tokenized within Maxio's hosted field environment; merchants using Maxio's hosted checkout operate in a reduced PCI scope.
• CCPA/CPRA: Billing data (payment method, billing address, subscription plan) is collected under a service contract with the customer. This is not a "sale" of personal information under CCPA.
• EU-US transfers: Maxio is a US-based company. Merchants processing EU subscriber data through Maxio should have a DPA in place. Maxio participates in the EU-US Data Privacy Framework.

Should You Block This Without Consent?

No. Maxio scripts provide essential billing and checkout functionality — subscription sign-up, payment processing, and account management — that is strictly necessary for completing transactions the user has explicitly initiated. Blocking Maxio would prevent users from subscribing, paying, or managing their billing accounts.