Telehealth payments: when to hold a card and when to charge it

Consider a patient who completes checkout on Monday. On Wednesday, the clinician asks for more information. The patient’s bank shows a pending payment, while your support team sees an order marked “pending.” Before anyone can explain what happens next, they need to know whether the card was charged or only placed on hold.

This is where telehealth payment authorization and capture matter. Your team needs to see the clinician’s decision, the payment status, and the pharmacy’s progress on the same order. Our guide to how ScalerMD works explains how those parts of the patient journey connect.

What is the difference between authorization and capture?

Authorization places a temporary hold on funds. Capture tells the payment processor to collect against that hold. The money then follows the processor’s settlement and payout schedule. NMI describes capture as marking an authorized transaction for settlement, so a successful capture does not mean the money is already in your bank account.^[1][7]

View full-size

This article covers medication orders paid before fulfillment, where collection depends on clinical approval. Consultation fees and memberships may be charged at different times. For each charge, decide who collects it, when it is due, and what happens if the patient cancels. Your processor must approve your business and support separate authorization and capture for the payment method you use. Start with our payments and checkout guide to check that setup.

Should you save the card instead?

Saving a card and charging later may fit better if you do not know the final price or how long review will take. Stripe’s Setup Intents let you save payment details without charging or reserving funds. You need the patient’s permission to use the card later, and they may still need to return to verify the payment.^[6]

Compare the options using your own review times and how often prices change. Also consider whether your team can reach patients who need to complete payment again. A saved card does not guarantee payment, and a hold will not stay open indefinitely.

What should happen between checkout and the pharmacy?

For the prepaid medication order described here, we recommend the sequence below. Adjust the point of collection to match your actual offer and the terms the patient accepts.

Keep the payment attached to the right order

Give staff access to the order number and its payment, clinical case, and pharmacy references. Record the amount and currency, the terms the patient accepted, and the hold deadline when the processor provides it. Keep clinical details out of payment descriptions.

Check what the patient owes before collecting

Confirm that approval applies to the current order, the price matches what the patient agreed to, and the patient has not canceled. The hold must still be valid. If your terms require the pharmacy to confirm availability or accept the order before charging, wait for that too.

Your payment system must also confirm that the transaction is ready for capture and specify the amount to collect. In Stripe, those are the requires_capture status and amount_to_capture field. A clinician’s approval cannot tell you whether the payment is ready.^[2]

View full-size

Follow up if a paid order stalls at the pharmacy

A captured payment does not tell you whether the pharmacy accepted, dispensed, or shipped the order. Track those steps separately and assign someone to follow up when a paid order has no pharmacy response. The clinical approval and order details must still be valid when you send it. Our order status guide explains how to identify which step needs attention.

What to do when an order changes or a payment fails

The next action depends on what happened to the money. Stripe lets you cancel an uncaptured payment or refund a completed one. NMI also allows some captured payments to be voided before settlement. Check the transaction’s current status and your processor’s rules before choosing an action.^[3][7]

Keep billing problems separate from treatment decisions. If a card fails, staff should see that the order needs payment. If the treatment plan changes, it needs the appropriate clinical review and the patient’s agreement to any revised purchase.

What if the card hold expires before clinical approval?

Check the deadline for each transaction. Hold durations vary by payment method and transaction type. Stripe provides a capture_before deadline for eligible card payments; when the authorization expires, the hold is released. Most Stripe payments allow only one capture, and collecting a lower amount normally releases the rest. Confirm how your own processor handles both cases.^[1]

Give your team a list of holds nearing expiry. Each entry should show the order, time remaining, reason for the delay, and person responsible for following up. Set alerts early enough for someone to act during support hours. An approaching deadline is a reason to investigate or contact the patient. It is never a reason to charge before the agreed conditions are met or rush a clinical decision.

Tell patients what to expect at checkout

Explain that the initial amount is a temporary hold, when you will collect it, and whether any separate fees apply. If treatment is not approved and no medication charge is due, tell the patient you are releasing the hold. Calling that a refund can confuse someone whose card was never charged. Avoid promising exactly when their bank will remove the pending amount.

How do you prevent duplicate charges?

A slow response can leave your team unsure whether a payment went through. Before trying again, check the transaction with the processor. A timeout does not prove that the charge failed.

Ask your implementation partner to show what happens when the same payment request is sent twice. Stripe supports a request identifier, called an idempotency key, that lets the system recognize a repeat request. Your system also needs its own record of the attempt because the processor’s protection has time limits.^[5]

Payment notifications can arrive twice or out of order, as Stripe documents. An older message should not make a completed payment look unpaid. Your team needs to check uncertain results against the processor’s current record.^[4]

What should support staff see?

Clinical review

Is review pending, does the clinician need more information, or has a decision been made? Show the decision, its reference, and when it was recorded.

Payment

Is the card on hold, awaiting capture, charged, expired, or voided? Is a refund pending? Keep the amount and reference for every attempt.

Pharmacy

Has the order been sent, accepted, or shipped? Show any problem, the pharmacy’s response, and the tracking reference.

These are suggested labels; your partners may use different names. Agree on what each status means during integration setup. Staff should be able to see “clinically approved” and “payment expired” together without mistaking either for a completed order.

ScalerMD’s NMI payment code has separate actions for authorization, capture, voids, and refunds. That informed this guide, but code alone does not show how a particular client’s setup behaves. When evaluating our platform for telehealth businesses, ask us to demonstrate the full payment process in the setup you plan to use.

What should you test before taking patient payments?

Ask your implementation team to run these cases with test patients and processor test tools. Write down what should happen, what actually happened, and who will fix any problem. Our prelaunch testing guide covers the rest of the patient journey.

1. An approved order produces one confirmed payment and reaches fulfillment once.
2. When treatment is not approved, the medication hold is released. Any separately agreed service fee follows its own billing terms.
3. An expired hold cannot release an order. A replacement payment appears under the same order, with both attempts accounted for.
4. A lower price uses partial capture where supported. A higher price requires the patient to agree to the revised purchase and payment.
5. A repeated request, lost response, or notification arriving out of order does not cause a second charge or pharmacy submission.
6. If a patient cancels while capture is processing, staff check the final payment result and stop the pharmacy order or escalate it.
7. If the pharmacy cannot fulfill a paid order, or a refund fails, the problem stays visible with someone assigned to resolve it.
8. If the system restarts after the processor collects payment but before the order updates, it restores the correct payment status.

Watch where orders get stuck

Track the time from card authorization to clinical decision, holds that expire before a decision, and the time from approval to capture. Also keep counts of payments with unknown results and paid orders awaiting a pharmacy response. Review these alongside cancellations and refunds to find slow handoffs. They should never become targets that pressure clinicians to approve treatment.

When calculating an expired-hold rate, use a group of successful authorizations whose holds have all ended. Count how many expired without being captured, then divide by that group’s total. Including fresh holds still waiting for review would make the rate misleading.

If you are choosing an implementation partner, our telehealth platform comparison covers the broader launch responsibilities. During a demo, ask the partner to walk through a delayed review, an expired hold, and a cancellation after payment. You should leave knowing who handles each case and what the patient will be told.