Medical Debt Collection Payment Processing: HIPAA and PCI
Industry Payment Guides

Medical Debt Collection Payments: HIPAA, PCI and Credit Rules

How agencies handle medical debt collection payment processing: keeping PHI out of payment flows and dispute evidence while meeting credit rules.

Smiling woman wearing a headset takes a call in a bright office with white shelves and colorful binders

Photo: Pixabay

On this page 6 sections
  1. Why Medical Debt Collection Payment Processing Carries Extra Risk
  2. Business Associate Agreements and Your Collection Agency's Processor
  3. Keeping PHI Out of Descriptors, Receipts and Your Medical Collections Payment Portal
  4. Fighting Chargebacks Without Disclosing Treatment Details
  5. Medical Debt Credit Reporting Changes and Payment Timing
  6. State Payment Plan and Interest Limits on Medical Debt

Key takeaways

  • Let only account identifiers and payment details reach your processor. That keeps health information away from vendors that won't sign a BAA.
  • Audit every free-text field your gateway passes along, especially receipt templates and text-to-pay messages.
  • Win unrecognized-charge disputes with authorization records and balance history, and leave itemized bills and treatment details out of the file.
  • Medical credit reporting is shaped by voluntary bureau policy and by state law, so set posting and reversal handling with both in mind.

Medical debt collection payment processing runs on the same card and ACH rules as any other collections work, with two extra layers on top. The first covers health information under HIPAA. The second is a fast-changing set of credit reporting and state laws aimed only at medical debt, and card data still falls under PCI DSS. Most of the risk sits where these layers meet. The working principle follows from that: payment data and health data should travel on separate paths, and only the minimum needed to identify the account should cross between them.

Agencies working receivables for hospitals, physician groups, labs or ambulance services feel these rules most directly. Treat everything below as general information, not legal advice. Federal privacy and collection laws carry penalties, and so do state medical debt statutes, so have counsel confirm any change to your process before you make it.

Why Medical Debt Collection Payment Processing Carries Extra Risk

Collection agencies already sit in the high-risk processing tier at most acquirers. Debtors often don't recognize the agency's name, which pushes disputes up, and underwriters ask for licenses and bonds before they approve anything. If you're starting from scratch, our guide to why collection agency merchant accounts get declined covers the underwriting side.

Medical receivables add a different problem. The data that explains why someone owes money is health information. Hospitals and clinics usually bring collection agencies in under a business associate agreement, because they are sharing patient information with you. Counsel can confirm exactly how HIPAA's privacy and security obligations apply to your role. The practical goal is easier to state: use and share only what each task requires.

Payment systems are full of places to leak more than that. Gateway memo fields, receipt templates, text messages and dispute uploads all accept free text. A collector who types "ER visit last March, Dr. Patel" into a gateway memo field has just sent patient information to a vendor that probably has no agreement covering it.

Medical debtors also behave differently from other debtors. Many expected insurance to pay, and many dispute the underlying bill. The person paying is often not the patient: a parent pays for a teenager, or an adult child pays for an elderly parent. Those habits show up in your chargeback and complaint numbers.

Business Associate Agreements and Your Collection Agency's Processor

Your client will usually require a business associate agreement (BAA) with you. You will typically need BAAs of your own with subcontractors that handle patient information on your behalf. In a collections shop, that list often includes the collection software host, cloud storage, the letter vendor, call recording, and any IVR or text-messaging service that sees account details.

Your card processor is a different case. HIPAA has a limited exception for payment processing, and many processors and acquiring banks decline to sign BAAs because they don't intend to receive health information. Confirm the exception's scope with counsel before you rely on it. Whatever its exact reach, the exception concerns processing a payment. Using your gateway as a place to keep service dates or provider departments falls outside that purpose, so keep those details out of it.

That leads to a design decision with two branches:

  • If your processor won't sign a BAA, build the integration so the only data reaching it is the cardholder name, the amount, an agency reference number, and the card or bank details.
  • If a vendor in the payment flow must see health details, such as a portal host that displays itemized balances, that vendor needs a BAA. It should also keep the itemization on its side of the integration.

When you evaluate payment gateways, ask for a field map that shows where every field travels after a payment is submitted, including what lands on the customer's receipt. That map tells you which fields must stay free of health details.

Keeping PHI Out of Descriptors, Receipts and Your Medical Collections Payment Portal

Acquirers generally require the statement descriptor to identify the merchant so the cardholder recognizes the charge. For a third-party agency, that means the agency's name or a recognizable DBA, plus a customer service phone number. It should never name a provider whose specialty reveals the type of care.

Here is an illustrative comparison using a fictional agency:

DescriptorAssessment
EXAMPLE RECOVERY [phone]Acceptable: identifies the agency and gives a number to call
EXAMPLE RCV LAKESIDE HOSPAsk counsel: more recognizable, but names the creditor
EXAMPLE RCV LAKESIDE ONCOLOGYReveals a cancer-care relationship on a statement others may see
LAKESIDE ONCOLOGY PMTMisidentifies the merchant and still reveals the type of care

The trade-off is recognition. Debtors know the hospital's name, not yours, and that gap drives "I don't recognize this" disputes. Close the gap in your letters and portal instead of the descriptor. Tell the payer exactly what will appear on their statement before they pay.

