HIPAA-Compliant Payment Processing for Telehealth: What Providers Need to Know
A practical guide to reviewing telehealth payment data, vendor roles, business associate agreements and the difference between HIPAA and PCI DSS.
HIPAA payment compliance depends on how patient information moves through the payment workflow and what each vendor does with it. A BAA is not automatically required for every card processor. Telehealth providers should review data flows, vendor roles, PCI DSS scope, access controls, integrations and whether services involve PHI.
TABLE OF CONTENTS
HIPAA-compliant payment processing starts with how patient information moves through your telehealth workflow. A payment product alone does not establish compliance. Review what data each vendor receives, what it does with that data and which contractual and security responsibilities apply.
A business associate agreement, or BAA, is not automatically required for every card processor. The answer depends on the vendor’s role, including whether it performs services involving protected health information (PHI) on behalf of a HIPAA-covered practice.
When is a payment vendor a business associate?
HHS explains a limited financial-transaction exception: a financial institution carrying out ordinary card processing, check clearing or funds transfers does not need a BAA for those activities alone.
The analysis changes when a vendor provides services such as billing, claims administration or practice management involving PHI on behalf of the practice. Those services fall within the business-associate analysis, and a BAA is generally required when the vendor is acting as a business associate.
Review each service separately. The ordinary payment-processing exception does not automatically cover an integrated patient database, billing platform or other additional service. Ask your privacy lead to document the vendor’s role and the reason a BAA is or is not required.
Where does patient information enter a payment workflow?
Trace a sample transaction from appointment booking through payment and reconciliation. Check:
- Invoice descriptions and custom fields for diagnoses, treatment details or other patient information.
- Checkout pages and payment links for information exposed outside the patient portal.
- Email and text reminders for details visible in a notification or shared inbox.
- Receipts and statement descriptors for information the patient would not expect others to see.
- EHR, scheduling and accounting integrations for the fields sent to each system.
- Support tickets, exports and chargeback evidence for unnecessary clinical records.
Use the least sensitive information needed for the payment task. Under HHS’s minimum necessary guidance, many payment and healthcare-operations uses and disclosures are subject to limits on PHI. Review the applicable exceptions and use a documented process rather than treating every disclosure identically.
Is PCI compliance the same as HIPAA compliance?
No. PCI DSS addresses protection of payment account data. HIPAA addresses protected health information and the responsibilities of covered entities and business associates. A workflow that meets card-data requirements still needs a separate HIPAA assessment.
Likewise, signing a BAA does not complete a practice’s compliance work. Review access controls, staff responsibilities, vendor arrangements and the handling of ePHI throughout the workflow. HHS risk-analysis guidance provides a starting point for identifying risks to electronic PHI.
What should telehealth providers ask a vendor?
- Which patient and payment fields will you receive, store or pass to another service?
- Which functions are ordinary financial transactions, and which involve PHI on our behalf?
- If you act as a business associate, what BAA and subcontractor arrangements apply?
- How are user access, data exports, retention and incident reporting handled?
- What documentation supports your payment-security claims?
- How should our staff submit billing support requests or dispute evidence without unnecessary PHI?
Get answers for the exact product and configuration you plan to use. A statement about one service does not establish that every integration or optional feature meets your needs.
What about recurring payments and saved cards?
Review the authorization, cancellation process and data flow for recurring charges. Determine whether the payment system stores clinical details, patient identifiers or only the information needed to process the payment. Ask the vendor how credentials and transaction records are protected, and include connected systems in the review.
What about FSA and HSA cards?
If FSA or HSA card acceptance is part of your requirements, ask the vendor to confirm support for your services and account setup in writing. Treat payment-method eligibility and HIPAA review as separate checks. Do not infer either from the other.
- HHS: Business associates and financial-transaction exception
- Social Security Act section 1179: Financial transactions
- 45 CFR 164.502: Minimum necessary and business-associate disclosures
- HHS: Minimum necessary requirement
- HHS: Summary of the HIPAA Security Rule
- PCI SSC: PCI Data Security Standard
- HHS: Security Rule risk analysis guidance
Questions related to this guide
How much are credit card processing fees?
Credit card processing costs most U.S. businesses between 1.5% and 3.5% per transaction. The floor is interchange — the card networks' published wholesale cost — plus your processor's markup. Online and keyed transactions cost more than in-person chip payments because card-not-present fraud risk is priced into the rate.
Read full answerWhat is a merchant account?
A merchant account is the arrangement with an acquiring bank and a payment processor that lets a business accept credit and debit cards. Card sales are authorized and settled through it, fees are deducted, and the funds are deposited to your business checking account, typically within 1–2 business days. Approval involves underwriting, because the bank takes on risk for every sale.
Read full answerWhat is a payment gateway?
A payment gateway is the software that securely captures card details on your website or app, encrypts them, and sends them to the processor for authorization — the online equivalent of the card terminal in a store. Gateways also handle recurring billing, tokenization, and fraud screening before a transaction ever reaches the networks.
Read full answerWhich industries are considered high-risk?
Commonly high-risk industries include CBD and hemp, firearms and ammunition, nutraceuticals and supplements, telehealth, vape and tobacco, subscription and continuity billing, travel, coaching and info products, debt services, adult products, and pawn. Most appear on the published restricted-business lists of Stripe, PayPal, and Square — which is why those providers decline them.
Read full answerWhat documents do I need to apply for a merchant account?
A standard merchant account application asks for a government-issued ID, your EIN or business registration, a voided check or bank letter for your settlement account, and about three months of recent bank or processing statements. High-risk businesses should also expect to provide licenses, supplier agreements, and financial statements.
Read full answerCan gun shops and FFL dealers accept credit cards?
Yes. Gun shops and federal firearms licensees (FFLs) can accept credit and debit cards, and Visa says it serves any legal purchase. Paying by card does not change the dealer's federal duties: record the sale on ATF Form 4473 and contact NICS before transfer. The harder part is finding an acquiring bank willing to board the business.
Read full answerWhat is a chargeback?
A chargeback is a card payment taken back by the cardholder's bank after the cardholder disputes it. The issuing bank sends the dispute through the card network to the merchant's bank, which deducts the amount from the merchant's account. Visa's merchant rules call this a dispute. Mastercard calls it a chargeback. The process is the same.
Read full answerReview your healthcare payment setup
Bring your billing workflow and integration requirements to discuss your payment setup.
Explore healthcare payments