Error 13: The merchant login ID or password is invalid or the account is inactive.
02/02/2022 17:12 PM
Response Reason Code: 13
Response Reason Text: The merchant Login ID is invalid or the account is inactive.
Important Note: AIM, SIM, and DPM are obsolete and in the process of being phased out. If you are using these integration methods, we strongly recommend that you use one of our modern connection methods to integrate with the Authorize.Net Payment Gateway. Visit our Developer Center and Upgrade Guide for more information on our current APIs.
This error indicates you are either posting the incorrect API Login ID within your script, connecting to a server that does not recognize your account, using an account that is inactive or when you do not include a valid Transaction Key or hash fingerprint with your transaction request. For security reasons we recommend always submitting a Transaction Key or fingerprint hash.
API Login ID:
- If you are posting your transaction requests to the gateway URLs https://test.authorize.net/gateway/transact.dll and you are using an account given to you by an Authorize.Net Reseller or from Authorize.Net Sales, you may encounter this error. The gateway URLs mentioned above only work with specific test accounts, available upon request by completing the form at https://developer.authorize.net/hello_world/sandbox/
- Please check your script and verify you are posting the API Login ID for the account in question. If you are not posting the correct API Login ID, or if you are not sending an API Login ID, please edit the script and confirm that the field
nameis set to the API Login ID that you may obtain from the Authorize.Net Merchant Interface. Please see the support article: How do I obtain my API Login ID and Transaction Key? for instructions on obtaining the API Login ID.
- If you are unable to log into your Authorize.Net Merchant Interface, this could indicate that your account is inactive. Please contact Merchant Support for assistance.
- If the account is active and the API Login ID is correct, please use the Data Validation Tool to validate the fields you are passing to us.
Transaction Key and Fingerprint Hash:
- If you are using SIM, make sure you are using a valid Transaction Key to generate and send a fingerprint hash along with your transaction request. The fingerprint hash should be submitted using the field
- If you are using SIM and submit a request for a Credit, Void, or Prior Authorization Capture (
PRIOR_AUTH_CAPTURE) you may encounter this error. For security reasons these transaction types must be processed by logging into the Merchant Interface directly, or by using a desktop application that uses AIM.
- If you are using AIM, please make sure you are sending a valid Transaction Key along with your transaction request. The Transaction Key should be submitted using the field
- If you are using an older Authorize.Net account and you submit a password instead of a Transaction Key, you may experience this error. Please ensure that you are submitting your Transaction Key instead.
- If you are using a third party shopping cart and you are receiving this error, please check with your shopping cart provider to confirm that your application can send the Transaction Key to Authorize.Net. Most up-to-date shopping carts should be able to store and use a Transaction Key.
- Some shopping carts, for backward compatibility with older connection methods, may provide the means to submit both a Transaction Key and a password. You should not use both the Transaction Key and the password simultaneously; doing so may also result in this error. We strongly recommend that you leave the password field blank.
- If the shopping cart has a field for a password but no field for the Transaction Key, please put the Transaction Key in the password field. Our system will recognize and validate the Transaction Key properly.
- While most shopping cart software will have a field for the Transaction Key, password, or both, some software may not. Please contact your shopping cart provider for details on how to upgrade to a more secure version of your shopping cart software.
Was this article helpful?