PCI Payment Gateway: Does It Make You Compliant?
Chargebacks, Fraud & Security

PCI-Compliant Payment Gateways: Does Yours Make You Compliant?

A PCI payment gateway doesn't make you compliant on its own. See which duties your integration type moves to the gateway and which stay with you.

Flat illustration of a laptop showing a padlock icon over a blue world map with connection lines to several continents

Photo: Pixabay

On this page 7 sections
  1. What a PCI-Compliant Payment Gateway Actually Certifies
  2. Shared Responsibility: What the Gateway Covers and What You Still Own
  3. Integration Type Decides Your PCI DSS Payment Gateway Scope
  4. One Gateway, Two Very Different Scopes: A Worked Example
  5. Is My Payment Gateway PCI Compliant? Check the Paperwork
  6. Duties That Stay With You Under Any Integration
  7. Red Flags That a Gateway Will Expand Your PCI Scope

Key takeaways

  • A gateway's Level 1 status covers the gateway's own systems. Your business validates its compliance separately, through your acquirer.
  • Most of your PCI scope depends on who serves the field where the customer types the card number. The gateway's badge does not decide it.
  • Ask for the gateway's Attestation of Compliance and a written responsibility matrix. A logo on a website proves nothing.
  • Keyed and recurring payments can pull you back into full scope when card numbers end up on sticky notes or in a rebilling spreadsheet.

No. A PCI payment gateway with Level 1 status has shown that its own systems meet the PCI Data Security Standard (PCI DSS). Your business still has to validate its own compliance with your acquiring bank. How much work that takes depends mostly on how your checkout and your billing process connect to the gateway. With a well-built integration, your side can shrink to a short questionnaire. A careless one can drag your whole office network into scope, even when the gateway behind it is flawless.

PCI DSS is not a federal law. The PCI Security Standards Council (PCI SSC) writes it, and the card networks enforce it through the merchant agreement you sign with your acquirer. Treat what follows as general information, and confirm your own obligations with your acquirer or a qualified PCI assessor.

What a PCI-Compliant Payment Gateway Actually Certifies

A gateway transmits and stores cardholder data for many merchants, so PCI DSS treats it as a service provider. The card networks sort service providers into levels, and Level 1 is the top tier. Reaching it typically involves an outside assessment of the gateway's systems rather than a self-assessment. Each network publishes its own level definitions, so check them directly if a vendor's claim sounds vague. The gateway summarizes its result in an Attestation of Compliance (AOC). An AOC is a signed document stating that the gateway met the standard as of a given date, for a named set of services.

That review covers the gateway's infrastructure, from its data centers to the controls on who can reach its card vault. Your checkout page sits outside it. So do your WordPress plugins and the laptop at the front desk, and nobody on the assessment team ever looked at either one.

Read "we're a PCI Level 1 gateway" as a statement about the vendor. It means one link in your payment chain has been audited. The links you control have not been.

Shared Responsibility: What the Gateway Covers and What You Still Own

PCI DSS expects merchants to keep track of every service provider that touches card data and to know which security requirements each provider handles. Providers, in turn, are expected to spell out that split for their customers. You'll usually see it as a responsibility matrix. That document lists each requirement and marks it as the gateway's job, your job, or shared.

On the gateway's side, the core job is the card vault. A well-run gateway stores card numbers securely and gives your system a token instead. A token is a stand-in value that can't be turned back into a card number anywhere outside the gateway. The gateway also encrypts traffic on its way to the card networks. Its own servers and employee access are its responsibility too, as is the response when something goes wrong on its side.

Your side starts where the customer meets the payment form. You have to secure every web page that loads or links to that form, along with the scripts and third-party tags running on it. If card numbers ever pass through your own computers or staff, those systems become yours to protect as well. You also handle the validation your acquirer asks for, usually through a Self-Assessment Questionnaire (SAQ). And you set the house rules, such as never taking a card number by email or chat.

Where the line between the two sides falls depends on your integration type. That is where most merchants misjudge their scope.

Integration Type Decides Your PCI DSS Payment Gateway Scope

One question settles most of it: who serves the field the customer types the card number into? When the gateway serves it, most of the burden stays with the gateway. When your server or your page code builds it, the burden comes back to you.

Integration typeWho serves the card fieldDoes card data reach your systems?Relative validation workloadWhat you still own
Hosted payment page (redirect)Gateway, on its own domainNoLightestThe page that sends shoppers to the gateway, and protecting that redirect from tampering
iFrame or gateway-hosted fieldsGateway, embedded in your pageNoLight, if your page meets the current eligibility criteriaAny script on the parent page that could interfere with the payment form
JavaScript or direct post with your own form fieldsYour pageNot your server, but your page controls the formModerate to heavyWeb server hardening and script controls, plus external scanning
Direct API (server-to-server)Your serverYesHeaviestClose to the full standard, across every connected system

Your acquirer decides which questionnaire applies, using eligibility criteria the PCI SSC publishes for each one. Those criteria change between versions of the standard. Read the current set rather than relying on a plugin's marketing page or a developer's memory.

The iFrame row needs a warning. Embedding the gateway's fields keeps the card number out of your hands, but a malicious script on your own page can still overlay or replace that form. PCI SSC guidance has tightened around exactly this risk. Our article on PCI DSS 4.0.1 payment page script rules covers what changed and what store owners now have to confirm.

