Troubleshoot common Authorize.Net credit card errors.

Skip ahead to 


Authorize.Net credit card errors happen for a number of reasons. This article will provide steps for how to resolve 3 of the most common credit card errors that users experience: Authorize.Net Test Mode,  Error 123, and declined Authorize.Net orders. 

Authorize.Net Test Mode

What is Test Mode? 

Test Mode allows you or your developer to test your website without submitting live payments. While in Test Mode, transactions will not be saved to the database or be viewable in search results or reports.For security reasons, all new Authorize.Net accounts are in test mode. 

Turning off Test Mode

To take your account out of Test Mode, please follow these steps:

  1. Log into the Merchant Interface at
  2. From the main menu, select Account > Settings
  3. Under the Security Settings section, click Test Mode
  4. Click Turn Test OFF to disable test mode for your account. 

Error 123

What is Error 123? 

This error shows that a user's personal Login ID is being used to connect a website or solution to the payment gateway. This error occurs if an Account Owner, Account Administrator, Transaction Manager, or Account Analyst login ID is used for website or software implementation.  Personal login IDs may not be used to connect to Authorize.Net for security reasons.

Resolving Error 123

To resolve this issue, the API Login ID and Transaction Key will need to be generated and added to your software's configuration so the website may connect to Authorize.Net properly.

To obtain the API Login ID:

  1. Log into your Merchant Interface.
  2. Click Account from the main toolbar.
  3. Click Settings in the main left-side menu.
  4. Click API Credentials & Keys.
If an API Login ID has already been generated, it will be visible here. If an API Login ID needs to be generated, you must enter the answer to your Secret Question in order to see the API Login ID.

Authorize.Net Declined Orders

Credit card transactions may be declined for a number of reasons. You can view declined Authorize.Net orders by searching the Authorize.Net Transaction ID in Web Shop Manager. To determine the reason for a decline, you need to review the ID transaction response from the payment gateway account. 

Viewing declined Authorize.Net orders in WSM

  1. In Web Shop Manager, hover the mouse over Orders and click All Orders.
  2. Identify the declined Authorize.Net order and click the Edit icon 20190815__221428
  3. In the Payment Information section, scroll down to Transactions
  4. Copy the Authorize.Net Transaction ID number in the ID field. 

Determining reason for a decline in Authorize.Net 

  1. Log into your Merchant Interface.
  2. Click Transaction Search from the main toolbar.
  3. Enter the WSM Transaction ID to look up the transaction.
  4. Click Search at the bottom of the page.
  5. Click the appropriate Transaction ID to review the transaction details.

On the Transaction Detail page, the transaction status Declined is displayed directly under the Transaction ID. A brief reason for the decline may be provided in parentheses.

For more information, see Authorize.Net Support Center.

Editing declined Authorize.Net orders in WSM

  1. In Web Shop Manager, hover over Reports and click Orders in Progress
  2. Highlight the declined order and click the Edit icon 20190815__221428
  3. Under Payment Information, edit customer information as needed. 
  4. Click Save.