Just a quick word of caution.....if you don't have to store CC data DON'T. Payment processors have recurring billing options where THEY take all the risk of storing such data.
If you store it and it leaks out or you get hacked....you/your client/the company you work for will be liable. Keep in mind you may have to go through a security audit if you choose to store CC data OK...warning over ;-) Cheers On Tue, 2010-02-16 at 11:49 -0500, Matthew Smith wrote: > What encryption algorithm would be appropriate for cc data? AES or blowfish? > What kind of performance hit would it have? > > Also, what datatype is used to store the encrypted info in the db? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:330781 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
