How Do I Secure Transactions?

E-Commerce
Secure Certificate
Server Number
Secure URL
Secure Forms
Secure Frontpage Forms

Computer Pal, Inc. has paired with E-Commerce Exchange to offer real time solutions that include credit card processing and pre-approved merchant accounts.  This process does not necessarily involve the Verisign certificates discussed below. This page merely describes the process of securing (encrypting) sensitive data between the server and client.

Now, on to secure transactions. 

Virtual domain accounts support SSL (Secure socket layer) secure transactions. This method allows for secure, encrypted communication between the user's web browser and your web site. SSL requires that a secure host have a "certificate" signed by a company such as Verisign or Thawte. You can obtain your own certificate if you do not want to have to use our host name in your URL. For a more in-depth explanation of the SSL process, click HERE.

First thing you will need to know is "What Server Am I On?"  

You will need to login to your account via telnet. Click on the word telnet for further instructions. At the telnet prompt you will see something like the following:

Please note:   "YourDomainPrefix" refers to that part of your domain name before the dot (".").  For example, if your domain name is xyz.com, then "YourDomainPrefix" would be xyz

Also note: The path of the secured server depends on which server you are on (www#). Please make sure you know what server you are on and that you follow the appropriate instructions.

You can use this as a template for all servers listed above. If you are not on one of these servers,  please read below.

If you are on servers nt4-nt5, www1-www37,
or w101-w208 try the following:

Other secured server goodies:

If you are using cgiemail with a secure form, please refer
to our faq on using email forms with cgiemail.

If you are using webform.cgi with a secure form, please refer
to our faq on using email forms with webform.cgi.

For cgiemail and/or webform.cgi using a secure form, follow the same steps as above.

If you are using Microsoft® FrontPage® 2000 try the following :

Let's say you have an index page that contains a link like this:

https://www#.securedweb.net/YourDomainPrefix/wwwfp/YourDirectory/YourPage.html

A Microsoft® FrontPage® 2000 form page referenced this way should need no other changes to submit securely and send email. A Microsoft® FrontPage® 2000 form referenced this way that saves the information to a file will need to have the permissions on the destination file set to 666 and the destination directory set to 777 (cannot be root frontpage directory)