Receipts are the next leak. Many gateways copy the order description into the customer's email receipt automatically. Use a neutral description such as "Payment on account [reference number]" and check that the template doesn't pull in other fields. Text-to-pay links carry their own risk, because phones get shared and messages preview on lock screens. The message should say only that your agency has sent a payment request. The balance and the provider stay hidden until the payer authenticates.

For a medical collections payment portal, four controls matter most:

  1. Require identity verification, such as the account number plus a date of birth or ZIP code, before showing any balance or creditor name.
  2. Show itemized service detail only on request, and only to the verified guarantor or patient.
  3. Use hosted payment fields or a hosted payment page, so card data never touches your servers. This keeps your PCI DSS scope as small as possible.
  4. Remove third-party tracking code, including ad pixels and session-replay tools, from every page behind the login. Those scripts can send account and provider details to companies with no BAA.

Our guide to self-service payment portals for debtors covers the recovery side of portal design. Phone payments need the same care. Pause-and-resume recording and agent-desktop masking are covered in PCI compliance for collection call centers.

Fighting Chargebacks Without Disclosing Treatment Details

When a payer disputes a charge, the instinct is to send everything, from the itemized bill to the visit notes. Resist it. The issuer's question is whether the cardholder authorized a payment to your agency. Whether care was delivered has no bearing on that question. Dispute evidence also passes through several hands (your processor, the acquirer, the card network and the issuing bank), and none of them needs health information to rule on authorization.

Illustrative example. A guarantor makes a partial payment through your portal toward a hospital balance. Weeks later the payment is disputed as unrecognized. A strong, minimal response includes:

  • The payment authorization record: date and time, IP address or call reference, the last four digits of the card, and the terms accepted.
  • An account statement showing the balance before and after the payment posted, identified by agency account number.
  • Proof that the payer was told what descriptor would appear on their statement.
  • Any payment-plan agreement the payer accepted, if the charge was part of one.

Leave out diagnosis and procedure codes, dates of service, department names, insurance documents and clinical notes. If your validation notice names a creditor whose name reveals a specialty, ask counsel whether to redact it in dispute uploads. Apply the same test each time: does the issuer need this to decide authorization?

Disputes from a third-party payer need extra care, because that person may have no right to see the patient's information at all. See when someone else pays a debtor's account for how consent works in that case. For card-not-present portal payments, 3D Secure authentication can shift liability for fraud-coded disputes. It won't help with cases where the payer admits paying but disputes the debt.

Medical Debt Credit Reporting Changes and Payment Timing

Medical debt credit reporting no longer follows one set of rules. Start with the nationwide credit bureaus, which have voluntarily limited how medical collections appear on reports in recent years. Those limits are company policy, not law, and the bureaus can change them. Confirm the current terms with the bureaus or your furnishing vendor before you set posting rules around them.

Federal rules have been in flux, with rulemaking and litigation pulling in different directions. Watch for further action, but build your process around what is in force today. State law adds its own layer. Some states restrict credit reporting of medical debt, and where a state bars it, payment timing stops mattering for those accounts because you can't report them.

Payments interact with reporting in two places. The first is posting speed. If a payment settles but sits unposted for a week, the tradeline is wrong, and wrong tradelines draw consumer disputes and regulator complaints. Ask counsel to walk your team through furnisher accuracy obligations, then set a posting deadline your software can actually meet.

The second is reversals. Card payments can be charged back weeks later, and consumers can contest ACH debits after they post. Decide with counsel how to update a tradeline when a payment you reported as paid is reversed, then apply that rule the same way every time. The ACH return limits for collection agencies explain how long each return window stays open.

State Payment Plan and Interest Limits on Medical Debt

States have been the most active regulators of medical debt. Depending on the state, these laws may cap interest, require payment plans, set plan terms, limit lawsuits or wage garnishment, or bar credit reporting entirely. Which rules apply can turn on where the patient lives rather than where your agency sits. Your collection software needs the debtor's state on every account, and your payment flows need to honor it. The broader shift toward state enforcement is covered in CFPB Steps Back, States Step Up.

For recurring plans, build the state rules into the schedule itself. Where a state caps or bars interest, the schedule shouldn't carry an interest line. Plan lengths should meet any state minimum. The authorization the payer signs should match the schedule your system actually runs.

Recurring debits from a bank account carry their own federal authorization requirements, so confirm with counsel what your authorization form and records must contain. On the card side, check your processor's requirements and the card networks' rules for recurring-billing disclosures and cancellation. Confirm your retry settings too before you switch on automatic retries for declined cards.

Many agencies assume a card fee is fine if the processor allows it. Processor approval only settles the card side. Federal and state debt collection laws limit which amounts a collector may add to a balance, and some states may have rules aimed specifically at fees on medical debt.

So a surcharging program or dual pricing setup that works for a retailer needs a legal review before it goes near a medical collections portfolio. Network rules on card fees are one question. Collection law decides whether you can charge the fee at all.

Your next action is a one-afternoon audit. Run a test payment through every channel you offer, including text-to-pay. Then read every place the transaction shows up: the statement descriptor, the email receipt, the gateway report and the dispute export. Anything beyond what identifies the account and the amount is a fix to make this month. If your current setup can't keep those paths separate, request a free quote and a MannyPay specialist will respond within one business day.

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading