Overview
This article explains what to do if you are attempting to run Credit Cards for Authorize.net and are presented with an "Unable to Authenticate" error.
Symptoms
‘Unable to Authenticate’ errors in RMA. See below for an example:
Cause
There could be multiple causes:
- Authorize.net Services may be down. Check their status by going to https://status.authorize.net
- The Payment Gateway.DLL or Authorizenet.DLL could be out of date.
- The Login ID or Password Transaction Key could be incorrect.
- Your copy of Windows no longer works with your credit card provider. This is usually to changing PCI compliance or security laws and standards. (As of now, anything older than Windows Server 2003 is not accepted).
Resolution
- Try a network client install on the PC that is having the issue, or try to manually re-register those DLL’s.See the help tips below:
- Reset your login ID and Transaction Key. This would be done through your authorize.net payment gateway, and usually done online.
- In Authorize.net, go to Settings, and then find ‘APIs/Transaction keys’ on the page. You can verify your Login ID and generate a new transaction key there. From there, add it in RMA by going to Lists>Accounting Setup>Credit Card and eCheck/ACH Pricessor Codes. See below:
- In Authorize.net, go to Settings, and then find ‘APIs/Transaction keys’ on the page. You can verify your Login ID and generate a new transaction key there. From there, add it in RMA by going to Lists>Accounting Setup>Credit Card and eCheck/ACH Pricessor Codes. See below:
- If your system is on Windows 2003 / Windows XP or older, then you need to update your operating system to work with credit card processing. Contact ARS for a quote on what we can do to ensure that your system is up to date!
