Cancelled a Subscription but Still Got Charged? The 2026 Refund Strategy Regulators Keep Pointing To

One of the most common refund complaints in 2026 is also one of the most frustrating: a customer cancels a subscription, receives no useful help, and then gets charged again. The FTC's consumer guidance on free trials, auto-renewals, and negative option subscriptions is direct: if a company charged you without consent or will not stop charging after you told it to cancel, dispute the charge with your credit or debit card company right away. That advice matters because customers often spend weeks arguing with support while their bank dispute deadline quietly shrinks.

Subscription disputes are everywhere because almost every digital product now wants recurring revenue: streaming, delivery memberships, AI tools, VPNs, dating apps, meal kits, fitness plans, photo libraries, design platforms, software trials, cloud storage, kids apps, and online courses. The business model can be legitimate when enrollment is clear and cancellation is easy. It becomes a refund problem when the company hides the recurring terms, makes cancellation confusing, ignores cancellation requests, or claims there is no record even when the customer has proof.

If you were charged after cancellation, your strongest evidence is the cancellation confirmation. Search your email for cancellation, subscription, membership, renewal, plan, receipt, invoice, trial, and the company name. Check screenshots on your phone. Look at browser history if you cancelled through a website. If cancellation happened by chat or phone, write down the date, time, number, agent name, and confirmation number. If you do not have a confirmation, look for indirect proof: a support ticket, calendar note, account status screenshot, or email saying your plan would end.

The refund argument should be simple: I cancelled before the renewal date, or I made a clear cancellation request, and the company charged me anyway. Do not dilute that with every complaint you have about the product. A bad product refund is one argument. A post-cancellation charge is another. The post-cancellation charge is often stronger because it focuses on authorization. Once you revoke authorization for recurring billing, the merchant needs a valid reason to charge again.

The practical refund playbook starts with a timeline. Write down when you signed up or bought the product, what you believed you were paying for, when the charge appeared, when you tried to cancel or complain, and what the subscription company or the merchant said in response. Most refund denials are easier to overturn when the customer can show dates instead of feelings. A support agent can ignore frustration. A bank, regulator, or escalation team has a much harder time ignoring a clean timeline with receipts.

Next, preserve evidence before it disappears. Download invoices, card statements, emails, chat transcripts, screenshots of the account page, cancellation confirmations, product pages, fare rules, and any public notice connected to the dispute. If your case involves a mobile app, take screenshots from inside the app before deleting it. If it involves travel, save the original itinerary and the cancellation notice. If it involves a subscription, save the page that shows the plan status. The best evidence is boring, timestamped, and easy for a stranger to understand.

Do not send the first appeal as an angry paragraph. Use a structured format: identify the charge, explain why it is disputed, attach evidence, request a specific remedy, and ask for written confirmation. For this post-cancellation recurring billing dispute, the request should be narrow. Ask for the exact amount you want refunded, the exact account or order number, and the exact reason the denial should be reviewed. If the first agent says no, reply with the same facts and ask for escalation to a billing, refunds, trust and safety, or executive support team.

If support refuses, decide whether the next step is a card dispute, regulator complaint, small claims demand, class action claim, or insurance claim. Those routes are not interchangeable. A chargeback is strongest when a service was not provided, a charge was unauthorized, or cancellation was ignored. A regulator complaint is strongest when the company pattern matters. A class action claim is strongest when an official settlement or lawsuit already defines eligibility. A small claims demand works best when the amount is large enough and your documents are complete.

You should also separate your evidence into three folders: proof of purchase, proof of problem, and proof of attempted resolution. Proof of purchase shows the amount, date, merchant, and payment method. Proof of problem shows the cancellation, failure, misrepresentation, outage, denied service, or unexpected charge. Proof of attempted resolution shows that you gave the merchant a fair chance to fix it. This folder structure sounds simple, but it matches how banks, regulators, insurers, and support supervisors actually review claims. If a reviewer can understand the case in two minutes, your odds improve.

