"...installs on virtually any shared hosting account WITHOUT Telnet, WITHOUT C libraries and WITHOUT system access..."
   
Common Processor Settings
   
 

Information on integrating SurfShopPRO™ with several popular bank processors is listed below for easy cutting and pasting.

We have outlined the values you need to enter in the HTML "Check Out" form for your Check-Out HTML Settings. We have attempted to make it as easy and universal as possible, however we cannot give pre-configured instructions for every possible combination of server, processor and web page. Some modifications may be necessary.

Some of the processors allow you to customize your currency type. In these examples, all currency is specified as US Dollars ("USD").

In order to test your configurations, it may be necessary to enter test values in these forms. In some cases, the URL for the test mode is different than that of the live mode. Check with your processor for the specifics on testing your site.

Note: This information is subject to change at any time. Consult with your payment processor for up-to-date technical information and specifications.

• Also, some of the coding below may not have been translated properly by your browser. First, paste the code into a text editor (not a word processor), then copy from there and paste into SurfShopPRO™PRO. Always back up before replacing your code with the code below.

Generic ECML

Between 1999 and 2001, the Internet Community attempted to move toward a standard for e-commerce configurations, called ECML, or Electronic Commerce Markup Language. While many of the previous bank processors do not use the ECML standard, we still support it. The code below should allow you to interface with any of these "generic" ECML processors.

autoconfig.cgi Settings
Cardservice Domain [depends on processor]
Transaction Result IOC_response_code
Approved Value 0
Declined Value 2
Declined Message IOC_reject_description
AVS IOC_AVS_result
Authorization Code [none]
Reference Number [none]

Check Out HTML
PayPal (WebAccept) PayPal does not pass any values back to SurfShopPRO™. For this reason, all of the values must be encoded in the ?return URL." PayPal uses a different tag for approved and declined transactions. The Transaction Result field and its Approved and Declined values are SurfShopPRO's values, not PayPal's.

autoconfig.cgi Settings

Cardservice Domain www.paypal.com
Transaction Result status
Approved Value Approved
Declined Value Declined
Declined Message [none]
AVS [none]
Authorization Code [none]
Reference Number [none]
   


Check Out HTML
AuthorizeNet This processor requires a special login field, "x_Login" to be provided by the merchant. In addition, you will need to configure your account using the AuthorizeNet administration website.

autoconfig.cgi Settings
Cardservice Domain secure.authorize.net
Transaction Result x_response_code
Approved Value 1
Declined Value 2
Declined Message x_response_reason_text
AVS x_avs_code
Authorization Code x_auth_code
Reference Number x_Cust_ID

Check Out HTML - Credit Card

Check Out HTML - E-Check
LinkPoint

LinkPoint allows you to specify certain fields that are "passed through" the transaction. You must include the following fields:

c
storeid
ud
key

autoconfig.cgi Settings
Cardservice Domain secure.linkpt.net
Transaction Result status
Approved Value Approved
Declined Value Declined
Declined Message [none]
AVS [none]
Authorization Code [none]
Reference Number [none]

Check Out HTML
MerchantAnywhere
(Transaction Central)

This processor does not allow for fields to be "passed through," so the "RefNo" parameter is used to send the customer's unique ID.

 
autoconfig.cgi Settings
Cardservice Domain www.oc2net.net
Transaction Result Auth
Approved Value \w\w\w\w
Declined Value Declined
Declined Message [none]
AVS [none]
Authorization Code TransID
Reference No. RefNo

Check Out HTML
EFTSecure This processor requires a Merchant ID and a Merchant Key to be provided by the merchant. Additional configuration may be necessary using the administration website.

autoconfig.cgi Settings
Cardservice Domain va.eftsecure.net
Transaction Result APPROVED
Approved Value Y
Declined Value N
Declined Message MSG
AVS AVS_MSG
Authorization Code CODE
Reference No. [none]

Check Out HTML - Credit Card

Check Out HTML - Check
WorldPay This processor requires an account number to be passed in the "instId" field.

autoconfig.cgi Settings
Cardservice Domain select.worldpay.com
Transaction Result STATUS
Approved Value Y
Declined Value C
Declined Message [none]
AVS [none]
Authorization Code authno
Reference No. [none]

Check Out HTML
VeriSign PayFlow VeriSign requires both a LOGIN and a PARTNER code.

autoconfig.cgi Settings
Cardservice Domain payflowlink.verisign.com
Transaction Result RESULT
Approved Value 0
Declined Value 12
Declined Message RESPMSG
AVS AVSDATA
Authorization Code AUTHCODE
Reference No. [none]

Check Out HTML - Credit Card

Check Out HTML - E-Check
FirstVirtual This processor requires a Merchant PIN and IPS number to be passed in the form. In addition, it requires the customer to provide a PIN number for the transaction. FirstVirtual does not pass any values back to SurfShopPRO™ . For this reason, all of the values must be encoded in the "return URL." The Transaction Result field and its Approved and Declined values are SurfShopPRO's values, not FirstVirtual's.

autoconfig.cgi Settings
Cardservice Domain www.fv.com
Transaction Result status
Approved Value Approved
Declined Value Declined
Declined Message [none]
AVS [none]
Authorization Code [none]
Reference No. [none]

Check Out HTML

 

MerchantTrust/ECX These processors use the same architecture to process transactions. The only difference is the name of the ID field and the URL used to call the processor.

autoconfig.cgi Settings
Cardservice Domain trans.quickcommerce.com (ECX)
trans.atsbank.com (MerchantTrust)
Transaction Result STATUS
Approved Value accepted
Declined Value declined
Declined Message REASON
AVS [none]
Authorization Code AUTHNO
Reference No. [none]

Check Out HTML - Credit Card

Check Out HTML - Check