eProcessing Network has developed a Web Order Template that does not require the merchant to run a database engine or shopping cart program, and can therefore be used from any existing website.
To integrate the eProcessing Network Secure Transaction Processing Server directly into a merchant's Web page, follow the instructions below:
- Requirements
- Options
The form declaration used in your order page should be:
| Back to Top |
ACCOUNT NUMBER
The merchants eProcessing Network account number must be passed in as follows:
DO NOT pass in the merchants' bank merchant account number. The account number you pass in MUST be the merchants' eProcessing Network account number.
05971 can be used for development/demo purposes, but the merchants real eProcessing Network account number must be used for live transactions.
| Back to Top |
ITEM IDENTIFIERS
Three identifiers for each item available from the merchants order page (quantity, description and cost) must be passed to the order.pl script.
| The quantity for each item can be hard-coded or input by the user, but the name of the quantity variable (e.g. ItemQty) must be the same for each item. The eProcessing Network Secure Transaction Processing Server will multiply quantity by cost of each item to display a summary of the order and calculate an order total. One suggested way of passing the quantity of each item is as follows:
The description of each item must be passed to the order.pl script using the name ItemDesc. These can be sent as HIDDEN values as follows: <INPUT SIZE=30 NAME="ItemDesc" VALUE=""> The cost of each item must be passed using the name ItemCost. One suggested way to do this would be: Always group your variables together in sequence, i.e. <INPUT SIZE=5 NAME="ItemQty" MAXLENGTH=3 VALUE="0"> |
| Back to Top |
POST PROCESSING RETURN URL
The URL for the customer to return to after the transaction is processed should be specified as follows:
<INPUT TYPE=HIDDEN NAME="URL" VALUE="http://www.merchants_page.com/gohere">
If you want eProcessing Network to send your customer to a URL depending on the Approval status of the transaction you would use the following:
<INPUT TYPE=HIDDEN NAME="ReturnApprovedURL" VALUE="http://www.merchants_page.com/gohere">
<INPUT TYPE=HIDDEN NAME="ReturnDeclinedURL" VALUE="http://www.merchants_page.com/gohere">
Be sure to change http://www.merchants_page.com/gohere to the correct URL.
| Back to Top |
LOGO URL
The logo to display on all transaction-related pages output by us can be specified as follows:
A complete URL is required, including "http://www.". This allows merchants to utilize different logos from different pages if so desired.
| Back to Top |
SALES TAX
If you need to collect sales tax in your state, use a checkbox to indicate that tax needs to be applied to the transaction as follows:
The eProcessing Network Secure Transaction Processing Server tests for the value of ApplyTax to be equal to on to multiply the order total by the tax rate specified. You can specify the tax rate to be applied as follows:
Be sure to change the .08125 to the rate applicable in your state.
| Back to Top |
SHIPPING METHODS
To offer multiple shipping methods, use radio buttons as follows:
Note that the VALUE field for each item starts with the dollar amount to charge for each item, followed by a semi-colon.
The eProcessing Network Secure Transaction Processing Server parses the dollar amount and displays the word Shipping, along with the description given with the selected RADIO button as a line item in the Order Summary.
| Back to Top |
BACKGROUND COLOR
The background color used by the eProcessing Network Web Order Template can be specified as follows:
where the value specified is any hex-based RGB value supported by the HTML <BODY> tag. If this value is not specified, a default value of #ffffff (white) will be used.
| Back to Top |
TEXT COLOR
The text color used by the eProcessing Network Web Order Template can be specified as follows:
where the value specified is any hex-based RGB value supported by the HTML <BODY> tag. If this value is not specified, a default value of #000000 (black) will be used.
| Back to Top |
BILLING INFO
If you are already collecting the customers' Billing Info, you can pass it to the eProcessing Network Transaction Processing Server, which will display the information in the form used to prompt the customer for credit card information. The format for these field names is as follows:
| BillFirstName |
| BillLastName |
| BillCompany |
| BillAddress |
| BillCity |
| BillState |
| BillZip |
| BillCountry |
| BillPhone |
| BillEMail |
This information can be passed in as a hidden type, i.e.
or by prompting the user with:
| Back to Top |
SHIPPING INFO
If you are already collecting the customers' Shipping Info, you can pass it to the eProcessing Network Transaction Processing Server, which will display the information in the form used to prompt the customer for credit card information, and email it to the merchant upon approval of the transaction. The format for these field names is as follows:
| ShipFirstName |
| ShipLastName |
| ShipCompany |
| ShipAddress |
| ShipCity |
| ShipState |
| ShipZip |
| ShipCountry |
| ShipPhone |
| ShipEMail |
This information can be passed in as a hidden type, i.e.
or by prompting the user with:
If you are not collecting shipping information from your web site, and you would like eProcessing Network to prompt the user, pass in the following input field:
| Back to Top |
USER-DEFINED VARIABLES
Any variables passed in with names that begin with "user" will be enumerated at the end of emails sent to the merchant for each transaction.
As an example, if your FORM passes in:
<INPUT TYPE="HIDDEN" NAME="userVar2" VALUE="UserVar 2 Value">
<INPUT TYPE="HIDDEN" NAME="userVar3" VALUE="UserVar 3 Value">
then the email the merchant receives for each transaction will include:
****** User-Defined Variables ******
userVar1 = UserVar 1 Value
userVar2 = UserVar 2 Value
userVar3 = UserVar 3 Value
Any variables passed in with names that begin with "customer" will be enumerated at the end of emails sent to the customer for each transaction.
As an example, if your FORM passes in:
<INPUT TYPE="HIDDEN" NAME="customerVar2" VALUE="CustomerVar 2 Value">
<INPUT TYPE="HIDDEN" NAME="customerVar3" VALUE="customerVar 3 Value">
then the email the customer receives for each transaction will include:
Var1 = CustomerVar 1 Value
Var2 = CustomerVar 2 Value
Var3 = CustomerVar 3 Value
(the word "customer" is truncated from the display of the variable names in the customers' email)
| Back to Top |
PAYMENT FORM HEADER
Any text sent in this field will be displayed at the top of the Payment Form immediately before the Order Summary. HTML tags are not supported.
| Back to Top |
RECEIPT HEADER
Any text sent in this field will be displayed at the top of the Receipt Page immediately before the Authorization Information. HTML tags are not supported.
| Back to Top |
RECEIPT FOOTER
Any text sent in this field will be displayed at the bottom of the Receipt Page. HTML tags are not supported.
| Back to Top |
EMAIL HEADER
Any text sent in this field will be displayed in the EMail Receipt sent to the customer immediately before the Order Summary.
| Back to Top |
EMAIL FOOTER
Any text sent in this field will be displayed at the bottom of the EMail receipt sent to the customer.
| Back to Top |
Recurring Billing
Merchants with Advanced Recurring Billing can set up a Recurring Method which can be passed to set create a Recurring transaction.
| Back to Top |
Service/Convenience Fee
Merchants wishing to charge a Service/Convenience Fee can add options include it in with the order.
ServiceFee or ServicePercent may be zero or not provided, but at least one of the two inputs is required to be non-zero.
For the option to charge the Service/Convenience Fee to one Merchant account and the other fees to another, please contact Support for details.
| Back to Top |
For questions, suggestions or special requests, email us at devutils@eprocessingnetwork.com.
