Payment Security

PCI DSS v4.0.1 Self-Assessment Questionnaire (SAQ C-VT)

PCI DSS SAQ C-VT framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
PCI DSS v4.0.1 Self-Assessment Questionnaire C-VT and Attestation of Compliance
  • Classification
    Category
    Payment Security
    Domain
    Cybersecurity
    Framework Family
    PCI Security Standards
  • Regulatory Context
    Type
    Assessment / Maturity Model
    Legal Instrument
    Standard
    Sector
    Financial Sector
    Industry
    Payment & FinTech
  • Region / Publisher
    Region
    Global
    Region Detail
    Global
    Publisher
    Payment Card Industry Security Standards Council (PCI SSC)
  • Versioning
    Version
    v4.0.1 SAQ C-VT (October 2024)
    Effective Date
    January 1, 2025 (the only SAQs accepted after PCI DSS v4.0 retired on December 31, 2024)
    Issue Date
    October 15, 2024
  • Adoption
    Adoption Model
    Industry Requirement
    Implementation Complexity
    Low
  • Official Reference
License Information

License included / downloadable: No

SAQ C-VT and its Attestation of Compliance can be downloaded from the PCI SSC Document Library at no charge after the Council's license agreement is accepted; the document is not provided with the platform.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
PCI DSS v4.0.1 Documentation
Official documentation detailing the PCI DSS version 4.0.1 security requirements and guidance.
PCI DSS SAQ C-VT Guidance
Provides detailed guidance on completing the Self-Assessment Questionnaire for PCI DSS compliance.
Key takeaways
  • PCI DSS v4.0.1 SAQ C-VT is for merchants that key transactions one at a time into a third-party virtual terminal from a single, isolated computer.
  • It covers Requirements 1 to 9 and 12, and eligible merchants store no account data electronically.
  • A virtual payment terminal submits transactions to a PCI DSS compliant third-party website and does not read data from the card.
  • The October 2024 edition restored the eligibility bullet on network segmentation to the wording used for PCI DSS v3.2.1.
  • SmartSuite IT Asset Management records the isolated computing device and what is installed and attached to it.

Overview

PCI DSS v4.0.1 Self-Assessment Questionnaire C-VT (SAQ C-VT) is the questionnaire and Attestation of Compliance for merchants that key card transactions one at a time into a third-party virtual payment terminal through a web browser on a single, isolated, Internet-connected computing device, and that store no account data electronically. It is a validation tool from the PCI Security Standards Council, not a standard: eligible merchants use it to self-assess against the applicable requirements of PCI DSS v4.0.1 and to report the result to their acquirer or payment brand. The Merchant Eligibility Criteria define a virtual payment terminal as a third-party solution used to submit transactions for authorization to a PCI DSS compliant third-party service provider (TPSP) website; unlike a physical terminal it does not read data from the card.

The October 2024 edition is where the Council's announced clarification of SAQ C-VT eligibility lives. Its Document Changes entry records that, in addition to aligning the content with PCI DSS v4.0.1 and adding the ASV Resource Guide to the resources list, the Council restored the eligibility bullet and footnote that refer to network segmentation to the wording used in SAQ C-VT for PCI DSS v3.2.1. That bullet now reads that the virtual terminal is accessed only from a computing device isolated in a single location and not connected to other locations or systems, which can be achieved with a firewall or network segmentation.

Section 2 contains Requirements 1 to 9 and 12; Requirements 10 (logging) and 11 (testing) are not included, so SAQ C-VT has no audit log, vulnerability scan or penetration test items. The v4.0.1 SAQs were issued on 15 October 2024, the v4.0 forms remained usable until PCI DSS v4.0 retired on 31 December 2024, and the best-practice items in the form became mandatory on 31 March 2025.

Why does it matter?

A virtual terminal moves card entry onto an ordinary computer with a web browser, so SAQ C-VT is less about a payment device and more about keeping one computer clean: nothing on it may store account data, nothing may be attached that reads cards, and it must be isolated from the rest of the business. The questionnaire adds the controls that make that isolation credible, anti-malware, patching, unique user IDs, multi-factor authentication for administrators and a specific rule for computers that face both the Internet and the cardholder data environment, while leaving out the logging and scanning regimes that a merchant-run payment application would attract.

