(USA) Payment Gateway Information and Set Up

Authorize.Net works with merchant accounts in the US only, but can work with customers/consumers in the following areas:

  • All Countries
  • Product prices are in USD
  • Customers purchasing in other currencies will be charged in their local currency at the exchange rate in effect at the time of the transaction


In terms of technical requirements when appropriating an Authorize.Net account, you will need to know the following:

  • You DO need the Customer Information Manager (CIM) option turned on.

  • You DON’T need the Automatic Recurring Billing (ARB) feature.

  • You will also need a merchant account with a compatible bank. Authorize.Net works with most merchant accounts, such as Wells Fargo, Bank of America, etc. If you need an Authorize.Net account and a merchant account, please contact one of Chargify’s partners who will help get you setup with everything you need within a week or so.

Response Reason Codes

In most cases, when a transaction can’t be processed - Authorize.Net will respond with a number of fields that can help you diagnose the issue. The important fields to look at in the gateway output log, are response_code, response_reason_code and response_subcode. The first two (response_code and response_reason_code) are very useful at diagnosing an issue, as there is a publically accessable site that you can view here (Response Code Descriptions) which details the various combinations and the possible description of the issue. However, there are a number of combinations that don’t have any descriptive text at all, and those are:

Response Code Response Reason Code
1 1
2 2
2 3
2 4

Need to understand an response code? Here is a link to’s current response codes.

In these cases, the error is usually (not guaranteed) that the merchant isn’t “white listed” for that customers card. In this case, they will need to call their issuing provider and ask about the decline. In most cases, the issues can be resolved. In these cases, the customer will most likely have to call their issuing provider to solve the potential issue.

AVS & Anti-Fraud Settings has a comprehensive article that explains all of the AVS settings. It’s worth reviewing to familiarize yourself with the AVS codes. This is especially helpful when examining transaction responses from

Response Delimiter Setttings

Due to a recently discovered issue, Chargify currently requires that you not change the Authorize.Net Direct Response Delimiter Settings. If you do, some transactions that rely on AVS may fail. Additionally, if these settings are changed, some successful transactions may refuse to allow refunds, generating the error “The credit card number is invalid”.

You can restore your default settings by following this guide:

  1. Log In to your Authorize.Net control panel and click on “Settings”

  2. From the Settings screen, select “Direct Response”

  3. Make the following selections under Direct Response Delimiter. (Note: These are the defaults)

  • Delimited Response: Yes

  • Default Field Separator: , (comma)

  • Field Encapsulation Character: (none)

We will soon be fixing this problem so that your settings do not affect our ability to parse certain responses from Authorize.Net. If you have been affected by this problem, in particular if you receive the error “The credit card number is invalid” when attempting to issue a refund, contact us and we can usually help you fix the issue.

Why transactions fail with “The transaction was unsuccessful” or “{field} is required

One reason is that your Authorize.Net configuration might be “Requiring” certain fields that are a part of the Authorize.Net Payment Form settings. These settings actually affect API transactions as well, and all should be unchecked.