![]() |
|
Perl: the Markov chain saw | |
PerlMonks |
comment on |
( #3333=superdoc: print w/replies, xml ) | Need Help?? |
<edit> Just to clarify, I HAVE to store the credit card numbers since the cards will need to be automatically rebilled. If It was just onetime transactions, there would be no problems.</edit> Recently an intresting problem has fallen in my lap. How to securely store creditcards to make them safe incase of a system penetration. Now, if the transactions I was expecting were one time transactions ( a sale for example ), I would store everything but the last 4 digits, and If the customer was going to make another one time transaction, just ask for the last 4 digits. But my problem is that I'm expecting recurring billing. A transaction every month , without having the customer to re-enter any information ( for a service based website. Not pr0n ;) Those were my younger broker days ;) So i'm forced to store credit card numbers. But every day in the news you read about X site being penitrated and Y number of CC's stolen. Well, I have come up with a number of possible solutions, and im hoping the Monestary can think of the best way for me to do it.
So, as you can see there is no perfectly secure way of storing the cards, unless I missed something. Im leaning twords the PGP encrpytion but the annoyance of having to manually do the recurring billing may not make it fly with the boss. So monks, is there anything I missed? Pete insert into pete values('red hair','near green eyes','overinflated ego'); In reply to Encrypting Credit card numbers by petethered
|
|