A payment gateway is an e-commerce service that authorizes payments for e-businesses and online retailers. It is the equivalent of a physical POS (point-of-sale) terminal located in most retail outlets.
There are three methods to link a web site to the EZ Payment Gateway for real-time transaction processing:
EditLink to the XML Gateway API -
XML Gateway API (The XML gateway API is a programming interface that resides on transaction servers which communicate directly to credit card processing networks. The programming interface requires that the merchant, or their web programming staff, be sufficiently knowledgeable in programming skills in any programming or object oriented scripting language. The XML Gateway API accepts the credit card purchasers information, and produces an authorization or decline directly from the merchant bank.
The XML Gateway API provides methods to perform the following operations: AUTH, SALE, SETTLE, CREDIT, VOID and QUERY. The information is passed via 128bit SSL https post in XML format. That post occurs in the background from the merchant's server. Thus the purchaser never leaves the merchant's website. The authorization information is returned in XML format with full error trapping and reporting to indicate the success or failure of the transaction.
This is the most secure method and the preferred method.
EditLink to the EZ Payment Gateway Secure Payment Form -
process.aspx (for merchants who do not have a secure server or for merchants who prefer to use the Payment Form)
- Merchant web site posts to the Secure Payment Form on our secure servers(merchant name, unique order ID, a total amount, and has a script with a URL to return authorization information.)
- EZ Payment Gateway - Secure Payment Form collects credit card and billing information and gets an authorization.
- EZ Payment Gateway - Transaction Gateway sends the authorization variables via http GET method back to merchant URL and script.
EditLink directly to the EZ Payment Gateway -
direct.aspx (only for merchants who have a secure server)
- Merchant web site posts to the Secure Payment Server (merchant name, all necessary billing information, the total amount, and a script with a URL to return authorization information.)
- EZ Payment Gateway - Transaction Gateway sends the authorization variables via http GET method back to merchant URL and script.
NOTE: For purposes of this section, a secure server is defined as a web server that has installed and is running at least SSL 2.0 (Secure Sockets Layer) and has a verifiable secure server digital certificate from a recognized certificate authority.
You must have a moderate understanding of HTML/CGI/ASP in order to fully exploit the features of the EZ Payment Gateway. Although it is true that the following snippets of HTML code can be copied and pasted directly into a web site and it would "work", it is not likely that all of the specific needs you have with your web site will be met simply by copying and pasting this code. These code snippets below will send the data to the EZ Payment Gateway, but the transaction status information will never make it back to the merchant without a script on the merchant server. Merchants that are unable to achieve the custom look/feel and programming required on their own should consult with a local Internet web designer/programmer for assistance or purchase the e-commerce Total Package.
EditPayment Gateway Setup
Link a website directly to the XML-Gateway-API
Link a website to the Payment Gateway Secure Payment Form - process.aspx
Link a website directly to the Payment Gateway - direct.aspx