Refund pages contrive somehow to be simultaneously accurate and useless. This one names what comes back, what does not, and why the second list has the shape it has.
Text current as of 28 August 2026Charging runs one month at a time, ahead of the month. Cancel and future charges stop while the month already paid for finishes. Errors of ours come back without a fight. A month that was delivered does not come back.
All your lines sit inside one subscription. Stripe takes it the same date every month, ahead of the period, at the counts standing on the account. A line added midway joins the next invoice. What the manifest totals is what recurs.
Do it in the portal, or ask us and we will. Cover keeps going until the paid period expires, then stops. Written confirmation of the stop date follows, so nobody is left guessing at it.
A managed line is not metered. The tenant gets built. The supplier licence gets bought for the period. The desk stands staffed whether or not your month proved eventful.
Refunding fractions would mean recouping the cost elsewhere, either from every customer through the headline rate or quietly from the next one. Neither is a sentence we would want to say out loud.
A chargeback freezes the account and inserts an adjudication between the problem and the fix. Write to support@clientdataarmor.com instead. Where the mistake is ours it usually gets corrected the same day, which beats waiting for a card network to reach a view.
Counts move in the portal. Upward bills from the next invoice. Downward starts at the next period, the present one being paid for already.
Where a change has to land on a particular date, a lease running out or a group of starters arriving, say so and we will arrange it around that.