eProcessingNetwork has developed an 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 Web site.
When a merchants customer goes to the merchants web page using this template, the customer is eventually led to an order page on the merchants Web site listing available items where the customer can select quantities of these items to purchase.
When the customer selects the Submit button from this order page, the customer is passed to a secure page on the eProcessingNetwork Secure Transaction Processing Server. This secure page prompts the customer for name, address, credit card and other information. eProcessingNetwork then uses this information to process the transaction on a real-time basis.
The customer is then presented with an HTML page that indicates the status of the transaction, and if the transaction is approved, email summarizing the transaction is automatically sent to both the merchant and the customer. If the transaction is declined, only the merchant receives the summary email.
Web page developers can integrate the eProcessingNetwork Secure Transaction Processing Server directly into a merchants Web page by simply following the instructions below.
FORM DECLARATION
The form declaration used in your order page should be:
<FORM METHOD=POST ACTION="https://www.eProcessingNetwork.com/cgi-bin/wo/order.pl">
ACCOUNT NUMBER
The merchants eProcessingNetwork account number must be passed in as follows:
<INPUT TYPE=HIDDEN NAME="ePNAccount" VALUE="05971">
DO NOT pass in the merchants' bank merchant account number. The account number you pass in MUST be the merchants' eProcessingNetwork account number.
05971 can be used for development/demo purposes, but the merchants real eProcessingNetwork account number must be used for live transactions.
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 eProcessingNetwork 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:
<INPUT SIZE=5 NAME="ItemQty" MAXLENGTH=3 VALUE="0">
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 TYPE=HIDDEN NAME="ItemDesc" VALUE="Large Widget" >
or you may need to allow the user to enter a description:
<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:
<INPUT TYPE=HIDDEN NAME="ItemCost" VALUE="34.95">
Always group your variables together in sequence, i.e.
<INPUT SIZE=5 NAME="ItemQty" MAXLENGTH=3 VALUE="0">
<INPUT TYPE=HIDDEN NAME="ItemDesc" VALUE="Small Widget" >
<INPUT TYPE=HIDDEN NAME="ItemCost" VALUE="29.95">
<INPUT SIZE=5 NAME="ItemQty" MAXLENGTH=3 VALUE="0">
<INPUT TYPE=HIDDEN NAME="ItemDesc" VALUE="Large Widget" >
<INPUT TYPE=HIDDEN NAME="ItemCost" VALUE="34.95">
This will ensure that the cost of each item is being multiplied by the correct quantity.
|
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.
LOGO URL
The logo to display on all transaction-related pages output by us can be specified as follows:
<INPUT TYPE=HIDDEN NAME="LogoURL" VALUE="http://www.MerchantsWebSite.Com/MerchantsLogo.gif">
A complete URL is required, including "http://www.". This allows merchants to utilize different logos from different pages if so desired.
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:
<INPUT NAME="ApplyTax" TYPE=CHECKBOX>
The eProcessingNetwork 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:
<INPUT TYPE=HIDDEN VALUE=".08125" NAME="TaxRate">
Be sure to change the .08125 to the rate applicable in your state.
SHIPPING METHODS
To offer multiple shipping methods, use radio buttons as follows:
<INPUT TYPE="radio" NAME="Shipping" VALUE="4.50;Regional (BC, Alberta, Manitoba)" CHECKED>Regional (BC, Alberta, Manitoba)
<INPUT TYPE="radio" NAME="Shipping" VALUE="5.95;USA and The Rest of Canada">USA and The Rest of Canada
<INPUT TYPE="radio" NAME="Shipping" VALUE="11.95;International">International
Note that the VALUE field for each item starts with the dollar amount to charge for each item, followed by a semi-colon. The eProcessingNetwork 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.
BACKGROUND COLOR
The background color used by the eProcessingNetwork Web Order Template can be specified as follows:
<INPUT TYPE=HIDDEN NAME="BackgroundColor" VALUE="#ffffff">
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.
TEXT COLOR
The text color used by the eProcessingNetwork Web Order Template can be specified as follows:
<INPUT TYPE=HIDDEN NAME="TextColor" VALUE="#000000">
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.
BILLING INFO
If you are already collecting the customers' Billing Info, you can pass it to the eProcessingNetwork 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.
<INPUT TYPE=HIDDEN NAME="BillFirstName" VALUE="John">
or by prompting the user with:
<INPUT TYPE=TEXT NAME="BillFirstName" VALUE="">
SHIPPING INFO
If you are already collecting the customers' Shipping Info, you can pass it to the eProcessingNetwork 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.
<INPUT TYPE="HIDDEN NAME"="ShipFirstName" VALUE="John">
or by prompting the user with:
<INPUT TYPE="TEXT" NAME="ShipFirstName" VALUE="">
If you are not collecting shipping information from your web site, and you would like eProcessingNetwork to prompt the user, pass in the following input field:
<INPUT TYPE="HIDDEN" NAME="ShippingPrompt" VALUE="Yes">
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="userVar1" VALUE="UserVar 1 Value">
<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="customerVar1" VALUE="CustomerVar 1 Value">
<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)
PAYMENT FORM HEADER
Any text or HTML code sent in this field will be displayed at the top of the Payment Form immediately before the Order Summary.
<INPUT TYPE="HIDDEN" NAME="PaymentFormHeader" VALUE="Display this text ">
RECEIPT HEADER
Any text or HTML code sent in this field will be displayed at the top of the Receipt Page immediately before the Authorization Information.
<INPUT TYPE="HIDDEN" NAME="ReceiptHeader" VALUE="Display this text ">
RECEIPT FOOTER
Any text or HTML code sent in this field will be displayed at the bottom of the Receipt Page.
<INPUT TYPE="HIDDEN" NAME="ReceiptFooter" VALUE="Display this text ">
EMAIL HEADER
Any text sent in this field will be displayed in the EMail Receipt sent to the customer immediately before the Order Summary.
<INPUT TYPE="HIDDEN" NAME="EMailHeader" VALUE="Display this text ">
EMAIL FOOTER
Any text sent in this field will be displayed at the bottom of the EMail receipt sent to the customer.
<INPUT TYPE="HIDDEN" NAME="EMailFooter" VALUE="Display this text ">
Recurring Billing
Merchants with Advanced Recurring Billing can set up a Recurring Method which can be passed to set create a Recurring transaction.
<INPUT TYPE="HIDDEN" NAME="RecurringMethod" VALUE="Recurring Method Number">
For questions, suggestions or special requests, send e-mail to DevUtils@eProcessingNetwork.com
|
