Current Authorize.Net AIM Module Release: 1.43
For sale via MIVACentral - $150.00

Current QuickCommerce AIM Module Release: 1.43
For sale via MIVACentral - $150.00

Miva Merchant Compatibility: 2.22 to 4.24

The AIM Modules versions are compatible with all versions of Miva Merchant from 2.22 to 4.24. The modules require no special additional files such as return scripts or commerce libraries, but they do require that the site is running Miva Empresa configured in a manner that supports OpenSSL communications at the programming level.

Features/Advantages

CVV2
The CVV2 option is selectable by card type. If you request CVV2 then a card code field will be displayed that the shopper can enter their card code into. Even if you request CVV2 it won't mean that the customer has to supply it. Depending on your account settings, and the card the shopper is using, the transaction server may allow a transaction even without a CVV2 card code. This is a good thing, because then you don't stop people from purchasing if they have cards that really don't have a CVV2 card code, and yet you have the control via your account settings to reject transactions from those cards that should have a CVV2 card code assigned to them, but that the shopper hasn't given you.

Supports E-Check payments
The system will offer your customers the option to pay with electronic checks using the AIM E-Check method. This feature requires your AIM gateway and Merchant accounts are setup to accept the E-Check transactions.

Support for five credit card types
This module supports Visa, MasterCard, American Express, Discover and Diner's Club.

Individualized sub-messages for E-Check and each credit card type
For E-Check you can use this feature to explain where someone would be likely to find the account number and routing number on a physical check so they would know what numbers to enter when they are requested. For credit cards, this sub message would be used to describe specific instructions or information for the shopper. Here is where you might want to explain about CVV2 card codes, or your policy on refunds, or whatever you want related to credit card processing. Since there is a separate message for each card type you can use this feature in conjunction with the card level CVV2 configurations so that only the cards that you want CVV2 codes for even mention them, and for those you do gather CVV2 codes for you can give precise instructions to the shopper of where to find the codes on cards of that particular type.

Supports "Transaction Key" based transactions
The AIM API supports sending a transaction key rather than sending a password, so with this module you have control over whether you will send the username and password, or username and transaction key to the transaction server for each transaction.

Supports transaction id based capture of previously authorized transactions
In Authorize-Only mode the module sends the all the vital information to the transaction server in real time, such as the credit card number, card code, and expiration date, and does not store it on your web site. As part of the authorization data returned the transaction server provides the module with a transaction id that uniquely identifies the authorization. The system stores this id rather than dangerously storing the sensitive data such as credit card numbers and CVV2 card codes. It uses this transaction id later during order processing so that you can capture the previously authorized funds when you are ready to ship the order.

Eliminates the need for a commerce library
Improper or incomplete commerce library installation is one of the most common reasons why a Miva Merchant account won't be able to use their real time card processing after an installation or upgrade. It's one more thing that can delay a launch, and one more thing that can go wrong later. And since a commerce library must be installed by the hosting provider it is also one more possible support issue you may have to wait for them to resolve.

Increases transactions speed
By the elimination of the need for a commerce library and full compliance to the AIM standard you will experience increased transactions speed over alternative methods.

Reduces transaction problems
By taking advantage of the AIM standard over previously available transaction methods (WebLink, ADC), elimination of the need for a commerce library, and the module's well thought out and implemented communication design, you will reduce transaction problems.

Most recommended method
The AIM standard is the newest, most secure and recommended method to submit transactions to Authorize.Net or QuickCommerce payment gateways.

Documentation

The following documentation for the AIM modules is in the Adobe Acrobat Portable Document Format. If you can't read the documentation you will need to download Adobe Acrobat Reader.

Authorize.Net AIM Module 1.43 Documentation

QuickCommerce AIM Module 1.43 Documentation