Authorize.net is one of the many payment processing providers we connect with through our Payment Gateway Feature.
To connect Authorize.net account, you will need both your Authorize.net API Login and Transaction Key. This is not the normal credentials you use to login to your account, but the credentials for connecting the two systems together through the API.
Here are the instructions for finding the Authorize.net API login and transaction key from Authorize.net. They are included below, but can also be found here.
- Log into the Merchant Interface at https://account.authorize.net. Click Account from the main toolbar.
- Click Settings from the menu on the left.
- Click API Credentials and Key from the Security Settings section.
4. On this page you will find your API Login ID
5. In order to obtain Transaction Key - under Create New Transaction Key, enter the answer to your Secret Question, click Obtain: 'New Transaction Key', and click Submit
NOTE: Authorize.net only displays a given Transaction Key when it is first generated. If you generate a new Transaction Key, any software or code using the previous Transaction Key will need to be updated with the new Transaction Key to avoid errors.
- If the "Disable Old Transaction Key" box is not checked, the old Transaction Key will automatically expire in 24 hours. When the box is checked, the old Transaction Key will expire immediately. If you have current software installations, do not check this box unless you need to immediately cease all payment processing through your software setup. By not checking the box, the old Transaction Key would remain valid for 24 hours, giving you time to update your software to use the new Transaction Key.
- Be sure to store the Transaction Key in a very safe place. Once it has been generated, it will not be viewable again. Do not share it with anyone, as it is used to protect your transactions.
- For Server Integration Method (SIM), the Transaction Key is also used to create a unique transaction fingerprint. Using the Transaction Key and a few pieces of information specific to the transaction, a script on the merchant's Web server uses a complex mathematical algorithm to generate a document fingerprint. This fingerprint is submitted along with the transaction information to the gateway.
- Before accepting the transaction, the gateway will use the Transaction Key and the transaction's data to recreate the unique transaction fingerprint. If the fingerprint generated by the gateway matches the fingerprint submitted with the transaction by the merchant, the transaction is accepted for authorization. If the fingerprints do not match, the origin of the transaction cannot be authenticated, and the transaction is rejected.
- For other APIs such as the Advanced Integration Method (AIM), Card Present (CP), Automated Recurring Billing (ARB) and Customer Information Manager (CIM), the Transaction Key is encrypted along with all other transaction data when it is sent to Authorize.Net, and is directly used to authenticate requests submitted to the gateway. If a request cannot be authenticated using the Transaction Key , the request is rejected.
- You may generate a new Transaction Key as often as you wish.