| 12:58 pm on Mar 12, 2012 (gmt 0)|
i thought it was a severe breach of terms and conditions to store security numbers.
in which case surely these guys should be sued into bankruptcy.
| 4:05 pm on Mar 12, 2012 (gmt 0)|
And in plain text no less. LOL . . . "Nothing will ever happen. You geeks are crazy, the sky is NOT falling, now shut up and get back to work."
| 4:59 pm on Mar 12, 2012 (gmt 0)|
Anyone storing CCs in plain text deserve to get hacked.
Actually, anyone storing CC's these days EXCEPT the CC processors themselves pretty much deserve to get hacked because there is no good reason to do it, not even for recurring billing.
Anyone storing security codes needs to be dragged out in the city square and flogged, that's plainly against the rules and in many places an actual crime.
Someone was either being lazy or too cheap to upgrade to modern APIs, obviously violating every CC processing rule in the book, and got what they deserved IMO.
Hopefully these people never get permission to process another credit card again but the greedy companies will just slap 'em with a little fine, smile and look the other way after all the dust settles.
| 5:45 pm on Mar 12, 2012 (gmt 0)|
Whilst I agree about the lack of security of the firm involved, the other issue is the theft of the credit card info. Who knows if it'll be used fraudulently.
It does make me wonder why the card processors allow such shoddy storage of data.
Perhaps the banks/card processors demand a higher degree of security before they will work with firms?
| 8:29 pm on Mar 12, 2012 (gmt 0)|
I hope my wife doesn't find out. :)
| 8:52 pm on Mar 12, 2012 (gmt 0)|
|I hope my wife doesn't find out. :) |
LOL. The credit card info being exposed won't be an issue for many as far as their names are not posted somewhere on the net :)