PCI Compliance For Payment Gateways

PCI compliance for payment gateways comes down to one fact most business owners miss: using a compliant gateway does not make your business compliant. The way you connect to the gateway (a hosted page, an iframe, a direct post form, or a server API) decides how much of PCI DSS v4.0.1 lands on you, which self-assessment form you file, and what your contract must say.

Last updated: November 2026

Key Takeaways

  • PCI DSS v4.0.1 is the current standard. Version 3.2.1 was retired on 31 March 2024, and 51 of the 64 new v4 requirements became mandatory on 31 March 2025.
  • PCI DSS is not a statute. It reaches you through your merchant agreement, and your acquirer and the card brands decide how you must prove compliance.
  • Your checkout design picks your paperwork: a fully outsourced hosted page or iframe can fit SAQ A, a merchant-built form that posts to the gateway is SAQ A-EP, and a site that accepts card data on its own servers is generally SAQ D.
  • PCI DSS Requirement 12.8 requires written agreements with your gateway, annual monitoring of its compliance, and a record of which requirements each side manages.
  • Utah’s breach law (Utah Code 13-44-202) requires a gateway that holds data it does not own to notify the owner immediately after discovering a breach, and that duty cannot be waived by contract.
  • Utah’s Cybersecurity Affirmative Defense Act (78B-4-702) lets a business that reasonably complies with the current PCI DSS, through a written cybersecurity program, raise a defense to certain Utah breach claims.

What PCI Compliance Means When You Use a Payment Gateway

The Payment Card Industry Data Security Standard (PCI DSS) is published by the PCI Security Standards Council. It applies, in the Council’s words, to entities that store, process, or transmit cardholder data or sensitive authentication data, or that could impact the security of the cardholder data environment. That last clause catches gateway users: your website can be in scope without touching a card number.

A payment gateway is a third-party service provider (a “TPSP” in PCI language). It carries its own PCI obligations and validates them separately. Your obligations do not disappear when you sign up with one. PCI DSS says so directly in the applicability notes to Requirement 12.8.1: using a PCI DSS compliant TPSP does not make an entity PCI DSS compliant, nor does it remove the entity’s responsibility for its own compliance.

“Of the 64 new requirements, 51 are future-dated and will be effective as of 31 March 2025.”

PCI Security Standards Council, August 2024

Because those requirements have been mandatory since 31 March 2025, a questionnaire you file now asks about controls an older one did not. Current documents are in the Council’s document library.

PCI Compliance Is a Contract Obligation, Not a Statute

No Utah or federal statute says “comply with PCI DSS.” The standard binds you because your merchant agreement with your acquiring bank or processor requires it, and that bank is bound to the card brands. The Council’s own PCI DSS page says whether an entity must comply with or validate compliance is at the discretion of the organizations that manage compliance programs, such as a payment brand or acquirer.

The penalties therefore come through your contracts. Visa states that it may assess the acquirer when a merchant does not comply or fails to fix a security issue, and how much of that reaches you depends on the pass-through language in your merchant agreement.

Merchant Levels: How Much Proof You Owe

Merchant levels are set by the card brands, not by the Council. Visa places merchants by Visa transaction volume over a 12-month period. Its published tiers are summarized below.

Visa level Annual Visa transactions Validation Visa lists
Level 1 Over 6 million (all channels), or a global merchant identified as Level 1 by any Visa region Annual Report on Compliance by a Qualified Security Assessor, quarterly ASV network scan, Attestation of Compliance
Level 2 1 million to 6 million (all channels) Annual SAQ, quarterly ASV scan, Attestation of Compliance
Level 3 20,000 to 1 million e-commerce Annual SAQ, quarterly ASV scan, Attestation of Compliance
Level 4 Under 20,000 e-commerce, and all other merchants up to 1 million Annual SAQ recommended, ASV scan if applicable, requirements set by the acquirer

Source: Visa compliance validation levels. Visa also states that any merchant that suffered a hack resulting in an account data compromise may be escalated to a higher validation level. For a Level 4 merchant, the acquirer’s requirements in your merchant agreement matter more than the table.

How Your Gateway Integration Changes Your SAQ

