Talk:Card security code: Difference between revisions

Revision as of 23:10, 3 August 2007

Revision as of 14:18, 4 August 2007

Line 40:

== Retention is possible ==

I'm not sure how to phrase this in the article, but since the CVV2 can be stored prior to the completion of a transaction, in the case of a time-delayed transaction this storage period may in fact be very lengthy. I am currently working with a client that requires up to six months between collection and charging, and for technical reasons verification of the card is not possible at time of collection. I realize this sounds stupid, but it is allowed (though discouraged) in the specs. I'm not sure if this should be listed as a "drawback," since it seems to be a problem with a particular system's business requirements rather than the number itself. But that could be arguable about most of the drawbacks, so I'm not sure.

[[User:12.205.149.45|12.205.149.45]] 22:54, 3 August 2007 (UTC)

:Encryption is the way to go. Max 7 day period between decryption and deletion of the encrypted CVV2...<span style="border:1px solid lime;color:green;">Gaimhreadhan ^{<font color="brown"><small>(kiwiexile at DMOZ) </small></font>}[[User_talk:Gaimhreadhan|<font style="color:green;background:lime;">talk</font>]]</span> • 23:10, 3 August 2007 (UTC)