0

Technically, according to PCI SSC you can hold onto CVV and other sensitive authentication data until authorisation has occurred. In other words the restriction on storing sensitive authentication data applies to post authentication/processing storage.
Is it a requirement that the CVV be encrypted prior to authorisation?

3

The requirement is to protect the data appropriately. Pre-auth, you are unlikely to have the CVV on disk (it should just be in RAM) but if you do, then yes you should encrypt, and then delete afterwards, so your assumption that "the restriction on storing sensitive authentication data applies to post authentication/processing storage" is incorrect.

  • The only reason i can think of that a CVV would ever need to be stored on disk would be in a "store and forward" scenario, where the processor is not currently available to handle the transaction. – Bobson Jul 25 '16 at 19:17
  • Agreed. There may be others, but I'm not sure what they would be. – Rory Alsop Jul 25 '16 at 22:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.