Authorize.net Setup

To set-up Authorize.net as the gateway on your event site, you'll need:

  • The ability to login to your Authorize.net account.
  • A current software subscription and a Chair login for the event site

Steps required:

  1. Login to Authorize.net account
  2. Generate login/key - copy and paste in an accessible place for later use.
  3. Adjust security settings
  4. Enable Customer Information Manager (CIM), for card vaulting, if needed.
  5. Login to Software (Event Site) and paste in API codes and select settings.

Important!   You will NOT be able to view the API Transaction Key (password) once you navigate away from the page it is issued on.   If you already have an API Login ID, but don't know the Transaction Key, you must generate a NEW API Login ID and Transaction Key set.

If your Authorize.net gateway account is in use on another web or software application, be aware that generating a new API Login ID and Transaction Key will also affect those connections.     A single Authorize.net account will use the same account settings for each application (which may prevent you from using both applications simultaneously).  This issue is most commonly encountered when an Authorize.net gateway is already in use with an online donations page and setting up an API login for the software auto-updates the settings for the existing account to match which can cause the existing application to stop working.   Contact your Authorize.net account representative for assistance in configuring your gateway for simultaneous use on different online applications.

1.  Login to your Authorize.net account:

1.  Login to your Authorize.net account:
Navigate to API Login screen

Go to Settings > Security Settings > Click on  API  Login ID and Transaction Key

2a.  To Create an initial API Login ID/Transaction Key on a New Account:

2a.  To Create an initial API Login ID/Transaction Key on a New Account:

1.  If your gateway does not yet have an API Login ID and Transaction Key, the header will begin with "Obtain"

2.  Answer the security question.  If you don't recognize the question, go to User Profile and select a different question.

3.  Submit

Copy API Login ID and Transaction Key

Copy API Login ID and Transaction Key

2b.  To Generate a New API Login ID/Transaction Key:

2b.  To Generate a New API Login ID/Transaction Key:
  1. Note that you have the option of disabling the existing Transaction Key immediately or allowing it to be usable for 24 hours.   If you elect NOT to disable it, the new and old Transaction Keys will work for the next 24 hours.  You should run a live test transaction after the 24 hour transition period to verify that the valid Transaction Key is being used by the software.
  2. Submit to generate new API Login ID and Transaction Key.
3.  Recommended:  Lower your security settings to reduce transaction failures:

Go to Account > Settings > Security Settings > Address Verification Service

Address Verification Service (AVS):

Address Verification Service (AVS):

Important!   If your ticket forms do not collect complete billing address information for each guest (via required fields), your AVS settings MUST be lowered.    

Card Code Verification (CCV):

Card Code Verification (CCV):

Go to Account > Settings > Security Settings > Card Code Verification

4.  Verify/Enable CIM to allow card vaulting:

4.  Verify/Enable CIM to allow card vaulting:

Go to Tools > Customer Information Manager > Sign up . . .

Note:  If CIM is already enabled on your account, a Customer Information Manager page will appear, and a link to "Discontinue Customer Information Manager (CIM) and terminate your CIM Service agreement" will appear below the Profile form.

4a.  Accept Terms and Conditions:

4a.  Accept Terms and Conditions:

Note:  Authorize.net has recently discontinued the $20 monthly fee for CIM on new accounts, so if you have a new Auth.net gateway, you should enable CIM now.          

If you have an older Authorize.net account and have previously paid the fee, that fee structure still applies.   You may choose to wait to enable CIM until you are ready to vault cards if you want to avoid unnecessary fees.

4b. Confirm that CIM has been enabled:

4b. Confirm that CIM has been enabled:

5.  Paste API codes into event software and specify settings:

5.  Paste API codes into event software and specify settings:

Login to your event site.

Go to:  Admin > Site Settings > Payment / Credit Card > Setup Gateway (Credit Card menu tab is only visible when logged in with Chair role).

1. If CIM is enabled on your Auth.net account, select Authorize.net - Card Vaulting Support CIM from the dropdown.

  • If CIM is not enabled on your Auth.net account, select Authorize.net - Card Not Present from the dropdown.

2. Choose Types of Credit Cards your gateway/merchant account will accept from dropdown

3. Paste in your API Login ID into Gateway API Login

4. Paste in Transaction Key into Gateway API Password

5. Save

 

 Finish setting up credit card processing on your event site:

 Finish setting up credit card processing on your event site:

Go to Admin > Site Settings > Payment / Credit Card > Credit Card General:

1. This descriptor will appear on the receipts generated by the software as the source of the transactions.  Ideally, it should match what will appear on your guests' credit card statements (this is dictated by your merchant account).

2. This box must be checked to allow vaulting or storing cards in your gateway for later access.  If unchecked, the check-in screen will not display the form for vaulting credit cards.   You can leave the box checked if you plan on vaulting cards, but are not yet set-up to do so.

3. SAVE

Be sure to test with a live online transaction (with vaulting or without vaulting)