Healthcare
Patient payments that respect the front desk and the chart.
Fusion Payments builds payment processing for medical and dental practices: a terminal that keeps checkout moving, balances that pay from a text the day the claim settles, cards on file for treatment plans — and a hard boundary that keeps patient records off the payment page entirely.
- Dental
- Medical
- Specialty clinics
The review is free · your compliance officer is welcome on the call
Fusion Payments — The boundary
The chart and the card never meet.
“HIPAA-compliant payments” is a phrase vendors sell and auditors wince at. What holds up under questioning is architecture: two systems, one boundary, and a payment page that cannot disclose what it never held.
- Register
- FP-PHI-3
- Revision
- 2026-08
- Written for
- Your compliance officer
The patient's name, tied to a treatment
A first name, on a receipt
Diagnosis and procedure codes
An amount due
Clinical notes, imaging, history
A tokenized card
Insurance detail and claim status
A receipt destination — email or phone
crosses: one balance figure, passed by reference · nothing else
How the boundary is held
- BND-01
hosted: card fields render inside the processor's hosted frame — card data never touches the practice's website, or ours · the boundary home files as CTRL-01
- BND-02
tokenized: a stored card is a token that charges one merchant account and reads as nothing anywhere else · card on file · payment plans
- BND-03
scoped: the front desk takes payments and sees balances — no role is ever shown a stored card number · role-based access
* We do not claim HIPAA certification — no payment vendor can certify a practice, and a page that says otherwise is selling a sticker, not a control. Compliance is a property of your whole program. What we control is the boundary above, and we will answer for it in writing, to your compliance officer, before anything is signed.
Where patients pay
Four moments a patient pays. The desk only works one of them.
Checkout is the only moment that needs a person. The other three run on the rail — after the claim, on the plan's schedule, and overnight through the site.
-
At checkout
01 The desk, kept moving
Tap, chip, or wallet at the countertop terminal — the receipt is texted or emailed before the follow-up is booked, and the line behind the patient stays a line, not a lobby.
runs: countertop terminal · tap, chip, wallet · at the desk
-
When the claim settles
02 The balance is a text, not a statement
The patient-responsibility balance goes out by text or email the day insurance finishes its math, and it pays from the phone. No portal login, no envelope, no sixty-day paper chase.
moves: balance → text-to-pay → posted · no login, no paper
-
On the plan
03 Card on file, on schedule
Treatment plans split into installments the patient agreed to, charged against a tokenized card on the dates the plan sets. Nobody at the desk spends Friday afternoon calling balances.
charges: tokenized card · agreed dates · no monthly chase
-
After hours
04 The site takes the payment
A balance paid from the couch at 9 pm posts through the same stack into the same ledger, reconciled with everything the desk took that day.
posts: site → same rail · one ledger · by morning
* The boundary holds at all four moments — the practice-management system and the payment stack share a balance figure and nothing else.
Fusion Payments — The fee math
Figures illustrative*
The fee posts three dollars at a time. Volume is what makes it real money.
A practice never sees a $350 fee line — it sees $3.48 on a copay, four hundred times a month, netted out before anyone reads it. Add it up across a year and that line is a salary.
Patient-side collections — two-provider practice
- Collected by card, patient side
- $38,400.00
- Average payment
- $96.00
- Card fee — 2.9% + 30¢ × 400
- − $1,233.60
- Deposited
- $37,166.40
What that line costs in a year
- One month
- $1,233.60
- A quarter
- $3,700.80
A year, at that pace
$14,803.20
equivalent: a front-desk salary, January through April — collected for care, paid to the processor
The other way to run it
A cash price and a card price, posted plainly.
The card price carries the cost of acceptance; the practice keeps the price it set — on card volume, the processing fee goes to zero. It is a different mechanism from surcharging, it works the same for a copay as for a crown, and it is priced against your own statement, not a brochure.
Read the worked ticket* Figures illustrative — one representative month at a 2.9% + 30¢ blend. Your rate, card mix, debit share, and payer mix differ, and fixed monthly fees are not shown. Bring a statement; we total yours line by line.
The front desk
The desk runs the day. The stack shouldn't run the desk.
-
Checkout keeps pace with the schedule
Tap or wallet at the counter, receipt already in the patient's email before the follow-up is booked. The terminal is the fastest thing on the desk — as it should be.
runs: checkout in seconds · receipt by text
-
The phone payment, without the sticky note
A patient reads their card once. It is tokenized on entry — never written on a Post-it, never repeated back, never in a drawer.
holds: a token, not a number
-
The morning reconciliation is one screen
Terminal, text-to-pay, plan charges, and portal payments post as one batch, matched to the deposit. Yesterday closes before the first patient signs in.
posts: four channels · one ledger · txn ↔ deposit
Fusion Payments — The other practice
Your website, handled.
Fusion Payments builds and hosts the sites its payment stacks run behind — one vendor, one accountable team, from the first visit to the deposit. If yours is due for a rebuild anyway, ask about the website program.
terms: asked for, not posted — priced alongside your statement reading
Fusion Payments — Questions from the practice
Asked at the desk. Answered plainly.
Five questions practice managers actually ask, answered the way we answer them on the phone.
- Index
- 05 questions
- Revision
- 2026-08
- Asked of
- A person, first
Q-01Is patient data on the payment page?
No. The payment page holds an amount due, a tokenized card, and a receipt destination — no chart data, no diagnosis or procedure codes, no insurance detail. The card fields themselves render inside the processor's hosted frame, so card numbers never touch the practice's website or Fusion Payments' systems. A page cannot disclose what it never held.
Q-02Can patients keep a card on file?
Yes. The card is tokenized the first time it is used, and what the practice holds is the token — it can charge your merchant account on the schedule a plan sets, and it reads as nothing anywhere else. The front desk never sees or re-keys the number, and nothing card-shaped sits in a drawer.
Q-03How do payment plans work?
A treatment plan splits into installments the patient agrees to up front — amounts and dates, in writing. Fusion Payments charges the card on file on those dates automatically and posts each installment to the same ledger as the desk's payments, so plans reconcile like everything else instead of living on a spreadsheet.
Q-04Does this integrate with my practice management system?
In most cases, yes. Fusion Payments posts payments against the balance your practice-management system reports, keyed by reference, so posting is automatic and the two systems never share chart data. Bring the system's name to the statement review and we will confirm the integration path before anything is signed.
Q-05Are you HIPAA-certified?
There is no such thing as a HIPAA-certified payment vendor — compliance belongs to a practice's whole program, and it is not a vendor's to certify. What Fusion Payments provides is architecture: patient records never touch the payment page, cards are tokenized on entry, and access is role-based. We document that boundary in writing for your compliance officer.
*If your question is about a specific practice-management system or plan structure, ask it at the review — with the statement on the table, the answer is usually a demonstration.
Start here
Tell us how your organization needs to show up and get paid.
We map the practical path from the website to the transaction and the systems behind it.
call: (407) 395-2832 · a person answers, not a queue
write: info@fusionpayments.com · read by the people who build
* The first conversation is a reading, not a pitch — bring last month's processing statement and leave with every line on it explained. No fee, no obligation.
