Index
Order Types
Responding to Your Customers
Custom Messaging
Securing Your Web Pages
Overview
Troubleshooting
Images
 
Testing Your Web Pages
Broadcast Email
Secure Secondary Posting
Additional Processing
Netcentives
Tags
FAQs

Securing Your Transactions

Troubleshooting

 

Although transaction originating on a unsecure server are encrypted before they are transmitted, customers may still be wary about entering their credit card information on a page where the security symbol doesn't reflect the secure nature of the transaction. Internet Explorer users will get a dialogue box telling them that the data is going to a secure server -- but only if they haven't turned the dialogue box off, and only after they hit the submit button. For Netscape users, the symbol at the bottom left hand corner of the screen doesn't change until after they hit the submit button.

In order to increase your customers' confidence in the security of their transaction, you may want to make use of the "Confirm" feature of ITPS. When you use the "Confirm" tag, your customers' data is passed from the entry page on the server where your web site is hosted (which may not be a secure server), to a custom response page that you have set up using Custom Messaging, which can be hosted on ITPS' secure server. You can take your customer's name and address information on the entry page, and wait until the custom response page is displayed before you ask for credit card information. This way, your customers can see the secure symbol at the bottom of the web browser before they enter their credit card information.

To use this feature, do the following:

  1. Add the following html tag to your original page:

    <input type=hidden name=Confirm value=On>

  2. Change the <form action> parameter to send the request to ITPS' secure server:

    <form action="https://www.neodata.com/ITPS2">

  3. Use the iResponse tag to select a custom web page to go back to your user, and use the double-bar substitution method to prepopulate the response page, using the data the user gave you on the first form. Example:

    <input type=hidden name=iResponse value="Some_Response_Page_Name">

    On the Some_Response_Page_Name:

    <input type=text name=FullName value="||FullName||">
    <input type=text name=StreetAdr value="||StreetAdr||">
    <input type=text name=SuppAdr value="||SuppAdr||">
    <input type=text name=City value="||City||">
    <input type=text name=State value="||State||">
    <input type=text name=Country value="||Country||">

    Note: Do not put the "Confirm" tag on the response page -- only on the original entry page.

  4. Solicit the credit card information on this page -- your users will see the "secured" symbol at the bottom of their browser screen when the response page is displayed.