Deadlines are another quiet danger. Merchant support tickets can drag on for weeks while card dispute windows, insurance filing windows, package travel deadlines, and settlement claim deadlines keep moving. Put every deadline in a calendar the same day you discover the problem. If the company says it is investigating, ask for a written response date and do not let that promise push you past your bank deadline. A polite delay from support can still cost you money if it leaves you with no external remedy.

When escalating, change the audience rather than repeating the same message. The first support agent may need a short refund request. A supervisor needs a precise appeal. A bank needs a dispute reason and attached proof. A regulator needs a pattern and timeline. A court or small claims demand needs damages and legal theory. Copying the same emotional complaint into every channel usually performs badly because each reviewer is looking for different information. Reframing the same facts for the right audience is often what turns a denial into a refund.

A good appeal letter for merchant support or card issuer should sound calm and factual: I am requesting review of charge or order [number] for [amount] dated [date]. The service or product was not provided as represented because [specific fact]. I contacted support on [date] and received [response]. I am asking for a refund to the original payment method and written confirmation that no further charges or penalties will be applied. I have attached receipts, screenshots, and prior correspondence. Please escalate this for manual review if frontline support cannot approve it.

LaimRefund is useful here because the hard part is not only writing politely. The hard part is matching your facts to the right policy angle. A subscription charge may need a negative option argument. A cancelled flight may need a passenger rights argument. A tariff refund may need a class action or unjust enrichment framing. A shutdown may need a services-not-provided chargeback. The free analysis helps organize the case before you pay for the full appeal letter, and that organization can prevent you from wasting your strongest evidence in the wrong channel.

If the company says there is no cancellation on file, ask for account logs. Many systems record when users open billing pages, click plan changes, or contact support. The company may refuse to provide internal logs, but asking in writing shows you are serious. If the company says the cancellation did not complete because you missed a final button, ask for screenshots of the required flow and where that requirement was disclosed. Complicated cancellation flows are exactly what regulators scrutinize. The company may still deny the refund, but the denial becomes useful evidence.

If the subscription was purchased through Apple, Google Play, Roku, PayPal, Stripe, Shopify, or another payment platform, contact that platform too. Many customers waste time emailing the app developer when Apple or Google controls billing. In your app store account, check subscriptions and purchase history. Cancel there if the subscription is still active. Then file the refund request through the platform and attach proof that you already cancelled or tried to cancel. If the platform denies it, ask for manual review and cite post-cancellation billing.

For card disputes, use the right reason. The strongest categories are recurring transaction cancelled, unauthorized charge, or services not as described depending on your issuer's menu. Attach the cancellation proof first, then the charge, then the merchant refusal. Keep the explanation short enough for a bank reviewer: I cancelled on [date], the merchant confirmed cancellation or received my cancellation request, the merchant charged [amount] on [date], and the merchant refused refund on [date]. I am disputing a recurring charge after cancellation.

Do not cancel the card as your first move unless the charges are continuing and the merchant will not stop. Replacing a card can prevent future charges, but it does not automatically recover old ones. Some recurring merchants may receive updated card numbers through account updater services. Ask your issuer to block the merchant or revoke recurring authorization if that option exists. Also remove the payment method from the merchant account after saving screenshots. If the company will not let you remove it, screenshot that too.

Regulator complaints help when the pattern matters. File with the FTC, your state attorney general, the CFPB if a financial product is involved, or a local consumer protection agency. Regulators may not resolve your individual refund immediately, but complaints build enforcement records. The 2026 wave of subscription cases exists because enough consumers reported similar behavior. Your complaint should include dates, charge amounts, cancellation proof, and the company's refusal. Avoid dramatic language. Regulators need patterns and documents.

LaimRefund can help when you have messy evidence and do not know which route is strongest. The tool can organize a post-cancellation charge into a merchant appeal, app store refund request, bank dispute statement, or regulator complaint. That matters because the same facts need different wording in each channel. Support needs a refund request. The bank needs a dispute reason. The regulator needs a pattern. A scattered complaint often loses. A structured claim has a much better chance.

Sources: FTC consumer guidance on free trials, auto-renewals, negative option subscriptions, and chargebacks; FTC 2026 subscription enforcement actions including Uber and Shutterstock; current consumer complaints about recurring charges after cancellation.