What telehealth companies need from a payment processor
Telehealth is on Stripe's restricted list together with online pharmacies and card-not-present prescriptions. That single fact explains most of the payment pain. The processor is being asked to board a clinical business it may not be set up to supervise, in states it may not want the license exposure for.
What should the processor do before you are live?
A useful processor does three unglamorous things. It reviews the licenses and the model before you are live. It tells you which products and which states the approval covers. It has a dispute process, because medical billing and subscription supplements attract chargebacks that are really "I didn't recognize it" and chargebacks that are really "the visit did not happen."
Where does Frame Payments fit?
Frame is built around that review for US regulated businesses. The telehealth page says so, and it also says Frame has not published a list of models it will accept. A practice Stripe has already approved, with clean disputes, should not move for philosophy.
What can no processor waive?
A few things processors cannot waive. A card network rule about pharmacies is not overridden by a payfac's API. A state that requires a particular clinician relationship will not accept a checkout form as a substitute. And a merchant of record for software companies is not a telehealth strategy. They are not going to be the seller of a prescription.
What should you take to the review?
Bring the underwriter the same story your medical director would tell a board. If the marketing site tells a different story, you will fail the review no matter whose logo is on the application.
01What should the processor do before you are live?
A useful processor does three unglamorous things. It reviews the licenses and the model before you are live. It tells you which products and which states the approval covers. It has a dispute process, because medical billing and subscription supplements attract chargebacks that are really "I didn't recognize it" and chargebacks that are really "the visit did not happen."
02Where does Frame Payments fit?
Frame is built around that review for US regulated businesses. The telehealth page says so, and it also says Frame has not published a list of models it will accept. A practice Stripe has already approved, with clean disputes, should not move for philosophy.
03What can no processor waive?
A few things processors cannot waive. A card network rule about pharmacies is not overridden by a payfac's API. A state that requires a particular clinician relationship will not accept a checkout form as a substitute. And a merchant of record for software companies is not a telehealth strategy. They are not going to be the seller of a prescription.
04What should you take to the review?
Bring the underwriter the same story your medical director would tell a board. If the marketing site tells a different story, you will fail the review no matter whose logo is on the application.
05Where were the figures on this page read?
The sources list names the pages. This edition was read on November 9, 2026. Stripe's US domestic card rate in that reading is 2.9% + $0.30, and a dispute received is $15.
Which sources were checked?
What telehealth companies need from a payment processor cites 1 source link. Fee figures are from the edition dated November 9, 2026. A later reading is dated where it is cited.
Last verified .
Which related pages should you read next?
These 8 pages sit next to What telehealth companies need from a payment processor.