Is Payment Processing Covered by HIPAA? Section 1179 Explained for Telehealth Companies
HIPAA's Section 1179 keeps the law off ordinary payment processing. It doesn't keep patient information out of your payment data. Here is where the line sits, and what to keep out of descriptors, receipts and webhooks.
Mostly, no. Section 1179 of HIPAA says the law's requirements don't apply to a financial institution's payment activities, from authorizing a charge through settling and collecting it, when the payment is for health care, and HHS doesn't treat a financial institution doing only that as your business associate. What §1179 doesn't do is take your own systems out of HIPAA, including the patient details they send into payment fields.
HIPAA Section 1179 (42 U.S.C. 1320d-8) is the provision that keeps HIPAA's requirements off a financial institution's payment activities: authorizing, processing, clearing, settling, billing, transferring, reconciling and collecting payments for health care or health plan premiums. It covers those payment functions themselves, not everything a payment company might do for a provider.
What does Section 1179 say?
It takes payment activity out of HIPAA. Section 1179 was part of HIPAA's administrative simplification provisions in 1996 and is codified at 42 U.S.C. 1320d-8. Without it, every bank and processor that touched a payment for a doctor's visit would have a HIPAA question to answer.
The exemption follows the activity, not the company. HHS's position, stated in the preamble to its 2013 Omnibus Rule (78 FR 5566), is that a financial institution performing only those payment functions isn't a business associate, while one that does more, such as patient billing services that involve protected health information (PHI), can be. Neither the statute nor HHS takes the telehealth company out of HIPAA. If you're a covered entity or a business associate, your own systems are in scope whichever processor you use, and whether your company is a covered entity at all is a question for your counsel.
When does a payment company become a business associate?
In HHS's reading, when it does something with patient information beyond the payment functions §1179 lists. Applied to a telehealth business, the line HHS describes in the Omnibus Rule preamble looks roughly like this:
| What the company does | Within §1179's payment functions? | Business associate? |
|---|---|---|
| Authorizes, settles and reconciles card or bank payments for visits and prescriptions | Yes | Not for that work, in HHS's reading |
| Retries a failed charge on a stored card or bank account | Yes | Not for that work, in HHS's reading |
| Sends patient statements on your behalf that describe the care | Goes beyond payment: patient billing services involving PHI | Can be |
| Hosts intake forms, visit notes or prescription records | No | Outside §1179; HIPAA's ordinary definitions decide |
The table is our sketch of HHS's line; it isn't a ruling on any vendor. This is a general explanation of the statute, not legal advice, and your privacy counsel should look at your actual data flows.
What "HIPAA compliant payment processing" can mean
For plain payment processing, §1179 has already answered the HIPAA question, and the obligations that remain sit with you and your business associates. So when a payment provider describes itself as HIPAA compliant, ask which of two things it means:
- The provider does work beyond payments, such as patient statements, reminders or a portal, and handles HIPAA for that work. That is worth knowing, and it is where a business associate agreement (BAA) belongs if one is needed.
- The label describes ordinary processing that §1179 had already taken outside HIPAA. That can be true and still say little about your own exposure.
Your exposure comes from what your systems put into theirs. A processor can't make your checkout compliant from the outside, and a perfectly ordinary processor can end up holding diagnoses and drug names because your integration sent them.
Where patient information leaks into payment data
Through the text fields your systems fill in, which travel further than most teams expect. For each one, ask whether someone who sees only the payment record could tell what condition the patient has or what was prescribed. If so, move the detail into your clinical systems and leave a reference ID behind.
| Field | Who sees it | Keep out | Use instead |
|---|---|---|---|
| Billing descriptor | The cardholder, and anyone who reads their statement | Drug names, conditions, "Rx" | Your brand name, with a website or phone number patients recognize |
| Order or line-item description | Processor reports, receipts, dispute records | Medication, dose, diagnosis | A plan or product label, such as "Monthly membership" |
| Metadata and custom fields | Stored by the processor; returned in API calls and webhooks | Chart numbers, diagnosis codes, intake answers | An opaque order ID that maps to your records internally |
| Automated receipts and invoices | The patient's inbox, sometimes a shared one | Medication and condition | Service category, amount and date |
| Webhook payloads and logs | Your logging, analytics and support tools | Anything listed above | IDs only; look details up inside your HIPAA environment |
| Dispute evidence | The card issuer and the cardholder | The full chart | Proof of authorization, delivery and the terms the patient accepted |
Descriptors carry an extra constraint. Visa's §1.5.1.12 requires the merchant name to be the name you primarily use with customers, shown on your website or app and used consistently across authorization, clearing and dispute records; for e-commerce, the website address can be used unless it is unrelated to that name. The goal is discreet and recognizable at once, which we cover in billing descriptors for telehealth.
PCI DSS applies even where HIPAA doesn't
Card data has its own standard, and §1179 doesn't touch it. PCI DSS v4.0.1 was published in June 2024, and the requirements that v4.0 had future-dated became mandatory on March 31, 2025. Two points matter most for a telehealth checkout:
- Hosted payment fields and tokenization keep card numbers out of your environment and reduce your PCI scope. Card data has no business in the EHR, the CRM or a support ticket, and the simplest way to keep it out is never to receive it.
- Requirements 6.4.3 and 11.6.1 target tampering with scripts on payment pages, which matters if your intake flow and your checkout share a page. SAQ A was revised in early 2025, so confirm which questionnaire applies to you rather than reusing last year's.
VyaPay's VyaCloud tokenization is built for the first point: card data never touches your servers, and your systems keep a token instead. The rest of the PCI picture is in PCI DSS 4.0.1 for telehealth checkouts.
Questions to ask a payment provider about patient data
Ask what it stores, where the visible text comes from, and whether any service reaches past payments.
- Which fields do you store from each transaction, and which of them appear on receipts, reports and webhooks?
- Can I set the descriptor and receipt text per product?
- Does any service you provide go beyond payment processing, such as patient statements, reminders or portals, and how do you handle HIPAA for it?
- How is card data captured: through hosted fields or tokenization, or through my servers?
- When you respond to a dispute or share purchase data with an issuer on my behalf, what exactly do you send?
These belong in your due diligence with the rest of the telehealth merchant account application checklist. VyaPay runs its own processor and underwrites in-house, so you can put them to the team that runs the stack: talk to VyaPay.
Frequently asked questions
Does my payment processor need to sign a BAA?
HHS's position is that a financial institution performing only the payment functions in §1179 isn't a business associate, so payment processing alone doesn't call for a BAA. A provider that does more with PHI, such as patient billing services, can be a business associate for that work, which is where a BAA comes in. Your counsel can tell you how that applies to a particular provider.
Should a telehealth receipt name the medication?
Not the automated receipt from your payment system, which can land in a shared inbox. If a patient needs an itemized record, for an HSA or FSA claim for example, provide it from your own patient systems, where your HIPAA controls already apply.
Does Section 1179 cover ACH and eCheck payments?
The section is written around payment activities rather than a particular payment method, so the same reasoning applies to a bank debit. So does the data advice: an ACH debit carries a company name and description that show on the patient's bank statement.
Does tokenization make a checkout HIPAA compliant?
No. Tokenization is a PCI DSS tool that keeps card numbers out of your systems. It does nothing about patient health information, which depends on what you put in descriptors, metadata and receipts, and on your own HIPAA program.
Sources
- Legal Information Institute, 42 U.S.C. 1320d-8 (HIPAA Section 1179)
- HHS, Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules (Omnibus Rule), 78 FR 5566, 2013
- PCI Security Standards Council, PCI DSS v4.0.1, June 2024
- Visa, Visa Core Rules and Visa Product and Service Rules, 24 October 2026 (section 1.5.1.12)
