Pre-service deposit and copay collection

How do we show a patient the expected copay or deposit before the visit and collect it on a secure screen, with the payment posted to the account?

Turn the estimate into a payment the patient can make from a text. Callvu prefills the patient, the visit and the expected amount (the copay from the benefits, the deposit from the estimate or the policy's deposit rule, any prior balance the policy allows to be requested), sends the patient a link before the visit or presents it at check-in, shows the amount with what it covers and the receipt terms, captures the payment on a secure screen that keeps card data out of the front desk and the call center, offers a plan where the amount is large, and writes the payment to the account in the billing system with the receipt and the check-in flag.

In scopeSimpleCallvu moves: prefill, write back

Last updated November 7, 2026.

The problem today

The front desk asked for the copay from the card's printed figure, took a credit card on a terminal that was not theirs, and the deposit for the procedure was never requested at all.

Today, without Callvu

Collecting before the service is the cheapest collection there is, and most hospitals do it badly: the copay is guessed from the card, the deposit for a scheduled procedure is a phone call that may not happen, and the payment is taken on a terminal or over the phone with the card number in the front desk's hands. Every dollar not collected before the visit costs several times more to collect after.

The amount is computable from the benefits and the estimate; the request is a text with a link; the capture must satisfy PCI DSS by keeping the card data on a secure screen outside the hospital's environment; the posting must land on the right account and encounter in the billing system so the claim and the statement reflect it. A receipt and a record of what the payment covers prevent the later dispute.

A deposit paid from the patient's phone the night before is a visit that starts on time.

How it runs

From the requestto the system of record.

A visit or a procedure is scheduled, or a patient arrives at check-in. Callvu prefills the expected amount and opens the collection.

Patient or guarantor
Sees the amount and pays on a secure screen from a text, the portal or at check-in.
Patient access
Sees the payment status at check-in; never handles card data.
Callvu
Prefills the amount, requests, captures, offers a plan and writes.
  1. Prefill the amount

    The patient, the visit or the procedure, the copay from the benefits check, the deposit from the cost estimate or the policy's deposit rule for the service, and any prior balance the policy allows to be requested are prefilled from scheduling and the billing system; the amount is shown with what it covers (the copay for this visit, a deposit against the estimated share, a prior balance) and the refund terms if the service does not happen.

  2. Request before the visit

    The patient receives a text or portal message with a link to the amount before the visit, on the hospital's lead time, and can pay the full amount or a part, or choose a plan where the amount qualifies; a patient who does not pay sees the same screen at check-in on the kiosk or from a code.

  3. Capture on a secure screen

    The card or bank payment is entered by the patient on a secure, process-controlled screen that keeps the card data out of the front desk, the call center and the recordings, tokenized at capture; a saved method on the account may be used with the patient's confirmation.

  4. Write back

    The payment is posted to the account and the encounter in the billing system with the receipt and what it covers, the check-in record shows the payment, the claim and the statement reflect it, and a payment against an estimate is reconciled at the final bill with any overpayment routed to the refund process.

Where it ends: The expected amount was computed, requested before the visit and paid from the patient's phone or at check-in on a secure screen, and the billing system holds the payment on the right encounter with the receipt. The Decision Trace shows the amount's basis and the policy applied; the Audit Trace shows the request, the capture and the posting with time.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

The handoff

Between the front doorand the back office.

The front door

A text or portal link before the visit, the kiosk or a code at check-in; the patient pays on a secure screen.

The back office

Patient access sees status; billing receives the posting on the encounter; nobody handles card data.

The Decision Desk

  • A deposit the patient disputes, a prior balance under review, or a payer whose contract limits advance collection goes to patient financial services in the Decision Desk with the account and only the allowed outcomes.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

23 hospitals in the Ministry of Health network run on Callvu.

Across Callvu customers

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Questions

What buyers ask next,answered plainly.

What amount is requested?

The copay from the benefits response, a deposit against the estimated share, or the policy's deposit for the service, with what it covers stated; a prior balance only where the policy allows.

How does the front desk stay out of PCI scope?

The patient enters the card on a secure screen from their phone or the kiosk; the front desk and the call center never see or key the number.

What if the patient overpays against the estimate?

The payment is reconciled at the final bill and the overpayment goes to the refund process.

Related processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.