Subscription Billing for Telehealth Companies
How telehealth subscription billing works: first charge on clinician approval, renewals on ship day, plans to create, patient self-service, FTC risks.
Article summary
TL;DR
Telehealth subscription billing follows the care, not the calendar. The first charge waits for the clinician's approval, renewals follow shipments, and a declined or stopped plan never rebills. Set up separate plans for consultations, memberships and treatment, give patients a portal to pause or cancel, keep health data out of billing, and run subscriptions on more than one processor.
- The FTC alleges Hims & Hers enrolled consumers in subscriptions "shortly after receiving consumers' intake forms" and failed to "clearly and conspicuously inform consumers when their prescriptions will be refilled" (complaint filed July 29, 2026).
- Stripe approval for "Telemedicine and telehealth services" is a restricted category and "may be modified or revoked by Stripe at any time".
- Stripe's contract: "User must not provide Protected Health Information to Stripe".
- ROSCA requires clear terms, express consent and simple cancellation for recurring online charges.
- In Tagada Rx, "Recurring treatments rebill the day the pharmacy ships".
On this page
This guide is part of our playbook on the best ecommerce platform for telehealth companies. The general guide, for any business: subscription payments. When to sell on subscription, and how to keep subscribers: subscriptions and churn for telehealth companies.
What makes telehealth billing different
| Ecommerce subscription | Telehealth subscription | |
|---|---|---|
| First charge | At checkout | After the clinician approves (card authorized at checkout) |
| Who decides the plan | The customer | The clinician, then the patient agrees |
| Renewal date | Fixed calendar date | When the next shipment goes out |
| Plan changes | Customer swaps product | Clinician changes the plan; billing follows |
| Stop | Customer cancels | Patient cancels, or clinician stops or declines |
| Data in billing | Product names | Neutral names only, no health data |
Fig. 1Two subscriptions, two billing clocks
Ecommerce subscription
- CheckoutFirst charge
- thenRenewalFixed calendar date
Charged on a fixed calendar date
Telehealth subscription
- AuthorizationCard held at checkout
- thenApprovalClinician review
- thenCaptureFirst chargeApproved
- thenShipmentPharmacy ships
- thenRenewalOn the next shipmentApproved
Charged when the next shipment goes out
Ecommerce bills on a date; telehealth bills on care events.
The billing events, in order
- Checkout. The patient sees the price, the cycle and how to cancel, and authorizes the card. ROSCA requires the terms before billing details4Restore Online Shoppers' Confidence Act, 15 U.S.C. § 8403.
- Clinician review. Approval captures the payment; a decline releases it and creates no subscription.
- First shipment. The renewal clock starts when the pharmacy ships.
- Renewal reminder. Tell the patient when the next charge and shipment will happen. The FTC's complaint against Hims & Hers turns partly on not doing so1FTC, FTC and States Act Against Hims & Hers for Deceptive and Unlawful Privacy Practices, press release, July 29, 2026 (allegations; the case is ongoing).
- Renewal. Charged when the next shipment is ready, then shipped.
- Plan change or stop. If the clinician changes or stops the plan, the next charge changes or stops with it.
Billing follows the clinician and the pharmacy.
Watch out
A subscription that starts at intake, before a clinician has reviewed anything, is the pattern the FTC alleges in its 2026 complaint1FTC, FTC and States Act Against Hims & Hers for Deceptive and Unlawful Privacy Practices, press release, July 29, 2026 (allegations; the case is ongoing). Start billing on approval.
Plans to create
| Plan | Billing | Notes |
|---|---|---|
| Consultation | One-time | Can stand alone for patients who don't want a subscription |
| Membership | Monthly or yearly | Its own plan and terms: memberships for telehealth companies |
| Treatment plan | Per shipment, cycle set per offer | Starts only after approval; changes when the clinician changes it |
| Non-prescription add-ons | One-time or on the treatment cycle | Named neutrally, clearly optional |
Keep each plan separate. A patient who cancels a membership shouldn't lose a treatment in progress by accident, and the reverse.
What patients must be able to do alone
The FTC alleges that Hims & Hers made cancellation hard "by hiding the cancellation button from consumers"1FTC, FTC and States Act Against Hims & Hers for Deceptive and Unlawful Privacy Practices, press release, July 29, 2026 (allegations; the case is ongoing). Build the opposite.
- See the next charge date and amount in their account.
- Pause or skip a shipment, within limits you set.
- Change frequency, where the clinician's plan allows it.
- Update the card without calling support.
- Cancel online, in as few steps as signing up. California requires online cancellation for online sign-ups5California Business and Professions Code § 17602 (contracts from July 1, 2025).
Fig. 2What the patient sees in the account
- Next charge
- Date and amount, shown
- Shipments
- Pause or skip, within your limits
- Frequency
- Change it, where the clinician's plan allows
- Card
- Update it without calling support
- Cancel
- Online, in as few steps as signing up
Illustrative record.
Everything here works without calling support.
Keep billing data clean
Plan names
"Monthly plan", "Membership", never a condition or a treatment.
Descriptor
Your brand name.
Metadata sent to the processor
Order and patient IDs, not intake answers. Stripe's contract forbids sending Protected Health Information3Stripe Services Agreement, §4 Third Party Data, modified September 28, 2026.
Emails about billing
Amount, date, link to the portal; nothing clinical.
The payment side of this rule: do you need a HIPAA BAA with your payment processor.
Don't tie subscriptions to one processor
Stripe says telehealth approval "is specific to each service offer and it may be modified or revoked by Stripe at any time"2Stripe, Prohibited and restricted businesses, read November 2, 2026. If that happens and your subscriptions only exist inside one processor, renewals stop.
- Keep the subscription logic in your billing layer, not only in the processor.
- Store cards in a vault you control, so renewals can be charged elsewhere.
- Have a second processor reviewed before you need it: payment routing and backup processors for telehealth companies.
Fig. 3A renewal that doesn't depend on one processor
approved declined or closed routing step
- RenewalNext shipment ready
- handled byBilling layerSubscription logic and card vault
- routes toProcessor AApproval revokedDeclined
- falls throughProcessor BReviewed beforehand, renewal chargedApproved
The subscription and the card live in your billing layer.
Checklist for choosing the tool
| Need | Question to ask the vendor |
|---|---|
| Charge on approval | Can the first charge wait for a clinical approval event? |
| Ship-day renewals | Can renewals be triggered by a shipment, not only a date? |
| NoRebill on stopped plans | Do declined or stopped cases stop billing automatically? |
| Patient portal | Can patients pause, skip and cancel alone? |
| Retries | Are failed renewals retried on a schedule? |
| Processor independence | Can a subscription be billed through another processor? |
| NoHealth data | Can billing run on IDs only? |
Failed renewals in detail: failed payment recovery for telehealth companies. Billing rules from the processor's side: how to sell telehealth services on subscription.
How Tagada helps
PSP-agnostic subscriptions, with retries and a customer portal
Tagada runs subscriptions on the processors you choose, as documented in the subscriptions guide, and TagadaPay keeps the data yours: "Your PCI-tokenized cards, your customer profiles, your subscription data, all portable."10TagadaPay, homepage, read November 2, 2026
- PSP-agnostic subscriptions with trials, pause and resume, and cancellation now or at period end7Tagada docs, Node SDK: subscriptions, read November 2, 2026
- Automatic retries on declined renewals7Tagada docs, Node SDK: subscriptions, read November 2, 2026
- A customer portal to "skip, pause, change frequency, swap product, cancel with your retention offers"8Tagada docs, Headless SDK: customer portal, read November 2, 2026
- Routing across TagadaPay and processors such as Stripe, NMI and Airwallex, with one logic, and a cascade to another processor when one is down or times out
Building the whole telehealth brand? With Tagada Rx, "The card is only captured once a doctor approves"9Tagada, Tagada Rx, read November 2, 2026, "Recurring treatments rebill the day the pharmacy ships", and "Declined, cancelled, and errored cases never rebill"6Tagada docs, Rx: how it works, read November 2, 2026. US patients only, by selection.

