Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Payment Gateway Security?

Payment gateway security protects the component that carries a transaction from a checkout page to an acquirer, including the integration pattern a merchant chooses and the fraud controls around it.

Illustration for the cybersecurity term Payment Gateway Security
Home / Blog / Cybersecurity Terms / What Is Payment Gateway Security?
17 November 2026

What Is Payment Gateway Security?

What Is Payment Gateway Security?

A payment gateway sits between a merchant’s checkout and the acquiring bank. It takes the payment details, applies fraud rules, routes an authorisation request through the card scheme, handles the authentication challenge where one is required, and returns a result the merchant can act on. Payment gateway security covers the gateway itself, the way the merchant integrates with it, and the operational controls around the merchant’s account, because an attacker will happily take the easiest of the three.

The integration choice deserves more attention than it usually gets. It determines how much card data touches merchant systems, which in turn determines the breach impact and the assessment burden, and it is effectively permanent once the checkout is built.

Integration Patterns and What They Cost

PatternWhere the card number goesMerchant exposure
Hosted payment pageDirectly to the gateway on its own domainLowest; the merchant page never sees the number
Hosted fields in an iframeTo the gateway, from an isolated frameLow, provided the surrounding page is protected
Direct post or client-side APIFrom the browser to the gateway, bypassing the serverModerate; the merchant page can be modified to intercept entry
Server-to-serverThrough the merchant’s own systemsHighest; full cardholder data environment

Note that every pattern except a fully hosted page leaves the merchant responsible for the integrity of the page that collects or frames the details, which is why PCI DSS version 4 introduced requirements to inventory and monitor the scripts loaded into a payment page, applicable from 31 March 2025. That change exists because of Magecart-style skimming, where the gateway performs perfectly and the merchant still loses every card.

How Gateways and Merchant Accounts Are Attacked

Controls Worth Specifying

  1. Verify every gateway response and webhook by signature, server side, and reconcile against the gateway’s own records before fulfilment.
  2. Rate limit and risk-score the payment endpoint specifically, with velocity limits per card, per device, and per IP range to stop card testing.
  3. Keep secret keys out of client code and repositories, rotate them on a schedule, and use separate keys per environment.
  4. Protect merchant portal access with multi-factor authentication, least privilege, and alerting on changes to settlement details or fraud configuration.
  5. Apply a content security policy and subresource integrity to the checkout, and keep an inventory of every script it loads.
  6. Use 3-D Secure 2 properly, passing the full data set so that the issuer can make a risk decision rather than challenging everyone.
  7. Feed gateway events into the same fraud scoring pipeline used elsewhere in the business.

Regulation in the UK and Turkey

UK gateways and their merchants operate under the Payment Services Regulations 2017, with strong customer authentication enforced for e-commerce since March 2022 and the technical standards maintained by the FCA. PCI DSS applies contractually through the acquirer, and a card data breach is also a personal data breach reportable to the Information Commissioner’s Office. Since October 2024 the Payment Systems Regulator’s reimbursement regime for authorised push payment fraud has changed the economics of account-to-account payment acceptance.

In Turkey, payment and electronic money institutions are licensed and supervised by the Central Bank of the Republic of Turkey under its 2021 regulation, which sets detailed requirements for information systems, authentication, and outsourcing, and the sector works to local card scheme rules alongside PCI DSS. A UK merchant selling into Turkey will usually need a local acquiring relationship, and the gateway integration and settlement arrangements will not simply mirror the UK ones.

Where a checkout and its gateway integration need testing against real abuse rather than against the integration guide, our web application security services cover payment flows end to end.

FAQ – Frequently Asked Questions

What Is Card Testing and Why Does It Target Us?

Card testing is the automated submission of many small authorisations to find which stolen card numbers still work. Attackers choose merchants with an unprotected payment endpoint, low-value items, and no velocity limits, regardless of brand or size. The cost lands on the merchant through authorisation fees, scheme fines, and a damaged approval ratio, so rate limiting the endpoint is a commercial control as much as a security one.

Is a Hosted Payment Page Always the Safest Option?

It gives the lowest exposure, because the card number never touches merchant systems and the page is served and maintained by the provider. The trade-off is checkout experience and branding, which is why hosted fields in an iframe are the common compromise. Either way the merchant still owns the integrity of the page that redirects or frames, and that is where skimming attacks land.

Do We Need to Verify Webhooks If They Come from the Gateway?

Yes, always. A webhook endpoint is a public URL and anyone can post to it. Verify the signature using the shared secret, check the event identifier against the gateway’s own records before acting, and treat a payment-confirmed callback as a prompt to query the gateway rather than as proof. Orders fulfilled on unverified callbacks are a long-standing source of loss.

Does 3-D Secure Shift Liability to the Issuer?

For authenticated transactions, generally yes, under the card scheme rules, which is one reason merchants adopt it beyond the regulatory requirement. The protection applies to fraudulent disputes rather than to every chargeback reason, and it depends on the authentication being completed properly. Exemptions taken to reduce friction also return liability to the merchant, so the configuration choice has a direct financial consequence.

Related Terms

You May Be Interested In These

What Is LoRaWAN Security?

Cybersecurity Terms

17 November 2026

What Is LoRaWAN Security?

Read More
What Is Steganography?

Cybersecurity Terms

17 November 2026

What Is Steganography?

Read More
What Is CMMC?

Cybersecurity Terms

17 November 2026

What Is CMMC?

Read More