What sits behind MyChart Bill Pay: the processing layer health systems overlook
Epic runs the billing experience. It does not run the payments. The card processor behind MyChart Bill Pay is a separate, swappable vendor contract, and it is where rate, patient-pay conversion, and margin actually live.
Most large health systems run Epic, and most patients pay their bills through MyChart Bill Pay. From the patient’s seat it feels like one system: log in, see the balance, enter a card, done. That seamlessness hides an architectural fact worth understanding, because it is where the money is.
Epic does not process the payment.
Epic is the billing system, not the processor
Epic Resolute handles the billing logic and MyChart presents the bill, but when a card is entered, that card data is handed to a separate payment processor through Epic’s payment-processing interface. Epic verifies the result and posts it back to the account. The processor, the gateway, and the sponsor bank behind that card transaction are a different vendor entirely, on a different contract, with their own rate.
That processing layer is the part nobody looks at, and it is fully contestable. You do not touch Epic to change it. You change the processor the gateway routes to.
Why this matters in dollars
Three things live in that swappable layer:
The rate. Patient card volume at a large group runs into the hundreds of millions. The effective rate on that volume, the interchange qualification, the handling of any commercial-card payments, the debit routing, all of it is set by the processor relationship, not by Epic. A group that has never re-bid the layer is almost certainly overpaying, and at that volume basis points are real money.
Patient-pay conversion. The payment experience inside Bill Pay, the available methods, card-on-file, wallets, text-to-pay, and whether financing is offered at the moment of the bill, all influence whether a collectible balance gets collected or ages. Some of this is Epic configuration; much of it is the capability of the processor and the tools layered on top.
Reconciliation. Auto-posting patient payments back to Resolute is table stakes for a competent Epic-integrated processor. The differentiation is at the edges: lockbox and paper, ERA and EOB matching, exception handling, and keeping unapplied cash low.
The closed-bundle trap
Some Epic-integrated payment vendors are a closed bundle: gateway, processor, and sponsor bank all the same company. That is operationally simple and it means the vendor keeps the entire processing margin. The alternative is a processor-agnostic, Epic-certified gateway that tokenizes the card and routes settlement to whatever acquirer you choose. The agnostic route is the one that lets a health system, or a payments partner working on its behalf, control where the volume settles and what the rate is.
The distinction is not academic. It is the difference between a fixed relationship you cannot shop and a layer you can competitively bid without ever disturbing the EHR.
A note on App Orchard
If anyone tells you to “get listed in App Orchard,” that program has been retired. Epic’s integration marketplace is now Showroom. The mechanics of integrating a payment partner are the same; the name changed.
What to actually do
You do not replace Epic. You audit the layer behind MyChart Bill Pay: what is the effective rate on patient card volume, who is the processor, is the gateway agnostic or a closed bundle, and what is patient-pay conversion doing. Most groups have never run that audit because the seamlessness of MyChart makes the processing layer invisible. Invisible is exactly where overpayment lives.
We run that layer audit as part of a Healthcare & Revenue-Cycle Payments engagement, no Epic disruption involved. Start with the pre-screening questionnaire.
