![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Once I get a policy in place, I may also set up some forms to accept credit cards for various purposes (registrations, membership dues, etc.) They won't be processed on-site, so a shopping cart would probably be overkill. Am I correct in thinking that having the form on a secure page would be safe enough? (as long as the recipient goes to the on-site webmail) |
#3
| |||
| |||
|
|
I am planning on upgrading the formmail script on a site I edit and was wondering if anyone could suggest a Perl or PHP script that is: cost effective (or free), supports multiple forms, allows attachments, can send to different/multiple email addresses, can process multi-page forms and easily configurable for programming newbies such as I. |
#4
| |||
| |||
|
|
"SlowRyde" <ayntryte (AT) ALL (DOT) invalid> wrote in message news:Kedmc.74350$7a5.63617 (AT) bignews6 (DOT) bellsouth.net... Once I get a policy in place, I may also set up some forms to accept credit cards for various purposes (registrations, membership dues, etc.) They won't be processed on-site, so a shopping cart would probably be overkill. Am I correct in thinking that having the form on a secure page would be safe enough? (as long as the recipient goes to the on-site webmail) No, that would be a bad idea. I would go one step further and say that you should NEVER store credit card information on a shared server...ever. Matter of fact, its probably against your merchant account's terms of service to do that. --Tina |
#5
| |||
| |||
|
|
Tina - AffordableHOST, Inc. wrote: "SlowRyde" <ayntryte (AT) ALL (DOT) invalid> wrote in message news:Kedmc.74350$7a5.63617 (AT) bignews6 (DOT) bellsouth.net... Once I get a policy in place, I may also set up some forms to accept credit cards for various purposes (registrations, membership dues, etc.) They won't be processed on-site, so a shopping cart would probably be overkill. Am I correct in thinking that having the form on a secure page would be safe enough? (as long as the recipient goes to the on-site webmail) No, that would be a bad idea. I would go one step further and say that you should NEVER store credit card information on a shared server...ever. Matter of fact, its probably against your merchant account's terms of service to do that. --Tina Thanks Tina, Protecting the user is my top priority. Any suggestions on a safe way to do this? |
#6
| |||
| |||
|
|
Once I get a policy in place, I may also set up some forms to accept credit cards for various purposes (registrations, membership dues, etc.) They won't be processed on-site, so a shopping cart would probably be overkill. Am I correct in thinking that having the form on a secure page would be safe enough? (as long as the recipient goes to the on-site webmail) No, that would be a bad idea. I would go one step further and say that you should NEVER store credit card information on a shared server...ever. Matter of fact, its probably against your merchant account's terms of service to do that. --Tina Thanks Tina, Protecting the user is my top priority. Any suggestions on a safe way to do this? Pass the information directly to the credit card processor - don't mess with trying to store it securely on your own. Too much risk. Credit card processors spend ALOT of money to make sure their data is stored securely...let them handle it. --Tina |

#7
| |||
| |||
|
|
Tina - AffordableHOST, Inc. wrote: Once I get a policy in place, I may also set up some forms to accept credit cards for various purposes (registrations, membership dues, etc.) They won't be processed on-site, so a shopping cart would probably be overkill. Am I correct in thinking that having the form on a secure page would be safe enough? (as long as the recipient goes to the on-site webmail) No, that would be a bad idea. I would go one step further and say that you should NEVER store credit card information on a shared server...ever. Matter of fact, its probably against your merchant account's terms of service to do that. --Tina Thanks Tina, Protecting the user is my top priority. Any suggestions on a safe way to do this? Pass the information directly to the credit card processor - don't mess with trying to store it securely on your own. Too much risk. Credit card processors spend ALOT of money to make sure their data is stored securely...let them handle it. --Tina Should I interpret that to say that a shopping cart is the best solution? I'm exploring uncharted territories here ![]() Thanks again, |
#8
| |||
| |||
|
|
On Wed, 05 May 2004 16:47:15 -0500, SlowRyde <ayntryte (AT) ALL (DOT) invalid> wrote: I am planning on upgrading the formmail script on a site I edit and was wondering if anyone could suggest a Perl or PHP script that is: cost effective (or free), supports multiple forms, allows attachments, can send to different/multiple email addresses, can process multi-page forms and easily configurable for programming newbies such as I. I've found the formmail at http://nms-cgi.sourceforge.net/scripts.shtml to be quite good. Off the top of my head, I think it satisfies all your requirements, but check it first. |
![]() |
| Thread Tools | |
| Display Modes | |
| |