Rob Crutchington discussing PCI compliance for card-accepting merchants - Global Banking & Finance Review
Rob Crutchington, Director of Encoded, addresses PCI compliance challenges faced by card-accepting merchants in protecting customer data from fraud and security breaches.
Business

PCI Compliance – What every card-accepting merchant should know

Published by Gbaf News

Posted on April 9, 2013

5 min read

· Last updated: October 31, 2023

Add as preferred source on Google

By Rob Crutchington – Director of Encoded

The Importance of PCI Compliance

Rob-CrutchingtonIt is fair to say that most card-accepting merchants understand the importance of protecting customer data from fraud and cybercrime. However, it might be news to many that in the event of a security breach they will be the ones fined. The buck stops with the merchant. Costs and expenses can quickly add up with payment network fines and assessments, forensic fees associated with a compliance audit of the merchant’s business environment and legal fees. Not to mention the damage to reputation and lost sales.

Consumer Perceptions of Card Security Risks

A recent report* based on a survey of 2,035 online consumers stated that nearly half (45%) of respondents saw contact centres in particular as the biggest security risk and the starting point for fraud. Findings also showed that many millions of consumers have been stopped from making purchases over the telephone when interacting with a call centre.

But surely the Payment Card Industry Data Security Standard (PCI DSS) takes care of all of this? When Visa®, MasterCard®, JBC®, Discover® and American Express® created a standard made up of 12 requirements designed to secure business systems that store, process or transmit card holder data it was meant to protect consumers and merchants against security breaches. However, what many organisations with call centres do not appreciate is that because PCI DSS covers the entire trading environment, all third-party partners and vendors that handle card data must also comply before full PCI compliance is achieved.

Understanding Third-Party PCI Compliance

Visa Europe Merchant Agents List
So which third-party partners and vendors are fully PCI DSS compliant? Payment schemes are building lists of registered Third Party Vendors that can demonstrate adequate levels of data security and acceptable business practices. For example VISA has its Visa Europe Merchant Agents List http://www.visamerchantagentslist.com/ and merchant services organisations such as Elavon are insisting that only organisations which appear on this list are used by customers. This means any company involved in accepting transactions, interactive voice response (IVR) payments, internet payment gateways and any other service or product that is directly or indirectly involved in data transactions must register and appear on the list. Contact-centres typically use multiple vendors for their technology so it is becoming increasingly important for management to understand just who does what in the process and who needs to be PCI compliant to avoid fines and lawsuits in the event of the unthinkable happening and customer card data being stolen.

Different Levels of Merchant Agent Validation

Not all PCI third-parties are created equal
The Visa Europe Merchant Agents list has two levels of organisations that provide services to merchants. These two levels have very different validation procedures. To achieve the top level of compliance, Level 1, an Attestation of Compliance (AOC) is needed and this level only applies to organisations that store, process and/or transmit more than 300,000 Visa transactions per year.

To achieve Level 1 status an Attestation of Compliance must be completed by an independent Qualified Security Assessor (QSA) along with a Report on Compliance. QSAs cost money and have very exacting standards. The high cost of going through full PCI DSS accreditation with an external QSA is leading to some vendors claiming to be compliant when in fact they have not been through the whole process and therefore do not have Level 1 status. This is putting merchants at risk.

For Level 2 registration organisations do not require an onsite security assessment by a QSA and are able to submit an annual self-assessment questionnaire including the Attestation of Compliance without reference to a QSA. Level 2 applies to smaller providers involved with less than 300,000 Visa transactions annually.

Increasing Scrutiny by Payment Providers

As Matthew Tyler, CEO of Blackfoot explained, “Payment schemes such as Visa and merchant service providers like Elavon are getting tough on organisations taking card payments. Many merchants don’t even realise they will be ones fined in the event of a data breach as they believe their bank or 3rd party supplier will be accountable. Some acquirers are even threatening to terminate Merchant Service Agreements if merchants fail to work with third-parties that appear on the Visa list. Organisations with call centres are seen as particularly vulnerable and should do everything in their power to work with only Level 1 vendors such as Encoded who have gone through extensive measures and inspections to achieve PCI DSS compliance.”

As recent research shows card security is important to consumers and they are becoming increasingly aware of both the technology and standards around payments. For call centres to build trust and confidence only the best technology from third-parties with Level 1 Visa clearance is good enough for customers. It can take years to rebuild a reputation after high profile data breaches such as those at Sony, Lush and the parent company of TK Maxx but it only takes a few minutes to check whether the vendor you are working with appears on the Visa Europe Merchant Agents list, has achieved full PCI DSS compliance and Level 1 status.

*Sabio and Avaya commissioned Davies Hickman Partners, an independent research consultancy, to complete a nationally representative survey (excluding NI) of 2,035 online consumers in January 2013.

 

 

 

Key Takeaways

  • Merchants are ultimately liable for PCI DSS compliance breaches even when using third-party vendors.
  • All third‑party providers (call centres, gateways, etc.) must maintain PCI DSS compliance and provide evidence such as AOC or SAQ.
  • Visa maintains registries like the Global Registry of Service Providers, and merchants should use listed compliant agents.
  • PCI DSS 4.0/4.0.1 increased scope and operational burdens for contact centres, making tokenization or out‑of‑scope methods more appealing.

References

Frequently Asked Questions

Who is ultimately liable for PCI DSS non‑compliance when third‑party processors are involved?
The merchant remains liable for fines and penalties, even if the breach or non‑compliance occurs via a third‑party vendor, as they bear responsibility for ensuring compliance across their entire environment.
What evidence must third‑party service providers supply to demonstrate PCI DSS compliance?
They must provide documentation such as an Attestation of Compliance (AOC) or a Self‑Assessment Questionnaire (SAQ), clearly indicating which PCI DSS requirements they cover.
How can merchants verify that third‑party agents are PCI DSS compliant?
Merchants should use service providers listed on registries like Visa’s Global Registry of Service Providers and require proof of current validation (AOC or SAQ) as part of due diligence.
What changed under PCI DSS version 4.0/4.0.1 for contact centres?
PCI DSS 4.0/4.0.1 tightened controls: pausing call recordings is no longer sufficient, scope has expanded dramatically, and many contact centres now opt to route card data entirely out of their environment to reduce compliance burden.

Tags

Related Articles

More from Business

Explore more articles in the Business category