We've been getting the following error after a successful DPM charge:
"The following errors have occurred.
(13) The merchant login ID or password is invalid or the account is inactive."
What's strange is, this message is being returned (from https://test.authorize.net/gateway/transact.dll) after a successful charge. We subsequently get a silent post notification for the completed transaction.
Has anyone run into this one before?
The error message that you referenced corresponds to our error 13. This error can only indicate that the API login ID that you are submitting is invalid, or that you are attempting to use account credentials on the incorrect system. For example, you may be attempting to utilize sandbox account credentials on our production system.
The only way you can get an error 13 and a successful transaction is if you are maybe running two transaction attempts or possibly redirecting inappropriately after the transaction.
Thanks for the response. I was able to confirm that the API login detail, sandbox endpoint, and redirect urls were correct. However, the AuthNet test environment throws that error if you try to submit the same amount and card number too many times in succession. If you wait a while and try again, or send a different transaction amount all works as planned.
This isn't a major issue, unless you happen to be testing your own handling of the duplicate transaction error :-(