Cancelling a subscription is an operational chain: how the customer cancels, what stops and when, which document is created, and what gets recorded.
Key takeaways
- Cancellation is a process with three dates: request, charge stop, and end of access.
- The common failure: the charge stops in one system and continues in another.
- Recording the request - when it arrived and on which channel - is what prevents a dispute.
- An orderly cancellation brings customers back later; one that feels like a trap closes the door.
Cancelling a subscription looks like a button and is actually a chain: the customer asks, the next charge stops, access changes on a defined date, a record is created, and sometimes a document too. A business handling cancellations by hand discovers this when a cancelled customer is charged again - the most expensive service failure there is, because it burns somebody who had already left.
This is an operational description, not advice. For questions about what must be allowed and in what manner, consult your accountant or legal adviser and the official authority pages.
The three dates
| Date | What it is | Why it matters |
|---|---|---|
| Request date | When the customer asked to cancel | This is what counts in a dispute, so it must be recorded |
| Charge stop date | When the next charge will not happen | With no definition, somebody forgets to stop it |
| Access end date | When the service actually ends | Usually the end of the paid period, but it has to be decided |
The gap between the second and third is the big source of customer confusion: they cancel and expect everything to stop immediately, and in practice they keep receiving service until the paid period ends. That is reasonable - and it needs saying explicitly on the cancellation screen.
The flow, in eight steps
- The customer asks to cancel - by form, email, phone or chat.
- The request is recorded with date, time and channel.
- The customer gets confirmation that the request was received, immediately.
- The charge instruction is cancelled in the collection system - the critical step.
- The subscription is marked cancelled in your system, with an end date.
- Access is set to expire on the agreed date.
- A record or document is created as needed.
- The subscription disappears from the next charge report - and somebody verifies that.
Step eight is the check nobody performs and the one that prevents the failure. A monthly report comparing active subscriptions against charges executed catches exactly the case of a cancelled customer being charged.
Why does a cancelled customer keep getting charged?
Four reasons, all technical rather than malicious:
- The cancellation was recorded in the CRM but not in the collection system. Two systems, one of which does not know.
- The request arrived on an unmonitored channel - a WhatsApp message to a salesperson who went on holiday.
- The cancellation happened after the charge had already entered that month's queue.
- There are two charge instructions for the same customer and only one was cancelled - which happens when a customer updates a card and a duplicate subscription is created.
The fourth is the hard one to find, and it is why it is worth checking quarterly whether any customers have more than one active charge instruction. The duplicate usually appears when a payment method is updated, as described in what a payment token is.
What the cancellation screen needs
- What stops and when - explicitly, not in small print.
- How long access continues for the period already paid.
- What happens to the customer's data - retained, deleted, downloadable.
- An option to pause instead of cancel, if you offer one.
- Written confirmation sent immediately after the request.
The fourth item is worth money: a large share of people cancelling would have settled for a two-month pause, and they choose cancellation only because it was the single option offered.
What to record, and why
- Date and time of the request, not only the processing date.
- The channel it arrived on.
- Who handled it on your side.
- What the customer was told about dates and money.
- Proof that the confirmation was sent back.
Those five together are the answer to any future dispute about "I asked to cancel two months ago". Without them it is the customer's word against yours - and in that situation it is simply better to refund.
How this looks on the collection side
Cancellation is not only a status; it is an action in up to three systems:
- On a card: cancelling the recurring charge instruction in the clearing system. The token can stay, but it must not be charged.
- On Masav: cancelling the mandate or removing the customer from the next charge file, depending on how you work.
- On links or manual charges: simply stop sending - but verify no automatic reminder is still running.
The third line surprises people: plenty of businesses cancel the charge and forget the reminder system, so a customer who cancelled keeps receiving "you have not paid" messages.
What to do after the cancellation
- Ask why, in one short question rather than a survey. Those answers are worth more than any market research.
- Do not send offers immediately. A customer who cancelled yesterday and gets a discount today concludes the old price was unnecessary.
- Leave the door open - one message after two months, no more.
- Look for a pattern: cancellations concentrating in a particular month or after a particular event.
What to measure in cancellations
Four numbers that turn cancellations from a nuisance into data:
- Monthly cancellation rate out of active subscriptions, as a baseline.
- How many were charge failures rather than requests - those are not cancellations at all but broken collection. The distinction is covered in the failed standing-order recovery ladder.
- How long the average subscription lasted before cancelling.
- How many cancellations converted to a pause, if you offer one.
The second number changes the picture in many businesses: once you separate people who asked to leave from people whose card expired, a large share of "churn" turns out to be a technical problem you can fix.
Sources
Frequently asked questions
When does a cancellation take effect?
That is what you define and show the customer in advance. The common practice is that the next charge stops and access continues to the end of the paid period, but it needs to be written rather than assumed. What matters: the date shown to the customer must be the date the system applies.
A customer cancelled and kept being charged. What now?
Refund immediately, without checking whether they are "right". This is a case where delay costs more than the amount: a customer charged after cancelling goes to their card company, and that is a chargeback costing more than the refund. After refunding, find which of the four causes did it.
Can I require a phone call to cancel?
That has a regulatory side and a business side, so the first belongs with appropriate advice and the official authority pages. On the business side: an awkward cancellation process produces chargebacks and complaints, both costing more than the subscription you were trying to save.
Should I offer a pause instead of cancellation?
In most businesses yes, and it recovers a meaningful share of customers. The condition is that the pause is genuine: a clear return date, no charges meanwhile, and an automatic resumption the customer knows about in advance. A pause that becomes a surprise the following month is a deferred cancellation.
Keep reading
Related service
Integrations
Make the systems you already pay for talk to each other.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.