|
Elizabeth
|
February 21, 2017 at 6:41 am
Does Auth SIM require the site to be PCI compliant?
|
|
Tony
|
February 21, 2017 at 7:39 am
Hi Dorian,
Any site that accepts payments must be PCI compliant, the difference is the level of compliance required.
Auth.net SIM is offsite, it directs the users to auth.net’s servers to make a payment and then back to your site, so for Auth.net SIM I believe you’ll need SAQ-A which is the lowest requirement.
|
|
Elizabeth
|
February 21, 2017 at 7:42 am
Has anyone else here had to go through this? Does this happen a lot? We have 16 sites and only one has had to go through this.
All we have is WordPress, EE4 and a few other plugins. We have SSL certs. What else could we possibly have to do?
|
|
Elizabeth
|
February 21, 2017 at 7:45 am
One of the locations is trying to switch to Wells Fargo. They sent back a 59 page report from TrustWave on how the site failed PCI compliance.
|
|
Tony
|
February 21, 2017 at 8:50 am
Has anyone else here had to go through this? Does this happen a lot?
I’m not sure what you mean? Plenty of users go through PCI compliance, it’s a requirement set by payment providers.
All we have is WordPress, EE4 and a few other plugins. We have SSL certs. What else could we possibly have to do?
Most of the PCI compliance is server related, what you need to do is depends entirely on your setup.
One of the locations is trying to switch to Wells Fargo. They sent back a 59 page report from TrustWave on how the site failed PCI compliance.
I have no idea what you have failed on so can’t really comment.
As mentioned most of the PCI requirements are server setup and your own internal procedures on card/data handling etc.
|
