11-22-2017 06:39 PM
And we have reset the transaction key, it did not work....
11-22-2017 07:09 PM
Have you see the error response tool for error 13
https://developer.authorize.net/api/reference/responseCodes.html?code=13
CODE: 13
EXPLANATION: The merchant login ID or password is invalid or the account is inactive.
INTEGRATION SUGGESTIONS: 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, or using an account which is inactive. Please follow these steps to ensure that your software is connecting correctly:
name
is set to the API Login ID that you may obtain from the Authorize.Net Merchant Interface. Please see the Getting Started Guide at https://www.authorize.net/content/dam/authorize/documents/gettingstarted.pdf for instructions on obtaining the API Login ID. For further information on the API Login ID, Transaction Key, or Test Mode, please check out our online video tutorials at https://www.authorize.net/videos/.
Hope it helps .
11-22-2017 08:34 PM
yes,we have tried the suggestion above all,and our account is correct but the error occurred when we change to the sandbox environment.
11-22-2017 10:59 PM
Hi @YYindependant,
Are you using sandbox credentials for the sandbox environment? Live production credentials only work on the production system, and sandbox credentials only work on the sandbox system.
Have you tried entering your sandbox credentials into one of the sample requests on the "Try It" tabs on our API Reference Guide? If the credentials work on a request to the sandbox there, you know the credentials are good and you're doing something in error in your code. If they don't work on the API Reference, either, then you're not using the correct credentials.
11-24-2017 09:11 AM