A telehealth platform can do everything right — licensed prescribers, identity checks, a clean refund policy — and still wake up to an email saying its payment account has been “deactivated following a review.” No warning, no appeal that goes anywhere, and a settlement reserve held for 90 to 120 days. Founders usually read this as a mistake. It almost never is. It is the predictable outcome of signing up with a payment aggregator whose risk model was never built for prescription billing in the first place.
Understanding why that happens — and what a real underwriting file looks like — is the difference between a business that bills reliably for years and one that spends every quarter rebuilding its checkout.
Aggregators are not underwriting you. They are underwriting a bucket.
Stripe, Square and PayPal onboard merchants instantly because they place everyone inside one large master merchant account. That speed is the product. The trade-off is that nobody reads your prescribing protocol before you take the first payment. Risk is assessed after the fact, by pattern: your chargeback ratio, your refund ratio, your descriptor complaints, keyword matches in your product copy, and the merchant category code you were slotted into.
When a pattern trips a threshold, the aggregator does not negotiate. Removing one merchant is cheaper than defending a category to its sponsoring bank. Card network rules also price risk at the portfolio level, so a handful of high-chargeback accounts in a shared bucket create a cost the aggregator simply removes rather than manages. Telehealth, peptides, supplements, nutraceuticals, prediction markets and anything with recurring refills sit near the top of that removal list.
The three triggers that cause most shutoffs
- Future delivery and recurring billing. You charge today for a shipment or consultation that happens later. The issuer treats unfulfilled value as the bank’s exposure, not yours.
- Regulated or restricted product language. Words like “prescription,” “GLP-1,” “research use only,” “peptide,” or “wager” are scanned for automatically, regardless of whether your operation is lawful.
- Chargeback velocity. Card brands monitor disputes as a ratio of monthly transactions. Subscription models that bill monthly and ship monthly can breach that ratio fast when refill reminders are weak.
Classification is the quiet variable
Before any bank looks at your financials, it looks at what kind of business you say you are. Two platforms with the same revenue and the same dispute history can receive completely different decisions because one is coded as a telemedicine service and the other as a direct-to-consumer supplement retailer. Founders who have read up on how business verticals are classified into categories tend to write much stronger applications, because they describe their operation in the language acquirers already use instead of inventing their own.
Get this wrong — even innocently, by picking the closest-sounding option in a dropdown — and you are exposed to a later “misrepresentation of business type” finding. That is one of the few things that moves a merchant onto the MATCH list, the shared terminated-merchant file that makes future approvals genuinely hard for years.
What an underwriter actually asks for
Specialized underwriting is slower than instant signup because a human reads the file. Expect to supply most of the following, and expect follow-up questions on anything vague:
- Three to six months of processing statements, or bank statements if you are pre-revenue.
- Incorporation documents, ownership breakdown and government ID for anyone holding a meaningful stake.
- A live, fully populated website — not a coming-soon page — with terms, refund policy, shipping timelines, contact details and clear pricing on every recurring plan.
- For telehealth: how patients are evaluated, who holds the prescribing license, which states or regions you operate in, and how pharmacy fulfillment works.
- For supplements and peptides: product labels, sourcing and manufacturing documentation, and marketing claims you are prepared to stand behind.
- Projected monthly volume, average ticket and highest expected ticket. Blowing past your stated volume is itself a reason for review.
- Chargeback history with reason codes, plus what you changed in response.
Security evidence belongs in the same file. Any merchant storing or transmitting cardholder data has an annual validation obligation, and the card brands’ own guidance on the PCI compliance process for merchants explains which self-assessment questionnaire applies to your setup. Using a tokenizing gateway rather than touching card numbers yourself usually reduces that scope considerably — and underwriters notice.
Recurring refill billing without the dispute spiral
Subscription prescription billing is where most telehealth chargebacks are born, and the causes are mundane. Cards expire. Patients forget a plan they signed up for in a clinical rush. A shipment is delayed and the charge lands first. The fixes are operational, not legal:
- Store credentials in a tokenized vault and run an account updater service so reissued cards do not fail silently and trigger involuntary churn.
- Send a pre-billing notice three to five days before each refill charge, with a one-click pause.
- Make the billing descriptor recognizable and include a working phone number — “unrecognized charge” disputes collapse when customers can call you instead of their bank.
- Charge after fulfillment is confirmed wherever the clinical workflow allows.
- Deploy dispute alerts so you can refund a questionable transaction before it becomes a counted chargeback.
Chargeback defense itself is evidentiary work: shipment tracking, consultation timestamps, acceptance of terms, IP and device data, and prior customer communications, assembled against the specific reason code. Generic rebuttals lose. Documented ones win often enough to keep ratios inside tolerance.
When a specialist provider is the right move
There comes a point where patching an aggregator relationship costs more than replacing it — usually the second warning email, or the first reserve. That is when it makes sense to work with a provider that places accounts directly with acquiring banks that already understand restricted verticals. Firms offering high risk merchant services, such as 2Accept, handle the parts founders tend to underestimate: preparing the underwriting file, matching the business to an acquiring bank that will keep it, integrating the gateway via API, hosted checkout or an EHR-native flow, and running chargeback defense afterwards. Their focus sits squarely on the verticals mainstream processors reject — telemedicine with HIPAA-compliant payment handling, peptides, prediction markets — along with subscription refill billing built on a tokenized vault with Account Updater, and FSA/HSA card acceptance for eligible services. The practical gain is not just approval; it is a processing relationship where your business model was disclosed and accepted up front rather than discovered later.
Build for the review you will eventually get
Treat payments as infrastructure with a compliance surface, not a checkout widget. Keep a current underwriting folder so a bank request takes a day instead of a fortnight. Maintain a second approved processor and a gateway that can route between them. Watch your dispute ratio weekly, not quarterly. Describe your vertical accurately everywhere — application, website, descriptor, marketing — because inconsistency is what underwriters read as risk. Businesses that do this stop treating account reviews as emergencies, which is the only sustainable position in a restricted category.

