Integration with Authorize.Net Through the AIM Plug-in

Attention: Authorize.Net has announced the discontinuation of support for its Hosted CIM used by the plug-in. We recommend that you instead use the API plug-in for configuring integration with Authorize.Net. For more details, see To Replace a Processing Center that Uses a Discontinued Plug-In.

MYOB Advanced offers three payment plug-ins for implementing integration with Authorize.Net. For a comparison of the features of the plug-ins, see Means of Integration with Authorize.Net.

In this topic, you will read about the details of integration for the Authorize.Net AIM plug-in. You will also learn how to set up and test a connection to Authorize.Net with the plug-in.

Integration Details

The plug-in uses Advanced Integration Method (AIM) to submit transactions to the payment gateway. It also uses the specific format of the transaction response returned by the gateway. To comply with the format, you should make sure that the settings of a direct response are configured as follows in the Merchant Interface: A comma is set as the default field separator, and field encapsulation is blank. You can do this under the Settings > Direct Response menu.

You use an MYOB Advanced form to fill in the customer's credit card details, and the system encrypts sensitive credit card information and stores it in the MYOB Advanced database. This behavior is not PCI DSS–compliant; thus, we recommend using the Authorize.Net API plug-in instead.

Integration with Authorize.Net also requires that you have a valid SSL certificate and that your website is capable of initiating both client- and server-side SSL connections.

Support of Multiple Currencies

Authorize.Net supports multiple currencies. You select the currency to be used for processing transactions when you set up the merchant account. Thus, you need to make sure that all accounts involved in the processing of payments are denominated in the currency you have specified in Authorize.Net for your merchant account. For each currency, you need to apply for a separate merchant account with Authorize.Net and configure a dedicated processing center in MYOB Advanced.

Support of Fraud Detection Services

The plug-in supports fraud detection services enabled in the Authorize.Net Merchant Interface when a user adds a new credit card for a customer by using the Authorize.Net-hosted form.

For example, if you turned on the address verification service provided in the Authorize.Net Merchant Interface, after you have integrated MYOB Advanced and Authorize.Net, the address will be verified by this service when a user adds a new credit card for a customer.

Integration Setup

To start processing payments from customers with Authorize.Net, you should perform the following steps:

  1. You sign up with Authorize.Net. You apply for a payment gateway account and a merchant account if you do not have these accounts. A merchant account is an agreement with a merchant bank that you use to accept payment by credit and debit card. Authorize.Net provides you with the URL and the login credentials to the Authorize.Net Merchant Interface. You sign in to the Merchant Interface, and create your account API login ID and transaction key. The processing center will use these two values to authenticate you and ensure that you are authorized to submit transactions. For details, see the Authorize.Net official site.
    Note: You can also create a sandbox account at Authorize.Net to get the URL and credentials to test payment processing.
  2. You configure the Authorize.Net processing center in MYOB Advanced by using the Processing Centers (CA205000) form.
  3. Optional: You create a vendor account for Authorize.Net by using the Vendors (AP303000) form and specify the accounts (and subaccounts) for recording any fees and charges applied by the center for processing your credit card transactions.
  4. You create a payment method for each bank operator whose cards you are going to process (such as Visa, Mastercard, or American Express), and associate payment methods with the Authorize.Net processing center. You can then use these payment methods as templates to create customer payment methods. For details, see To Add a Payment Method for Payment Processing.
  5. You collect credit and debit card details from your customers, and create customer payment methods for all customers whose payments you want to process with Authorize.Net. For details, see Configuring Customer Payment Methods.
  6. You test payment processing with Authorize.Net, as described in the next section.

Authorize.Net Test Mode

After initial setup, your Authorize.Net account is placed in test mode by default; you can view a red bar with the warning in the Authorize.Net Merchant Interface. In test mode, Authorize.Net does not process transactions and always returns a successful response. Thus, a test payment never gets charged.

Alternatively, you can create a sandbox account at Authorize.Net and use the URL and the login credentials provided for the sandbox account.

The MYOB Advanced plug-in also has a parameter whose value controls whether a transaction sent to the payment gateway is marked as a test transaction. It can be used to test payment processing when your Authorize.Net account is in live mode.

To switch test mode off, perform the following steps:

  1. Log in to the Authorize.Net Merchant Interface, and switch off test mode on the Authorize.Net side.
  2. Reconfigure the Authorize.Net processing center in MYOB Advanced. To do this, on the Processing Centers (CA205000) form, change the TESTMODE value to 0. Save your changes.
    Note: If you have configured the plug-in to use the URL and login credentials for your sandbox account, you need to change these values to production ones and then switch off test mode on the Authorize.Net side.