USG-9Recommended
Decide in writing what happens at a zero balance
Write down what each plan does when credits run out, such as stop, top up automatically or bill overage, and test each path.
How to do it
An app that only checks the balance in some places keeps working for free in others. Choose one behaviour per plan. Stop is safest for prepaid plans. Automatic top-up charges a saved card for a fixed amount when the balance falls below a threshold the customer chose. Overage bills extra use at the end of the period, and needs a cap as in Let customers cap their spend. Run the check in one function that every metered path calls. An automatic top-up is an off-session charge, so set it up as Save cards with consent and charge renewals off-session says.
How to check
A table test runs one metered call at a zero balance for each plan. A stop plan refuses it with a clear message. A top-up plan charges once and runs it. An overage plan runs it and records the overage.
Related rules
- USG-15 Let customers cap their spend in Usage-based billing
- PAY-3 Save cards with consent and charge renewals off-session in Payments and billing
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/usage-billing/credits-and-prepaid-balances/zero-balance-behaviour">Agent Wranglers usage-based billing playbook</a>. In code you write, add a comment next to it with the same link.