Refunds, cancellations, and chargebacks for telehealth subscriptions
Telehealth is a higher-risk category to payment processors before you make a single mistake: subscriptions, health claims, and shipped goods that cannot be restocked. Your refund policy is not customer-service copy — it is merchant-account risk management.
Photograph via UnsplashThree separate things get conflated: cancellation (stop future billing — make it effortless and instant), refunds (return money — write product-specific rules: visits rendered are earned; medication not yet shipped is refundable; shipped compounded medication cannot be restocked, so decide between goodwill refund and replacement-only), and chargebacks (the patient asks the bank — each one costs a fee plus the sale, and a dispute rate near 1% can end the merchant account regardless of who was right). The operational levers: clear recognizable billing descriptors, pre-charge reminders for renewals, self-serve cancellation, fast support that answers before the bank does, and evidence packages that use order and encounter records — never clinical detail.
Three different problems wearing one trench coat
Cancellation is a subscription-management question; make it self-serve, instant, and confirmation-emailed, because every hard-to-cancel flow becomes a chargeback with worse economics and regulatory attention (the FTC’s click-to-cancel expectations point the same direction). Refunds are a policy question with a clinical twist: a completed clinician review is a service rendered, and shipped compounded medication cannot be resold. Chargebacks are a survival question: the dispute rate, not the dollars, is what threatens the account.
A refund matrix that works
| Situation | Policy | Why |
|---|---|---|
| Cancel before monthly check-in review | No further charge; subscription ends | Nothing rendered yet this cycle |
| Visit completed, prescription declined | Refund medication component; visit earned (state it clearly) | Clinical review is a real service either way |
| Medication ordered but not shipped | Refund on request; stop the order | Recoverable cost |
| Shipped, cold-chain excursion or damage | Replace at no cost, fast | Pharmacy/carrier issue; replacement beats refund |
| Shipped, patient changed mind | Goodwill case-by-case; no restock possible | Balance retention vs. abuse; log the pattern |
| “It didn’t work” | Clinical conversation first — dose review, not checkout flow | Often a titration issue; a clinician answer retains |
Keeping the dispute rate down
- Descriptor hygiene. The card statement should say your brand name, recognizably. Mystery descriptors are the #1 “fraud” dispute source.
- Pre-charge notice on renewals. An email two or three days before each cycle, with the amount, the date, and a manage link — especially before a dose-step price change. See subscription pricing.
- Self-serve cancel, honored instantly. Then say so on the statement-descriptor page your support links to.
- Answer support faster than the bank. Same-day responses on billing tickets convert would-be disputes into refunds or saves.
- Watch the rate weekly. Disputes ÷ transactions, by cohort and product. A creeping rate is an early-warning signal about descriptors, expectations, or a partner’s traffic quality.
- Underwrite honestly. Processors that understand telehealth exist; hiding what you sell from your processor is how accounts get frozen with a month of revenue in reserve.
When the dispute arrives anyway
Some disputes come regardless. Treat each one as a case with a deadline: networks give a response window measured in days, and a missed window is a lost sale plus a fee no matter the merits. Triage first — if the medication never shipped or the case is genuinely gray, refund and move on; representment exists for the disputes where services were rendered and terms were clear. Assemble the evidence pack from the operational record — consent, encounter timestamps, delivery confirmation, the cancellation policy as accepted — submit through the processor, and log the reason code and outcome — win rates by code teach you which fights are worth having.
Then read the codes in aggregate. A cluster of “transaction not recognized” is a descriptor problem; “cancelled recurring” clusters mean the cancel flow or the pre-charge notice is failing; “product not received” points at a carrier or a pharmacy. And flag repeat disputers at intake — a patient who has charged back once and reordered is a risk decision, not a marketing win.
The clinical wrinkle
Never fight a dispute with clinical records. Evidence packages use operational facts — consent captured, encounter completed at a timestamp, order shipped and delivered, terms accepted — which is one more reason the program’s records need to be structured and exportable per patient. See records in cash-pay programs.
Frequently asked questions
What should a telehealth refund policy cover?
Separate rules per component: completed clinician visits (earned when rendered), medication not yet compounded or shipped (refundable), compounded medication shipped (not restockable — typically replacement for damage/excursion, goodwill refunds case-by-case), subscriptions (cancel anytime going forward, with a clear cutoff relative to the monthly clinician review and pharmacy order). Publish it, link it at checkout, and honor it fast.
Why do chargebacks matter so much for telehealth?
Card networks track dispute rates per merchant; sustained rates around 0.9–1% trigger monitoring programs, fines, reserves, and termination. Health subscriptions attract disputes ("I forgot I subscribed", "it did not work", family members seeing a statement). Losing the merchant account stops revenue entirely — a worse outcome than any refund.
Can we require patients to contact us before disputing a charge?
You cannot prevent a cardholder from disputing, but you can make contacting you the obviously faster path: visible support, one-click cancel, fast refunds within policy, and billing descriptors that name your brand. Most disputes are confusion, not fraud; speed and clarity absorb them.
What evidence wins a telehealth chargeback?
Signed consent and terms acceptance, the order and delivery confirmation, encounter timestamps showing services rendered, cancellation-policy acceptance, and support correspondence. Submit operational records, not clinical content — never disclose diagnosis or treatment detail to a card network. When services were rendered and terms were clear, representment win rates are decent; when the product is undelivered, refund instead of fighting.
Labs for telehealth programs: at-home kits vs. draw networks
How kits and draw sites compare on completion, panels, and cost — and how to build the lab loop so results actually gate care.
Read the guide
Patient support for telehealth programs: the tickets that actually happen
The real ticket mix, the clinical/non-clinical triage line only licensed staff may cross, and the notifications that prevent the biggest queues.
Read the guide
Do cash-pay telehealth programs need NPIs, CPT codes, and superbills?
Which pieces of the insurance world still apply when you never file a claim — and why superbills are a revenue feature for cash-pay programs.
Read the guideFrom first call to first patient, in weeks.
A 15-minute intro call, sandbox credentials the same day, go-live in 3–4 weeks — new launches and existing patient bases alike.