Payment Processing for Therapy: Four Decisions That Change the Rate
A framework for payment processing in a medical practice: card-on-file consent, HSA and FSA cards, effective rate versus headline rate, and whether the processor sits inside the EHR.
Action required
Denial recovery queue
01 · Classify
Eligibility, coding, documentation
02 · Correct
Fix the root record
03 · Respond
Resubmit or appeal on time
Reason → owner → deadline → evidence → outcome
At a glance
What you’ll leave with
- Choose a processor on four decisions: card-on-file consent that covers no-show fees, HSA and FSA authorization at your merchant category code, effective rate versus headline rate, and whether the processor sits inside the EHR.
- A stored card is a network-rules decision first: obtain express informed consent that names how the credential will be used, and never store the card verification code after authorization.
- Therapy received as medical treatment is a qualified medical expense. Confirm your processor transmits a health-care merchant category code so HSA and FSA cards authorize at the desk.
Payment processing for a medical practice looks like a commodity until the first no-show fee bounces, the first HSA card declines at check-in, or the first monthly statement shows fees that were never in the demo. The advertised percentage is the least useful number on the quote. What changes the money you keep, and the work the front desk does, are four decisions: whether you can store a card on file with consent that covers missed-appointment charges, whether HSA and FSA cards will authorize under your merchant category code, whether the quote is a headline rate or the effective rate after interchange, monthly fees, PCI, and chargebacks, and whether the processor sits inside the EHR or beside it.
The decision
How should a therapy practice choose a payment processor?
Judge a processor on four decisions, not the advertised percentage. Can you store a card on file with consent that covers no-show fees. Will HSA and FSA cards authorize at your merchant category code. Is the quote the effective rate after interchange, monthly fees, PCI, and chargebacks. Does the processor sit inside the EHR so charges post to the visit. Get those answers in writing, and ask for a quote that itemizes every fee.
A therapy practice is not a retail counter. The same card is used for a copay at check-in, a patient-responsibility balance after the remittance posts, a private-pay session, and, when the policy allows it, a missed-appointment fee. Those are different transaction types with different consent, different card-network flags, and different tax treatment. A processor that is fine for a one-time checkout can still fail the week a family no-shows and the front desk has no stored credential, or the week a parent hands over an FSA card and the authorization declines because the merchant category code is wrong.
Treat the choice the way you would treat practice software or a clearinghouse: write the tests before you sit through a demo. The comparison below is that test. Run every finalist through the same four rows, with your own visit mix, not the vendor’s sample charges.
The centerpiece
What is the difference between a headline rate and an effective rate?
The headline rate is the percentage a processor advertises. The effective rate is what actually leaves each deposit: interchange set by the card networks, the processor’s markup, monthly or PCI fees, and chargeback costs. Two quotes with the same headline can produce different deposits. Ask every vendor to itemize those components in writing, or treat the quote as incomplete.
Interchange is not a processor’s invention. Card networks set it by card brand, card type, and how the transaction is submitted, and it is usually the largest piece of what you pay. The processor then adds its own markup, which may be a second percentage, a per-transaction fee, or both. Monthly account fees, PCI non-compliance fees, terminal rental, chargeback fees, and batch fees sit on top. A quote that names one percentage and stays silent on the rest is not cheaper. It is incomplete. Do not invent a typical rate, and do not accept one from a sales deck. Ask for a quote, in writing, that lists every line.
Those cost lines only matter if the processor can also do the work. The table below is the centerpiece of the evaluation: four decisions that change both the effective rate and the daily workflow. Score every finalist on the same rows. A cheaper headline that fails card-on-file consent or HSA authorization is not cheaper once the front desk is collecting by phone.
Four decisions that change what you keep, and the work around it
Comparison| Decision | What actually changes | What to verify before you sign |
|---|---|---|
| Card-on-file for no-show fees | A stored credential turns a missed-appointment fee from a statement into a charge the policy already named. Without consent that covers that use, the charge is a dispute waiting to happen. | Written cardholder consent that names how the stored card will be used, including missed-appointment fees, last four digits, how to cancel, and how the practice notifies of changes. Confirm the processor vaults the card and never stores the verification code after authorization. |
| HSA and FSA handling | Families with these cards expect to pay for therapy that treats a diagnosed condition. A wrong merchant category code declines the card at the desk. A no-show fee is not medical care, so it may not belong on these cards at all. | Ask which merchant category code the processor will transmit. Health-care codes (physicians, hospitals, and other medical care providers) let FSA and HRA debit cards authorize without an inventory system. Confirm HSA, FSA, credit, and debit are all accepted, and that receipts itemize the service. |
| Headline rate versus effective rate | The percentage on the homepage is not the percentage that leaves the deposit. Interchange, monthly fees, PCI fees, and chargebacks move the number, and they move it differently by card mix. | Itemized quote covering interchange pass-through or bundled pricing, per-transaction fees, monthly fees, PCI fees, chargeback fees, terminal or software fees, payout timing, and what happens to pricing if volume falls. Same visit mix for every vendor. Ask for a quote rather than a typical rate. |
| Processor inside the EHR or beside it | Inside the EHR, the front desk charges the card on file from the visit, posts the payment to the same record, and collects a no-show fee without a second login. Beside it, someone exports, retypes, and reconciles two ledgers. | Charge, refund, and void from the appointment itself. Payment status writes back to the chart and the family ledger. Payout reports match visits, not a weekly bulk deposit you have to unpack. Card-on-file collected at booking is available at check-in. Exit: how you take the tokens or the history with you. |
Worked example
How the four rows flip a cheaper-looking quote
Fictional case
Two quotes, one scorecard
North Loop Pediatric OT is a fictional solo practice used only to show the method. The owner sees about twenty private-pay and copay visits a week, takes a card at most of them, and wants to charge the no-show fee named in the attendance policy. Two processors make the shortlist.
A standalone processor. The sales page leads with one percentage. Card-on-file exists in a separate vault. HSA and FSA “should work.” The owner would log into a second dashboard to charge a missed visit, then type the payment into the EHR. The quote does not itemize interchange, PCI, or chargebacks.
Processing that lives in the EHR. The quote lists interchange pass-through, a per-transaction fee, payout timing, and chargeback handling, and it says “ask for a quote” on volume tiers rather than advertising a single percentage. Card-on-file is collected at booking. The visit screen can charge that card, including a no-show fee the family already consented to. The merchant category code is a health-care code.
On headline rate, A looks cheaper. On the four rows, A fails three: no written consent language for no-show use, no confirmed merchant category code, and a second ledger for every refund. B’s itemized quote is the only one that can be compared to a deposit. The owner still asks B for the same visit mix in writing. The method did not pick a brand. It discarded the quote that could not be verified.
Send both vendors the same email: itemize interchange, monthly fees, PCI, and chargebacks against last month’s actual card mix; confirm the merchant category code; attach the card-on-file consent the processor expects; and show a refund posting back to a fictional visit. Keep A in the race only if those answers arrive in writing. Most of the time they do not, which is the point of the test.
Stored credentials
Can I store a card on file to charge a no-show fee?
Yes, if the cardholder gave express informed consent that names how the stored card will be used, including missed-appointment charges, and if a fee is permitted for that patient. Card networks require that consent before you store a credential. PCI forbids storing the card verification code after authorization. Medicare allows a missed-appointment fee only when the same policy and amount apply to every patient, billed to the patient, never to Medicare. Check each payer contract.
Visa’s stored-credential rules are the clearest public statement of what “consent” means in this market, and other brands run parallel requirements. Before you store a payment credential for a future charge, you obtain the cardholder’s express informed consent to an agreement that names the last four digits, how the stored card will be used, how the cardholder will be notified of changes, the expiration of the agreement if there is one, and, for merchant-initiated charges, the event that prompts the charge, how the amount is determined, and how to cancel. You retain that agreement for as long as the consent lasts, and you produce it if the issuer asks. A buried sentence in the intake packet is not that agreement. A checkbox that says “keep this card on file” without naming no-show fees does not cover a no-show fee.
The fee itself is a separate legal question from the card. CMS treats a missed-appointment charge as a charge for a missed business opportunity, not for a service. Medicare permits the practice to bill the beneficiary directly when the same policy and the same amount apply to Medicare and non-Medicare patients alike, and the charge never goes on a Medicare claim. Medicaid generally runs the other way: participating providers accept the state payment as payment in full, and a missed-visit fee is often not allowed. Commercial contracts vary. The no-show fee scripts and the cancellation policy template cover who you may charge. The processor only covers whether you have a credential and the consent to use it.
Copy-ready
Card-on-file consent that covers a no-show fee
Adapt this to your financial policy and have counsel review it. Replace bracketed values. Collect it at intake, store it with the chart, and charge only the uses it names.
Card on file: consent to store and charge
I authorize [Practice name] to store the card ending in [last 4] and to charge it for:
• The estimated patient share at each visit (copay, deductible deposit, or private-pay fee), as disclosed before the visit.
• Patient-responsibility balances that remain after insurance posts, as shown on an itemized statement.
• Missed-appointment or late-cancellation fees of $[amount], as described in the attendance policy I received, when I miss a visit or cancel with less than [24/48] hours’ notice, and only if a fee is permitted for this account.
The practice will notify me at [email / phone] before changing this agreement. I can cancel this authorization by [phone / email / portal] and the practice will stop using the stored card after that notice, except for charges already incurred.
This authorization continues until I cancel it or until [date / end of care]. I understand the card verification code is not stored after authorization.
Signature and date: ______________________
Tax-advantaged cards
Do therapy practices need to accept HSA or FSA cards?
You have no federal duty to accept them, but families with these cards expect to use them for therapy that treats a diagnosed condition. The IRS treats therapy received as medical treatment as a qualified medical expense, and FSA and HRA debit cards authorize at merchants with health-care merchant category codes. Confirm your processor transmits a health-care code. A retail code declines the card.
Qualified medical expenses follow Internal Revenue Code section 213(d): diagnosis, cure, mitigation, treatment, or prevention of disease, or care that affects a part or function of the body. Publication 502 includes “therapy received as medical treatment.” An IRS FAQ states that therapy to treat a diagnosed condition is a medical expense that an HSA, FSA, Archer MSA, or HRA may pay, and that marital counseling is not. Speech, occupational, and physical therapy furnished as treatment for a diagnosed condition sit on the qualifying side of that line. General wellness, enrichment, or a program that is not medical treatment does not. The family’s plan administrator, not the front desk, is the substantiation authority. Keep itemized receipts so the family can document the service.
Acceptance at the terminal is a merchant-category-code problem, not a clinical one. Revenue Ruling 2003-43 and Notice 2006-69 limit FSA and HRA debit cards to merchants and providers with health-care merchant category codes (physicians, pharmacies, dentists, vision-care offices, hospitals, and other medical care providers). At those merchants the card can authorize without an Inventory Information Approval System. At grocery, discount, and similar stores, the IRS requires an inventory system or the 90-percent rule after the transition period in Notice 2007-2. A therapy clinic should never need that inventory system. What it does need is the right code on the authorization. If HSA or FSA cards decline at your desk, the first call is to the processor: what merchant category code is going out with the charge? Ask them to confirm a health-care code in writing.
Workflow
Should payment processing be built into the EHR?
Processing inside the EHR lets the front desk charge the card on file from the visit, post the payment to the same record, and collect a permitted no-show fee without a second login. A processor beside the EHR means exporting, retyping, and reconciling two ledgers. Integration is a workflow question, not a feature checkbox. Watch whether charges, refunds, and payouts write back to the chart.
The daily test is concrete. A copay collected at check-in should land on that appointment, not in a processor dashboard someone reconciles on Friday. A refund should reverse the same visit. A no-show fee should attach to the missed slot, with the consent already on file. Payout reports should break down by session, so the deposit matches the schedule. Some therapy EHRs collect a card at booking, charge it when the visit is finalized, and pay out daily through the processor. Callie’s scheduling tools do that with Stripe, and other than the card processing fee Callie does not take a cut. That is one shape of “inside the EHR.” The row in the comparison table is still the test: charge, refund, and status on the appointment, or a second system the front desk has to remember.
HIPAA follows the work, not the brand. HHS is explicit that a financial institution processing a consumer’s card, check, or electronic funds transfer for health care payment is providing its normal financial services, not acting as your business associate for that transfer. The EHR that stores the token next to the chart, invoices families, or runs billing on your behalf is a different relationship: that vendor typically is a business associate, and a written agreement belongs in place before any patient information flows. Ask which role each company is playing. A processor that only moves funds, and an EHR that holds the record, are not the same contract.
Scope
What PCI work remains when the processor vaults the cards?
You still have PCI work. Outsourcing the vault can shrink the questionnaire you file, often to SAQ A when all card-not-present data stays with a compliant processor and never touches your systems. You still confirm that processor’s attestation, keep paper receipts secure, and never store the card verification code after authorization. Your acquirer tells you which SAQ applies. Do not guess it from a sales slide.
PCI DSS Self-Assessment Questionnaire A is written for merchants who accept only card-not-present transactions, outsource all processing of account data to a PCI DSS compliant processor, and do not store, process, or transmit account data electronically on their own systems. Typed-in charges through a virtual terminal on an isolated computer are a different questionnaire (SAQ C-VT). A practice that keys cards into a spreadsheet, photographs cards, or saves CVV for later charges has left those short questionnaires behind. The payment brands and your acquirer decide which form you file. The operational rule for a small clinic is simpler than the form names: keep card data out of email, shared drives, and paper charts, and let the processor’s vault be the only place a full account number lives.
- 01
Inventory how cards actually enter the practice
Online booking, a hosted payment page, a terminal at the desk, a virtual terminal for phone-in cards, and any card a staff member writes down. Each channel has a different PCI shape. If any channel puts account data on a practice computer, say so before anyone assigns you SAQ A.
- 02
Get the processor’s attestation in writing
SAQ A requires you to have reviewed the processor’s PCI DSS Attestation of Compliance for the services you use. Ask for it. A marketing badge is not that form.
- 03
Confirm the merchant category code and the stored-credential flags
The same onboarding call should confirm the health-care MCC for HSA and FSA cards, and that stored-credential transactions (including unscheduled charges such as a permitted no-show fee) are flagged the way the card networks require.
- 04
File the SAQ your acquirer assigns, on that acquirer’s calendar
Annual self-assessment is the common pattern for small merchants. Your acquirer, not the EHR vendor, tells you which questionnaire and what evidence they want. Put the due date on the annual compliance calendar.
Once the PCI path is named, put the commercial terms next to it. The checklist below is the same four decisions plus the exit questions vendors like least. Send it as an email. Written answers are the quote.
Field checklist
10 itemsBefore you sign with a payment processor
- Itemized quote covering interchange or bundled pricing, per-transaction fees, monthly fees, PCI fees, chargeback fees, equipment or software fees, and payout timing, against your own visit mix. Ask for a quote. Do not accept a typical rate.
- Written card-on-file consent that names copays, posted patient balances, and missed-appointment fees, plus last four digits, cancellation, and how you notify of changes.
- Confirmation that the processor vaults the credential and that the card verification code is never stored after authorization.
- Merchant category code in writing, and a test HSA or FSA authorization in the trial.
- Charge, refund, void, and payment status on the appointment inside the EHR, or an honest count of extra logins if the processor sits beside it.
- Payout reports that break down by session, not only a bulk deposit.
- Who handles chargebacks, what the fee is, and how the family is notified.
- Which PCI SAQ the acquirer assigns, and the processor’s current Attestation of Compliance for the services you use.
- Whether the EHR vendor is a business associate (almost always yes) and whether the processor is only moving funds or also doing billing on your behalf.
- Exit terms: how stored cards, payment history, and open payment plans leave with you, in what format, at what cost, and on what timeline.
“A headline rate is a marketing line. The processor you can live with is the one that charges the card you already have consent to use, on the visit it belongs to, at the effective rate you can find on the deposit.”
Quick answers
Payment processing for a medical practice: FAQ
How should a therapy practice choose a payment processor?
Choose payment processing for a medical practice on four decisions, not on the advertised percentage. Confirm card-on-file consent that covers no-show fees, HSA and FSA authorization at a health-care merchant category code, an itemized effective rate (interchange, monthly fees, PCI, chargebacks), and whether charges post inside the EHR or in a second system. Ask for a written quote against your own visit mix.
Can I store a card on file to charge a no-show fee?
Yes, when two conditions both hold. First, the cardholder gave express informed consent that names how the stored card will be used, including missed-appointment charges, last four digits, cancellation, and notice of changes. Card networks require that agreement before you store a credential, and PCI forbids storing the card verification code after authorization. Second, a fee is actually permitted for that patient: Medicare allows a missed-appointment charge only when the same policy and amount apply to every patient, billed to the patient and never to Medicare; Medicaid often forbids the fee; commercial contracts vary. The processor stores the credential. Your policy decides whether you may use it.
Do therapy practices need to accept HSA or FSA cards?
No federal rule requires it, but families with these cards expect to pay for therapy that treats a diagnosed condition. The IRS treats therapy received as medical treatment as a qualified medical expense, and FSA and HRA debit cards authorize at merchants with health-care merchant category codes. Confirm your processor transmits a health-care code. A missed-appointment fee is not medical care, so charge it to a regular card when a fee is permitted. Keep itemized receipts; the plan administrator substantiates the expense.
Should payment processing be built into the EHR?
Prefer it when the alternative is a second ledger. Processing inside the EHR lets the front desk charge the card on file from the visit, post the payment to the same record, and collect a permitted no-show fee without another login. A processor beside the EHR means exporting, retyping, and reconciling. The test is write-back: charges, refunds, and payouts on the appointment, or a dashboard someone has to remember. Some therapy EHRs, including Callie, collect a card at booking and charge it when the visit is finalized. Judge that on the workflow, not the logo.
What is the difference between a headline rate and an effective rate?
The headline rate is the percentage on the sales page. The effective rate is what leaves each deposit after interchange (set by the card networks), the processor’s markup, monthly or PCI fees, and chargebacks. Two quotes with the same headline can produce different deposits because the rest of the stack differs. Ask every vendor to itemize those lines against your own card mix. If they will not, treat the quote as incomplete. This article does not publish typical rates; processors change them, and a typical rate is not your rate.
Do I need a business associate agreement with my payment processor?
It depends on what the company is doing. HHS says a financial institution processing a consumer’s card, check, or electronic funds transfer for health-care payment is providing its normal financial services, not acting as your business associate for that transfer. An EHR, billing vendor, or processor that also invoices families, stores tokens next to the chart, or runs accounts receivable on your behalf is typically a business associate, and a written agreement belongs in place before patient information flows. Ask which role each vendor is playing, and keep the signed agreement in the same folder as your other BAAs.
Primary sources
Bibliography / 10- 01Business Associates Frequently Asked QuestionsU.S. Department of Health & Human Services
- 02Medicare Claims Processing Manual, Chapter 1, §30.3.13, Charges for Missed AppointmentsCenters for Medicare & Medicaid Services
- 0342 CFR §447.15, Acceptance of State payment as payment in fullCode of Federal Regulations
- 04Publication 502, Medical and Dental Expenses (Therapy)Internal Revenue Service
- 05FAQs about medical expenses related to nutrition, wellness, and general health (Q7, therapy)Internal Revenue Service
- 06Revenue Ruling 2003-43, Debit cards for health FSAs and HRAsInternal Revenue Service
- 07Notice 2006-69, Debit cards, substantiation, and inventory information approval systemsInternal Revenue Service
- 08PCI DSS Self-Assessment Questionnaire A, Version 4.0PCI Security Standards Council
- 09FAQ: Can card verification codes/values be stored for card-on-file or recurring transactions?PCI Security Standards Council
- 10Improving Authorization Management for Transactions with Stored CredentialsVisa
Written by Callie Editorial
Published November 10, 2026
Educational content, not legal, billing, or patient-specific clinical advice.