A Self-Assessment Questionnaire (SAQ) is the form most merchants below Level 1 use to validate. Each SAQ has eligibility criteria, and the integration method you or your developer chose is what decides which criteria you meet. For PCI compliance for payment gateways, it is the decision that matters most, and a web developer often makes it without asking the owner.

Integration Who serves the card form Typical SAQ What stays on you
Full redirect to a hosted payment page The gateway SAQ A, if every eligibility criterion is met The web server holding the redirect, script-attack eligibility confirmation, TPSP oversight, paper records
Embedded iframe served by the gateway The gateway, inside your page SAQ A, if every element of the payment form originates from the gateway Your parent page and its scripts, plus the same items as a redirect
Direct post or JavaScript form built on your site that sends card data to the gateway Your website, posting to the gateway SAQ A-EP Your website is treated as part of the cardholder data environment
Server-side API where card data reaches your servers Your systems Generally SAQ D The full standard for your environment

Your acquirer, not this table, has the final word on which SAQ you file.

SAQ A: card handling fully outsourced

SAQ A is for card-not-present merchants whose account data functions are completely outsourced to PCI DSS validated and compliant third parties. The merchant must confirm that all processing is outsourced, that it does not electronically store, process, or transmit account data on its systems, that it has reviewed its provider’s Attestation of Compliance, and that any retained account data is on paper only. For e-commerce, all elements of the payment page delivered to the customer’s browser must originate only and directly from a PCI DSS compliant provider.

Even here, your website is not out of the picture. The SAQ A instructions say requirements that refer to the cardholder data environment apply to the merchant website that provides the address of the provider’s payment page, because that website affects how account data is transmitted.

The January 2025 SAQ A change

The Council revised SAQ A in January 2025, effective 31 March 2025. It removed Requirements 6.4.3 and 11.6.1 (payment page script management and tamper detection) and the related targeted risk analysis in 12.3.1 from SAQ A. In exchange, it added an eligibility criterion: merchants must confirm their site is not susceptible to attacks from scripts that could affect the merchant’s e-commerce system. The Council was explicit that this changes how SAQ A merchants report, not the underlying requirements. Read the Council’s announcement before you sign that confirmation: it is a factual statement to your bank about your website.

SAQ A-EP: your page controls the payment flow

SAQ A-EP covers e-commerce merchants whose website does not itself receive account data but controls how customers, or their account data, are redirected to the provider. Each element of the payment page comes from either the merchant’s website or a compliant provider. Here the SAQ says requirements referring to the cardholder data environment apply to the merchant website itself. That pulls the payment page script rules, including 6.4.3 (an authorized, integrity-checked inventory of every payment page script) and 11.6.1 (a change and tamper detection mechanism for payment pages), squarely onto your site.

SAQ D: everything else

SAQ D for Merchants applies to merchants eligible to self-assess who do not meet the criteria for any other SAQ. The Council’s examples include e-commerce merchants that accept cardholder data on their website and merchants with electronic storage of cardholder data.

Tokenization: What It Does and Does Not Solve

Most gateways return a token after the first charge so you can bill a returning customer or run a subscription without keeping the card number. That is valuable. If your systems never store the primary account number, a large part of Requirement 3 (protecting stored account data) has nothing to attach to. PCI DSS Requirement 3.5.1 lists index tokens as one approved way to render the card number unreadable where it is stored.

Tokenization is not a scope eraser. A token protects what you store afterward, not the moment of capture. If the card number passed through your server or your JavaScript on its way to the gateway, that path is still in scope. Two other rules matter:

  • Never keep the security code. Requirement 3.3.1 says sensitive authentication data is not retained after authorization, even if encrypted. A customer service habit of writing the three-digit code on a call sheet violates this.
  • Keep only what you need. Requirement 3.2.1 requires retention and disposal policies that limit stored account data to what legal, regulatory, or business needs require. That overlaps with Utah’s disposal rule, discussed in our guide to data retention documentation.

The Responsibility Matrix and Requirement 12.8

After a breach, the first question is who was supposed to do what. PCI DSS Requirement 12.8 answers it:

