According to Rob Crutchington at automated card payment solutions firm Encoded, at a time when the security of sharing personal details is of particular concern every contact centre should have a PCI DSS Compliance Programme in place. He cites five reasons why.
With payment card fraud continuing to rise and data theft constantly in the news, just look at all the recent cyber attacks, non-PCI DSS compliant contact centres could be risking more than just a fine.
1. News travels fast
Survey findings from the Contact Babel, The UK Contact Centre Decision-Maker’s Guide 2015, worryingly revealed that almost a third of medium sized organisations have no PCI DSS compliance programme in place. With several versions of the standard now available via SAQ (Self Assessment Questionnaire) there is little argument as to why a programme shouldn’t be at least road mapped.
In the age of social media, where good news travels fast and bad news even faster can a brand afford for clients’ card data to be lost with the resulting PR backlash?
2. The buck stops with the merchant
Delivering a good customer experience is about more than swift call response times. Paying for goods and services remotely is the norm for consumers and they expect their personal card account information to be kept safe. Every contact centre that accepts credit and debit card payments over the telephone is responsible for safeguarding their customer’s information and can be held liable for security compromises.
The Payment Card Industry Data Security Standard (PCI DSS) is intended to protect cardholder data wherever it resides and failure to comply with PCI DSS can result in hefty fines, not to mention the damage to reputation and lost sales. By complying with PCI DSS, merchants and service providers meet their obligations to the payment eco-system and build a culture of security that benefits everyone.
3. PCI DSS Compliance is not a one off exercise
PCI DSS is a change in mind-set, a change in attitude towards the handling of card data. It’s not like other industry accreditations where organisations can prepare the night before an audit and scrape a pass. It is the implementation of security procedures that will underpin the company’s behaviour when dealing with payments as well as how networks are designed, plus how access is granted and logged.
4. Awareness is increasing
PCI DSS was originally the brainchild of the world’s five largest payment card providers VISA, MasterCard, American Express, Discover and JCB International. Today, it is a global framework that provides guidance on how to process, store and transmit information about payment cards and their owners, with the aim of reducing the incidence of card fraud and promoting best practice in information security.
In the event of a loss of data or cards being used fraudulently, fines are passed down the chain from VISA and MasterCard at the top to the merchant/retailer at the bottom. The consumer doesn’t suffer financially as measures are in place and assurances given to prevent this happening. However, if something goes wrong, consumer brand loyalty can quickly fade.
Customers transact with an organisation because they feel confident that their payment cards will not be compromised, their personal details are secure and their identities cannot be stolen.
In the event of a security breach individuals will be inconvenienced and could suffer emotional distress at the thought of their details being stolen and used fraudulently. This could lead to a reduction in customer confidence in both the method of payment and the retailer who caused the problem. Reactive contact centres could find themselves quickly playing catch up as their customers vote with their feet.
5. Becoming and remaining PCI DSS compliant
Every contact centre that accepts credit and debit card payments over the telephone needs to be PCI DSS compliant. However, what many contact centres don’t realise is that PCI DSS covers the entire trading environment, meaning all third-party partners and vendors that handle card data on their behalf or supply services where card data is transmitted, must also comply before full PCI DSS compliance is achieved.
The latest version of PCI DSS introduced a new requirement compelling service providers to supply a ‘Responsibility Matrix’ which defines who is responsible for each of the 300+ PCI controls; namely the client, the supplier or both. It is worth stating at this point that PCI is not intended to trip up organisations or waste time; it is intended to secure cardholder data. Achieving PCI DSS compliance increases trust between an organisation and its partners and suppliers and boosts customer confidence.
The best way to minimise future costs as the standard evolves is to take good advice in the first place.
Ed Says… Some interesting points made here not least of which is the assertion made elsewhere by Encoded that ‘there is no such thing as a PCI DSS compliant software solution’.