Why telehealth brands get dropped by payment processors

Why is telehealth high risk at all?

Risk here is not a judgement about your business, it is a prediction about chargebacks. Card-not-present, subscription billing, health claims and a product the cardholder sometimes does not recognise on a statement are each a risk factor, and prescription telehealth has all four.

Visa and Mastercard place telemedicine under merchant category codes that mark it as high risk, which changes underwriting, reserves and pricing before anyone looks at your specific business.

The subscription part is the one founders underestimate. A patient who forgets they signed up for a monthly refill disputes the charge rather than cancelling, and that dispute counts against you whether or not you refund it.

What changed in April 2026?

Visa's excessive dispute threshold dropped to 1.5%, counted on card-not-present transactions only. Crossing it puts a merchant into a monitoring programme with fees and remediation requirements attached.

For a brand doing a few hundred orders a month, 1.5% is a small number of disputes. Three in two hundred gets you there.

The practical defence is unglamorous and works. A recognisable billing descriptor, an email before every renewal rather than after, a cancellation path the customer can find without emailing you, and refunding a disputable charge before it becomes a dispute. Each of those removes chargebacks that would otherwise count.

Which processors actually work?

Stripe is the one worth being specific about, because it is the default most founders reach for and we support it. Stripe lists telemedicine among its restricted businesses, and does not sign a BAA for the core payments product. Plenty of telehealth brands do run on Stripe, and plenty get declined or terminated, and which happens depends on what you sell and how the account is presented. Treat approval as conditional rather than given.

Authorize.Net, paired with a high-risk acquirer, is the common alternative and is what brands move to when the first route closes. Dispense Flow supports both, so switching is a configuration change rather than a rebuild.

Specialist high-risk processors underwrite telehealth deliberately and price for it. They cost more per transaction and are far less likely to freeze you at the moment you are growing, which is the trade worth making once you have volume.

On HIPAA: a payment processor that only ever sees a name, an amount and a card does not necessarily need a BAA, because that is not protected health information. What matters is not sending clinical detail into the payment flow. Putting the medication name in the statement descriptor is the mistake to avoid, and it is also how patients end up disputing a charge they would rather not explain. The BAA question is covered here.

How do you avoid a frozen account?

Tell the truth in underwriting. Describe what you sell, that prescriptions are involved, and who dispenses. An account approved on a vague description is an account that gets reviewed again later, and the second review goes worse than the first would have.

Keep the dispute rate down with the operational basics above, and watch it monthly rather than quarterly.

Have the second gateway set up before you need it. The worst version of this problem is a freeze during a growth month with no alternative configured, because setting one up takes days you do not have when revenue has stopped.

Expect a reserve. A rolling reserve on a high-risk account is normal, and it changes your cash flow, so model it rather than discovering it.