PCI DSS 4.0.1 for Telehealth Checkouts: Keeping Card Data Out of Your EHR
Telehealth companies collect card numbers in more places than they plan to: intake forms, phone calls, chat. PCI DSS 4.0.1 is far easier to live with when card data never lands in clinical systems at all.
Keep card numbers out of your EHR by never letting your systems receive them. Capture cards in hosted payment fields or through a tokenization service, store tokens, and take phone payments in a virtual terminal rather than in clinical notes. PCI DSS v4.0.1 is the current standard, and the requirements v4.0 had future-dated, including controls on payment-page scripts, became mandatory on March 31, 2025.
PCI DSS scope is the set of systems, people and processes that store, process or transmit cardholder data, plus anything connected to them. Everything in scope has to meet the standard's requirements, so the direct way to shrink a PCI program is to keep card data out of systems that don't need it.
What PCI DSS 4.0.1 changed, and when
As of November 2026: PCI DSS v4.0.1 was published by the PCI Security Standards Council in June 2024. The requirements that v4.0 introduced as future-dated became mandatory on March 31, 2025. SAQ A was revised in early 2025.
For a telehealth checkout, three parts of that matter:
- The version. v4.0.1 is the current version, and the one your next assessment should use.
- Script controls. Requirements 6.4.3 and 11.6.1 target tampering with payment pages: 6.4.3 deals with managing the scripts that run on them, and 11.6.1 with detecting unauthorized changes to them.
- SAQ A. The questionnaire for merchants that outsource card capture was revised in early 2025. If you validate with an SAQ, confirm with your acquirer which one applies now, rather than reusing last year's.
This is an overview of the standard as it affects telehealth, not advice on which questionnaire or assessment applies to you. Your acquirer sets your validation requirement, and a qualified security assessor can tell you how your setup measures against it.
How card data ends up in telehealth clinical systems
Through convenience, one workflow at a time. Telehealth companies take payment information alongside clinical information, and the two drift together unless someone keeps them apart.
| Where card data turns up | How it gets there | The fix |
|---|---|---|
| EHR or intake forms | A card field added to the intake questionnaire so patients "do it all at once" | Collect payment in hosted fields; the intake form never asks for card data |
| Patient charts and notes | Staff type a card number into the chart during a phone intake | A virtual terminal for phone payments; nothing written in the chart |
| Support tickets, chat and email | Patients send card numbers to "update billing" | Reply with a payment link; mask and delete what arrives |
| Call recordings | A card number read aloud on a recorded line | Pause recording for payment, or send a payment link |
| Spreadsheets | Staff tracking payment plans by hand | Saved cards and scheduled billing in the payment system, with tokens |
| Application logs | Request bodies logged in full during debugging | Card capture that never passes through your servers, and logs that hold tokens only |
Each row is also a patient-privacy problem: a system that holds card numbers next to diagnoses turns one incident into two kinds of breach.
Hosted fields and tokenization keep card numbers off your servers
They move card capture to the payment provider. Hosted payment fields are inputs served by the provider and embedded in your checkout, so the card number goes from the patient's browser to the provider without touching your systems. Tokenization replaces the card number with a token that your systems can store and use to charge the card again, for renewals or installments, without ever holding the number.
Both reduce your PCI scope, and for a telehealth company that is the main benefit: if your EHR, CRM and support tools never receive a card number, they don't have to be secured as if they might. VyaPay's VyaCloud tokenization works this way. Card data never touches your servers, and your systems keep a token instead. How tokens support card-on-file renewals and retries is in recurring billing for subscription telehealth.
What they don't do is make the page itself someone else's problem. The page that loads the hosted fields is still yours, and scripts running on it are what the payment-page requirements address. How those requirements apply to a hosted-fields checkout depends on your validation route, which is a question for your acquirer or assessor.
Scripts on the payment page: requirements 6.4.3 and 11.6.1
They exist because a script running on a payment page can change it. Requirement 6.4.3 is about managing every script that runs on the payment page, and 11.6.1 is about detecting tampering with the page. Together they target attacks that alter a checkout without touching your servers.
Telehealth intake pages can collect a lot of scripts: analytics, chat widgets, scheduling tools, session recording and advertising pixels. If your checkout sits on the same page as your intake flow, every one of those is on your payment page. Two steps make the requirements manageable:
- Keep checkout on its own lean page, with only the scripts it needs to take payment.
- Know who can add a script, and keep a list of what runs there and why.
The same third-party scripts on intake pages raise a separate patient-privacy question, because they can see what a patient types about their health. That one belongs to your HIPAA counsel, not your PCI assessor.
Phone intake and the virtual terminal
Phone payments invite improvisation. A few rules keep card data out of everything except the payment system:
- Enter the card directly into the virtual terminal while the patient is on the line.
- Never write it down: not in the chart, the CRM, a sticky note or a chat to a colleague.
- Don't read the full number back to the patient.
- Pause call recording while the card is given, if your phone system records.
- Give each staff member their own login, and remove it when they leave.
- Where possible, send a payment link so the patient enters the card themselves.
VyaPay offers a virtual terminal and payment links for exactly this split: staff can take a payment, or send one, without the number passing through anything else they use. Training matters as much as tooling here. New intake staff should hear the rule on their first day, along with what to do when a patient emails a card number anyway.
PCI DSS and HIPAA are separate programs
They protect different data, and passing one says nothing about the other. Section 1179 of HIPAA keeps the law off a financial institution's payment activities, but it has no bearing on PCI DSS. PCI DSS protects card data and says nothing about patient health information. Tokenization keeps card numbers out of your systems; it doesn't keep a diagnosis out of an order description.
The discipline is the same in both: put as little as possible into payment fields, and keep clinical and payment data in systems built for each. Where patient information leaks into payment data, and what to send instead, is in our explainer on HIPAA Section 1179 and payment processing.
A PCI checklist for a telehealth launch
- Map every channel where a patient could give you a card number: checkout, intake, phone, chat, email and payment plans.
- Route each one to hosted fields, tokenization, the virtual terminal or a payment link.
- Remove card fields from EHR, CRM and intake forms.
- List the scripts on your payment page and who can change them.
- Train intake and support staff, and write down what to do with card numbers that arrive by email or chat.
- Ask your acquirer which validation it requires under v4.0.1.
- Re-check whenever you add a channel, a vendor or a script.
Your PCI scope is one item in the larger underwriting file described in the telehealth merchant account application checklist. To see how VyaCloud and the virtual terminal would fit your intake flow, talk to VyaPay.
Frequently asked questions
Does PCI DSS 4.0.1 apply to a telehealth company?
If you accept cards, yes: the obligation comes with card acceptance, through your merchant agreement. v4.0.1 is the current version, and the requirements v4.0 had future-dated have been mandatory since March 31, 2025.
Can our EHR store card numbers if the vendor says it's secure?
If it stores them, it's in your PCI scope, along with whatever connects to it. Keeping card numbers out of the EHR entirely is simpler than securing it to PCI's standard.
Which SAQ should we complete?
Your acquirer tells you which validation it requires. SAQ A was revised in early 2025, so check the current version against how you capture cards rather than relying on an old assessment.
Does a token count as card data?
A token from a tokenization service stands in for the card number and can't be used as one outside that service. That is why storing tokens instead of card numbers reduces your PCI scope.
