There may be no point in storing the hash of the credit card number. Since you can't reverse engineer it, you having nothing to send to the credit card company to validate the next purchase. (All you can do is assure that the next time the same customer types in some credit card number, it hashes the same as the previous time.)
I'm with those who say "Why do we make you type in your credit card number each time you make a purchase? Because we feel the best was to protect it is to no't store your credit card number in our database. When you type it in, we encrypt what you type and forward it to the credit card clearning house, and they let us know that your charge has been approved." Bill On Tue, 22 Oct 2002 09:13:05 -0500, J. Stephen Wills wrote: >I'm sure that, based on his feedback to me, BillD could add further and more >insightful comment. :-o > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
