Payments that understand
how medicine is billed.
Generic processors were never built for specialty pharmacy billing
A patient moves from 10mg to 20mg and the bill has to prorate. A card declines on a refill and you need a retry before treatment lapses. A compounded medication is priced by formulation, so the payment system has to know the clinical context. Off-the-shelf processors handle none of this, so teams end up writing custom billing logic on top of them and maintaining it forever.
Manifold handles this complexity natively because it is connected to Core.
Every charge goes to the processor most likely to approve it
Manifold looks at each card before it charges it, picks the right processor, and retries elsewhere when one declines. You see every approval, every decline, and the exact reason behind each one.
Multi-processor support
Connect several processors and Manifold spreads charges across them, fails over when one declines, and favors the one that costs you least.
BIN mapping
Manifold reads the card type, issuing bank, and network at the moment of the charge and sends it to the processor best suited to that card.
Network tokenization
Stored cards become network tokens, which shrinks your PCI scope, lifts authorization rates, and keeps saved credentials current on their own.
Built for the moments that break generic tools
Each of these used to mean a ticket, a spreadsheet, and someone adjusting a charge by hand. In Manifold, each one is a single event that runs to completion.
A patient moves from 10mg to 20mg
No one on your team touches the bill.
- 01Prorate the current cycle
- 02Raise the recurring amount
- 03Charge the difference
A renewal payment fails
The patient hears from you before their treatment lapses.
- 01Retry on a backup processor
- 02Start the dunning sequence
- 03Notify the patient
A patient asks for a refund
Pharmacy, support, and finance all see the same record.
- 01Refund on the original payment path
- 02Link it to the order in Core
- 03Log it to the audit trail
You add a new processor
Your application code stays exactly as it is.
- 01Connect the processor
- 02Set the routing rules
- 03BIN mapping and failover update
Billing logic that follows the patient’s treatment
Healthcare billing is more than a checkout page. Subscriptions renew, doses change, and refunds have to trace back to an order. Manifold runs all of it without manual intervention.
Dosage and plan transitions
When a patient changes dose, switches medication, or upgrades a plan, Manifold prorates the cycle and adjusts the recurring charge for you.
Subscription and recurring billing
Automatic retries, dunning sequences, and grace periods keep patients on treatment and keep your revenue predictable.
Refunds and disputes
Refunds, chargebacks, and disputes are handled from one screen, with a full audit trail on every transaction.
Complex medical billing
Split payments, insurance coordination, copay collection, and custom billing rules for specialty medications all run on the same rails.
Native to Core, so payments share a record with everything else
Manifold is part of the platform, not a third-party integration. Payment events move through the same data layer as prescriptions, orders, and patient records. When a refund goes through, pharmacy and support see it instantly.
- A change in the clinical workflow updates billing on its own.
- Every transaction is linked to a patient, an order, and a prescription.
- Analytics tracks payment health next to your operations.
- One audit trail spans payment, pharmacy, and clinical data.
Payments that keep working when the billing gets complex
Talk to our team about Manifold for your healthcare operation, or email us at [email protected].