Key takeaways
- Telehealth is card-not-present by definition, which raises dispute exposure and underwriting scrutiny compared with an in-person clinic.
- Membership and subscription models must satisfy California's Automatic Renewal Law and clear refund terms to keep disputes low.
- Tokenized card storage and hosted fields keep payment data separate from health data and shrink compliance scope.
Telehealth providers payment processing in the Bay Area sits at the intersection of two things underwriters watch closely: healthcare and card-not-present billing. The region has an unusually deep telehealth bench, from venture-backed virtual clinics in San Francisco and Palo Alto to solo therapists in Berkeley and Marin, weight-management and hormone practices in Walnut Creek and San Jose, and hybrid practices that see patients in person in Oakland and by video everywhere else. Each has a slightly different processing profile, and the differences matter for approval, cost and dispute control.
How telehealth is classified
Most telehealth practices process under MCC 8011 (physicians), 8099 (medical services not elsewhere classified), 8021 (dentists) or 8049/8050 for specific specialties, depending on the provider type and the acquirer's judgment. The code affects interchange, and healthcare codes generally carry favorable rates. What changes the picture is the channel. A clinic that takes a card from a patient at the front desk in a chip reader is a low-risk, card-present merchant. The same clinic billing a video visit by keyed card or online form is card-not-present, and the acquirer's model for fraud and disputes changes accordingly. Practices that add memberships, prepaid packages or medication programs move further along that spectrum.
Membership models and the Automatic Renewal Law
Direct-care and membership telehealth has grown fast in the Bay Area. If you bill monthly or annually on a recurring basis, California's Automatic Renewal Law applies: present the recurring terms clearly before the patient agrees, get affirmative consent, send an acknowledgment that includes the terms and how to cancel, and offer online cancellation to anyone who enrolled online. There are additional notice rules for renewals of longer terms and for price changes; check the current rule with counsel. Treat this as a dispute-prevention system as much as a legal requirement. Patients who understood what they signed up for, received a reminder before the charge, and could cancel in two clicks rarely call their bank.
A purpose-built recurring billing platform records consent, sends pre-billing notices, handles failed-payment retries without hammering a card, and keeps an audit trail you can attach to a dispute response. Managing this manually inside an EHR is where practices tend to get into trouble.
Refunds, no-shows and the dispute file
Telehealth chargebacks come from predictable places: a patient disputes a no-show fee, a patient did not recognize the practice's descriptor, a membership renewed after the patient thought they had cancelled, or a medication program shipped a product the patient decided they did not want. Write your policies for each of those, post them, and have the patient acknowledge them at intake. Card networks monitor merchants around a 0.9%-1% dispute ratio, and a virtual practice with a few hundred visits a month can cross that line with a surprisingly small number of disputes. The mechanics are covered in more depth in Telemedicine Providers and Chargebacks: How to Keep Your Ratio Down.
Keeping payment data and health data apart
HIPAA governs protected health information; PCI DSS governs cardholder data. They are separate regimes and the cleanest architecture keeps them separate. Take cards through hosted payment fields so card numbers never touch your practice-management system, and store them as tokens through tokenization so a patient's card on file is a reference, not a number. That reduces your PCI questionnaire, and it means a breach of your clinical systems does not become a card breach as well. Confirm with your processor and counsel what, if anything, in a payment record constitutes PHI in your workflow; a line item that names a procedure can be, and a generic visit description generally is not.
Bay Area specifics that affect your setup
- Multi-state licensure: many Bay Area practices see patients in several states. Your processor will ask where patients are located, because the underwriting footprint follows the patients, not just the provider.
- Employer and platform billing: practices serving tech-company benefit programs often invoice the employer rather than the patient, which is an ACH or invoice relationship rather than a card one.
- Sliding-scale and community clinics in Oakland, Richmond and San Jose often mix grant billing, insurance and small patient payments, and want low per-transaction costs on the patient side.
- Compounded medication and weight-management programs draw extra underwriting attention because of the shipped-product component and the regulatory attention on those categories.
Choosing rails for different payment types
Patient copays and visit fees belong on cards, with a clear descriptor and instant receipt. Employer contracts, larger prepaid packages and B2B relationships often work better on ACH, which settles in 1-3 business days, costs a flat fee and avoids card disputes entirely. A practice that invoices institutions should look at invoicing tools that let the payer choose card or bank transfer from the same link. Payouts to contracted clinicians are a separate accounts-payable question, not a merchant-processing one, but the same platform can often handle both sides.
Underwriting: what to present
Have your professional licenses, a description of the services and any products shipped, your intake and consent documents, your refund and no-show policy, your membership terms, and a walkthrough of how a patient goes from booking to payment. If you dispense or ship medication, explain the pharmacy relationship and licensing. Practices that present this clearly get approved faster and on better terms than practices that describe themselves as a generic clinic and let the underwriter discover the membership program on their own.
Telehealth in the Bay Area is a mature, well-understood category for the right processor. The work is on your side: build the consent and refund machinery properly, keep the card data out of your clinical systems, and treat the dispute ratio as a clinical-quality metric rather than an accounting footnote.
Ready to get set up with Flux?
Cards, ACH, and stablecoins in one platform, with volume-based pricing. No setup fees or contracts.
Get Started