Re:Why blurring sensitive information is a bad idea
by nodata on Thursday November 25, 2010 @03:52AM
(#1939758)
But that's for debit cards - I think most banks include the account number in a debit card number. You would still need the CCV number from the back of the card for the attack to work.
[ Parent
| on HN ]
Re:Why blurring sensitive information is a bad idea
by InclinedPlane on Thursday November 25, 2010 @04:26AM
(#1939812)
I haven't noticed any other bank which had the same practice.
Also, not all online merchants use CCV. Also consider the risk of creating fake physical CCs, no address or CCV necessary.
Re:Why blurring sensitive information is a bad idea
by Cushman on Thursday November 25, 2010 @06:38AM
(#1939991)
Just checked— my credit union debit card number includes my account number.
Re:Why blurring sensitive information is a bad idea
by hboon on Thursday November 25, 2010 @04:17AM
(#1939798)
CCVs aren't always required for transactions.
Re:Why blurring sensitive information is a bad idea
by lwhi on Thursday November 25, 2010 @06:35AM
(#1939985)
CCV proves the cardholder was present at the time of the transaction. Online merchants are never allowed to store CCV numbers.
Re:Why blurring sensitive information is a bad idea
by dedward on Thursday November 25, 2010 @10:03AM
(#1940344)
edit: CCV proves that you at one time had access to the CCV number.
Online merchants are supposed to comply with PCI-DSS - not store your CCV ever, never transmit your number unencrypted, never store cardholder information unencrypted, plus tons of management controls and audit controls over the same.
In practice, let's just say lazy programming is everywhere. I've seen many people who handle online transactions and violate PCI-DSS to some degree, including storing CCV numbers.