When attempting to connect to the AIM API, I am receiving error 13 “The merchant API login ID is invalid or the account is inactive.” Why?
Error 13 may be received for several reasons. If you are using a test account, please ensure you are using your API Login ID which can be obtained from the Settings section of the Merchant Interface. Test accounts should use the following URL to post data to when attempting to use the AIM API: https://test.authorize.net/gateway/transact.dll. If you are using a live production account you should be posting to https://secure.authorize.net/gateway/transact.dll. If you have followed the steps above and are still receiving this error you should change your post URL to: https://developer.authorize.net/tools/paramdump/index.php. This URL is a script designed to show you the name/value pairs being submitted from your script. You will see if the information being posted is properly formatted.
- I am attempting to connect to the CIM or ARB API and am receiving error E00007 "User authentication failed due to invalid authentication values." Why?
- Why do I get the error message "Specified class not registered in registry" when attempting to connect to an Oracle database?
- How do I login to a non-production instance (i.e. Sandbox, Pre-Release, etc.), with a session id, or other API versions?