Suspending service for non-payment: a fair process

Every business that sells an ongoing service eventually faces the question: the customer hasn't paid, so what now? Keep providing the service and you are extending unsecured credit. Cut it off too quickly and you lose good customers whose card simply expired. A clear, fair suspension process sits between the two.

This guide sets out how to design one for software, internet, security, hosting, membership and other recurring services.

Why you need a written process

Without a process, suspension decisions are made case by case, usually by whoever happens to notice. That leads to inconsistent treatment, awkward conversations and, sometimes, disputes. A written process means:

• Customers know the rules before they sign up.
• Your team applies the same rules to everyone.
• Suspensions are predictable, so they rarely come as a shock.

Put the key points in your terms and conditions and your onboarding emails. See recurring billing customer onboarding.

Step 1: Separate failed payments from unwillingness to pay

Most overdue subscription accounts are not customers refusing to pay. They are expired cards, insufficient funds on the day, or a debit order returned unpaid. Your first response should be recovery, not suspension:

• Retry failed card payments on a sensible schedule.
• Ask the customer to update their card or banking details.
• Re-present unpaid debit orders where appropriate. See unpaid debit order reason codes.

This is dunning, and it recovers a large share of failed payments without any loss of service. See dunning management.

Step 2: Set a grace period

A grace period is the time between a payment becoming overdue and service being restricted. During it, the customer keeps full service but sees clear reminders. Choose a length that:

• Gives time for at least one or two retries and reminders.
• Matches how quickly customers can realistically act (for example, around payday for consumers).
• You can apply consistently to everyone.

Tell the customer the exact date service will be restricted. A vague "your account may be suspended" is easy to ignore.

Step 3: Warn clearly, in more than one place

Customers miss emails. Before restricting service, make the problem visible:

• Email reminders at the start and near the end of the grace period. See payment reminder email templates.
• An in-app or on-screen banner telling the customer what is owed and how to pay.
• A direct pay link or "update card" link, so fixing it takes one click.

The aim is that nobody is suspended without knowing why and how to fix it.

Step 4: Restrict, don't destroy

When the grace period ends, restrict access in a way that is easy to reverse:

• Keep the customer's data. Deleting data for non-payment creates more problems than it solves, and may conflict with your record-keeping and privacy obligations.
• Limit the account to billing, so the customer can still sign in, see what they owe, pay and update their payment method.
• Consider essential services carefully. Where a service affects safety or wellbeing, check your legal and contractual obligations before restricting it.

Step 5: Restore access immediately on payment

The moment the customer pays or adds a working payment method, restore service automatically. Making a customer wait for someone to switch them back on after paying turns a recovered account into a complaint. Send a short confirmation and a receipt.

Step 6: Decide what happens next

If an account stays suspended, you will eventually need to decide whether to cancel the service, hand the debt to collections, or write it off. Follow your credit control process, and see bad debt write-off for the final step.

Common mistakes

• Suspending on the first failed payment, before any retry or reminder.
• Different rules for different customers without a documented reason.
• No way to pay while suspended, so the customer can't fix the problem.
• Manual reactivation that leaves paying customers locked out.
• Applying new rules to existing customers overnight. Give them notice and time first.

How CentraPoint helps

CentraPoint handles the recovery stage with dunning retries and past-due handling for subscriptions, and can re-present unpaid debit orders. For platforms that bill their own users, CentraPoint also works out each customer's account standing: ok, grace (something is due, so show a banner) or locked (the grace period has ended, so limit the account to billing until it is paid). Locked customers can still sign in, see and pay their invoices and add a card, and paying unlocks them at once.

Your platform reads the standing from the API or follows the customer.standing.changed webhook, and stays in control: CentraPoint never blocks your users itself. Customers who existed when the rules were switched on get extra time before any rule applies. See the account standing guide, features and pricing.

Frequently asked questions

How long should a grace period be?

Long enough for retries and at least two reminders, and short enough that unpaid service doesn't build up. Choose one length, publish it, and apply it consistently.

Should I delete a suspended customer's data?

No. Restrict access instead, and follow your own data retention policy and legal obligations for what happens if the account is eventually closed.

Can customers still pay while suspended?

They should be able to. Limiting the account to billing lets customers pay and update their payment method, which is the fastest route to getting them back.