Can a subscription keep charging after the account is deleted?

Yes. Billing is attached to a payment authorization, and the authorization is held by the card, mandate, or wallet rather than by the login. Deleting an account or losing the password does not necessarily revoke the authorization, and some providers only stop billing when the payment method itself is revoked or replaced.

What is the first thing to find when the login is gone?

The charge itself. Open the card or bank statement, find the merchant descriptor and the amount, and match it to a service. The receipt row tells you who is billing, which is the fact every later step depends on: support email, support form, or the payment rail all need a merchant to name.

Is revoking the card a good first move?

It is the last resort, because a replaced card breaks every other recurring payment attached to it. Try the merchant first, with the descriptor and the charge date as evidence. Revoke the authorization only when the merchant cannot be reached, refuses to cancel, or the account cannot be recovered. Then replace the card and move the legitimate subscriptions over.

How does a subscription inventory prevent this?

It records the merchant, amount, and next charge date while the login still works, so the question starts from evidence instead of memory. SaaSClerk builds that inventory from twelve months of billing email, read-only, then emails fourteen days before each renewal. The scan is free; keeping alerts running costs $39 a month billed yearly on Starter ($468 a year).

SaaSClerk Blog · SaaS spend management

How to Cancel a SaaS Subscription When the Login Is Gone

Short answer: stop trying to reach the login. The thing that keeps charging is a payment authorization held by a card, a bank mandate, or a wallet, and that authorization can outlive the account, the mailbox, and the person who created it. Find the charge on the statement, identify the merchant descriptor, try the merchant with that evidence, and revoke the authorization only if the merchant cannot or will not stop. A subscription inventory built from billing receipts makes the first step a lookup instead of a memory test; the scan is free, and renewal alerts cost $468 a year on Starter.

This situation is more common than it sounds. Someone joins a company, signs up for a tool with a work email and a personal card, and leaves. A trial converts on an address that was deleted when the project ended. A founder pays for a service through an old account that nobody can recover. In each case the account is unreachable and the charge continues, because the charge never depended on the account in the first place.

Why the login is the wrong lever

A login is a permission to use a product. Billing is a permission to take money. They are granted separately and they are revoked separately: deleting an account changes the first, and often leaves the second untouched. Payment providers hold the authorization record; the SaaS company submits charges against it. That is why people who cancel by deleting an app, abandoning an inbox, or forgetting a password keep getting billed.

The practical consequence is that the working path starts from the money, not from the product. The statement is the one document that exists whether or not you have an account, and it names the merchant in a form the merchant itself recognizes.

The sequence that ends the charge

Find the charge on the statement. Write down the merchant descriptor exactly as it appears, the amount, the date, and the card or account. Descriptors are often shortened or include a processor name, so keep a screenshot.
Match the descriptor to a service. Search twelve months of billing email for the amount or the descriptor. A receipt from the same merchant is normally enough to identify the product, the plan, and the original signup address.
Contact the merchant with evidence. Use the receipt's reply address or the product's billing form. State the merchant descriptor, the charge date, and the last four digits. Ask for cancellation and written confirmation of the date billing stops.
Do not accept silence as cancellation. Ask for a confirmation reference. If the next statement still shows the charge, escalate inside the merchant before touching the card.
Revoke the authorization as the last resort. Block the merchant or replace the card, and move every legitimate recurring payment to the new number. This works because the authorization dies with the credential, and it costs you the setup of every other subscription on that card.
Write down the outcome. Merchant, amount, cancellation date, confirmation reference, and the next date to check the statement. A row with a date is the difference between a decision and a hope.

What not to do

Deleting the app does not cancel a subscription. Unsubscribing from marketing email does not cancel it either; billing notices can arrive from a different address. Filing a chargeback as the first step is also a poor trade: it disputes a charge you can usually stop at the source, and it spends the relationship you may still need for a refund on previous months. Chargebacks belong after a documented refusal, and they run on deadlines that vary by card network and country.

The other mistake is trusting memory about which card holds the subscription. A team often has several: a company card, a founder's personal card, a wallet balance, an app-store payment method. The charge lives on exactly one of them, and the statement is the only reliable record.

Prevention: build the list while the login still works

Every step above gets shorter when an inventory exists. The merchant is already named, the amount and interval are known, and the next charge date is on the row, so the problem becomes visible before the statement does.

SaaSClerk builds that inventory from the mailbox, read-only: twelve months of billing email into one line per service with name, amount, interval, and next renewal date, plus an email fourteen days before each renewal. The scan is free and needs no card. Starter is $39 a month billed yearly ($468), Business $119 a month billed yearly ($1,428).

What the product now does about the wall: a signed cancel link rides along with each renewal email. It carries the billing record in its signature, stays valid for fourteen days, and needs no session — opening it from the mailbox is enough. Clicking it asks the payment processor to stop the subscription; the page then reports whether the stop is in progress or already in effect, next to the paid-through date. The cancel action behind a login still exists for anyone who is signed in. The limits are stated plainly: the link is only issued for subscriptions that have a live payment order, and a stop counts when the processor confirms it, not when the click happens. The related case of a payer who has never signed in — claiming the workspace their payment created through a single-use 48-hour link — was already live before this one.

Quick reference

Situation	Right move
Login works, you want to stop a renewal	Cancel in the product, get written confirmation
Login is gone, the merchant is reachable	Statement evidence, then merchant support, then confirmation
Login is gone, the merchant ignores you	Revoke the authorization, replace the card, document the date
You cannot name the merchant	Search billing email for the amount; build the inventory

One last thing

If a charge is already running against a login you cannot recover, start with the statement today and work the sequence above. If the charge is still a renewal in the future, run the free scan at saasclerk.app while you still have the login — the list you build now is the one that answers the question later.