Skip to content
Gambling Dictionary

PCI DSS

PCI DSS is a set of security standards created by the major card networks to protect cardholder data wherever it is stored, processed or transmitted. In iGaming, any operator or provider handling card payments is generally expected to meet its requirements, which cover areas such as secure networks, access control, encryption and ongoing monitoring.

PCI DSS, the Payment Card Industry Data Security Standard, is a security framework developed by the major payment card brands to safeguard cardholder data. Its aim is to reduce card fraud and data breaches by setting baseline controls for everyone who stores, processes, or transmits that data.

Rather than a law, PCI DSS is a contractual standard enforced through the payment ecosystem. Organisations that handle card payments are generally required to comply as a condition of accepting cards, with the level of validation scaling to how much card data they handle.

At a high level, the standard addresses areas such as building and maintaining secure networks, protecting stored cardholder data, encrypting data in transit, restricting access on a need-to-know basis, monitoring and testing systems, and maintaining a security policy. The intent is defence in depth around card information.

A practical example in gambling: an operator that stores card details must keep that data in a protected environment, limit which staff and systems can reach it, and log access. Many operators reduce their burden by using a compliant payment service provider so that raw card data never touches the operator’s own systems.

A common misconception is that compliance is a one-off certificate. In practice it reflects an ongoing state, and security must be maintained continuously; being validated at one point does not guarantee a system stays secure or compliant afterwards. Another misconception is that PCI DSS is a government regulation, when it is industry-driven.

  • It applies to card data specifically, not every type of payment.
  • Using a compliant provider can shrink, but not always eliminate, an operator’s own obligations.
  • Controls include encryption, access restriction, and monitoring.

The precise requirements, validation levels, and how they apply depend on transaction volumes, the services used, and the standard’s current version, as well as the jurisdiction. Operators should treat specifics as matters to confirm with qualified assessors and payment partners rather than assume.