Secure Payment Gateway: What It Covers and the Security Work That's Yours
A secure payment gateway handles PCI, tokenization and fraud filters, but your checkout scripts and staff habits stay yours. See what to check and ask.

Photo: Pixabay
On this page 6 sections
- What a PCI Compliant Payment Gateway Has to Prove
- Your Integration Method Decides How Much PCI Lands on You
- Payment Gateway Tokenization and Who Owns the Card Vault
- Fraud Filters a Secure Payment Gateway Should Give You
- The PCI Work That Stays With You
- Seven Questions to Ask a Payment Gateway Before You Sign
Key takeaways
- Ask for the gateway's Attestation of Compliance for Service Providers. The PCI Council does not recognize a "certificate of compliance" as proof of validation.
- If your checkout embeds the gateway's form in an iframe, SAQ A now requires you to confirm that scripts on your site can't be used to attack your e-commerce system. If you redirect shoppers to the gateway's hosted page, that criterion doesn't apply.
- Since 2025, Visa's VAMP flags a merchant once card-testing attempts reach 20% of its authorizations and 300,000 in a month. A single weekend attack can push a small store past both thresholds.
- Before you store cards on a gateway, get its card-vault transfer policy in writing. Gateway tokens generally don't work with any other provider.
A secure payment gateway does four things. It proves its own PCI DSS compliance with a signed Attestation of Compliance, and it replaces stored card numbers with tokens. It keeps card data off your servers, and it gives you fraud controls you can tune. It does not make your business compliant. Your checkout page, your staff's phone habits and your yearly validation stay with you. Since March 31, 2025, the scripts running on your checkout page are on that list too.
The split matters most for businesses that rarely see a physical card: online stores, subscription sites, medical offices taking balances by phone, firms that bill by invoice. For the mechanics of authorization, start with how a payment gateway gets online payments approved.
What a PCI Compliant Payment Gateway Has to Prove
PCI DSS (the Payment Card Industry Data Security Standard) is not a federal law. The PCI Security Standards Council writes it, and the card brands require it through their network rules. Your merchant agreement with your processor and acquiring bank makes it a contractual obligation for you. The current version is v4.0.1, which replaced v4.0 on December 31, 2024.
A gateway that calls itself PCI compliant should hand you proof. The PCI Council's third-party security assurance guidance points merchants to the service provider's Attestation of Compliance, or AOC. Two details trip people up. The document should be the AOC for Service Providers, because an AOC for Merchants says nothing about the services a vendor sells you. And a "certificate of compliance" with a logo on it is not something the Council recognizes as validation. Check the date as well. If the AOC has expired, ask the gateway why.
That AOC covers the gateway's systems and staff, not yours. Your acquirer will still ask you to validate your own compliance, usually with a self-assessment questionnaire (SAQ) each year. If a "PCI non-compliance fee" shows up on your statement, it comes from your processor, not from Visa or Mastercard. It is a pricing decision, and it usually stops once you file. The terms are in your own agreement.
Your Integration Method Decides How Much PCI Lands on You
Any reputable gateway encrypts card data in transit. The bigger decision is how card data reaches the gateway, because that sets how much of your setup falls into PCI scope.
| Integration method | Who serves the card form | Does card data touch your server? | Your typical PCI burden |
|---|---|---|---|
| Redirect to a hosted payment page or payment link | The gateway | No | Lightest |
| Hosted fields (iframe in your checkout) | Gateway serves the fields; you serve the page around them | No | Light, but you must vouch for your page's scripts |
| Direct post or JavaScript form | You | No, but your web server delivers the form | Heavier; your web server is in scope |
| Server-side API | You | Yes | Heaviest; the longest questionnaire |
Your acquirer decides which questionnaire you file based on how you actually integrate, so ask before you build. Our comparison of hosted, plugin and API gateway integration covers the build side.
The 2025 Rule Change for Iframe Checkouts
Hosted fields don't make your checkout page untouchable. If an attacker can change your page, they can swap the gateway's iframe for a lookalike form and collect card numbers before the gateway ever sees them. This is digital skimming, sometimes called Magecart, and PCI DSS v4.0 added two requirements aimed at it. Requirement 6.4.3 asks for an authorized, integrity-checked inventory of every script on the payment page. Requirement 11.6.1 asks for a change- and tamper-detection mechanism on that page, checked at least weekly. Both started as "future-dated" requirements and became mandatory on March 31, 2025.
Most merchants have the next part wrong. In January 2025, the Council removed 6.4.3 and 11.6.1 from SAQ A, the shortest questionnaire, effective March 31, 2025. In their place it added an eligibility criterion: you must confirm your site is not susceptible to attacks from scripts that could affect your e-commerce system.
According to PCI SSC FAQ 1588, as summarized by assessor SecureTrust, that criterion applies to merchants who embed the gateway's form in an iframe. Merchants who redirect shoppers to the gateway's hosted page don't need it, and neither do merchants who fully outsource their website to a compliant provider. So the questionnaire got shorter, but a merchant using an iframe still has to stand behind every script on the page.
In practice, keep checkout lean. Pull chat widgets, ad pixels and tag-manager containers off payment pages. Patch your cart and plugins on a schedule, and know exactly who can edit checkout templates. Self-hosted carts such as WooCommerce and Magento put that patching on you or your developer. Hosted platforms such as Shopify run the checkout page themselves.
Payment Gateway Tokenization and Who Owns the Card Vault
Tokenization replaces the card number with a random stand-in value. The real number sits in the gateway's vault. Your system keeps only the token, which is worthless to a thief outside that gateway. That is how a membership site bills monthly, or a dental office runs a payment plan, without anyone on staff holding a card number.
Gateway tokens are issued by the gateway and generally work only there. Network tokens come from the card brands' own token services and are tied to the card account, so they can survive a card reissue. Many gateways support both and pair them with an account updater that keeps saved cards current. That pairing matters if your revenue depends on recurring billing.
Most merchants never ask about portability. Gateway tokens generally don't work anywhere else, so if you switch, the old gateway usually has to send the underlying card data to the new provider's vault through a PCI compliant transfer. Some gateways treat that as routine, while others charge for it or move slowly. Get the policy in writing. To see how tokens shrink your audit, read how tokenization cuts PCI scope. For where each technology applies, see tokenization vs. encryption for merchants.
Fraud Filters a Secure Payment Gateway Should Give You
PCI protects card data. Fraud filters decide which transactions get through. Most gateways offer some version of these:
- Velocity rules cap how many attempts one card or one IP address can make in a set window.
- AVS (Address Verification Service) compares the numeric parts of the billing street address and ZIP code with the issuer's records. It works best on U.S.-issued cards, and many foreign issuers return no usable result.
- CVV checks confirm the security code printed on the card. PCI DSS Requirement 3.3.1 bars merchants from keeping that code after authorization, even encrypted, so it should never be written down or saved.
- IP and geography rules flag orders routed through proxies or placed from a country that doesn't match the billing address.
- Amount rules hold unusually large orders for review or block suspiciously small ones.
The issuing bank can approve a sale even when AVS or CVV fails. Your gateway rule decides what happens next. On many gateways a filtered sale is authorized first and then voided, so the customer may see a pending charge for a few days. Word your decline message with that in mind. Our breakdown of AVS and CVV mismatches covers which combinations are worth accepting. Online sellers should also read Discover's new card verification rule explained.
Card Testing Now Has a Visa Ratio Attached
In card testing, a bot runs stolen or generated card numbers through a checkout or donation form, usually for small amounts, to learn which cards are live. Visa calls it enumeration, and its 2025 overhaul of the Visa Acquirer Monitoring Program (VAMP) measures it directly. This is a network rule, and Visa applies it through your acquirer. The enumeration ratio is enumerated authorization attempts (approved plus declined) divided by all authorization attempts. A merchant is flagged when that ratio reaches 20% and the enumerated count reaches 300,000 in a month. Merchants over the line must put risk controls in place.
Illustrative example. Assume an online store sends 12,000 genuine authorization attempts to Visa in a month. Over one weekend, a bot with no velocity limit in its way pushes 310,000 attempts that Visa identifies as enumeration. The ratio is 310,000 ÷ 322,000 = 96.3%, and the count clears 300,000, so the store meets both thresholds. Now assume the same attack hits a checkout with a per-IP velocity limit and a CAPTCHA, and only 2,000 bot attempts reach authorization. The ratio is 2,000 ÷ 14,000 = 14.3%, and the count is nowhere near 300,000. Same attacker, very different month.
The count floor doesn't protect small merchants, because a bot can generate 300,000 attempts in a weekend. Each attempt may also carry a per-authorization fee, so check whether declined transactions cost you money under your pricing. For the dispute side of Visa's monitoring, see what triggers Visa monitoring program enrollment.
Prevention is cheap if you set it up before the attack. Put a per-IP velocity limit and a CAPTCHA on checkout and donation pages, and require CVV and ZIP on every online sale. If your products allow it, set a minimum order amount, since testers favor tiny charges. For higher-risk orders, 3-D Secure authentication asks the issuer to verify the cardholder. It can move fraud liability off the merchant for authenticated sales. Confirm how that works on your account.
The PCI Work That Stays With You
Card-not-present sales carry more fraud risk and different rules than tapped or dipped cards, as our comparison of card-present vs. card-not-present payments explains. What's left on your plate depends on how you take them.
Online Stores and Subscription Sites
File your SAQ each year and run any vulnerability scans your acquirer requires. Treat checkout like a cash drawer, where every change is deliberate and traceable to one person. Subscription businesses also need to protect customer logins, because a stolen account with a saved card is a ready-made fraud tool. Read up on account takeover fraud if you store cards.
Phone and Keyed Payments at Medical, Dental and Professional Offices
When staff type card numbers into a browser-based virtual terminal, that workstation becomes part of your card environment. Keep it patched and limit who uses it. Card numbers never belong in patient charts, client files or on scrap paper. Call recordings need the same care. If you keep a recording of a caller reading out the security code, you are storing sensitive authentication data, which Requirement 3.3.1 prohibits. Pause recording during card capture. Keying into a standalone terminal or PIN pad keeps the PC out of the card flow entirely.
Professional firms should invoice with hosted payment links instead of asking clients to email card numbers. If a client emails one anyway, run the payment through your secure channel. Then delete the email from every folder, including sent and trash.
Medical and dental offices also have HIPAA obligations, which come from federal law, not from PCI. A gateway's PCI attestation says nothing about HIPAA. This is general information, so confirm your obligations with a qualified compliance professional.
Your Gateway Login Is a Target, Too
Anyone with your gateway credentials can issue refunds to their own cards. Turn on two-factor authentication and give each employee a separate login. Limit refund permissions to the people who need them, and remove access the day someone leaves.
Seven Questions to Ask a Payment Gateway Before You Sign
- Can you send your current Attestation of Compliance for Service Providers, and when does it expire?
- Which integration methods work with my cart or software, and which questionnaire would my setup likely fall under?
- If I embed your hosted fields, what do you provide to help me confirm my page isn't susceptible to script attacks?
- If I leave, will you transfer my stored card data to a new provider, and what does that cost?
- Do you support network tokens and account updater for recurring billing?
- Which fraud filters are included and which cost extra? Are filtered sales declined outright or authorized and then voided?
- Does the merchant login support two-factor authentication and per-user permissions?
MannyPay sets merchants up on payment gateways including Authorize.net and NMI and connects them to carts like Shopify and WooCommerce. For a comparison that also weighs fees and support, read how to choose a payment gateway provider.
This week, log in to your gateway and confirm that velocity limits and two-factor authentication are on. Then list every script that loads on your checkout page and ask your processor which SAQ you're expected to file. If the answers don't match how you take payments, request a free quote and a MannyPay specialist will respond within one business day.
Sources
- PCI Security Standards Council: PCI Data Storage Do's and Don'ts
- PCI Security Standards Council: Third-Party Security Assurance Information Supplement
- Visa Acquirer Monitoring Program Fact Sheet (2025)
- Trust Payments: VAMP Merchant Guidance
- Solidgate: Visa Monitoring Programs
- SecureTrust: PCI DSS v4.0.1 Requirements, Key Updates
- HALOCK: PCI SSC Updates SAQ A
- Compyl: PCI DSS 4.0.1 Compliance Guide
- VikingCloud: PCI Compliance for Third-Party Service Providers and Merchants
- Paytia: Sensitive Authentication Data Under PCI DSS
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.


