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 the Settings tab
• 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

• Do not mark any Authorize.Net "Form Fields" as "required" in the settings.  For more information, please see Why do Authorize.Net transactions fail with "The transaction was unsuccessful" or "{field} is required"?
• Please do not change the Authorize.Net "Direct Response Delimiter" settings.  For more information, please see Authorize.Net Direct Response Delimiter Settings

LESSONS FROM OTHER CHARGIFY MERCHANTS

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. Obscure setting in Auth.net can make all transaction fail! Within the Authorize.net settings, there is a section called "Card Code Verification (CCV) Settings". And within that section, there is a setting that dictates what Auth.net should do if the 3-digit security code on the customer's credit card (the "CVV" code) is missing or does not match what the bank says it should be. There is apparently a checkbox that makes this code required for every transaction. We do not submit the code with every transaction. We only submit it when we store a credit card in Auth.net's CIM data "vault". The default setting for this checkbox is OFF, and it should stay that way. If you check the box, then transactions will fail. Worse yet, you will get an error message that is very vague and just says the transaction failed.

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.