Payments and AI Credits

Each paid plan should clearly show price, billing period, included seats, included usage, AI-credit allowance, limits, overages and renewal/cancellation terms before payment.

The final checkout must identify the contracting entity, billing email, payment provider, tax/VAT handling and customer support route.

Plan changes, downgrades, upgrades, renewals, trials and failed-payment consequences must be visible before the customer accepts a paid plan.

AI credits or usage allowances may represent model calls, agent work, automations, file processing, knowledge-base operations, connected-tool use or other metered product activity.

The final policy must state whether credits expire, roll over, are refundable, can be transferred, are promotional, or are lost after cancellation.

The final product should define whether credits are a billing unit, usage allowance, promotional balance, prepaid pack or internal fair-use measure.

When limits are reached, Max AI may pause expensive work, ask for approval, require a plan upgrade, or stop new AI operations until more allowance is available.

Overage charges should not be enabled until the customer-facing checkout and terms clearly explain them.

A protective default is to block or ask for approval when usage is exhausted, instead of silently charging more.

Max AI may keep usage, billing, plan, credit and payment-provider records to operate invoices, limits, credits, support and disputes.

The final policy should define how customers can raise a usage or billing dispute and what records are used to investigate it.

The final checkout must confirm tax/VAT handling, invoice details, billing address requirements and whether prices are shown inclusive or exclusive of tax.

The final legal and finance review should confirm whether the offer is business-only, consumer-ready, UK-only, EU-ready or international.