Authorize.Net Advanced Integration Method (AIM)
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 Authorize.Net merchant gateway for the Advanced Integration Method (AIM).
The complete set of variables specific to Authorize.Net's AIM is available directly from Authorize.Net in their documentation when you have set up an Authorize.Net account. This information is available when you login to their website in the following location:
https://secure.authorize.net/
In the Help section of the site (accessible through the left hand navigation) click the Documentation and Reference Guides link at the bottom of the page, and then click on the Advanced Integration Method (AIM) link in the following page.
The merchant gateway support provided within eCart is designed to facilitate the configuration of your checkout form using Authorize.Net, but you are responsible for the proper configuration of your merchant account to take advantage of these features.
Be sure to read Authorize.Net'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 Authorize.Net.
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 AIM 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.
Authorize.Net also performs a form POST containing the information pertinent to your transaction to an http:// location. You must enable the POST of this information and configure the passback location in your Authorize.Net account in the following location for this information to be returned to your site:
The complete set of variables specific to Authorize.Net's AIM is available directly from Authorize.Net in their documentation when you have set up an Authorize.Net account. This information is available when you login to their website in the following location:
https://secure.authorize.net/
In the Help section of the site (accessible through the left hand navigation) click the Documentation and Reference Guides link at the bottom of the page, and then click on the Advanced Integration Method (AIM) link in the following page.
The merchant gateway support provided within eCart is designed to facilitate the configuration of your checkout form using Authorize.Net, but you are responsible for the proper configuration of your merchant account to take advantage of these features.
Be sure to read Authorize.Net's documentation to ensure that your implementation works within their acceptable parameters and requirements.
Server Requirements
Specific to your web application server model, the following components/libraries need to be installed in order to support using AIM in your website. You will need to confirm with your hosting provider that your server supports the following for your model:- ASP - Msxml2.0
PHP - curl library
Submitting checkout information
The Insert Checkout Form feature of eCart provides a Local Checkout configuration for Authorize.Net 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 Authorize.Net.
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 AIM 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, Authorize.Net 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.
Authorize.Net also performs a form POST containing the information pertinent to your transaction to an http:// location. You must enable the POST of this information and configure the passback location in your Authorize.Net account in the following location for this information to be returned to your site:
- Go to https://secure.authorize.net/ and login with your merchant account information.
- In the left navigation, click the Settings link.
- Under the Transaction Response section, click the Relay Response link.
- Specify the http:// location that the transaction details should be posted to upon completion of the transaction
- Go to https://secure.authorize.net/ and login with your merchant account information.
- In the left navigation, click the Settings link.
- Under the Transaction Response section, click the Response/Receipt URLs link.
- Specify the http:// location that the transaction details should be posted to upon completion of the transaction