Northwest Payment Brokers
For dental practices

A $3,000 crown costs you $90 in fees. Every time.

Dental tickets are large and they repeat: crowns, ortho, implants, treatment plans. At typical rates a busy practice hands $30,000 or more a year to processing. The procedures don't change; what you pay to collect for them can.

Get my free statement review
A dental office front desk runs a patient's credit card on a Dejavoo countertop terminal showing a $98 charge.

What dental offices are up against

High tickets, high fees

A percent that feels small on a $40 sale is real money on a $3,000 treatment. Across a day of crowns and ortho, those fees quietly pay for a hygienist's hours.

Cards on file for treatment plans

Phased treatment and in-house plans need a card kept on file. It has to be charged on schedule and stored the compliant way. The front desk should never re-key a number.

Practice-management software

Dentrix, Open Dental and Eaglesoft each want payments to post back clean. Pick the wrong processor and you match up the books by hand every day.

Patients notice fees

Adding a fee for a nervous patient is not the same as adding one for a contractor. The program has to fit the moment at the chair, not just the spreadsheet.

The program fit

The systems we’d quote

What happens to a card at your dental front desk

Dental patients pay in a few ways: at checkout after the visit, over the phone, or from a card kept on file for a treatment plan. Each path handles the card number differently.

At the counter, the terminals we recommend for dental offices encrypt the card number point to point, the moment the chip is dipped or the card is tapped. The strongest setup is a PCI-listed P2PE solution, which is validated as a whole: the device, the application, the key management and the decryption environment. With that in place and tokenization on top, your front desk computer, your practice software and your office network never hold the real number. They keep a token, a stand-in that only the processing company can match back to a card. A stolen front desk PC would give up no card numbers. It could still expose whatever it is signed in to, so that computer, its logins and the saved tokens need the same locks as any system with patient payment records. This protection comes from one specific terminal and processing pairing, not from card terminals in general, so ask any vendor to show you theirs on the PCI list. We ask for you and share the answer.

Treatment plans and phone payments take the other path. A card read to you over the phone, or typed into a virtual terminal to start a plan, goes in through a screen, so that screen is briefly in PCI scope in a way a terminal is not. Where it gets typed decides the risk. On the processing company's own hosted page, the number goes straight to their vault and comes back as a token before your software sees it. In a field your own system saves, it does not. Ask any vendor which one you get; we ask that question for you.

Set up this way, card numbers stay off your systems, and that is what cuts down your yearly PCI paperwork. Card data also stays apart from your patient charts.

PCI and HIPAA are separate rules for separate data, and the HIPAA exemption people quote is narrower than it sounds. Federal law places a processor's own transaction handling outside HIPAA, so a processor that only moves card data is usually not your business associate. That exemption is theirs, not your office's. A payment record you keep because a named patient paid for dental care is still your data under your rules. A vendor that goes further, such as sending patient statements, balance reminders or working your receivables, does that work on your behalf and should sign a Business Associate Agreement.

We never touch your patients' cards ourselves. We place the processing and the hardware, and we put in writing what each one does with card data.

Related payment options

Frequently Asked Questions

Can you store a card on file for treatment plans?

Yes. A virtual terminal keeps the card safely on file. You can charge phased treatment, balances and membership plans on schedule. The front desk never has to ask for the number again.

Do you work with Dentrix, Open Dental or Eaglesoft?

We match you to a processor that works with your practice software. Cards on file and payments post back on their own. They land in the patient ledger. Nobody types them in twice.

Should a dental office surcharge patients?

Sometimes, but with care. Many offices would rather use dual pricing. Others eat the fee on the insurance part. A tense checkout is a bad place for a surcharge. We walk through what fits your patients before anything goes live.

Can patients finance large treatment plans?

Yes. We set up patient financing. A patient can say yes to the whole plan and pay over time. Your office is paid in full up front. More patients say yes to big cases.

How do in-house membership plans get billed?

On a set schedule against the card on file. We set the plan to bill each month or each year. Staff never touch it.

What's the real saving for a practice my size?

Send one recent statement. At dental ticket sizes, the gap between a listed rate and a rate we bargain for is often thousands a year. We show you your exact rate and the savings in writing first.

Is any payment setup HIPAA certified for a dental office?

No. The federal government does not certify any company or product as HIPAA compliant, so read that label as sales talk. What a dental office can check: whether the company that runs your card payments is a PCI DSS Level 1 service provider, whether its encryption is PCI-validated point-to-point, and whether it will sign a BAA when the work calls for one.

Does my payment processor need to sign a Business Associate Agreement?

Usually not, if it only handles card data. Federal law puts a processor's own transaction handling outside HIPAA's reach. But the moment a vendor handles patient information on your behalf, a BAA is not optional, it is required. That covers patient statements, balance reminders by text, and accounts receivable work. If a vendor would touch patient health information, we will make sure they sign a BAA with your practice before it goes live.

What do encryption and tokenization actually do?

Encryption scrambles the card number inside the terminal at the moment of payment, so it travels as unreadable data. Tokenization replaces it with a substitute number for anything you keep on file, like a card saved for a payment plan. On a card tapped, dipped or swiped through a reader that is part of a PCI-listed P2PE solution, that combination keeps the real number off your front desk computer, out of your software and out of your backups. Two limits worth knowing. It depends on the entire deployment being a PCI-listed P2PE solution, device, application, keys and decryption together, not on the hardware merely looking modern or the reader alone appearing on a list. And a card read to you over the phone and keyed in is a different path, protected only if it is typed into the processor's own hosted page rather than a field your system stores.

See what your practice is really paying to collect.

One statement, 24 hours, your real number in plain English.