Each balance goes out by text or email as a pay link, the payment posts to one ledger, and your team works only the accounts that need a person.
One office or many · 15+ automations · Part of the Dion suite
Illustrative preview · sample names, placeholder amounts
Dion Pay is a patient payment platform for dental practices and dental groups that keeps each patient's balance on one ledger, sends it as a text or email pay link, and posts every payment back on its own.
The problem
Patient balances are assembled from a claim here, a treatment charge there and a membership somewhere else — and multiplied by every office. Asking for the money starts with working out the number.
The film
A balance from the chair to paid: the team’s ledger, plans that ask on their own, and what the patient sees on their phone.
How the work flows
An illustrative day. The steps are real; the times are an example.
MDRCM sends the patient's share after adjudication. It lands on the ledger as one entry, stamped with the office that did the work.
One click from the patient's page sends a text or an email with a link to a checkout for that exact balance.
No account, no password. Card, or Affirm financing where the practice offers it.
Stripe confirms, the ledger is credited, the balance drops — nobody keys it in. Minutes later Finance and Insights have the same payment.
Before the office opens, instalments paid overnight are settled and every instalment due today is asked for.
One plan instalment was declined. It sits in the failures queue with the card's reason and a recovery step, not in an inbox.
Features
Patients → the patient's ledger
Insurance responsibility, treatment charges, membership dues and deposits are each one entry, marked with where it came from. Nothing is ever erased — every change stays in the history.
What comes out The same figure on the front desk screen, the statement and the pay link. Mistakes are fixed with a visible correcting entry.
Patient page → Send pay link
A text or email carries a link to a secure checkout for the exact balance. Card details go to Stripe, never to Dion. Affirm is offered at checkout where the practice has it on.
What comes out A paid balance, a numbered receipt, and the method and time on the ledger.
Payment plans
Split a balance into scheduled instalments, or accept a plan agreed in Dion Clinical. Every plan shows its progress, the next due date and anything that needs a person.
What comes out A pay link for each instalment on its due date; the plan advances only when money arrives.
Available Charging a saved, patient-authorised card on the due date is built — switched on per practice, then per plan, and only on a signed plan.
Statements
Each statement freezes the figures it was issued with, with an aging view and a pay link printed on it. Overdue statements are filtered in one click.
What comes out A statement a patient can hold that always matches what was sent. Generated every month.
Failures · Disputes
Declines become ranked, deduplicated work with the card's reason in plain words. Disputes carry their evidence deadline; early fraud warnings prompt a refund while one still helps.
What comes out One queue for what failed, one for what is contested — nothing lost in a notification email.
Collections
Every overdue account moves through a clear sequence of reminders that ends with a call from a person. Nothing goes to an agency or a credit bureau.
What comes out Today's list of who is due for which message, sendable one at a time or in bulk, only during daytime hours.
Insurance receipts
Each posted remittance from MDRCM arrives as one receipt with the claims it pays and any adjustments.
What comes out What each carrier check or EFT paid, and what is still waiting to be applied.
Deposits · Unapplied credit
Every Stripe payout is broken into the payments behind it. Money that names no charge sits in its own list until someone applies it.
What comes out A deposit report you can export to CSV, and no mystery credit on an account.
Terminal
Pair a card reader at the front desk; a tap posts to the same ledger as an online payment.
What comes out One record for the patient, whichever way they paid.
Available Built — turned on per location as each office's readers are registered.
Analytics · Export
Outstanding balances by age, payments by method, and balances by practice and by office — all computed from the ledger, not a page of results.
What comes out CSV exports of the registers behind every total.
What runs on its own
What gets done without anyone being asked, and what it leaves behind.
| What | When | What it produces |
|---|---|---|
| Post a payment to the ledger | The moment Stripe confirms it | The balance drops and a numbered receipt exists. |
| Settle a delayed payment | When a slower payment clears or fails | The ledger follows the final outcome, not the first attempt. |
| File a failed payment | The moment a payment or instalment fails | A ranked item in the failures queue with the card's reason. |
| Record a refund | The moment a refund is issued or changes | A visible refund entry on the patient's ledger. |
| Open a dispute | The moment a chargeback is filed | A dispute with its evidence deadline, updated through to its close. |
| Flag early fraud warnings | The moment the card network warns | A prompt to refund before a dispute lands. |
| Save a patient's card | When the patient finishes the save-card link | A card on file tied to the patient's authorisation. |
| Report each deposit | Every time Stripe pays out | The payments inside each bank deposit. |
| Post the patient's share of a claim | When MDRCM finishes a claim | A charge on the ledger stamped with its office. |
| Post insurance receipts | When MDRCM posts a remittance | A receipt with the claims it pays. |
| Take charges from other Dion apps | When Lead Intelligence, Clinical or Patient Engagement send one | Deposits, plans and memberships on the same ledger. |
| Send due plan instalments | Every morning | A pay link for each instalment due; paid ones settled. |
| Generate monthly statements | Monthly | Frozen statements for every open balance. |
| Share payments with the rest of Dion | Within minutes | Finance and Insights see the same payments. |
| Refresh patients and contacts | Continuously | Names and contacts current from the practice system. |
| Check payments against the ledger | Overnight | A report for a person to review — never an automatic fix. |
You choose how far it goes
Where money moves, Pay runs on written rules you can read, not a model’s judgment. Some steps can run fully on their own within limits you set; some stay with a person by design.
| Workflow | Assist | Your control |
|---|---|---|
| Posting payments | Always automaticPayments from links, plans and readers post themselves the moment Stripe confirms them. | Append-only: a wrong entry is reversed in view, never erased. |
| Plan instalments | On the due date Pay sends the patient a pay link for the instalment; the patient pays. | Switched on plan by plan, only on a signed plan. A refused charge never moves the plan forward. |
| Monthly statements | Statements are prepared every month; your team reviews them and sends. | Per-practice auto-send switch. |
| Collections messages | Pay works out who is due for which step; a person sends, one at a time or in bulk. | Daytime send hours. Collection holds. A practice can be held from texting entirely. |
| Charges from other Dion apps | Always automaticDeposits, plans, memberships and claim responsibility post as they arrive. | Each app is limited to its own practices and can add to the ledger, never clear a patient's debt. |
| Large staff charges | Charges above the practice's threshold wait off the ledger for a second person to approve. | A named billing approver per practice. |
| Reconciliation | Overnight, Pay checks payments against the ledger and reports anything that doesn't match. | Never self-corrects — a person decides every fix. |
| Disputes and fraud warnings | Filed with the deadline in view; a person refunds or submits evidence. | The evidence clock on every dispute. |
Works with the rest of Dion
Pay holds the one balance a patient sees. The other Dion apps don’t charge patients on their own — they post to Pay’s ledger against the same shared patient record, and they hear back when the patient pays. Dion Pay is part of Dion Health, the healthcare management company.
Built for one office or fifty
What it takes off your team
Enter your volume across every location. The arithmetic and every assumption are on the page.
Your volume
Assumptions — edit to match your practice
Estimate — change the assumptions to match your practice. The defaults are conservative guesses, not measurements from any practice: tasks = payments through Pay + instalments due + failed payments; hours = each task times its minutes.
Who it’s for
Trust and control
No entry is edited or deleted. Corrections are new entries, with the history kept.
Dion never sees or stores a card number.
Staff see only the practices granted to them. Sign-in is limited to approved domains.
Opening a patient's ledger is logged. Large staff charges need a second approver.
Dion Pay is a patient payment platform for dental practices and dental groups. It keeps what each patient owes on one ledger, sends the balance as a text or email pay link, and posts every payment back automatically. Payment plans, monthly statements and a worklist for the accounts that need a person run from the same ledger.
Dion Pay is for dental practices, from a single office to a group with many locations, and for the people who handle patient balances: front desk, office managers, treatment coordinators and group owners. Each person is granted only the practices they work for, so a group can share one ledger without everyone seeing everything.
Dion Pay is dental payment software that replaces the mix of spreadsheets, separate text-to-pay tools and hand-keyed payments many practices use to collect from patients. The patient pays from a link, the payment posts to the ledger without anyone typing it in, and statements and reminders come from the same balance the front desk sees.
Dion Pay sits beside your practice management system rather than replacing it. Patients and contacts stay current from the practice system where it is connected, and the patient's share of a processed claim arrives from MedicalDentalRCM. Payment plans agreed in Dion Clinical and case deposits from Lead Intelligence post to the same ledger.
Dion Pay does not use AI to decide who is charged. Money moves by written rules: a payment posts when it is confirmed and an instalment is requested when it is due. People make the judgment calls, such as who to call or how to answer a disputed charge, and large staff charges wait for a second person to approve them.
Dion Pay handles patient billing information with access controls and an audit trail of the kind the HIPAA security rule describes. Staff see only the practices they are granted, and every opening of a patient's ledger is recorded. Card numbers go to the payment processor and are never stored by Dion, and patients need no account or password.
Yes. Every ledger entry carries the office that did the work, so balances roll up by office and by practice for a group view. Staff are granted exactly the practices they work for, and each practice's payments go to its own payment account, so money is never pooled across entities.
Start with the live demo on this page. Dion configures the practice's settings and connects its payment account, and once that is done the front desk can send its first pay link by text or email from the patient's page. The other Dion apps your practice uses post to the same ledger.
See it in the live demo, or sign in if your practice is already set up.