Extensions
Live

Split Payment on the Client Overview

Split a client's charges between two payers, such as two parents, and charge both saved cards from the client's Overview in one step.

Built by

The problem it solves

When two people pay for one client, staff have to work out each share by hand and run two separate charges. It's easy to charge the wrong card or the wrong amount, and nowhere records the agreed split.

What's included

  • Two payers, each one of the client's notification contacts paired with a saved card
  • Editable percent split, where payer 2 always gets the rest so it adds up to 100 (new clients default to 50/50)
  • Saved split collapses to a one-line summary per payer
  • Live preview of each card's share, rounded to the cent and always summing to the total
  • Confirmation popup with cautionary copy before any card is charged
  • Cards charged one after another, with a status for each and a Retry if a card is declined
  • Warnings when the client has fewer than two contacts or saved cards

How it works

It appears as a card on the client's Overview tab. Support Engineering turns it on per org. It reads the client's notification contacts and saved Stripe cards, and saves the split in the client's metadata under split_payment without overwriting other keys. Each share is charged with createBillingItem, with a new idempotency key on every attempt so a retry never repeats a charge, and a note like "Split payment: 40% of $100.00". If one card is declined, the other charge still goes through. Both cards have to be saved on the client's own record, because Healthie only stores cards on user accounts and notification contacts aren't users. In sub-orgs it shows only in the org it's enabled for. Authenticates the same way as Healthie's other embedded staff-side widgets: a JWT delivered via postMessage, sent as a Bearer token with an AuthorizationSource: ThirdPartyApp header.

Example configuration

mutation ChargeSplitCard($input: createBillingItemInput!) {
createBillingItem(input: $input) {
billingItem { id state amount_paid }
stripeError
messages { field message }
}
}

# Example variables
{"input": {"sender_id": "patient_id", "amount_paid": "40.00", "stripe_customer_detail_id": "card_id", "should_charge": true, "stripe_idempotency_key": "split-payment-<uuid>", "note": "Split payment: 40% of $100.00"}}

A Client Overview card for practices where two people share the cost of care, like divorced parents or a parent and a guardian. Staff pick two of the client's notification contacts as payers, match each to a saved card on the client's record, and set the percentage split. They enter a charge amount, check each payer's share, and charge both cards after a confirmation step. Healthie's core billing handles the charges, so they show on the client's Billing tab and are refunded there.

Building on Healthie?

Talk to our team about API access, white-label, and enterprise architecture — or dive into the docs.