A payment gateway can't process a live card payment until it proves it protects card data. The proof is PCI DSS, the Payment Card Industry Data Security Standard, and for a gateway it isn't a one-time certificate. It's a yearly assessment of your systems, your people and your processes, which your acquirers will ask to see every time it renews.
This page explains PCI compliance for payment gateways from a PSP's side: what the standard requires, which validation level applies, what falls inside scope, how the assessment runs and how running on SaaS or on your own infrastructure changes your share of the work.
What PCI DSS is, and which version applies
The PCI Security Standards Council maintains PCI DSS. The council published PCI DSS v4.0.1 in 2024 as a limited revision with no new or deleted requirements, and v4.0 was retired on December 31, 2024. Since then, v4.0.1 is the only active version.
Version 4 added 64 new requirements, and 51 of them were future-dated to March 31, 2025. Those now apply to every assessment, so a gateway built against an older checklist has catching up to do.
The 12 PCI DSS requirements for a payment gateway
PCI DSS groups its controls into 12 principal requirements. Here are the PCI DSS requirements for payment gateway teams, with what each tends to mean in daily work.
| # | Requirement | What it means for a gateway |
|---|---|---|
| 1 | Install and maintain network security controls | Firewalls and segmentation around the cardholder data environment |
| 2 | Apply secure configurations to all system components | Hardened servers and containers, no default passwords |
| 3 | Protect stored account data | Encrypted vault, no CVV kept after authorization, masked card numbers |
| 4 | Protect cardholder data with strong cryptography during transmission | TLS everywhere card data travels, including to acquirers |
| 5 | Protect systems and networks from malicious software | Anti-malware and controls on what can run |
| 6 | Develop and maintain secure systems and software | Secure code reviews, patching, control of payment page scripts |
| 7 | Restrict access by business need to know | Role-based access to card data and admin tools |
| 8 | Identify users and authenticate access | Unique accounts and multi-factor authentication |
| 9 | Restrict physical access to cardholder data | Data center controls, or your cloud provider's attestations |
| 10 | Log and monitor all access | Central logging and alerts on access to the vault |
| 11 | Test security of systems and networks regularly | Vulnerability scans, penetration tests, change detection on payment pages |
| 12 | Support information security with policies and programs | Policies, training, incident response and third-party management |
Requirements 6 and 11 now include controls for scripts on payment pages, one of the v4 additions. A hosted payment page that loads outside scripts has to inventory and monitor them.
PCI DSS compliance requirements for payment gateways: your level
Card schemes set validation levels for service providers, and a gateway is a service provider. Visa's requirements for service providers (in its document dated October 2017) define two levels.
| Level | Who | Validation every 12 months |
|---|---|---|
| Level 1 | Stores, processes or transmits 300,000 or more Visa transactions a year | Attestation of Compliance by a Qualified Security Assessor; Visa can request the full Report on Compliance |
| Level 2 | Fewer than 300,000 Visa transactions a year | Attestation of Compliance for Self-Assessment Questionnaire D |
Visa's current compliance page says issuers and acquirers must ensure their service providers demonstrate PCI DSS compliance at least every 12 months. If you expect to pass 300,000 Visa transactions within a year or two, plan for the assessor-led route from the start, since changing level later means another round of work.
What falls inside PCI DSS scope
Scope covers every system that stores, processes or transmits cardholder data, plus systems connected to them or able to affect their security. In a gateway that usually means the vault, the payment page, the card connectors, key management and everything with network access to them.
The goal of a good design is a small scope. Tokenization keeps card numbers inside the vault, and network segmentation keeps tokens-only services out. A hosted payment page or embedded fields keep card data away from merchants' own servers, which also shrinks their scope.
How PCI DSS compliance for payment gateways changes your merchants' work
Your merchants have their own PCI DSS obligations, and the integration they choose decides how heavy those are. That makes your checkout design part of your sales pitch.
A merchant that sends shoppers to your hosted payment page never touches card numbers, so its questionnaire is short. A merchant whose own page collects card data and sends it host-to-host takes on much more, since its servers become part of the payment flow. Offering a hosted page and SDK fields lets most merchants stay on the lighter side.
How PCI compliance for payment gateways is assessed
A first assessment takes planning, and the yearly renewal is lighter once controls are in place. These are the usual stages.
- Define scope with a diagram of every system and data flow that touches card data.
- Run a gap assessment against all 12 requirements, often with the assessor's help.
- Fix the gaps and collect evidence, from policies to logs to configuration records.
- Have a Qualified Security Assessor test the controls and issue the Report on Compliance and Attestation of Compliance.
- Run external vulnerability scans every quarter through an Approved Scanning Vendor.
- Repeat the assessment every 12 months and keep evidence current in between.
Stage 3 takes the longest on a first assessment. Evidence that controls ran all year, not just on the day of the audit, is what assessors look for.
SaaS or self-hosted: who carries what
Where your gateway runs decides how much of the assessment is yours. The split on our platform shows the general pattern.
| SaaS | Your own cloud account or servers | |
|---|---|---|
| Platform software | Covered by our PCI DSS v4.0.1 Level 1 certification | Same software, certified on our side |
| Hosting environment | Ours, inside our certification | Yours, inside your scope |
| Your assessment | Your own processes and anything you connect | Your hosting environment as well, with our support during the audit |
| Independent check | We're listed in Visa's Global Registry of Service Providers | Your own validation |
On SaaS, most of the technical controls are ours to maintain. Self-hosted, you take on the environment, which is why banks with data residency rules budget for their own assessment.
Questions
What is PCI compliance for a payment gateway?
It's the gateway's proof that it meets PCI DSS, the card industry's security standard. A gateway validates as a service provider every 12 months, usually through an assessment by a Qualified Security Assessor.
Which PCI DSS version applies in 2026?
PCI DSS v4.0.1. Version 4.0 was retired on December 31, 2024, and the future-dated requirements of version 4 became effective on March 31, 2025.
Does using a hosted payment page make a merchant PCI compliant?
It doesn't remove the merchant's obligations, but it keeps card data off the merchant's servers, which makes its validation much lighter than with a host-to-host integration.
Do I need my own PCI DSS assessment if I use white label gateway software?
On SaaS, the vendor's certification covers the platform, and you validate your own processes. If you host the software yourself, your hosting environment needs its own assessment.