Healthcare

Far more common than most organizations acknowledge. Nearly half of patients have received a medical refund (Onbe), and nearly seven in ten have experienced a delayed, lost, or incorrect one. The volume is driven by structural factors unique to healthcare: estimated charges collected before insurance adjudication often overshoot the final patient responsibility, duplicate payments occur when patients pay at point of service and insurance subsequently covers the same amount, and coding corrections generate credits. CMS data shows Medicare improper payment rates of 6-10% annually. Unlike retail, healthcare refunds often involve multiple payers and can take 60-90 days to fully adjudicate, creating a long tail of refund obligations that strains billing departments year-round.

Yes, and the trend is accelerating. 83% say faster digital payments would improve satisfaction—a 13-point increase from the prior year (Onbe, 2026). 79% say digital refunds improve provider confidence, and 78% would seek a new provider after a poor payment experience. The perception gap is widening because patients now experience instant refunds from retailers and gig platforms, creating a baseline expectation that healthcare's 3-4 week paper check cycle violates. This is not purely generational: patients over 55 who have adopted mobile banking increasingly expect the same speed. Providers who dismiss refund method as low-priority underestimate its influence on experience scores, online reviews, and referral willingness.

Three structural barriers. Legacy billing systems were built around check-based AP workflows and lack native digital disbursement capabilities. Fragmented integrations—separate EHR, PMS, and revenue cycle platforms that don't share a unified patient payment record—make triggering digital refunds difficult without custom work. And compliance anxiety leads finance teams to conflate payment processing with PHI handling, assuming digital refunds create HIPAA exposure when in practice the payment platform processes only financial data. The loaded cost of paper checks runs $4-$8 each when printing, mailing, lost-check calls, reissuance, and unclaimed property reporting are factored in. The irony: lost mail containing patient financial information arguably creates greater compliance risk than encrypted digital transactions.

The billing system identifies a patient credit—overpayment after adjudication, duplicate charge, or coding correction—and triggers a refund through the API. Push-to-card via Visa Direct or Mastercard Send delivers to the patient's debit card in under 30 seconds, best for smaller refunds where speed maximizes satisfaction. ACH delivers overnight at lower per-transaction cost, better for larger amounts where same-day timing is less critical. The patient receives a branded notification specifying the amount, originating visit, and confirmation reference. This specificity matters because patients often have multiple balances across visits and providers—a generic refund with no context generates the same confusion and inbound calls that paper checks produce.

Yes, and the threshold is lower than expected. 78% say a poor payment experience would drive them to look elsewhere; 71% cite a frustrating experience as reason enough to switch (Onbe, 2026). The refund is uniquely damaging because it follows a situation where the organization already owes the patient money—any delay feels like the provider is holding funds the patient is rightfully owed. In urban and suburban markets with multiple health systems, patients have alternatives and increasingly exercise them. For organizations subject to HCAHPS scoring and value-based reimbursement, patient experience directly influences revenue, making the refund a financial issue beyond the individual patient relationship.

Payouts Network is PCI DSS Level 1 certified and processes payment data only—not PHI. The API transmits only the data elements needed to execute the refund: payment amount, card token or bank routing, and a patient identifier for reconciliation. No diagnosis codes, procedure descriptions, or clinical records pass through the platform. This architecture means Payouts Network operates as a payment processor, not a HIPAA business associate—similar to a credit card terminal at a hospital gift shop. The patient notification references visit date and amount but contains no clinical information. For organizations requiring a Business Associate Agreement (BAA) as an additional safeguard, one can be executed, though the data flow does not technically require it. All data is encrypted at rest (AES-256) and in transit (TLS 1.2+).