Requirement What it requires Practical step
12.8.1 A list of all TPSPs that receive account data or could affect its security, with a description of each service List the gateway, processor, hosting company, e-commerce platform, and any plugin vendor that touches checkout
12.8.2 Written agreements including the TPSP’s acknowledgment that it is responsible for the security of account data it handles or could impact Find that acknowledgment in the gateway’s terms; if it is not there, ask for it
12.8.3 A process for engaging TPSPs, including due diligence before engagement Keep a dated file showing what you reviewed before signing
12.8.4 Monitoring each TPSP’s PCI DSS compliance status at least once every 12 months Calendar an annual request for the gateway’s current Attestation of Compliance
12.8.5 Information on which requirements each TPSP manages, which the merchant manages, and which are shared Get the gateway’s responsibility matrix in writing and keep it with your SAQ

The applicability notes to 12.8.4 contain a point that deserves a lawyer’s attention: where a provider meets PCI requirements on your behalf and fails to meet them, those requirements are also “not in place” for you. Your compliance rides on the vendor’s performance, which is why the contract matters.

Contract Clauses to Negotiate With Your Gateway

Whether or not your gateway will negotiate, know what your agreement says before you need it. These are the clauses I look at first:

  1. Security acknowledgment. The Requirement 12.8.2 acknowledgment that the gateway is responsible for the account data it handles. Without it, your own SAQ has a gap.
  2. Annual Attestation of Compliance. A commitment to deliver a current AOC on request, and notice if the gateway falls out of compliance for the services you use.
  3. Responsibility matrix. The 12.8.5 allocation, incorporated by reference so it cannot change silently.
  4. Breach notice to you. A defined notice period and a duty to share what the gateway learns. Utah already requires the gateway to notify you immediately in many cases (see below), and a contract can add detail and remedies on top of that.
  5. Fines, assessments, and indemnity. Who bears card brand assessments and forensic investigation costs when the breach starts on the gateway’s side. Compare the indemnity with the limitation of liability clause, which often caps it to a few months of fees. Our article on contract indemnification in Utah explains how those two provisions interact.
  6. Token portability on exit. Whether stored tokens or the underlying card data can be migrated to a new provider. If not, switching gateways means asking every subscriber for their card again.
  7. Governing law and dispute resolution. Under Utah Code 78B-4-705, a choice of law provision designating Utah applies the state’s cybersecurity affirmative defense to the fullest extent possible in a civil action, even one brought in another state. Venue and arbitration terms matter too; see dispute resolution clauses.

If you need help with the review itself, that is routine work for a Utah business contract lawyer.

Utah Data Breach Notification Law and Payment Cards

Utah’s Protection of Personal Information Act is Title 13, Chapter 44. The current chapter text sets out the rules most gateway users need.

What counts as personal information

Under 13-44-102, “personal information” is a person’s first name or first initial and last name combined with certain data elements, when either the name or the data element is unencrypted or not otherwise protected. For payment cards, the element is a financial account number or credit or debit card number together with any required security code, access code, or password that would permit access to the account. Encryption matters: data rendered unreadable or unusable falls outside the definition. Financial institutions are exempt (13-44-103).

What you must do after a breach

  • Investigate. A business that owns or licenses the data must, on becoming aware of a breach, conduct a good faith, reasonable, and prompt investigation into the likelihood of misuse for identity theft or fraud.
  • Notify residents. If misuse has occurred or is reasonably likely, notify each affected Utah resident in the most expedient time possible without unreasonable delay. Notice may go by mail, electronically, or by telephone.
  • Notify the state at 500. If 500 or more Utah residents are affected, also notify the Office of the Attorney General and the Utah Cyber Center.
  • Notify credit bureaus at 1,000. If 1,000 or more Utah residents are affected, also notify each nationwide consumer reporting agency.

The gateway’s duty to you

Subsection 13-44-202(3) is the provision most relevant to payment gateways. A person that maintains computerized personal information it does not own or license must notify and cooperate with the owner or licensee immediately after discovering a breach, if misuse occurs or is reasonably likely. Cooperation includes sharing information relevant to the breach. Subsection (7) adds that a waiver of the section is contrary to public policy and void. A gateway contract that tries to excuse breach notice does not work in Utah.

Enforcement and penalties

Under 13-44-301, the Attorney General enforces the chapter. Civil penalties are up to $2,500 for a violation or series of violations concerning a specific consumer, and up to $100,000 in the aggregate for related violations concerning more than one consumer. The aggregate cap does not apply when the violations concern 10,000 or more Utah residents and 10,000 or more residents of other states, or when the business agrees to settle for more. The chapter creates no private right of action, but it expressly preserves private claims under other law, including contract and tort. An administrative action must start within 10 years, and a civil action within five years, after the alleged breach last occurred.

