Switching from OpenLoop or Bask? Free white-glove migration in days.
PharmaBro
  1. Home
  2. Glossary
  3. Rebill engine
Payments

Rebill engine

Definition

Billing infrastructure that charges a stored card on the day a prescription actually ships, at the dose that shipped, rather than on a fixed calendar date.

Generic subscription billing charges on a calendar. Telehealth does not work that way: a shipment can be delayed by a pharmacy backorder, gated by an incomplete check-in, or changed by a dose adjustment. A calendar charge in any of those situations bills for something that did not happen.

A rebill engine ties the charge to the fulfillment event and to the dose. It also handles the recovery layer: smart retry scheduling, card account updater coverage for expired and reissued cards, and routing across multiple merchant IDs.

The recovery component is where the measurable money is. Failed payments in subscription businesses are mostly technical rather than intentional, and a meaningful share can be recovered by retrying correctly.

Why it matters

A well-run rebill engine recovers 0.5 to 1% of billings every cycle. At $89,700 in monthly billings that is roughly $673 a month, about $8,000 a year that calendar-based billing would have written off.

FAQ

Rebill engine, in practice

Because a Stripe subscription bills on a calendar and cannot express dose-aware, ship-date billing. On a titrating therapy like a GLP-1, where the dose changes over the patient's life and shipments can be gated by a check-in, calendar billing produces charges for shipments that never left.