Key benefits include:

  • A defined device, not a network

Eligibility turns on one computing device in a single location, isolated by a firewall or segmentation; footnote 1 allows several such browsers in the same network zone as long as they are isolated from other system types.

  • No Requirement 10 or 11

The form has no audit logging and no vulnerability scanning or penetration testing requirements, which is the main difference from SAQ C.

  • Eligibility wording restored

The October 2024 edition reinstated the v3.2.1 segmentation bullet and footnote in the eligibility criteria, the clarification the Council's 15 October 2024 bulletin announced for this SAQ.

  • Malware and phishing addressed

Requirements 5.2 to 5.4 ask for anti-malware that is deployed, current, scanning, logging and tamper-resistant, plus processes and mechanisms against phishing.

  • The provider's status is part of eligibility

The virtual terminal must be provided and hosted by a PCI DSS compliant TPSP, and Requirement 12.8.4 asks the merchant to monitor its providers' compliance status.

How does it work?

The PCI DSS Self-Assessment Completion Steps apply unchanged: confirm from the eligibility criteria and the Self-Assessment Questionnaire Instructions and Guidelines that C-VT is the right form; confirm the scope, which here is the isolated device and anything on its network segment; assess against the requirements; complete Section 1 (AOC Parts 1 and 2), Section 2 (the questionnaire) and Section 3 (AOC Parts 3 and 4); and submit the SAQ and AOC with any requested documentation to the payment brand or acquirer.

Each requirement receives one response from In Place, In Place with CCW, Not Applicable and Not in Place. A compensating control is documented in the Appendix B worksheet, a Not Applicable answer in Appendix C, and Appendix D for Not Tested stays empty because that option is not offered in this SAQ. The responses are summarized by requirement in Part 2g, the eligibility criteria are certified in Part 2h, and Part 3 states the overall result as Compliant, Non-Compliant with a target date, or Compliant but with Legal exception.

The Expected Testing column tells the merchant what to examine, observe or interview for each item, for example device configuration settings for 1.5.1 and anti-malware configurations and logs for Requirement 5. The Not Applicable example given is the media controls in 9.4.1 to 9.4.6, which apply only if paper media with cardholder data is kept. Future-dated items were best practice until 31 March 2025; a legal restriction is handled as Not in Place with a Part 3 attestation; and the customized approach cannot be documented in an SAQ.

Key Elements

  • Merchant Eligibility Criteria

The only payment processing is through a virtual payment terminal accessed by an Internet-connected web browser; the solution is provided and hosted by a PCI DSS compliant TPSP; it is accessed only from a computing device isolated in a single location and not connected to other locations or systems; the device has no software that stores account data, such as batch processing or store-and-forward; no attached hardware captures or stores account data; no other electronic receipt, transmission or storage of account data; retained account data is on paper only.

  • What counts as a virtual payment terminal

A third-party solution for submitting payment card transactions for authorization to a PCI DSS compliant TPSP website, into which the merchant manually enters account data through a securely connected web browser, one transaction at a time, from an isolated computing device.

  • Requirement 1: Network Security Controls

1.3.1 and 1.3.2 inbound and outbound traffic to and from the CDE restricted to what is necessary; 1.3.3 network security controls separating wireless networks from the CDE; 1.5.1 security controls on company- and employee-owned computing devices that connect to both untrusted networks and the CDE, with defined configuration settings, controls actively running and not alterable by users except by documented management authorization.

  • Requirement 2: Secure Configurations

2.1.1 configuration policies; 2.2.2 vendor default accounts; 2.2.4 only necessary services, protocols, daemons and functions enabled; 2.2.5 insecure services justified and mitigated; 2.2.6 security parameters set; 2.2.7 non-console administrative access encrypted; 2.3.1 and 2.3.2 changed wireless defaults and rotated wireless keys.

  • Requirements 3 and 4: Account Data