Utah’s Cybersecurity Affirmative Defense Act

Utah enacted the Cybersecurity Affirmative Defense Act in 2021. It sits in Title 78B, Chapter 4, Part 7, and for businesses that take payments it is the most useful statute on the books.

Under 78B-4-702, a business that creates, maintains, and reasonably complies with a written cybersecurity program in place at the time of a breach has an affirmative defense to a claim brought under Utah law or in Utah courts alleging it failed to implement reasonable information security controls. Separate defenses cover claims that it failed to respond to or notify about the breach appropriately, if the written program had response and notification protocols and the business followed them.

The program must provide administrative, technical, and physical safeguards, be scaled to the size and complexity of the business and the sensitivity of the data, and reasonably conform to a recognized framework. Under 78B-4-703(1)(b)(iv), for information the PCI DSS is intended to protect, reasonable compliance with the current version of the PCI DSS qualifies. When a framework is revised, the business must reasonably conform to the revised version no later than one year after it is published (78B-4-703(3)(a)).

Three limits matter:

  • It must be written. A gateway’s AOC is not your program. You need your own document, which can be short for a small business.
  • Known, ignored threats defeat it. The defense is unavailable if the business had actual notice of a threat, did not take known remedial steps in a reasonable time, and the threat caused the breach. A risk assessment, by itself, is not actual notice.
  • It is a defense, not a cause of action. Section 78B-4-704 says the Part creates no private claim when a business fails to comply.

The integration choice, the SAQ, the 12.8 file, and a short written program are what let a Utah business stand behind this defense if a breach reaches court. See our overview of litigation for how those cases move.

Frequently Asked Questions

Does using Stripe, Square, or another big gateway make my business PCI compliant?

No. PCI DSS says that using a compliant service provider does not make you compliant and does not remove your own responsibility. A well-designed integration can shrink your obligations to SAQ A, but you still validate annually and keep the required documentation.

What is the current version of PCI DSS?

PCI DSS v4.0.1, released by the PCI Security Standards Council in June 2024 as a limited revision of v4.0. Version 3.2.1 was retired on 31 March 2024, and the future-dated v4 requirements became effective on 31 March 2025.

Which SAQ do I file if my checkout uses an iframe?

Often SAQ A, if every element of the payment form originates from the PCI compliant gateway, no account data touches your systems, and you can confirm your site is not susceptible to script attacks affecting your e-commerce system. Your acquirer makes the final call.

What is the difference between SAQ A and SAQ A-EP?

Under SAQ A, the gateway serves the entire payment page. Under SAQ A-EP, your website does not receive card data but controls how it reaches the gateway, so your website is treated as part of the cardholder data environment and carries far more requirements.

Is PCI DSS required by Utah law?

No statute requires it. It binds you through your merchant agreement. Utah’s Cybersecurity Affirmative Defense Act, however, treats reasonable compliance with the current PCI DSS, within a written cybersecurity program, as a basis for an affirmative defense to certain breach claims.

Do I have to notify customers if my payment gateway is breached?

If you own or license the data and the investigation shows misuse occurred or is reasonably likely, Utah Code 13-44-202 requires notice to affected Utah residents, plus the Attorney General and Utah Cyber Center at 500 residents and credit bureaus at 1,000. A gateway holding your data must notify you immediately when misuse is likely.

Choosing a gateway, renewing a merchant agreement, or writing the cybersecurity program that supports Utah’s affirmative defense? These are contract and liability questions, and a short review before you sign is cheaper than one after a breach.

Schedule a consultation or call (801) 613-1472. Offices in Lindon and West Jordan. More on business matters at Business Lawyer Utah.

Written by Jeremy Eveland, a Utah business attorney licensed in Utah, Nevada, California, and Texas, who advises companies on contracts, vendor agreements, and data security liability.

This article is general information, not legal advice, and it is not a PCI assessment. PCI DSS requirements, card brand programs, and Utah statutes change. Your acquirer and a Qualified Security Assessor determine your validation requirements. Reading this article does not create an attorney-client relationship.