Payment Solutions for Medical Billing Companies and RCM Firms
Quick answer: a medical billing company or RCM firm collects patient payments that belong to its client practices. That means two hard requirements: every payment must settle to the right practice's own merchant account, and your agents must be able to take payments by phone without handling card numbers. The way to meet both is one payment system that holds a separate merchant account connection per practice, routes each payment automatically, and captures card details on the phone keypad instead of in your agents' headsets. Shuttle does this across agent calls, IVR, payment links and bank payments.
A billing company serving 40 practices is running 40 businesses' receivables. The statements go out under each practice's name. The patient thinks they're paying their doctor or dentist, because they are. The practice expects its money in its bank account, reconciled against its ledger.
Most payment tools assume you're collecting your own money. The moment you collect for client practices, you inherit two problems those tools can't solve: where the money settles, and what happens to your PCI position when your agents spend all day taking cards over the phone. This guide covers both, plus the collection workflows (statements, plans, IVR self-pay) that billing operations actually run.
The money has to land in each practice's account
A merchant account is tied to one legal entity. Payments processed on it settle to that entity, and the card statement shows that entity's name.
Run every practice's patient payments through your own single merchant account and the problems stack up fast:
Settlement goes to you, not the practice. Now you're disbursing client funds from your own account, with the trust-accounting burden and timing risk that brings.
The patient's card statement shows your name. Patients don't recognise the billing company they've never heard of. Unrecognised descriptors get disputed, and those chargebacks land on your account.
Your acquirer sees unregistered aggregation. Processing other entities' payments through your own merchant account breaches most merchant agreements. We cover this fully in our guide to taking payments on behalf of your clients.
The clean model: each practice keeps (or gets) its own merchant account, and your system routes every payment to the right one. The practice keeps its own gateway relationship and settlement. You keep one operation, one workflow and one screen for your agents. Shuttle is built around exactly this: each practice connects its own merchant account or gateway credentials once, and routing happens per payment automatically, across 40+ supported payment gateways. One practice on Stripe and another on the acquirer their bank set up years ago both work; nobody has to switch.
Taking patient payments by phone without touching card data
Patient balances are collected on the phone. Statement queries turn into payments, outbound balance calls end in payments, and the patient on the line wants to settle now.
The default way billing teams handle this is the risky way: the agent asks for the card number and keys it into a virtual terminal. Once your agents hear or see card numbers, your operation is inside PCI DSS scope: the phone system, the call recordings, the agents' screens, the desktop environment, the training and vetting behind them. For a billing company, that's dozens of practices' patients' card data concentrated in one contact centre.
Two patterns keep card data out of your environment while keeping the phone channel:
Agent-assisted secure capture. The agent stays on the call. The patient types their card number on the phone keypad; the digits go to the payment gateway, and the agent sees only masked progress on screen. The conversation continues, and the card number never enters your phone system or recordings. This is how DTMF payment capture works.
IVR self-payment. The patient calls the number on their statement, keys in a reference and pays through an automated flow with no agent at all. This absorbs the routine statement payments so your agents handle the exceptions and the conversations that need a human.
Real calls fail in predictable ways, so the fallbacks matter as much as the happy path. Patient's card is in another room: send a payment link by SMS or email and they finish on their own phone. Call drops mid-payment: same recovery. Patient prefers not to use a card: take a bank payment on the same call. Every one of these is a payment that would otherwise become another statement cycle.
A note on recordings: billing operations already manage call recordings carefully because calls contain patient information. Keypad capture takes the card numbers out of those recordings entirely, so your payment flow stops adding card data to an already sensitive asset. PCI DSS governs the card data; your obligations for patient health information are a separate matter and stay with your existing compliance programme.
Statements, plans and the rest of the collection workflow
Phone is the pressure point, but billing operations collect across a wider surface, and per-practice routing has to hold everywhere:
Pay-now on statements. A payment link on the e-statement or patient portal message, and an IVR number on the printed statement, both settling to the issuing practice's account.
Payment plans. Patient balances are frequently paid in instalments. Agreeing a plan on the phone and automating the collections beats chasing a new payment every month.
Reconciliation per practice. Every payment carries its practice and patient references, so posting back to your billing platform or the practice's ledger is a data exercise, not a matching exercise. Shuttle exposes this through payment APIs and webhooks rather than assuming any particular practice management system.
The same applies to dental billing companies, veterinary billing services and specialty RCM firms: the operational shape (many client practices, each with its own merchant account, phone-heavy patient contact) is identical even where the terminology differs.
Why billing companies can go live quickly
An RCM firm doesn't wait for anyone to adopt anything. The patient call volume is already in your contact centre, the practices' merchant accounts already exist, and every payment your agents take today is a payment you could route properly tomorrow.
The practical path: talk to us about your practice mix and call volume. If your team wants to explore the technical side first, docs.shuttleglobal.com covers the flows, and sandbox accounts are available for testing before any practice account is connected. Adding each practice after the first is configuration, not a new project.
Medical billing payments FAQ
How do medical billing companies take patient payments by phone without PCI problems?
Use keypad capture instead of verbal card numbers. Either the agent stays on the line while the patient types their card number (the digits route to the payment gateway, not the agent), or the patient pays through an IVR flow with no agent involved. In both patterns card data stays out of your phone system, recordings and agent screens, which keeps those systems out of PCI DSS scope.
Can we collect for multiple practices through one system?
Yes, if the system supports per-client merchant account routing. Each practice connects its own merchant account or gateway credentials, and every payment routes to the right one automatically. Your agents work one queue; each practice's money settles to that practice.
Does the money come to us or to the practice?
To the practice, directly. In the routing model you never hold patient funds: each payment settles from the practice's own merchant account to the practice's bank. That keeps you a billing service rather than a money handler, and keeps the patient's card statement showing the practice they recognise.
What if our practices use different payment gateways?
That's normal and it's fine. One practice on Stripe, another on Worldpay, a third on whatever their bank installed: each connects the account they have, provided it's among the 40+ gateways Shuttle supports. You don't have to standardise your clients onto one provider. Phone keypad capture works on many supported gateways; payment links cover the rest.
Can we set up payment plans for patient balances?
Yes. Agree the plan on the call, and the instalments collect automatically against the practice's merchant account, with the same per-practice routing and reconciliation references as one-off payments.
How quickly can a billing company get started?
Quickly, because nothing waits on downstream adoption. Sandbox accounts let your team trial the agent-assisted and IVR flows before connecting any real practice accounts, and going live is then per-practice configuration, driven by your own rollout pace rather than a vendor project plan.
Related reading
Take Payments on Behalf of Your Clients - the multi-merchant-account problem across every servicer vertical
DTMF Payments - how keypad capture keeps agents out of PCI scope
ACH and Bank Payments Over the Phone - for patients who won't pay by card
Contact Centre Payments - the complete guide for phone-led payment operations
Payment Infrastructure for Healthcare - Shuttle's healthcare overview
Ready to route every patient payment to the right practice? Talk to us. If your team wants to dig into the technical detail first, docs.shuttleglobal.com covers the flows, with sandbox accounts available for testing.