Telehealth failed payment recovery works best when it distinguishes a recoverable collection problem, the source of involuntary churn, from a cancellation, a missing payment method, or a clinical issue. Give each failed invoice one collection workflow, provide a secure way to update payment details, and measure recovery against the original failed balance.
The objective is to collect valid charges with clear patient communication. It is not to retry indefinitely or make clinical decisions based solely on whether a card transaction succeeds.
Start with the reason for the failure
Your payment provider may return a decline category or require further customer action. Use the documented meaning of that result. Avoid inventing a reason such as insufficient funds when the provider has not supplied it.
Some failures can be retried under the provider’s supported rules. Others require a new payment method or authentication. One payment provider’s retry documentation distinguishes retryable failures from hard declines and explains how default payment-method settings affect retries.
That distinction matters operationally. A patient may update a card on their account while an existing subscription still points to an older method. Test which record your integration updates and which method the next collection attempt will use.
Create one owner for each unpaid invoice
Store the invoice identifier, amount, failure status, next action, and responsible workflow. If a processor already schedules retries, a separate platform job should not independently charge the same balance.
| Failure situation | Suggested next step | What to avoid |
|---|---|---|
| Temporary failure with supported retry | Follow the configured collection schedule | Adding uncoordinated manual charges |
| Missing or unusable payment method | Request an update through a secure page | Asking for card details in email |
| Authentication required | Direct the patient to the supported verification flow | Repeating an action that cannot resolve it |
| Canceled service or disputed obligation | Route for account review | Treating it as ordinary payment recovery |
| Payment later succeeds | Close the recovery task and reconcile | Continuing reminders or attempts |
The subscription billing guide explains how collection status should interact with pauses, refunds, and service periods.
Write messages that explain the next action
A useful message identifies the account issue, the amount where appropriate, and a secure next step. Keep diagnosis, medication, and other sensitive details out of routine subject lines and general payment notifications.
An example operational message is: “We could not complete your scheduled payment. Please sign in to review your billing details or contact support if the charge does not look right.” This is sample wording, not a complete notice for every service or jurisdiction.
Explain what happens after the update. If another attempt is scheduled, say so through the appropriate channel. If the account needs manual review, provide a realistic support route instead of implying that changing the card guarantees immediate fulfillment.
Separate payment support from clinical follow-up
Define who handles financial questions and who handles care questions. Payment failure can create an operational interruption, but the clinical team should establish how patient concerns and continuity needs are addressed.
For example, a patient might report a payment problem and also mention a new symptom. Support should follow the clinical escalation procedure for the symptom rather than keeping the entire conversation in a billing queue. Staff do not need to make a treatment decision to recognize that the message has a different owner.
Document this handoff in the service workflow. Avoid a blanket rule that a failed card automatically closes all communication with a patient.
Test the recovery flow end to end
Use synthetic accounts to test expired cards, missing methods, required authentication, manual payments, cancellations, and late-arriving success notifications. Confirm that a successful payment closes the correct invoice and stops related messages.
Also test repeated events. Payment provider webhook documentation explains why integrations need to handle duplicate deliveries. A repeated notification should not create a second reminder sequence or a duplicate charge request.
If you are changing platforms, check historical unpaid invoices separately from new renewals. The subscription migration guide helps assign ownership across the cutover boundary.
Measure recovery without inflating the result
Define a cohort of invoices that first failed within a specified period. Measure the amount later collected against the original amount due for those invoices. Keep retry attempts separate from distinct invoices so multiple attempts do not enlarge the denominator.
Divide the amount recovered during your chosen observation window by the original failed balance for the same invoice cohort. Label the window and use the same definition each time you compare recovery rates.
Track additional measures:
- Time from first failure to successful collection.
- Share requiring a payment-method update.
- Support contacts per failed invoice.
- Refunds or disputes after recovery.
- Remaining balances that require review or write-off.
Use the funnel metrics guide to keep these events distinct from new patient acquisition. Reflect actual retained revenue in the patient LTV model.
Frequently asked questions
How many dunning retries should we use?
Choose a supported schedule with your processor and review its fit with your terms and service. There is no universal retry count that is correct for every payment method and situation.
Should we immediately cancel a failed subscription?
Not automatically. Define the commercial process, patient communication, and clinical escalation responsibilities before choosing a status transition.
Can support collect card details manually?
Use an approved secure payment flow. Ordinary email, chat notes, and spreadsheets are not appropriate substitutes for the processor’s card-update mechanism.
What is the most important recovery control?
One invoice should have one coordinated collection process. Clear ownership reduces duplicate attempts, conflicting messages, and reconciliation problems.