Keyed and Recurring Payments Follow the Same Logic

Phone and mail orders keyed into a gateway's virtual terminal can qualify for a shorter questionnaire written for that setup. The idea behind its eligibility conditions is that the card number travels from the caller straight into the gateway's web page and lands nowhere else. Writing the number on a notepad first breaks that. Keying it on the PC that staff also use for email and web browsing exposes it to any malware that machine picks up. Check the current criteria before you assume you qualify.

Recurring billing works the same way. If the gateway stores the card and gives you a token for future charges, the card number never sits in your systems. If you keep full card numbers in a CRM or a spreadsheet so you can rebill each month, every system holding them comes into scope. The network rules for storing credentials are a separate subject, covered in our guide to saving customer cards on file.

One Gateway, Two Very Different Scopes: A Worked Example

This is an illustrative scenario, not a client story. Assume two businesses use the same Level 1 gateway with the same AOC.

Business A is a WooCommerce store. Its WooCommerce payment integration uses the gateway's hosted fields, so the card number goes from the shopper's browser straight to the gateway. Only tokens and the last four digits of each card end up in the store's database. On top of that, the owner reviews what loads on the checkout page and removes marketing tags that don't need to run there. This store is a strong candidate for the lightest questionnaire, as long as it meets the current eligibility criteria.

Business B is a five-person bookkeeping firm that charges clients a monthly retainer. Clients read their card numbers over the phone. A staff member writes each one on a sticky note and then types it into the virtual terminal on a shared office PC. To run next month's charge, the firm keeps full card numbers in a client spreadsheet. Every one of those touchpoints is now in scope, from the sticky notes to the spreadsheet, along with the shared PC and the network it sits on. That pushes the firm toward the longest questionnaire, and the gateway's Level 1 status does nothing to reduce it.

Business B can get most of the way to Business A's position without changing gateways. Staff key cards straight into the virtual terminal on a dedicated device and stop writing them down. Monthly charges move to the gateway's tokenized billing, and the card numbers in the spreadsheet are securely deleted. New clients receive a gateway-hosted invoice or payment page instead of being asked to read their card aloud. Both firms use the same vendor. The entire difference in scope comes from how each one handles card data.

Is My Payment Gateway PCI Compliant? Check the Paperwork

Logos and "PCI compliant" badges are marketing. To confirm a gateway's status, you need documents:

  1. Ask for the current AOC. Look at the date first, because an old attestation tells you little about today. Then confirm that the level matches what the vendor claims and that the listed services include the ones you actually use, such as the hosted page or the token vault.
  2. Ask for the responsibility matrix. If a gateway can't tell you in writing which requirements it covers and which fall to you, that is your answer.
  3. Look for the gateway on network lists. Some card networks, Visa among them, publish public lists of service providers that have validated compliance. Ask your gateway which lists it appears on. Then search the network's site for the exact legal entity you contract with, not only the brand name. A missing listing alone doesn't disqualify a vendor, but it is a reason to ask more questions.
  4. Confirm which integration you'll actually use. Many gateways offer hosted options and a raw API side by side. The AOC covers the gateway's side of each, but your scope depends on the one your developer or plugin implements.

When you compare payment gateways for your store, ask for these documents before you sign, not after your first questionnaire comes due.

Duties That Stay With You Under Any Integration

Validation comes first. Your acquirer tells you which questionnaire applies and where to submit it, and you repeat it on the schedule your acquirer sets. Some processors add a monthly fee for merchants who haven't validated. That fee is the processor's own pricing, not a card network rule, so look for it on your statement and in your merchant agreement.

Depending on your questionnaire, you may also need periodic external vulnerability scans from a scanning vendor approved by the PCI SSC. Your acquirer can tell you whether that applies to your setup and how often the scans must run.

Checkout scripts need ongoing attention. Keep an inventory of everything that loads on the payment page and remove anything that doesn't need to be there. Treat plugin and theme updates as security work, because a compromised plugin is a common way for card skimmers to reach a site.

Staff habits can undo good engineering. Put the rule in writing: no card numbers by email, text, chat or paper. Train every new hire on it. A single inbox full of emailed card numbers puts that inbox, and the computer reading it, in scope.

Finally, keep up with your vendors. Each time you do your own validation, collect an updated AOC from your gateway and from every other provider that touches card data, and file it with the responsibility matrix.

Red Flags That a Gateway Will Expand Your PCI Scope

  • Your developer says the integration needs card numbers to pass through your server, even though a hosted option exists.
  • A plugin offers to "save card details for manual processing" in your order database.
  • The vendor can't produce a current AOC, or the AOC it sends doesn't list the service you're buying.
  • Recurring billing would require you to store card numbers yourself because the gateway has no token vault.
  • Onboarding or support staff ask you to email card data for testing or troubleshooting.
  • Nobody can tell you which questionnaire your setup is expected to fall under.

Pull your gateway's AOC and responsibility matrix this week, then work out which integration type your checkout actually uses. Those two answers cover most of what your next questionnaire will ask. If you're choosing or replacing a gateway, request a free quote from MannyPay. Before you commit, ask the specialist who responds which integration options fit your platform.

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading