Can Telehealth Clinics Charge After a Visit?

Is a saved card the same as an authorized payment?

No. Stripe's Setup Intents documentation describes saving a payment method without creating a charge. Its separate authorization-and-capture guidance describes reserving funds and collecting them later within an authorization window. These are provider-specific examples of different payment mechanisms, not confirmation that a clinic qualifies or that its software supports either.

MerchantBridge analysis: start with the business question: do you need to collect a known fee after the visit, determine an amount later or simply avoid asking the patient to re-enter payment details? Those are different requirements. This guide addresses timing for a licensed practice charging its own service fee, not the separate question of how a marketplace splits money among providers.

Sources: Stripe: The Setup Intents API; Stripe: Place a hold on a payment method; MerchantBridge Advisors: Clinic & Telehealth Payment Processing

Describe the booking-to-payment sequence

For a fictional practice charging a disclosed consultation fee after attendance, map four events: booking, permission to use the payment method, confirmation that the appointment occurred, and the charge. Identify which system supplies each event and who can correct an error. Do not use a clinical note or diagnosis as the payment trigger sent to an external reviewer.

If you are considering an authorization at booking instead, compare the appointment lead time with the provider's actual capture deadline. Stripe documents that uncaptured authorizations expire. Do not assume a reservation made weeks before the appointment will remain available or rely on a single network's timing for every card.

• Fee: fixed, variable or part of a separately reviewed recurring service.
• Trigger: the exact operational event that permits the charge.
• Timing: expected gap between booking, attendance and payment.
• Exceptions: cancellation, rescheduling, no-show and incorrect attendance status.
• Responsibility: which team handles a failed payment or customer query.

What permission should the payment setup capture?

Stripe's saved-payment guidance requires permission for future off-session charging and terms describing timing and amount determination. The clinic must confirm the requirements applicable to its own provider and arrangement. A saved token alone should not be treated as unrestricted permission for any later fee.

MerchantBridge's practical recommendation is to review the patient-facing payment explanation alongside the software configuration. Does the wording match the charge your system will actually initiate? Have cancellation or no-show fees been addressed separately if you intend to use them? Get the appropriate professional review of the terms; this article is operational payment preparation, not legal advice.

Plan for a charge that cannot complete automatically

Stripe notes that later customer authentication can still be required when a saved payment method is used. Ask your proposed provider how the practice can invite the patient to complete an outstanding payment through its approved flow. Decide which staff member sees that operational exception and how the appointment record avoids being marked paid prematurely.

Test with clearly fictional records in the provider's test environment: a completed visit, a canceled visit, an expired authorization and a payment requiring customer action. The goal is to verify the business event and payment result stay aligned. Do not send real patient names, medical records or card details to MerchantBridge to demonstrate a problem.

Bring the timing requirement into the processing review

MerchantBridge can explore potential payment relationships for licensed U.S. clinics and telehealth businesses. Describe the actual services, operating locations, booking platform, fee structure and intended charge timing. State what works today and what is only proposed so partner questions can focus on the unresolved connection.

Acceptance of the business and support for the workflow are separate confirmations. Provider approval, integration availability and account terms remain with the partner. Keep clinical care distinct from RUO research-product sales and submit only business information in the initial inquiry.