Authorize.net Setup
Important: Returning customers can migrate (copy) credit card settings from a previous event site.
This article walks you through the process of connecting your event site to your authorize.net account.
Once your event site is setup for credit card processing using your Authorize.net account, there are additional steps necessary to confirm/enable card vaulting and confirm/edit the fraud settings in your Authorize.net account.
Instructions for those steps can be found here:
Setting up Authorize.net for Vaulting Credit Cards
Authorize.Net Fraud Detection Settings
To set-up Authorize.net as the gateway on your event site, you'll need:
- An e-commerce type Authorize.net account, with the Customer Information Manager option.
- The ability to login to your Authorize.net account.
- A current software subscription and a Chair login for the event site
Connecting your Authorize.net account to your event site:
- Login to Authorize.net account
- Obtain/Generate login/key - copy and paste in an accessible place for later use.
- Login to Software (Event Site) and paste in API codes and select settings.
A. Obtaining Your Authorize.net API Login/Key in "New Authorize.net"
Authorize.net is rolling out a major overhaul of their website. If the images below do not match your view - scroll down to view instructions illustrated on Auth.net's retiring layout.
1a. Login to Authorize.net > Account > Account and API Settings
2a. Obtain/Generate API Login and Transaction Key
- The API login is used to connect your Auth.net account to a software platform. Once generated, it does not change.
- If you are connecting your auth.net account to an external platform for the first time, you will have to generate both the API login and a transaction key (we provide these instructions as a courtesy to our customers - but don't have access to an Auth.net account that hasn't already generated a api login so can't show you that screen). If you need help generating the api login, contact an Auth.net rep or their help desk for assistance.
- The Transaction Key is the "password" that protects the connection between external websites and your Auth.net account - and can be changed as needed for security reasons. The same transaction key is used on all external connections. Be aware that new transaction keys only display ONCE - so be sure to copy it to your clipboard before leaving the screen - then pasting it directly into your event site (step 5) or a password manager if you're using it on multiple platforms.
- If you need to generate a new Transaction Key - you must update it everywhere you're using an API connection from external platforms to your Auth.net account.
3a. Paste API codes into event software and specify settings:
Login to your event site, then Go to: Site Settings > Customize Your Site > Payment/Credit Card > Setup Credit Card Gateway (this tab is only visible when logged in with Chair role).
Optional: Add identifier to track where transactions originated
If you are processing credit cards on more than one event site, you can add a flag to each transaction that will allow your bookkeeper to trace/reconcile transactions to the event site that generated them.
4a. Test witha live transaction and review other Auth.net settings
B. Alternate Instructions for Old/Retiring Auth.net Website
1b. Login to your Authorize.net account > Account > Settings
Navigate to API Login screen
Go to Settings > Security Settings > Click on API Credentials and Keys
2b. To Create an initial API Login ID/Transaction Key on a New Account:
Note: We provide these instructions as a courtesy to our customers - but we do not have access to a "new" auth.net account - so this image is out-of-date. . . If you need help creating your first API login and transaction key, contact a Auth.net rep or help desk for assistance.
Copy new API Login ID and Transaction Key
3b. To Generate a New Transaction Key:
If you are connecting an existing Auth.net account, you will use the same API login and transaction key on all applications. The API login does not change - the transaction key acts as a password that can be updated as needed to ensure security. If you Auth.net is in use elsewhere - you'll find the API login on the screen shown below. If you have the Transaction Key stored, you can use it on your event site.
If you don't have access to the current Transaction Key- create a new one - then replace everywhere Auth.net is in use. The new transaction key will work immediately. The previous transaction key will continue to work for 24 hours unless you choose to disable it immediately. Be sure to update on ALL software applications before the old key expires or is disabled.
4b. Paste API codes into event software and specify settings:
Login to your event site, then Go to: Site Settings > Customize Your Site > Payment/Credit Card > Setup Credit Card Gateway (this tab is only visible when logged in with Chair role).
Optional: Add identifier to track where transactions originated
If you are processing credit cards on more than one event site, you can add a flag to each transaction that will allow your bookkeeper to trace/reconcile transactions to the event site that generated them.
