 |

Table of Contents
License Agreement
Program Credits
|
 |
 |
 |

Software Manual
|
Payment Method Management
Configuring available payment methods is quite simple. All of the controls are in the Orders and Payment | Manage Payment Methods function.
First, you have to decide which type of order process best suits your site. You can choose more than one of the following methods:
Contact Customer
No payments accepted online. The customer is notified that you will contact them via telephone to discuss payment options.
Offline Processing (Credit Card & Switch/Solo Cards)
Collect credit card and/or Switch/Solo card information on your own secure server, encrypt the numbers and then email the primary order email address an encrypted decrypt key. Credit card numbers can then be decrypted using the Manage Online Orders function.
Accept Checks or Purchase Orders
You can allow your users to pay by check or purchase order by presenting them with a printable/faxable version of their order which can be sent in to you for payment.
Process Payments Through PayPal
You can accept payments with your PayPal account. If users don't have their own account, they will be prompted by PayPal to create one.
Process With A Payment Gateway
Collect credit card information on your own secure server and have an online processing partner validate and process the order or use an online processing partner's secure order form for credit card number entry. Both methods are supported and are easilly configurable.
Currently a large listing of payment processors are supported:
- Authorize.Net (SIM & AIM)
- Cardservice Linkpoint (HTML & API)
- Verisign (Payflow Link)
- iTransact
- WorldPay (WorldDirect)
- Bank Of America
- Planet Payment
- RTware
- 2CheckOut (Authnet)
- Wells Fargo (Secure Source & BOA)
- PaySystems
- ViaKlix
- GoRealtime.Com
- ECHOnline
- EFSNET
- InternetSecure
- Caledon
- PlugNPay
- SurePay
- SkipJack
- PSiGate
- Netbilling
- BluePay (API)
- NOCHEX
- SECPay
- Protx
- Spectre
- FirstPay
To configure this software package to work properly with your online processing partner's methods, every bit of information that is transmitted can be configured. In some cases, namely the interfaces that do not use a third party payment gateway, it is not necessary to make any modifications.
If you are using a third party payment gateway, you will need to edit the 'Form Content' field to include your login information for that gateway. Login information fields are surrounded by HTML comments:
<!-- ### -->
<INPUT TYPE="HIDDEN" NAME="LOGIN" VALUE="your_username">
<!-- ### -->
You will need to replace the string 'your_username' with the username your processor assigned you.
Since all pieces of transmitted information are configurable and this package is an open source the opportunity is here to configure this package for processors other than those that are provided in the package. There is an insert function available in the administrator utility to allow you to configure a processor that is not currently supported. Just follow a similar processor's entry as an example if you choose to create a new one.
In addition, the secure server payment script is entered in the Global Settings function separately so it is possible to post information from this program to another secure script, even an ASP script on an NT web server. The information collected there can be sent, for validation, off to your online processing partner's site before returning to your non-secure site for order fulfillment. The possibilities are endless. This program is capable, however, of running securely on it's own.
If your selection was to use offline processing, you will need to select the credit cards you wish to accept. The cards indicated here will be selectable in a drop-down box on the credit card entry screen during the order process. If you selected to use an online processing partner's order form this information will be collected on their site.
Setting Up Specific Online Processors
Several online processors are listed below because their setup requires additional configuration using the admin functions on their site or require the entry of a key or password in addition to the entry in the 'Form Content' section of a username. Review the instructions below.
If your processor is not listed below with specific instructions, no configuration on their site using their admin utility is necessary. The following processors do not require additional setup, however do require that your password be entered in addition to your username. Passwords are entered in the 'Transaction Key/Password' field and are encrypted for your security.
- SECPay
- EFSNET
- Protx
- Caledon
- FirstPay
- SurePay
The remaining processors below require additional configuration using the processor's site admin utility. Please check the required module list at the bottom of this section to ensure that your processor does not require any additional software modules or programs to run.
Authorize.Net AIM & Wells Fargo (Authnet Interface)
- Login to your account at the processor's site and choose the Settings function.
- Under the Settings | Test Mode function, set the system to 'LIVE MODE'.
- Under the Settings | Transaction Version function, set the Transaction Version to '3.1'.
- Under the Settings | Password-Required Mode function, check the box next to 'Require Password for ALL Transactions'.
- Under the Settings | Obtain Transaction Key function, provide your 'Secret Answer' and check the box labeled 'Disable Old Transaction key'. After clicking the submit button, you will be presented with your Transaction Key, which you will need to copy.
- Under the Settings | Form Fields function, uncheck every checkbox, then check these two: Invoice # - Required and Customer ID - Required.
- Logout of your account at the processor's site and login to the administrator utility.
- For the Payment Method select the appropriate payment method.
- In the Update Payment Method function set the Active Status to Active.
- Now drop down to the Form Content section and edit the initial value field for your processor login. This hidden form field is surrounded by HTML comments at the top of the form content textarea. This allows you to locate it quickly. Replace the string 'your_username' with your processor login.
- In the 'Transaction Key/Password' field, enter the Transaction Key you created and copied while using the processor interface.
- Click 'Submit' and log out of the administrator utility. You are done.
* Please see the note about additional software at the bottom of this page.
Authorize.Net SIM
- Login to your account at the processor's site and choose the Settings function.
- Under the Settings | Test Mode function, set the system to 'LIVE MODE'.
- Under the Settings | Transaction Version function, set the Transaction Version to '3.1'.
- Under the Settings | Password-Required Mode function, check the box next to 'Require Password for ALL Transactions'.
- Under the Settings | Obtain Transaction Key function, provide your 'Secret Answer' and check the box labeled 'Disable Old Transaction key'. After clicking the submit button, you will be presented with your Transaction Key, which you will need to copy.
- Under the Settings | Form Fields function, uncheck every checkbox, then check these two: Invoice # - Required and Customer ID - Required.
- Logout of your account at the processor's site and login to the administrator utility.
- For the Payment Method select the appropriate payment method.
- In the Update Payment Method function set the Active Status to Active.
- Now drop down to the Form Content section and edit the initial value field for your processor login. This hidden form field is surrounded by HTML comments at the top of the form content textarea. This allows you to locate it quickly. Replace the string 'your_username' with your processor login.
- In the 'Transaction Key/Password' field, enter the Transaction Key you created and copied while using the processor interface.
- Click 'Submit' and log out of the administrator utility. You are done.
2CheckOut
- For the Payment Method select the appropriate payment method.
- In the Update Payment Method function set the Active Status to Active.
- Now drop down to the Form Content section and edit the initial value field for your processor login. This hidden form field is surrounded by HTML comments at the top of the form content textarea. This allows you to locate it quickly. Replace the string 'your_username' with your store id number.
- Logout of the administrator utility and open a browser session with your online processor. Login to your account and select the Shopping Cart | Cart Details function.
Set the value for the field named "Return to a routine on your site after caredit card processed" to "Yes".
For the "Return URL" field, enter in the full path to your script. Example: http://www.yourdomain.com/cgi-bin/cp-app.cgi
- Log out of processor's admin utility. You are done.
WorldPay
- For the Payment Method select the appropriate payment method.
- In the Update Payment Method function set the Active Status to Active.
- Now drop down to the Form Content section and edit the initial value field for your processor login. This hidden form field is surrounded by HTML comments at the top of the form content textarea. This allows you to locate it quickly. Replace the string 'your_username' with your Installation ID from WorldPay.
- Logout of the administrator utility and open a browser session with your online processor. Login to your account and select the Settings function.
- In the Installations section, click the button under Configuration Options for the Installation ID you want to manage.
- On the Configuration Options page, enter the full http path to your script (Example: http://www.yourdomain.com/cgi-bin/cp-app.cgi) in the 'Merchant's Shop URL' and "Callback URL" fields. Then check the boxes next to "Callback enabled?" and "Use callback response?". Click the "Save Changes" button.
- Log out of processor's admin utility. You are done.
Cardservice Linkpoint (API Only)
- When you signed up for your API processing account at linkpoint, you were provided with a key file. The contents of this key file need to be entered into the file /ccp51/data/keys/linkpoint.txt via FTP for this method to work properly.
- No other configuration is necessary for this method (other than entering your storename in the Form Content section of the payment method screen as instructed above).
* Please see the note about additional software at the bottom of this page.
Cardservice Linkpoint HTML
- Using the administrator, click on Orders & Payment then select the Manage Payment Methods function.
- For the Payment Method, select the appropriate payment method.
- In the Update Payment Method function, set the Active Status to Active.
- Now drop down to the Form Content section and edit the initial value field for your processor login. This hidden form field is surrounded by HTML comments at the top of the form content textarea. This allows you to locate it quickly. Replace the string 'your_username' with your processor login.
- Logout of the administrator utility and open a browser session with your online processor. Login to your account.
- Go to Customization then Payment Form Settings and make the following changes:
Delete any text in the "Recipient's Top" and "Recipient's Bottom" textboxes.
For the "Order Submission Form URL", enter in the full path to your script. Example: http://www.yourdomain.com/cgi-bin/cp-app.cgi
For the "Thank You Page URL", enter in the same URL as above and check the boxes for "Check here if this url is a CGI script." and "Check if you wish to automatically display specified URL after the LinkPoint HTML receipt page." Make sure both are checked.
For the "Sorry Page URL", enter in the same URL as above and check the boxes for "Check here if this url is a CGI script." and "Check if you wish to automatically display specified URL after the LinkPoint HTML receipt page.". Make sure both are checked.
In the "Custom Fields" section, enter in under the column "Name" for #1: "usrnum" and for #2: "tracknum". There is no need to check the boxes for "Make Viewable" or enter anything in the field "Caption" for either of these "Name" entries.
In the "Customer's Receipt" section, uncheck the box "Check here if you would like to receive a copy of each receipt". You don't want CardService sending anything to your customer as the software does it for you.
Click "Submit" at the bottom of the page.
- Log out of processor's admin utility. You are done.
Bank Of America & Wells Fargo (BoA Interface)
- Using the administrator, click on Orders & Payment then select the Manage Payment Methods function.
- For the Payment Method, select the appropriate payment method.
- In the Update Payment Method function, set the Active Status to Active.
- Now drop down to the Form Content section and edit the initial value field for your processor login. This hidden form field is surrounded by HTML comments at the top of the form content textarea to allow you to locate it quickly. Replace the string 'your_username' with your processor login.
- Logout of the administrator utility and open a browser session with your online processor. Login to your account.
- Using the processor's admin interface, turn off all notification by email, both to you and the customer.
- Change your confirmation pages to custom instead of the default page and make the address for both pages 'http://www.yourdomain.com/cgi-bin/cp-app.cgi' or whatever location you have the program located. Regardless, make this the address for *BOTH* your reject and accept confirmation pages in the custom
confirmation pages.
- Log out of processor's admin utility. You are done.
Verisign Payflow Link
- Using the administrator, click on Orders & Payment then select the Manage Payment Methods function.
- For the Payment Method, select the appropriate payment method.
- In the Update Payment Method function, set the Active Status to Active.
- Now drop down to the Form Content section and edit the initial value field for your processor login. This hidden form field is surrounded by HTML comments at the top of the form content textarea to allow you to locate it quickly. Replace the string 'your_username' with your processor login.
- Logout of the administrator utility and open a browser session with your online processor. Login to your account. Select the Account Info function.
- Go to General - Edit Configuration and make the following changes:
For Return URL Method, choose POST.
For Return URL, enter the full http path to your script. Example: http://www.yourdomain.com/cgi-bin/cp-app.cgi
For Required Fields, check the boxes for Name, Address, City, State, Zip, Country and Email.
- Go to Security Options and make the following changes:
Add the full http path to your script as an "Accepted URL". Example: http://www.yourdomain.com/cgi-bin/cp-app.cgi
- Click the submit button at the bottom of the page to update your settings.
- Log out of processor's admin utility. You are done.
ECHOnline Credit Card & eCheck
- Login to your account at the processor's site and choose the Settings function.
- Under the Settings | Test Mode function, set the system to 'LIVE MODE'.
- Under the Settings | Transaction Version function, set the Transaction Version to '3.1'.
- Under the Settings | Password-Required Mode function, check the box next to 'Require Password for ALL Transactions'.
- Under the Settings | Obtain Transaction Key function, provide your 'Secret Answer' and check the box labeled 'Disable Old Transaction key'. After clicking the submit button, you will be presented with your Transaction Key, which you will need to copy.
- Under the Settings | Form Fields function, uncheck every checkbox, then check these two: Invoice # - Required and Customer ID - Required.
- There is no configuration needed using the ECHO administrator utility - just be sure to have your ECHO merchant id and password that were issues to you.
- Login to the administrator utility.
- For the Payment Method select the appropriate payment method.
- In the Update Payment Method function set the Active Status to Active.
- Now drop down to the Form Content section and edit the initial value field for your merchant id. This hidden form field is surrounded by HTML comments at the top of the form content textarea. This allows you to locate it quickly. Replace the string 'your_username' with your merchant id.
- In the 'Transaction Key/Password' field, enter the password you have been issued for your merchant id.
- Click 'Submit' and log out of the administrator utility. You are done.
* Please see the note about additional software at the bottom of this page.
Planet Payment & RTware
- Using the administrator click on Orders & Payment then select the Manage Payment Methods function.
- For the Payment Method select the appropriate payment method.
- In the Update Payment Method function set the Active Status to Active.
- Now drop down to the Form Content section and edit the initial value field for your processor login. This hidden form field is surrounded by HTML comments at the top of the form content textarea. This allows you to locate it quickly. Replace the string 'your_username' with your processor login.
- Logout of the administrator utility and open a browser session with your online processor. Login to your account and select the Settings function.
- Select the General Connection Setup function, then Response String Version. Ensure that the response string version is set to 3.1.
- Under the General Connection Setup function, select the Referrer URLs function. Choose to add a URL and on the following page, enter the full http path to your script.
- Under the General Connection Setup function, select the Response/Reciept URLs function. Choose to add a URL and on the following page, enter the full http path to your script. You do not need to make this a default Recipient Link or Relay Response URL, but it's acceptable if you choose to do so.
- Under the Payment And Receipt Forms function, select the Receipt Method function. Select to use a POST receipt method. Enter the full http path to your script in the Recipient Link URLs field.
- Under the Payment And Receipt Forms function, select the Form Fields function. There uncheck every checkbox, then check these two: Invoice # - Required and Customer ID - Required.
- Under the Automated Direct Connect function, select the ADC Relay Response function. Enter the full http path to your script in the URL field.
- Under the Security function, uncheck the Require Password For All Transactions box.
- Under the Email Receipts function, uncheck the Email Transaction Receipt To Customer box.
- For the CVV2 Verification and Address Verification functions, select levels that you feel comfortable with.
- Log out of processor's admin utility. You are done.
SkipJack
- Login to your account at the processor's site and choose the 'Preferences' function.
- Select the 'Response Files' function.
- Click the 'Send Customer to the following WebPages/URLs' radio button and in the four text boxes provided under that button, enter in the full path to your script. Example: http://www.yourdomain.com/cgi-bin/cp-app.cgi. The same entry goes in all four text boxes.
- Logout of your account at the processor's site. You are done.
PSiGate
- Integration with PSiGate is simple and only requires you to choose the correct payment method (payment form or secure server) via the administrator. Remember to enter in your Merchant ID in the administrator's Form Content section for the method you choose.
- The default PSiGate response method is a GET response. If you have changed this to a POST response at PSiGate, change back to GET.
- PSiGate regulations specify that you must inform them whether you will be using their payment form or your own secure server to collect credit card information. Inform them of the method you're using and PSiGate will configure your account correctly.
NetBilling
- Under the Fraud Controls function, choose the Fraud Defense sub-function. Under the Enable Fraud Defense
heading, make sure that Fraud Defense is Enabled. Under the Order integrity heading, make sure 'Enforce order integrity' is checked. Copy the Order integrity key as you will need it later. Make any other changes to these settings you wish. Click the Apply button.
- Under the Security function, choose the Access Security sub-function and for Payment Form Interfaces, make sure that 'Enable Payment Form V2.x (Universal) interface' is checked. Click the Apply button.
- Under the Setup function, choose the Website tools sub-function and click 'Browse Sites'. Choose to add a new site at the bottom of the list. Enter a Site Tag, Site Name and URL. Make note of the Site Name you choose. The URL used here is for reference only, so you can enter your main site URL here (not the full http path to cp-app.cgi).
- On the same page, next to the site you've added, click the 'Config' link. On the following page, enter your name, phone and email address in the Website Information section. Then, in the Default payment form settings section, enter the full path to your script for the Return URL and GiveUp URL fields. Example: http://www.yourdomain.com/cgi-bin/cp-app.cgi. Also, set the Return Method to POST and the Postback CGI URL to blank. For the Payment options field, make sure 'Accept Credit Card payments for this site' is checked and the Payment Form field is set to the default for your Site Name. Click the Apply button.
- Return to the Setup function, then choose the Website tools sub-function and click 'Browse Sites'. Next to the site you added previously, click the 'Email' link. On the following page, in the Email templates sent to merchant section, enter your email address in the 'To' field, and select the any email templates for your site you wish to use for the Standard receipt and Decline notice emails (if you don't want to use the default templates). Click the Apply button.
- Logout of your account at the processor's site and login to the administrator utility.
- For the Payment Method select the appropriate payment method.
- In the Update Payment Method function set the Active Status to Active.
- Now drop down to the Form Content section and edit the initial value field for your processor login. This hidden form field is surrounded by HTML comments at the top of the form content textarea. This allows you to locate it quickly. Replace the string 'your_accountnum:your_sitename' with your account number, followed by a colon (:) followed by the Site Name you created using the NetBilling administrator.
- In the 'Transaction Key/Password' field, enter the Crypto Hash you copied while using the processor interface.
- Click 'Submit' and log out of the administrator utility. You are done.
Additional Software Needed For Some Processors
The following processors integrations require the installation of non-standard Perl modules. The modules that need to be installed by the administrator of the webserver are: Crypt::SSLeay, HTML::Parser, HTML::Tagset, IO::Socket::SSL, libnet, libwww-perl, MIME::Base64, Net_SSLeay and URI. If you attempt to set up a connection with or otherwise use one of the following processors without these modules installed, a 'protocol not supported' error message will be presented.
- Authorize.Net (AIM Only)
- Wells Fargo (Secure Source Only)
- ECHOnline
- EFSNET
- Caledon
- SurePay
- BluePay (API)
- FirstPay
The following processor integrations require the use of the program cURL. This program is freely available as are the Perl modules above. If you are using a processor that uses the cURL program, ensure that you have the correct path for cURL set up in the Global Settings | Manage Program Settings function.
- Cardservice Linkpoint (API Only)
|
 |