3.1.1 policies; 3.3.1 no retention of sensitive authentication data once authorization is complete; 3.4.1 PAN masked when displayed; 4.2.1.2 wireless networks that transmit PAN or connect to the CDE use strong cryptography for authentication and transmission.

  • Requirements 5 and 6: Malware and Patching

5.2.1 and 5.2.2 anti-malware deployed and effective; 5.3.1 to 5.3.5 automatic updates, scanning or continuous behavioral analysis, removable media, audit logs and no user disabling; 5.4.1 anti-phishing processes and mechanisms; 6.3.1 vulnerabilities identified and ranked; 6.3.3 security patches installed, critical ones within one month.

  • Requirements 7, 8 and 9: Access and Premises

7.2.2 least privilege by job function; 8.2.1 unique IDs; 8.2.2 no shared accounts; 8.2.4 approved changes to IDs; 8.2.5 immediate revocation for terminated users; 8.3.1 authentication by at least one factor; 8.3.6 passwords of at least 12 characters (eight where the system cannot support 12); 8.4.1 multi-factor authentication for non-console administrative access into the CDE; 9.1.1 policies; 9.2.1 facility entry controls; 9.4.1 to 9.4.6 media controls.

  • Requirement 12 and the Attestation

12.1.1 and 12.1.2 the information security policy and its review; 12.6.1 a security awareness program; 12.8.1 to 12.8.5 the TPSP list, agreements, due diligence, compliance monitoring and responsibility record; 12.10.1 an incident response plan. Section 1 holds AOC Parts 1 and 2 and Section 3 holds Parts 3 (status and signatures in 3a to 3d) and 4 (action plan on request).

What does it cover?

SAQ C-VT is for brick-and-mortar or mail and telephone order merchants whose only card processing is manual entry into a hosted virtual terminal from one isolated computer, with no electronic storage and no other electronic channel for account data (Merchant Eligibility Criteria). The assessed environment is that computer, its browser connection, the network segment and any wireless network it sits on, the administrators and users who touch it, the paper the merchant keeps and the TPSP that hosts the terminal. E-commerce channels, service providers, merchants that batch or store transactions in software, and merchants with card readers attached to the computer fall outside it.

What are its objectives?

The questionnaire is arranged so that a qualifying merchant can show the following:

That the seven eligibility criteria are met for the channel, certified in Part 2h, including that the terminal is hosted by a PCI DSS compliant TPSP.

That the computing device is isolated, configured securely, protected against malware and phishing, and patched (Requirements 1, 2, 5 and 6, including 1.5.1 for devices that reach both untrusted networks and the CDE).

That no account data is stored after authorization, PAN is masked, and any wireless path uses strong cryptography (Requirements 3 and 4).

That access is individual, approved, revoked on termination and, for administrators, protected by multi-factor authentication (Requirements 7 and 8).

That premises, paper media, policies, awareness, provider oversight and incident response are in place (Requirements 9 and 12) and the result is attested in Parts 3 and 4.

Framework in Context

SAQ C-VT is the manual-entry counterpart of SAQ C, which covers Internet-connected payment application systems and carries Requirements 10 and 11 as well. A merchant that takes cards through a physical standalone terminal looks instead at SAQ B or SAQ B-IP, and one that stores account data electronically or has several channels moves to SAQ D for Merchants. The requirements in Section 2 are the applicable subset of PCI DSS v4.0.1 (June 2024); the Council's SAQ Instructions and Guidelines document, reissued with the v4.0.1 SAQs, explains the choice among forms, and the TPSP hosting the terminal validates its own compliance separately.

Common Framework Mappings

SAQ C-VT's mappings are those of the parent standard restricted to Requirements 1 to 9 and 12; the endpoint, access, malware and policy controls it tests correspond to control families in the frameworks listed below.

Mapped frameworks include:

CIS Controls v8.1

COBIT 2019

CSA CCM v4

HIPAA

ISO 27001:2022

ISO 27002:2022

NIST CSF 2.0

NIST 800-53 Rev.5

SOC 2

SWIFT CSCF

SMARTSUITE

