Advanced Integration Method (AIM) is Authorize.Net's recommended connection method and offers the most secure and flexible integration for all types of transactions, including mobile, websites and other business applications.
Authorize.net Advanced Integration Method (AIM) allows merchants to host their own secure payment form on a website, mobile device, etc., and send transactions to the payment gateway using an end-to-end secure sockets layer (SSL) connection.
Apply for a Authorize.net Account
Authorize.net Advanced Integration Method (AIM) is bundled with osCommerce Online Merchant and is also available as a separate Add-On package existing store owners can use to upgrade to.
This document can be found online at:
https://library.oscommerce.com/Package&en&authorizenet&oscom23&aim
All secured API transaction calls sent to Authorize.net are performed by verifying Authorize.net's SSL certificates to guarantee the identity of Authorize.net. This is performed by using the following public keys in order if they are available:
A test connection link is available on the payment module configuration page which can be used to test if API transaction calls to Authorize.net can be verified from your web server. If the test connection fails, please contact your hosting provider as they may need to update your web server configuration. The SSL certificate verification can also be disabled on the payment module configuration page however it is highly discouraged to disable.
Parameter | Description | Default |
---|---|---|
Enable Authorize.net Advanced Integration Method | Setting this parameter to True makes the payment method available to customers during the checkout procedure. | True |
API Login ID | The API Login ID used to connect to the Authorize.net transaction gateway. | |
API Transaction Key | The API Transaction Key used to authenticate transactions sent to Authorize.net. | |
MD5 Hash | The MD5 hash value used to verify transactions with. | |
Transaction Method |
The following transaction methods are available to process transactions with:
|
Authorization |
Set Order Status | The orders status will be updated to this value when a successful transaction has been made. | Default Order Status |
Review Order Status | Set the status of orders flagged under review to this status level. | Default Order Status |
Transaction Order Status | Transactions are logged in this private order status level. | Authorize.net [Transactions] |
Payment Zone | If set, this payment method will only be available to orders made within the defined zone. | |
Transaction Server |
The following transaction servers are available to process transactions through:
|
Live |
Transaction Mode |
The following transaction modes are available to process transactions through:
|
Live |
Verify SSL Certificate | Verify Authorize.net's identity when API communication calls are sent. | True |
Proxy Server | Send API communication calls through this proxy server. | |
Debug E-Mail Address | Send invalid transaction parameters to this e-mail address. | |
Sort Order | The position to show the payment method on the checkout payment page against other available payment methods. |
The separate Authorize.net Advanced Integration Method (AIM) Add-On package is available at:
http://addons.oscommerce.com/info/5662
An online demonstration is available at:
For the online demonstration, Authorize.net Advanced Integration Method (AIM) has been configured with Authorize.net's test server environment and requires a test payment card to purchase an order.
After extracting the Add-On package, copy the files located in the catalog directory to your osCommerce installation directory on the server. The files must be copied in the correct directory structure as extracted from the Add-On package.
The file listing is as follows:
The standard language definitions in English are provided in the Add-On package. For additional languages, copy the English language definition file to the appropriate language directory and open the file with a text editor to edit the language definitions. The location of the language definition file must be in:
When the files have been copied to their appropriate locations, the payment module will be available on the Administration Tool -> Modules -> Payment -> Install Module page where it can be installed, or on the Administration Tool -> Modules -> Payment page if the module was already previously installed.
If the module was already previously installed, it is important to visit the module configuration page to make sure new parameters are automatically installed in the database.