Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 38 Next »

Integrating Authorize.net into your UltraCart account


The first set of steps are listed at Authorize.Net's web site.


  1. Log in to your Authorize.Net account
  2. Navigate: Home Page →  Account →  Settings
  3. In the first section of links click on "Payment Form". Then click on "Form Fields". Make sure none of the boxes have "Required" checked and then save. Click "Settings and Profile" on the left hand side of the screen.
  4. Click on "Transaction Version" and set it to "3.1" then Save.
  5. Click on "Email Receipts" and make sure "Email transaction receipt to customer" is not checked. Save.
  6. Click on "Card Code Verification". Authorize.Net suggested to UltraCart support that (N) be checked. Individual settings may vary by merchant. Save.
  7. Click on "Address Verification Service (AVS)". Authorize.Net suggested to UltraCart support that (B), (E), (G), (R), (S), (U) and (N) be checked. Individual settings may vary by merchant. Save.
  8. Click on "API Login ID and Transaction Key". A secret question will be asked to which you should know the answer. Answer the question and click submit. On the next page the transaction key will be disabled. Highlight the key with your mouse. Then choose Edit → Copy from the menu on your browser. This will place the transaction key in your computer's clipboard.
  9. You will also need to retrieve your "api_username": On the Settings page, under "Security Settings" section, Click on the link called "API LOGIN and Transaction KEY": which will provide you both items together than you must copy and paste into UltraCart's transaction gateway configuration page.
  10. Log out of Authorize.Net


The following steps will take place inside of UltraCart

Step 1

Log in to your UltraCart account and Navigate:

Home → Configuration → Checkout → Payments


From the "Credit and Debit Cards section simply select the card types you would like to accept.

You can access additional setting options by clicking on the "Settings" button shown below.

When you click on Settings the following popup will be displayed.


  • A - Allows the setting of Surcharge fees and percentages - Not Recommended.
  • B - "Charge appears on statement" (enter your business name as it will appear on their statement)
  • C - Charge During Checkout
    •  No
    • Yes (Recommended)
  • D - Collect card verification number (checked is the recommended setting for most merchants)
  • E - "After failed attempt" (Default setting is 3 attempts)

Simply click anywhere on the screen to close the window.

Step 2

To configure the Authorize.net 3.1 gateway click on the Connect Single button as shown below.

The next screen will present an alphabetical listing of our integrated Payment Gateways.  

Clicking on the check box to the left of Authorize.net 3.1 will expand the settings portion.


Your final objective is to enter the credentials that you were given when signing up with Authorize.net.

  • Authorize.Net API Login    
  • Authorize.Net Transaction Key   
  • Authorize.Net Send Recurring Billing Flag  (set to yes if instructed to when you establish your account)
  • Methods (select card types your accounts is configured to process).  You can also authorize E-Checks.

Click the Save button when finished.

Congratulations! Your UltraCart account is now configured to use Authorize.Net

Reviewing Transaction History of placed orders

When an order is placed that has not been successfully processed for payment, it will go into the Accounts Receivables department.  There, you can review the transaction responses in order to determine why the transaction failed. To see the transaction history of an order in the A/R department, navigate:

Main Menu > Operation > Order Management > Accounts Receivables


Click on the hyper-linked OrderID of the order (it should be color coded in pink signifying a "bad transaction"). Then scroll down below to the "Last Transaction" section. It appears below the "Payment" section and above the "Merchant Comments".

If there has been more than one transaction recorded, you'll also see a link that will take you to the complete transaction history.

When viewing the transactions the following authorize.net documents will provide you more details on the various response codes. These should help you determine the exact cause of the failed transaction:

Frequently Asked Questions

FAQ's - Click any question to reveal or hide the answer.)

 All of a sudden our orders are not processing, what could cause it to stop the credit card authorizations from working?

For various reasons, including higher than normal processing to excess chargebacks can cause the account to placed on hold. but the most common reason is accidental change of the Authorize.net transaction key. When you generate a new transaction key form within Authorize.net and existing transaction key's in use (such as the on inside UltraCart) will expirer after 24 hours. Failure to update the transaction key within UltraCart's configuration area will result in the transactions being rejected by the gateway due to a transaction key mismatch.

 I see UltraCart records the transaction ID for successfully authorizations within the "Transaction History" page of an order invoice. Can I use that to look the transaction up in Authorize.net?

Answer: Yes, you can look up all unsettled and settled transactions that have occurred within the last two years. See the following Authorize.net help doc for details: https://support.authorize.net/authkb/index?page=content&id=A714&actp=LIST

 If we configure UltraCart to require the "Company" field during checkout, is the company field passed to Authorize.net during the authorization?

Yes, the billing address company field will be passed along with the rest of the billing address and credit card details.

 Do you know circumstances why Authorize.net accepts or rejects transactions?

Yes. We track all the response codes that we get back from auth.net and there is a running list of what they mean here.

http://developer.authorize.net/tools/responsereasoncode/

They send both an error and a response code, or multiples of they have a need.

Helpful resources

https://www.authorize.net/support/CP/helpfiles/Reports/Transaction_Detail/Transaction_Detail_Reports.htm




  • No labels