Our documentation has moved!

You are currently viewing a legacy version of our help articles.
For the most up-to-date version, please use the new Chargify Help & Support Site.

Authorize.Net (USA) Payment Gateway Information and Set Up

Authorize.net works with Merchant Accounts (and therefore, Chargify merchants) in these countries:

  • USA

Authorize.net works with customers/consumers in these countries:

  • All countries
  • Product prices in US dollars
  • Customers purchasing in other currencies will be charged in their local currency at the exchange rate in effect at the time of the transaction

Requirements when using Authorize.net gateway

  • You DO need the Customer Information Manager ("CIM") option turned on. It will usually cost extra money per month, usually $20/month. (see note below from customer if you just added CIM!)
  • You do NOT need the Automatic Recurring Billing ("ARB") feature.

Currency Settings

Authorize.net supports transactions in US Dollars.

Compatible Banks... where to get your Merchant Account

Authorize.net works with merchant accounts at most banks in the USA, such as Wells Fargo, Bank of America, etc.

If you need an Authorize.net account and a merchant account, contact one of Chargify's Partners, who will get you set up wtih everything you need within a week or so.

Can I run test transactions against Authorize.net before I use my production Authorize.net account for real transactions?

Yes. Do NOT use Authorize.net's Test Mode in one of their regular accounts.  Instead, get a "Developer Account". You can get one here.

Enter the Developer Account credentials they give you into your Chargify test site settings.

Later, you can use your real/production Authorize.net credentials with your Chargify production site.

Chargify sites that are in test mode will only connect to an Authorize.Net "Developer Account" gateway.  Chargify sites that are in live mode will only connect to an Authorize.Net "real" gateway account.

Where do I find my API Login ID and Transaction Key

The credentials you will need to enter on Chargify's Settings tab ARE NOT the same as the credentials you use to log in to the Authorize.Net web interface.

You can find your credentials (and generate new Transaction Keys) as follows:

  • Log in to the Authorize.Net web interface
  • Click on Settings
  • Click on API Login ID and Transaction Key, which is found in the General Security Settings section
  • Follow the on-screen directions

Authorize.Net Required Settings

How Do I Configure Card Code Verification (CCV or CVV)?

In Authorize.Net Admin Interface

  • Configure settings to reject transactions when the card code does not match: Settings -> Card Code Verification -> Check "Does NOT Match (N)"
  • DO NOT set "Card Code" to "Required" under Settings -> Payment Form -> Form Fields (setting this to Required here effectively rejects any transaction where the CVV is NOT provided, which will cause recurring transactions to fail!)

At this point, CVV checking is enabled for your gateway account, and Authorize.Net will reject transactions where the acquirer indicates that the CVV on the card does not match the one submitted. This may seem incompatible with recurring billing, but it is not! The key to understanding why is to know that Authorize.Net will only run this CVV rejection filter IF we both send them a CVV code with the transaction AND it does not match. If we do not send them a CVV code, then they will not reject the transaction! But you're not done yet!

In Chargify Admin Interface

  • Mark the CVV as required in Chargify: Settings -> Fields -> Check the "Required?" box for "CVV"

With this setting, Chargify will make CVV a required field for the following: Hosted signup page, Hosted card update page, Admin subscription creation page, Admin card update page, API subscription creation, API subscription edit for card update.

Chargify (and, in fact, no merchant or system) is allowed to store the CVV. So, we only send it to Authorize.Net when we have it... and that is when the cardholder provides it to us the first time. When we have it, we send the CVV to the gateway on the initial transaction, which is either the first purchase we run against the card after it is added or updated, or a $1 authorization-only transaction (if there is no money currently due). This allows Authorize.Net to run the CVV rejection filter when the card is first stored. Thereafter, there is no need to verify it any longer. Either it was correct, and we stored the card, or it was incorrect, and we returned a decline response to the cardholder.


Recurring billing is compatible with the CVV rejection filter provided by Authorize.Net. This rejection filter will only be run when a CVV is provided, and we only provide the CVV when it is both available and has a bearing on the transaction (i.e. the first time we see a new card).

By following the above instructions, Chargify will require cardholders to enter the CVV for their card, and Authorize.Net will verify that CVV before the card is stored or used to make the first purchase.


  1. If you just added the CIM option, it will not be available to Chargify for 24-48 hours. You will get an error message when trying to process credit card charges. The error will be something like "Invalid credit card" or "Transaction could not be processed". Things will "magically" start to work 24-28 hours after you have turned on CIM.

  2. Avoid settings under "Payment Form" in Authorize.Net!  Marking fields as "Required" in the "Payment Form" settings make those fields required for every transaction. We do not submit every field with every transaction - for example, we only submit the CVV when we store a credit card in Auth.net's CIM data "vault". The default setting for most of these checkboxes is OFF, and they should remain on the defaults.

  3. Another setting that can make all transactions fail! If you're using Authorize.Net's Fraud Detection Suite, there are many settings in there that can affect our ability to process transactions for you. For instance, one merchant was unable to process any transactions because he had his "Velocity" set to 1, which meant that Authorize.Net would refuse any transactions after the first 1 for the day. Note that transactions performed within Authorize.Net worked fine all day long, but any transactions attempted from an outside service like Chargify were declined. It was especially mysterious because we perform a $1 auth-only on every new card before even trying the real amount to be charged, so... even his first Chargify signup of the day failed, since our initial $1 check on the card counted as his 1 transaction for the day.

Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request


  • 0
    Paul Boomer

    How does one test the API connection between Chargify and Authorize.net in test mode when the test/development account within Auth.net does not have the CIM option? As predicted, when testing with the hosted signup page, we receive the "Customer Information Manager is not enabled" error message.

    Constructive criticism - Starting with Chargify has been a tad frustrating as it seems everywhere we look for answers to questions, we're thrown in to an infinite loop for what'd seem like basic setup questions. You start with great information but the information seems just short of a full answer. For instance, you talk about the need to test your site but, you don't fully explain - or it's a rather confusing explanation - how to test. Videos and screen shots alone will do you and ultimately your customers a great deal of good.

  • 0
    Michael Klett

    Hi Paul, thanks for the feedback.  Please be aware that you can enable CIM within an Authorize.Net test/development account.  From what I understand, the details around this sometimes change (i.e. sometimes it is already enabled, sometimes it is not) but you should be able to enable it either way.



  • 0
    Arif Khan

    While filling out the application for Authorize.net... a little confused as to what Payment Processor to select on this screen? 

  • 0
    Frans van der Lee

    In Lessons from other Merchants above, #2 is confusing me where it states "There is apparently a checkbox that makes this code required for every transaction." - I don't have that checkbox in my CCV settings on authorize.net - does anyone know if it is no longer there? My options are below, I'm assuming if I don't check the box next to "Does NOT Match (N)" then I will have no CCV verification!

    Reject Transaction If Card Code value...

        Does NOT Match (N)

        Is NOT Processed (P)

        Should be on card, but is not indicated (S)

        Issuer is not certified or has not provided encryption key (U)

Please sign in to leave a comment.
Powered by Zendesk