Frequently asked questions
When should a telehealth subscription start billing?
Can I use Stripe Billing for a telehealth subscription?
Should renewals follow a fixed date or the shipment?
Do I need a separate plan for memberships and treatment?
Sources
Checked November 3, 2026- FTC, FTC and States Act Against Hims & Hers for Deceptive and Unlawful Privacy Practices, press release, July 29, 2026 (allegations; the case is ongoing)
- Stripe, Prohibited and restricted businesses, read November 2, 2026
- Stripe Services Agreement, §4 Third Party Data, modified September 28, 2026
- Restore Online Shoppers' Confidence Act, 15 U.S.C. § 8403
- California Business and Professions Code § 17602 (contracts from July 1, 2025)
- Tagada docs, Rx: how it works, read November 2, 2026
- Tagada docs, Node SDK: subscriptions, read November 2, 2026
- Tagada docs, Headless SDK: customer portal, read November 2, 2026
- Tagada, Tagada Rx, read November 2, 2026
- TagadaPay, homepage, read November 2, 2026
Tagada
Bill when the clinician approves and the pharmacy ships
Funnels, one-click upsells, subscription billing and payment routing, on one customer record.
- 01Create your free account
- 02Connect your store or build a checkout
- 03Launch funnels, upsells and subscriptions
