eWay XML
The complete set of variables specific to eWay XML is available directly from eWay in their documentation on their website:
http://www.eway.com.au/support/xml.aspx
The following is a breakdown of the information necessary to configure eCart to work with information architecture specific to submitting and retrieving information from the eWay XML merchant gateway available from eWay.
The merchant gateway support provided within eCart is designed to facilitate the configuration of your checkout form using eWay XML, but you are responsible for the proper configuration of your merchant account to take advantage of these features.
Be sure to read eWay's documentation to ensure that your implementation works within their acceptable parameters and requirements.
The Local Checkout server behavior configures the server-side code necessary on your checkout page to pass your merchant information, shopping cart data, and customer payment information directly to eWay.
Local Checkout details the minimum variable requirements for you during the configuration process. As well, all optional variables are available for configuration. Please consult your eWay XML documentation to determine which optional variables may be necessary for you to configure specific to your development needs.
The Local Checkout Response data bindings provides all of the variables passed back to the specified page through the Bindings panel. These bindings can be applied to the page for you to use and store the transaction information on your website.
The variables passed back to your site using this method are the same variables that can be passed to the website initially, as well as information specific to the processing of the transaction that are generated during processing.
http://www.eway.com.au/support/xml.aspx
The following is a breakdown of the information necessary to configure eCart to work with information architecture specific to submitting and retrieving information from the eWay XML merchant gateway available from eWay.
The merchant gateway support provided within eCart is designed to facilitate the configuration of your checkout form using eWay XML, but you are responsible for the proper configuration of your merchant account to take advantage of these features.
Be sure to read eWay's documentation to ensure that your implementation works within their acceptable parameters and requirements.
Server Requirements
eWay requires that you use a secure connection (HTTPS) to transmit transaction data. This means you will need to get an SSL certificate to secure at a minimum, the checkout page on your website.Submitting checkout information
The Insert Checkout Form feature of eCart provides a Local Checkout configuration for eWay XML that directly configures and inserts a checkout form on your page, which can then be customized to meet your needs.The Local Checkout server behavior configures the server-side code necessary on your checkout page to pass your merchant information, shopping cart data, and customer payment information directly to eWay.
Local Checkout details the minimum variable requirements for you during the configuration process. As well, all optional variables are available for configuration. Please consult your eWay XML documentation to determine which optional variables may be necessary for you to configure specific to your development needs.
Retrieving transaction information from the payment gateway
When you submit a transaction for processing, eWay XML responds to the same page and returns the transaction information directly to your server session, allowing you to capture the transaction results for use on your site.The Local Checkout Response data bindings provides all of the variables passed back to the specified page through the Bindings panel. These bindings can be applied to the page for you to use and store the transaction information on your website.
The variables passed back to your site using this method are the same variables that can be passed to the website initially, as well as information specific to the processing of the transaction that are generated during processing.