Timeline for Is storing CVV compliant with PCI standards?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2016 at 6:45 | vote | accept | András Gyömrey | ||
| Sep 29, 2015 at 19:17 | review | Late answers | |||
| Sep 29, 2015 at 20:56 | |||||
| Feb 4, 2015 at 1:19 | comment | added | Hamhot Ptonel | You can store it for however long the card brand allows you to. One year is not the rule (whether that's ideal or unideal for a particular merchant or service provider.) You'll have to ask card brands, issuers, and banks to know how long you're allowed to store it pre-authorization and what other requirements are in effect. The PCI DSS explicitly doesn't have an answer because the PCI DSS doesn't cover pre-authorization data. | |
| Feb 3, 2015 at 21:22 | comment | added | András Gyömrey | I understand, but this means that booking industry is pretty much unoriented in terms of safe methodologies. Like I said in the post, you can have a CVV stored for a whole year (in advance). And PCI DSS doesn't seem to have an answer for that. | |
| Feb 2, 2015 at 8:55 | history | answered | Hamhot Ptonel | CC BY-SA 3.0 |