h1. Advanced Integration Method (AIM)
The Advanced Integration Method is the recommended connection method and offers the most secure and flexible integration. AIM allows merchants to host their own secure payment form and send transactions to the payment gateway using an end-to-end secure sockets layer (SSL) connection.
* Employs industry standard secure data encryption technology - 128-bit Secure Sockets Layer (SSL) protocol.
* Uses transaction key authentication for ultimate security.
* Allows control over all phases of the customer's online transaction experience.
* Configurable transaction response integrates easily with merchant applications.
The Advanced Integration Method is included in osCommerce Online Merchant v2.2 and is available as a separate add-on for existing store owners who are running earlier versions of osCommerce Online Merchant v2.2.
{note}This payment module requires account settings to be defined on the Authorize.net Merchant Interface in order to function correctly.{note}
{note}This payment module requires PHP to support cURL or access to the "curl" program file.{note}
{toc:minLevel=2}
h2. Authorize.net Merchant Interface Settings
+MD5 Hash+
The MD5 Hash feature allows transaction responses to be securely received from the payment gateway. The MD5 Hash is calculated with a secret word that is configured in the Authorize.net Merchant Interface \-> Settings \-> MD5 Hash section.
h2. Configuration Settings
+Enable Authorize.net Credit Card AIM+
Setting this parameter to _True_ makes the payment method available to customers during the checkout procedure.
+Login ID+
API login ID for the payment gateway account.
+Transaction Key+
Transaction key obtained from the Authorize.net Merchant Interface.
+MD5 Hash+
The MD5 hash value securely verifies the results of a transaction. This must match the value entered in the Authorize.net Merchant Interface Security section.
+Transaction Server+
The following transaction servers are available to process transactions through:
|*Live*|The _Live_ server is used in live environments to process and receive payments from customers.|
|*Test*|The _Test_ server is only used to test transactions in a staging environment. No transactions are processed and no payments are made when transactions are being tested.|
+Transaction Mode+
The following transaction modes are available to process transactions with:
|*Live*|The _Live_ mode verifies and processes the credit card information for processing.|
|*Test*|The _Test_ mode only verifies the credit card information for testing purposes when the Live transaction server is being used. No transactions are processed and no payments are made when transactions are being tested.|
+Transaction Method+
The following transaction methods are available to process transactions with:
|*Authorization*|The _Authorization_ transaction method only authorizes transactions and must be captured manually through the Authorize.net Merchant Interface.|
|*Capture*|The _Capture_ transaction method authorizes and transfers the funds to your Merchant account.
+Payment Zone+
If set, this payment method will only be available to orders made within the defined zone.
+Set Order Status+
The orders status will be updated to this value when a successful transaction has been made.
+Sort Order+
The position to show the payment method on the checkout payment page against other available payment methods.
+cURL Location+
The location and filename of the cURL "curl" program file.
h2. Manual Installation (as an Add-On)
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:
* includes/languages/english/modules/payment/authorizenet_cc_aim.php
* includes/languages/espanol/modules/payment/authorizenet_cc_aim.php
* includes/languages/german/modules/payment/authorizenet_cc_aim.php
* includes/modules/payment/authorizenet_cc_aim.php
The standard languages definitions in English, Spanish, and German are provided in the add-on package. For additional languages, copy one of the existing language definition files to the appropriate language directory and edit the file with a text editor to edit the language definitions. The location of the language definition file must be in:
* includes/languages/<language>/modules/payment/authorizenet_cc_aim.php
When the files have been copied to their appropriate locations, the payment module will be available in the Administration Tool \-> Modules \-> Payment Modules listing where it can be installed.
The Advanced Integration Method is the recommended connection method and offers the most secure and flexible integration. AIM allows merchants to host their own secure payment form and send transactions to the payment gateway using an end-to-end secure sockets layer (SSL) connection.
* Employs industry standard secure data encryption technology - 128-bit Secure Sockets Layer (SSL) protocol.
* Uses transaction key authentication for ultimate security.
* Allows control over all phases of the customer's online transaction experience.
* Configurable transaction response integrates easily with merchant applications.
The Advanced Integration Method is included in osCommerce Online Merchant v2.2 and is available as a separate add-on for existing store owners who are running earlier versions of osCommerce Online Merchant v2.2.
{note}This payment module requires account settings to be defined on the Authorize.net Merchant Interface in order to function correctly.{note}
{note}This payment module requires PHP to support cURL or access to the "curl" program file.{note}
{toc:minLevel=2}
h2. Authorize.net Merchant Interface Settings
+MD5 Hash+
The MD5 Hash feature allows transaction responses to be securely received from the payment gateway. The MD5 Hash is calculated with a secret word that is configured in the Authorize.net Merchant Interface \-> Settings \-> MD5 Hash section.
h2. Configuration Settings
+Enable Authorize.net Credit Card AIM+
Setting this parameter to _True_ makes the payment method available to customers during the checkout procedure.
+Login ID+
API login ID for the payment gateway account.
+Transaction Key+
Transaction key obtained from the Authorize.net Merchant Interface.
+MD5 Hash+
The MD5 hash value securely verifies the results of a transaction. This must match the value entered in the Authorize.net Merchant Interface Security section.
+Transaction Server+
The following transaction servers are available to process transactions through:
|*Live*|The _Live_ server is used in live environments to process and receive payments from customers.|
|*Test*|The _Test_ server is only used to test transactions in a staging environment. No transactions are processed and no payments are made when transactions are being tested.|
+Transaction Mode+
The following transaction modes are available to process transactions with:
|*Live*|The _Live_ mode verifies and processes the credit card information for processing.|
|*Test*|The _Test_ mode only verifies the credit card information for testing purposes when the Live transaction server is being used. No transactions are processed and no payments are made when transactions are being tested.|
+Transaction Method+
The following transaction methods are available to process transactions with:
|*Authorization*|The _Authorization_ transaction method only authorizes transactions and must be captured manually through the Authorize.net Merchant Interface.|
|*Capture*|The _Capture_ transaction method authorizes and transfers the funds to your Merchant account.
+Payment Zone+
If set, this payment method will only be available to orders made within the defined zone.
+Set Order Status+
The orders status will be updated to this value when a successful transaction has been made.
+Sort Order+
The position to show the payment method on the checkout payment page against other available payment methods.
+cURL Location+
The location and filename of the cURL "curl" program file.
h2. Manual Installation (as an Add-On)
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:
* includes/languages/english/modules/payment/authorizenet_cc_aim.php
* includes/languages/espanol/modules/payment/authorizenet_cc_aim.php
* includes/languages/german/modules/payment/authorizenet_cc_aim.php
* includes/modules/payment/authorizenet_cc_aim.php
The standard languages definitions in English, Spanish, and German are provided in the add-on package. For additional languages, copy one of the existing language definition files to the appropriate language directory and edit the file with a text editor to edit the language definitions. The location of the language definition file must be in:
* includes/languages/<language>/modules/payment/authorizenet_cc_aim.php
When the files have been copied to their appropriate locations, the payment module will be available in the Administration Tool \-> Modules \-> Payment Modules listing where it can be installed.