MULTICHANNEL The PCI Minefield
By Patrick Juan, Director, Solutions Consultant, Ingenico Enterprise Retail
P
ayment Card Industry Security Standards Council (PCI SSC) requirements tends to get a bit complex and jargon-filled, so
it can be tricky for merchants to understand exactly what they need to do to ensure they are compliant. So, to break it down, the PCI defines a compliance framework for security that merchants must comply with, in order to be allowed to take card payments in their physical and digital stores. Without PCI compliance, merchants will not find an acquirer to work with, and could be fined by the card schemes indirectly through the acquirers. The level of compliance required by merchants depends on the total value of card transactions they process.
It’s essential that merchants look out for PCI compliance from their payment providers, and
FOR INCLUSION CALL THE CLASSIFIEDS TEAM ON 01271 866 112
Don’t miss a sale Use all stock across all channels
Multi-Channel Retail Software
Sanderson.com T: 0333 123 1400
www.directcommercemagazine.com | Direct Commerce Omni-Chanel small ad
86x65mm.indd 1 18/10/2018 10:27 E:
info@sanderson.com 11
there’s two primary standards that they should be aware of. These are PCI PIN Transaction Security (PCI PTS) for payment terminals and PCI Data Security Standard (PCI DSS) for payment gateways in store and online. Additionally, merchants must manage their payments assets adequately, ensuring that it doesn’t manage cardholder sensitive data such as the card number or CV2 numbers.
In order to do this, merchants should employ a PCI Point to Point Encryption (P2PE) solution (sorry, we can’t completely avoid jargon). P2PE means that the card data is encrypted at source on the PIN pad and stays encrypted until it reaches a PCI DSS environment, usually a PCI DSS compliant gateway. By using a compliant PCI P2PE solution, the merchant PCI compliance burden is significantly reduced. Continues overleaf >
EXPERT ROSTER
How can merchants reduce the burden of compliance?
EXPERTS ON CALL
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42