Charged After Cancelling? What the Terms Actually Say

• A charge after cancelling almost always means the renewal fired before the cancellation registered — a timing race, not a broken promise
• A charge landing after a confirmed cancellation is a different, rarer case, and it's the one worth escalating
• Of the three offers this site tracks, only Lovescape publishes a renewal and refund clause specific enough to quote directly here
• Cancelling a few days before the renewal date, not on it, prevents most of this before it happens

This is a narrower question than how to cancel a subscription or what you can get refunded, and it gets searched by people who already did the first thing right and still watched a charge go through. The honest answer splits into two cases that feel identical from inside your bank app and are not identical at all, and the terms each company actually publishes turn out to disagree with each other more than the marketing pages ever let on.

Two different things hiding under one search

The first case is a renewal that was already queued to fire before your cancellation reached the billing system. Nobody did anything wrong; the cancellation button and the billing run operate on separate schedules, and a cancellation submitted close to the renewal date routinely loses the race. This is the overwhelming majority of "charged after cancelling" cases, and it is not refundable on the strength of timing alone — you had access for the period, and the period is what you're being billed for.

The second case is a charge that landed after a cancellation you can point to a specific date and confirmation for — not "I meant to cancel" but "I cancelled on the 4th and the charge is dated the 9th." That's rarer, and it's the version with an actual case behind it, because at that point the company's own system failed to do the one thing cancelling is supposed to do.

Scenario one: the renewal beat the cancellation

Billing systems in this category process on their own clock, usually once a day, and a cancellation flips a flag that the next run reads rather than stopping a charge already in flight. Submit it the same morning the renewal is scheduled and there's a real chance the charge has already left before your click registers on their side. This isn't specific to any one app — it's how subscription billing generally works, and it's the reason the cancellation guide's core advice is to act a few days ahead of the date rather than on it.

There's nothing to dispute here beyond asking, and asking is worth doing anyway: some support teams will refund a renewal that fired within a day or two of a cancellation attempt as a goodwill gesture, even though nothing in the terms obligates them to. That's a request, not a right, and it's worth going in with that framing rather than treating a same-day miss as an error on their end.

Scenario two: a charge landed after a confirmed cancellation

This is the version worth taking further. You cancelled, you have something to show for it — a confirmation screen, an email, a support reply — and a charge still landed on or after your next billing date. That's not a timing race; the cancellation registered and the billing system charged you anyway, which is the kind of error every one of these companies' own terms would call a mistake rather than a policy.

The paper trail is what makes the difference between a request and a case. "I cancelled" without a date and a confirmation is hard for support to act on quickly; "I cancelled on the 4th, here's the confirmation, and I was charged on the 9th" usually gets resolved in one message, because the dates alone make the error visible to whoever reads it.

What six companies' own terms say about the moment you cancel

Reading the actual documents rather than the pricing page turns up more disagreement than you'd expect on exactly this question — some spell out what "cancel late" costs you, some describe what you're allowed to do with your bank afterward, and some say almost nothing at all.

Read across that table and the range runs from Nomi, which states there's simply nothing to argue for once a charge has processed, to CrushOn, which goes a step further and has you agree in advance not to take a disputed charge to your own bank outside of fraud — a clause detailed in our piece on that specific line. Lovescape sits closer to the plain end: no refund by default, with the door left open exactly where a law requires it, and nothing in its terms that reaches for your bank relationship the way CrushOn's does.

Where GoLove and OurDream stand

The table above only includes companies whose terms have been read closely enough to quote a specific renewal and refund clause, and GoLove and OurDream aren't in it — not because either one's policy is worse, but because neither has been read that closely for this comparison yet. Guessing at a company's cancellation clause is worse than leaving the row blank, so it stays blank until it's actually been checked.

If a charge from either one lands after you believe you cancelled, treat it as scenario two above rather than assuming a specific clause applies: check the confirmation you were given, check the charge date against it, and go to support with both. And check their current terms directly on their own site before drawing a conclusion from anything you've read secondhand, including this page — a policy read once is only accurate until the next revision.

If a charge has already landed, in order

• Check the charge date against your actual renewal date first — the two get confused more often than either side of this dispute expects
• Pull up the cancellation confirmation now, whether that's an email, a screen you screenshotted, or a support thread with a timestamp
• Message support in one short paragraph: the cancellation date, the charge date, the amount, and what you want. No argument, no history
• If support won't move and the dates genuinely don't line up, a chargeback through your bank is the real recourse — see the full refund playbook for how to weigh that against what it costs you

That last step is worth going in with eyes open about. A chargeback usually wins against a small subscription merchant, and it also usually ends the account permanently — this category's processors share fraud signals widely enough that the effect can reach past the one app. Save it for the case where support has genuinely failed you on a documented post-cancellation charge, not as a faster substitute for asking first.

The fix that avoids the whole question

Nearly everything above is downstream of one habit: cancelling a few days before the renewal date instead of on it. That alone removes the timing race that accounts for most of what gets searched under "charged after cancelling," and it leaves you with a confirmation that's already a few days old — and therefore unambiguous — if a charge somehow lands anyway. The rare genuine error is much easier to prove when the cancellation clearly predates the billing cycle it should have stopped, rather than arriving on the same morning as the charge itself.

Verdict

Start by working out which of the two situations you're actually in, because they call for different moves: a same-day miss is worth one polite ask and nothing more, while a charge that landed after a dated, confirmed cancellation is worth pushing on with the specifics in hand. Read the company's own terms before you conclude anything about what it owes you — as the table above shows, the six companies with published policies don't agree with each other, and the one you're dealing with may be closer to Nomi's flat no or closer to Lovescape's law-dependent exception. Either way, cancelling early enough to lose the timing race entirely is the cheapest fix available, and it works regardless of which company you're subscribed to.