How SmartSuite Supports PCI DSS v4.0.1 SAQ C-VT

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use IT Asset Management (ITAM) for the record of the isolated computing device and what is installed and attached to it, Compliance Management for the Requirement 1 to 9 and 12 responses and appendices, Cyber & IT Risk for the endpoint, anti-malware and patch evidence, and Third Party Risk Management for the virtual terminal provider under Requirement 12.8.

Isolated Device Record (Part 2h, 1.5.1)

Describe the computing device, its location, the firewall or segmentation that isolates it, the absence of storage software and card readers, and the 1.5.1 settings that users cannot alter.

Requirement Responses (Section 2 and Part 2g)

Keep the included sub-requirements of Requirements 1 to 9 and 12 as records with one response each, the Expected Testing evidence and any Appendix B worksheet or Appendix C explanation.

Endpoint Protection Evidence (5.2, 5.3, 5.4, 6.3)

File anti-malware configuration and update records, scan and audit log settings, anti-phishing measures, vulnerability rankings and patch dates for the device.

User and Administrator Access (8.2, 8.3, 8.4.1)

List every user ID for the device and the virtual terminal, approvals for changes, revocation dates for leavers, password settings and the MFA used for administrative access into the CDE.

Virtual Terminal Provider Oversight (12.8)

Record the TPSP that hosts the terminal, its PCI DSS compliance status and the date checked, the written agreement, and which PCI DSS requirements it manages on the merchant's behalf.

Attestation and Action Plan (Parts 3 and 4)

Store the Part 3 status, signatures and dates, the roles of any QSA or ISA, and target dates for any Not in Place item should the acquirer request a Part 4 plan.

Related frameworks

CIS Controls v8.1

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO 27002:2022

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

SOC 2

SOC 2 is the AICPA examination, under AT-C 105 and 205, of a service organization's controls against the 2017 Trust Services Criteria, issued as a type 1 or type 2 attestation report.

SWIFT CSCF

The SWIFT Customer Security Controls Framework (CSCF v2026) sets 32 mandatory and advisory controls that every Swift user attests to each year under the Customer Security Programme.

FAQ

Frequently Asked Questions For PCI DSS v4.0.1 SAQ C-VT (Cardholder Data Security Controls for Virtual Terminal Merchants)

The Merchant Eligibility Criteria describe it as a third-party solution used to submit payment card transactions for authorization to a PCI DSS compliant third-party service provider's website, into which the merchant manually enters account data from an isolated computing device through a securely connected web browser. Unlike a physical terminal it does not read data from the card. The SAQ applies only to merchants that key in a single transaction at a time.

Merchants whose only payment processing is through a virtual terminal accessed by an Internet-connected browser, hosted by a PCI DSS compliant TPSP, from a computing device isolated in a single location and not connected to other locations or systems, with no software that stores account data, no attached card readers or other capture hardware, no other electronic channel for account data, and any retained account data on paper. Card-present and mail or telephone order merchants both qualify; e-commerce channels and service providers do not.

The Document Changes entry for October 2024 says the Council restored the eligibility bullet and its footnote that refer to network segmentation to the wording used in SAQ C-VT for PCI DSS v3.2.1. The bullet states that the virtual terminal is accessed only from a computing device isolated in a single location, which can be achieved with a firewall or network segmentation, and the footnote explains that several such devices may share a network zone if they are isolated from other system types. The same entry records the alignment with PCI DSS v4.0.1 and the addition of the ASV Resource Guide to the resources list.

Section 2 contains Requirements 1, 2, 3, 4, 5, 6, 7, 8, 9 and 12, each reduced to the sub-requirements relevant to an isolated virtual terminal device. Requirements 10 (logging and monitoring) and 11 (security testing) are not included, so the form contains no audit log, vulnerability scan or penetration test items. The Part 2g summary in the AOC therefore lists ten requirements rather than twelve.

Requirement 1.5.1 applies to any computing device, company- or employee-owned, that connects to both untrusted networks such as the Internet and the cardholder data environment. It requires specific configuration settings to prevent threats entering the network, security controls that are actively running, and controls that users cannot alter unless management documents and authorizes an exception case by case for a limited period. The Expected Testing is to examine policies, configuration standards and the device's settings.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.