How to cancel a subscription that does not want to be cancelled

Recognise the standard playbook

Retention flows follow a predictable script: bury the cancel link, add confirmation steps, offer a discount, offer a pause, then offer the discount again. Each step exists because a measurable share of people stop there.

None of the offers are traps in themselves, but a pause is not a cancellation. If your goal is to stop paying permanently, decline the pause — it typically resumes silently.

The order of operations that works

Work through the channels in increasing order of effort, and stop as soon as one succeeds. Most cancellations resolve at step one or two.

• Account settings on desktop web — mobile apps often hide the option entirely
• Support chat with a plain, repeated request and no explanation offered
• Email to billing support asking for written confirmation and an effective date
• Store-level subscription management if you subscribed through an app store
• Card-level action as a last resort, after documenting the attempts above

Document everything, briefly

Save the confirmation screen or email with the effective date. If a charge appears afterwards, that single artefact resolves the dispute in one message instead of five.

Note the exact merchant descriptor from your statement too. Disputes stall most often because the name on the card differs from the brand name you remember.

When to involve your bank

Blocking a merchant at the card level is effective but blunt: it can stop legitimate charges too and does not end the contractual relationship, which may still accrue a balance. Use it after documented cancellation attempts have failed, not instead of them.

If a charge posts after a confirmed cancellation, that is a straightforward dispute and your documentation makes it a short one.

Prevent the next one

After cancelling, add the merchant to a watch list and check for a reappearing charge in sixty days. Reactivation after a trial accepted during the cancellation flow is common enough to be worth one calendar reminder.

This is exactly the kind of thing worth automating. A recurring-charge view that keeps showing the merchant after you cancelled is a much better safety net than memory.