![]() ![]() ![]() |
|
1080p: I heard all the CC data was encrypted with AES256, still...
1080p: I heard all the CC data was encrypted with AES256, still...
throbb:1080p: I heard all the CC data was encrypted with AES256, still...
the earth will be swallowed by the sun before they crack it.
codyc1515:
It is in fact two-factor in most cases, you have 1) the card and 2) the pin or 3) the CVC. To combat the real problem what we need is to have the CVC be dynamic rather than static, like, the CVC could be a screen on the card just like the bank tokens and the CVC would only be valid once.
SaltyNZ:
There is, and most NZ retailers are picking it up over the next 12 months or so. Basically, whenever the card issuers detect an unusual transaction online they will redirect you to a secondary authentication/verification page to do further checking before allowing you to continue. If the purchase is within your normal patterns, it stays out of the way. But as soon as a red flag is raised, it kicks in.
National Bank are great; I bought some clothes for the kids in San Francisco while I was there. Within 30s of the transaction, they called me and asked me if I was overseas, where I was, and what I had just bought. Having verified the transaction was legit, they asked how long I expected to stay, and the security system was pacified for a week. It was outstanding.
Kyanar:
Wouldn't work. Technically, the CVC is not actually required to process a transaction - the only requirement is that if it is provided, it must be correct. You don't see this buying from most NZ merchants as all the NZ processors require it, but overseas processors (especially the ones that specialise in "high risk") do not necessarily. So your solution, though a good start, still wouldn't work.
|
![]() ![]() ![]() |