Timeline for PCI DSS 3.0 and card swipe terminals for our merchants
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 13, 2015 at 5:33 | vote | accept | Skelter | ||
| Sep 12, 2015 at 3:52 | answer | added | mostlyinformed | timeline score: 1 | |
| S Jul 13, 2015 at 20:43 | history | suggested | user59735 | CC BY-SA 3.0 |
corrected spelling, tag
|
| Jul 13, 2015 at 20:34 | review | Suggested edits | |||
| S Jul 13, 2015 at 20:43 | |||||
| Jul 9, 2015 at 17:31 | comment | added | JekwA | You're simply a service provider. You're responsible for ensuring any computer YOU control that stores, processes or transmits cardholder data is PCI compliant. So from the point the data hits your secure portal till you send it off to the processor you're responsible. They're responsible for the swiping and sending the data to your portal so THEY would need to manage all the inventory of the swipe devices and inspection and whatnot. | |
| Jun 9, 2015 at 16:47 | answer | added | AndyMac | timeline score: 1 | |
| Jun 9, 2015 at 6:04 | comment | added | Skelter | We're not the processor. We collect and transmit their transactions to a processor. | |
| Jun 9, 2015 at 2:26 | comment | added | gowenfawr | "Many are not PCI certified yet." I think you're already past the point of Trouble. Are you their processor? I believe you're responsible for collecting their SAQs. | |
| Jun 9, 2015 at 1:26 | review | First posts | |||
| Jun 9, 2015 at 3:10 | |||||
| Jun 9, 2015 at 1:25 | history | asked | Skelter | CC BY-SA 3.0 |