Unified payments

Get paid without chasing anyone.

Text a payment link inside the patient thread. Tap-to-pay at the front desk with nothing but an iPhone. Every charge reconciles against the visit — automatically.

app.moxcares.com
Moxcares payments summary with today, week and month net takings, outstanding aging buckets, and the transaction report with platform fees, refunds and net totals.

The problem

Payments, insurance, and the chart live in three different systems.

So every dollar gets touched by a human twice — once to collect it, once to make the systems agree it was collected.

Payments sit outside the chart

A standalone terminal or processor that has no idea which visit, provider, or balance the money belongs to.

Insurance is a separate system

Claims go out of one tool, ERAs come back into another, and the patient balance is calculated by hand in a third.

Reconciliation is a staff task

End of day someone exports, matches, and re-keys. Every mismatch is a ticket, and every ticket is unbilled time.

Follow-ups are by staff

Past-due balances get chased by whoever remembers, on whatever channel they prefer, until they quietly age out.

Front-desk staff member buried in insurance paperwork and separate billing systems

What we built

One spine: chart, claim, invoice, payment.

Moxcares runs payments and insurance on the same record as scheduling, charts, and patient communication. Mox works the follow-ups and closes the balances — reports reconcile against claims because they were never separate to begin with.

01

Visit closes

The note is signed and the codes are set — the charge already knows the appointment.

02

Claim goes out

837P submits and 277/835 responses post back against the same visit automatically.

03

Balance calculated

Patient responsibility is derived from the payer response, not guessed from a spreadsheet.

04

Invoice auto-dispatched

A text-to-pay link goes to the patient in the thread they already use — no portal login.

05

Mox closes it out

Follow-ups, plan offers, and receipts run automatically. Reports reconcile to the claim.

Why this is different

The invoice knows the appointment. The balance knows the claim.

Everyone else bolts a payment processor onto a billing tool onto an EHR. We built them on one spine, so nothing has to be re-keyed, reconciled, or chased between systems.

What you get

Payments that live inside the visit, not next to it.

Text-to-pay links

Send a payment link right inside the patient thread. Patients pay in two taps — no login, no app, no invoice PDF chase.

Tap-to-pay at the front desk

Accept all major cards, Apple Pay, Google Pay, and chip transactions on one compact processor-provided device. Check and cash are logged against the visit just the same.

Statements that reconcile themselves

Every charge posts against the visit and the patient balance automatically. End-of-day reconciliation stops being a person's job.

Past-due nudges that don't feel like collections

Friendly reminder cadence, patient can text a question, and staff can offer a payment plan without leaving the thread.

PCI-compliant by default

Card data never touches your servers. Patients can securely store a card on file; the processor holds the vault and we hold the receipts. Your PCI scope stays small.

Refunds and adjustments in one click

Refund, void, or adjust a charge from the visit — the ledger, the statement, and the patient balance all update together.

Turn on payments in an afternoon.