The Billing You Never Think About Is the Billing That Works

There are two ways to lose a subscriber. They can decide to leave, which is a product problem and takes real work to fix, or their card can fail, which is an administrative problem and is largely solvable by doing nothing clever at all. Operators spend enormous effort on the first and routinely ignore the second, even though the second is cheaper to address by a wide margin. A card expires, a bank declines a foreign transaction, an account is briefly empty on the wrong morning. None of those people wanted to cancel. Whether they end up cancelled depends entirely on what your platform does in the following week, and that is a setting rather than a strategy.

Everything else here is plumbing. The grace period is the part that changes outcomes, because it converts a hard failure into a soft one. Without it, a declined charge on a Tuesday morning means somebody discovers they have been locked out on Tuesday evening, usually in front of their family, and the emotional register of that moment is not one you recover from with an email. With it, they carry on watching, the payment retries on Thursday and succeeds, and they never learn anything happened. The right length is a judgement about your market rather than a universal number, which is why it is a setting rather than a default somebody chose for you. It sits alongside cancellation behaviour and wallet rules under the subscribers manager.

Automation is only trustworthy if you can audit it. Every renewal, retry, refund, credit and failed charge is recorded against the account it belongs to, with a running balance and a transaction history the subscriber can read themselves without contacting anybody. That last part quietly removes a large share of billing enquiries, because most of them are somebody wanting to know what a charge was for. Where money moved through a viewer's balance rather than a card, the same ledger shows it, and where it came through a provider the order records which one. The transactional side of that is the orders manager, and the totals roll into the sales dashboard.

Billing is the one part of a platform where the first live test is also the most expensive one, and it is the part most likely to be configured slightly wrong. A test mode puts every payment through your gateways without charging anybody, so a signup, a renewal, a failed charge and a cancellation can all be walked through before launch. It is worth doing properly rather than assuming, because the failure modes are not obvious from the settings screen. A misconfigured gateway looks identical to a working one until money is supposed to move. The providers themselves are covered under payment gateways, and the plans the whole thing bills against under packages and subscriptions.