form processing

[WayneK]

Hi gang me again :)

Just a theorectical question related to storing credit card numbers.

Is this viable. (Somewhat simplified)

Order form located on the secure server.

Site owner notified via email he has an order. (no cc number in the email)
Owner goes to area where orders are kept. (access restricted via .htaccess)
Owner views the orders and processes the info manually.
Owner has a button to delete the txt file when he is done.

Are there formprocessing scripts that do this. I haven't found one that stores the info, presents it then give the option to remove it.

Is this reasonably secure?

Wayne

[Justin]

It would be MUCH better to send that info to you in an email. PGP encryption would be an added bonus but just emailing it would be better than having it web based.

You shouldn't store the CC numbers ANYWHERE, especially somewhere that is web accessible - regardless of .htaccess protection... It's just a very bad idea IMO :(

This form should send you the info in an email immediately, never storing this info. Yes, it is stored on the server in the form of an email, but this would be much harder to comprimize that storing it right there on the server...

Put it this way - a user wants a secure server - they want to see that little padlock icon before entering their CC info. These users (I am one of them) would leave the site in a heartbeat if their browser gave them any indication that something wasn't right (even something simple like an image being called from a different URL is enough).

What would these users do if they knew how their info was being retrieved (via a web site with a password)? I doubt they'd continue with their order...

In other words, IMO this would be creating a false sense of security - that user is ensured that their CC info is being sent in a secure manner - it's not likely that anything would happen, but if it did, you would be liable if only for the fact that the user was ensured a safe transaction, and that wasn't the case on the back end of the process...

Sorry - I don't mean to sound rude - I just think that every precaution should be taken to ensure things are done in a safe, secure manner, especially in a time where people would just LOVE to find something bad to say about internet commerce. Someone hears about a person getting ripped off (or E-screwed as an IBM commercial put it) and immediately their confidence level goes way down - remember how fragile the average person's view of the internet is... they are easily put off (keep in mind I'm talking about the casual surfer with an AOL account and no real knowledge of the internet).

Hope this helps... again, sorry for sounding rude - my intent was to try to help you find a better solution (PGP encrypted email being the best way IMO), not to knock your idea :)

------------------
Justin Nelson
FutureQuest Support

[WayneK]

No problem.

I was just thinking out loud. I was trying to avoid PGP or emailing it in the open cos this client just isn't able to understand all this. And the server he is using is keeping a real tight rein on scripts, thereby forcing the use of their cart. But they do generate traffic.

The last time I used PGP for myself it fouled up the registry when i uninstalled it. Perhaps I will give it another chance.
[This message has been edited by WayneK (edited 11-15-99)]

[Rich]

I would agree with all of Justin's points on this subject. Credit card information should never be transmitted or stored in anything other than in a strongly encrypted format. With every passing day there is an increasing concern over the privacy and security of consumer's personally identifiable information. Now is the time to set your company and its Web site apart from the rest by publically stating that your company shares these privacy concerns and by actively implementing the most secure measures possible to protect all of your visitor's information.

At the present time, there are only two three methods available to securely process credit card transactions over the Internet:

(1) Use a payment service gateway to process and store the transactions on their servers. CyberSource, CyberCash, Authorize.Net, and Signio are examples of these types of services.

(2) Use PGP encrypted email to receive transactions and then process these transactions offline by using a dial-up product like IC Verify, PCAuthorize, or MacAuthorize.

(3) Use a shopping cart application (or other local custom application) that stores the transaction data in an encrypted form for later retreival and processing. The actual processing would be performed using local PC software and a dial-up connection as in (2).

Rich