Workflow
From balance to paid, in the fewest taps possible.
Patients pay what they understand, through the channel they already use. This workflow is designed around that. Walk the diagram below to see who acts at each step — a person, MEDBIX, an AI agent, the clearinghouse, or money moving — and where a named decision is required.
Diagram
The steps
Each step shows who acts: a person, MEDBIX, an AI agent, the clearinghouse, or money moving.
- Money moves
- MEDBIX
- Clearinghouse / payer
- 1
Balance & statement generated
Money movesFrom posted patient responsibility.
- 2
Statement + portal / pay link
MEDBIXStaff preview; patient magic link.
- 3
Optional SMS reminder
Clearinghouse / payerOpt-out respected.
- 4
Stripe Checkout → payment recorded
Money movesPosted back to the ledger.
The principles behind it
No account required
Magic links instead of passwords.
Respect the patient
Opt-outs honored automatically.
Card data stays with Stripe
MEDBIX never stores it.
Ownership
Who does what
| Who | What they do in this workflow |
|---|---|
| Accountant | Generates statements and reminders. |
| Patient | Opens the link and pays. |
| System | Records payment and updates balances. |
Features in this workflow
On the floor
What this looks like in practice
These cues come from the same workflow — useful when you are mapping MEDBIX to how your team already works.
money
Balance & statement generated
From posted patient responsibility.
system
Statement + portal / pay link
Staff preview; patient magic link.
external
Optional SMS reminder
Opt-out respected.
Next
Walk it live, or open a related feature
A demo follows this path with synthetic data. Feature pages spell out capabilities, roles and guardrails for each piece.
Other workflows
The full RCM loop
From insurance on file to money in the bank, in one loop.
Claim status lifecycle
Every status a claim can be in, and how it gets there.
The human approval gate
AI can suggest. Only your team can send.
Denial workflow
From denial to resubmission, with a person at the wheel.
Tenancy model
Billing company on top. Practices underneath. Walls in between.
Deep dive
What Patient Payment Workflow means in daily ops.
Practical context for Patient Payment Workflow: how teams use it, where it sits in the loop, and what to ask in a demo.
- Tied to how billing work actually splits
- Clear on human vs machine responsibility
- Links into related MEDBIX areas
Practice
Where this shows up on a busy day.
From morning eligibility checks to end-of-day posting, Patient Payment Workflow connects to the queues your team already lives in.
- Morning coverage and claim build
- Midday scrub and approval
- Afternoon denials and patient pay
Control
Keep a person on the send button.
Whatever page you're on, MEDBIX keeps AI in a propose role. Approvals, posting and rule activation stay human.
- Named approvals
- Visible AI proposals
- Immutable audit trail
Next
Walk Patient Payment Workflow live
Bring your payer mix and the friction you feel today. We'll map it onto sample data in thirty minutes.
- Sample data only
- Your questions drive the agenda
- Written follow-up after
Common questions
Can patients set up autopay?
Recurring automatic charges aren't live yet. Pay links are.
Is the portal clinical?
No, billing only.
Want to walk MEDBIX against your real claim mix?
Thirty minutes with sample data. We'll follow one claim through the gate, then talk about your payers, practices and where the rework hurts today.
Notes from the billing floor
Occasional, practical writing on denials, A/R and running a billing company. No spam, unsubscribe any time.