Not one we lead with. We can board this if you want it. It is not one we know inside out, so we would be setting it up rather than advising you on it — and we would tell you that before you signed anything. Talk it through with us.
Business software · LQpay · via PayCompass
LQpay
Patient payments that post themselves back into the practice management system.
- Medical & dental
- Professional services
An independent assessment. Vigilant can place LQpay, and is paid the same either way — which is why the drawbacks are on this page too.
What it is
Patient balances behave differently from ordinary receivables. High-deductible plans have pushed more of the bill onto the patient, paper statements are slow and expensive, and the longer a balance sits after insurance adjudicates, the less likely it is ever paid.
LQpay handles the whole post-insurance collection loop. Upload an AR report of balances owed and it sends patients actionable mobile statements by SMS or email for card entry on their phone. Card-on-file and text-to-pay shorten the cycle. In-office payments run on a WiFi terminal.
The distinctive part is the RPA posting. Rather than requiring a formal integration, LQpay connects to the existing EMR, EHR or practice management system and posts payments back in real time or as a scheduled daily batch, aligned to how the practice already works. It is HIPAA and PCI compliant, and there are builds for dental, eye care, orthopedics, pediatrics and veterinary.
Who it fits
Best for
Medical, dental, optometry, veterinary and specialty practices with a real post-insurance patient balance problem.
Probably not ideal for
Anything outside healthcare. The posting automation is the product and it only means something against a practice management system.
Key capabilities
- Batch billing
- Upload an AR report and patients receive actionable mobile statements by SMS or email.
- Text to pay
- Patients pay from a phone in seconds instead of returning a paper statement.
- Card on file
- Stored cards for balance-after-insurance and recurring treatment plans.
- RPA posting
- Payments post back into any EMR, EHR or practice management system in real time or as a daily batch.
- In-office
- WiFi wireless payment terminal for at-the-desk collection.
- Compliance
- HIPAA and PCI compliant, with no long-term contract.
Strengths and tradeoffs
Strengths
- Posts into practice management systems via RPA, which means it works with systems that have no API — the usual blocker.
- Real-time or daily batch posting, so the front desk stops re-keying payments entirely.
- Batch AR upload turns an ageing report into a wave of statements by text and email in one action.
- HIPAA and PCI compliant, with card-on-file for balance-after-insurance.
- Keeps your processing negotiable — it is not tied to one acquirer the way a bundled product is.
- No long-term contract stated, which is unusual in healthcare payments.
Tradeoffs
- Healthcare is the whole focus; outside it there are better and cheaper general tools.
- RPA posting is powerful but needs configuring against your specific PM system and validating before you trust it.
- Smaller vendor than Clover or Fiserv, so the support bench is thinner.
- No dual pricing, so card cost stays with the practice.
- The collection toolkit is narrower than a general AR platform like Hyfin.
Pricing
Subscription plus processing, quoted per practice.
Pricing reflects what the vendor publishes or what we have seen quoted. Your actual terms depend on volume, card mix and what is negotiated — which is the part we do.
Vigilant's assessment
The one we lead with when the practice management system is the bottleneck and you want to keep the processing negotiable. Bundled products win on single-vendor simplicity; this wins on not having to commit three years of processing to fix a posting problem.
How it compares
Three stages of the same problem: collecting the balance, posting it, and recovering what never got paid. Most practices need the first two; some need all three.
| Criterion | LQpay Purpose-built patient payments | Clover PracticePay Bundled with Clover processing | TSI Recovery and late-stage AR |
|---|---|---|---|
| Best at | Posting into any PM system, processor stays open | One vendor for terminal, posting and processing | Recovering balances that have already aged out |
| How it posts | RPA into any EMR/EHR or PM system | Direct connections to most Windows PM systems | Does not post — it collects |
| Collection channels | Batch AR upload, SMS and email, terminal | Text-to-pay, links, front desk | Letters, calls, digital outreach |
| Processing | Quoted per practice, negotiable | Clover/Fiserv, bundled | Not applicable |
| Contract | No long-term contract stated | Three years to get the hardware offer | Per placement or contingency |
| When to use it | Balances are current but posting is manual | You want one vendor and the term suits | The balance is months old |
| Card on file | Yes | Yes | No |
| Watch out for | RPA needs validating on your system | Volume floors and early termination fees | Recovery rates and patient relationships |
| Pick it when | The front desk is re-keying every payment | Simplicity matters more than rate freedom | Collections have already failed |
Verdict. Fix the posting and keep your options: LQpay. Want one vendor and the three-year term is fine: Clover PracticePay. Chasing balances that are already 90 days out: TSI, and fix the front end so it stops happening.
Ready
Start now
Talk it through with someone who has installed LQpay — including whether it is genuinely the right fit for you.
Start now
