Telehealth Payment Processing: Collecting Payments for Virtual Visits

Telehealth has become a permanent part of healthcare delivery, and with it comes a payment challenge that in-person practices don’t face in the same way: collecting payment for a visit that takes place before, during, or after a video call, from a patient who may be in a different state, using a platform that may or may not be HIPAA compliant. This guide covers the payment requirements specific to telehealth billing.

1. Telehealth Payment Timing: Before, During, or After?

Telehealth practices have three options for when to collect payment:

Cash-pay and subscription telehealth practices — direct primary care, async care, mental health subscriptions — almost universally use pre-visit capture or recurring subscriptions. Insurance-covered telehealth typically uses post-visit billing after EOB.

2. Pre-Visit Payment Capture on WooCommerce

For pre-visit payment collection, the workflow on WooCommerce typically looks like:

1. Patient books appointment through a WooCommerce product/booking system
2. At checkout, patient enters card details and provides billing authorization
3. Card is authorized (hold) or charged immediately depending on practice policy
4. If hold: provider captures charge after visit completion; uncaptured holds expire automatically
5. Receipt generated and emailed to patient post-visit

ConvesioPay supports both authorization-only (hold) and immediate charge patterns on WooCommerce, giving practices flexibility in their collection timing.

3. No-Show and Late Cancellation Policies

Telehealth no-shows are a significant revenue loss for practices that don’t collect payment upfront. To enforce no-show fees:

• Collect card on file at booking (not just at visit time)
• Display the cancellation/no-show policy clearly at booking with explicit agreement required
• Store card credentials securely for later charge if needed
• Charge the no-show fee automatically when the condition is met

The authorization language at booking must explicitly state that the card may be charged for a no-show or late cancellation fee and specify the amount. Vague or buried language creates disputes.

4. Subscription Telehealth Models

Subscription-based telehealth, where patients pay a monthly fee for unlimited or capped visits, requires the same infrastructure as any membership model:

• Reliable recurring billing with low involuntary churn
• Network tokenization for automatic card updates
• Dunning management for failed charges
• Patient self-service to update payment methods

The additional complexity for telehealth subscriptions: multi-state licensing. A telehealth provider can only see patients in states where they’re licensed, which means subscription telehealth platforms often need to manage whether patients can be served based on their state at time of visit, even if they signed up from an eligible state.

5. Multi-State Payment Considerations

While payment processing itself is not state-regulated in a way that changes your processor requirements, telehealth across state lines introduces some payment-adjacent considerations:

• Sales tax on telehealth services — most states don’t tax medical services, but rules vary; some states tax certain telehealth services differently than in-person care. Consult your tax advisor for states where you have significant patient volume.
• Currency — US-only telehealth doesn’t require multi-currency, but international telehealth platforms need processors that support foreign currency acceptance without excessive FX fees
• State-specific billing requirements — some states have specific requirements for telehealth billing codes and documentation that affect what appears on the patient’s receipt

6. HIPAA Compliance for Telehealth Payments

Telehealth payment systems must meet HIPAA requirements just as in-person payment systems do. The telehealth-specific risks:

• Video platform integration — if your payment system is integrated with your telehealth video platform, confirm the entire stack has BAAs in place
• Email confirmations — visit confirmations and receipts sent by email must not include PHI in unencrypted messages; keep to financial confirmation details only
• Patient portal access — telehealth patients often access records and payment history remotely; strong authentication (at minimum, password + email verification) is required
• Async care documentation — async telehealth (messaging, photo-based consultations) often involves clinical content in the communication thread; ensure your billing system doesn’t inadvertently expose this in payment communications

7. Integrating Payment with Telehealth Platforms on WooCommerce

WooCommerce can serve as the commerce layer for telehealth practices in several configurations:

• Standalone patient billing portal — WooCommerce handles billing and payment; a separate telehealth platform handles video and clinical records
• Integrated booking + payment — WooCommerce Appointments or similar plugin handles scheduling; ConvesioPay handles payment at time of booking
• Membership + visit portal — WooCommerce Subscriptions manages membership billing; patients access care through a linked telehealth platform

For practices building the integrated model on WooCommerce, ConvesioPay provides payment processing, ConvesioPay supports subscription billing, and Convesio’s HIPAA-compliant hosting provides the infrastructure layer.

For more on HIPAA requirements, see HIPAA Compliant Payment Processing: The Complete Guide. For patient portal setup, see Patient Payment Portal: Building a Secure Online Payment Experience.