- This topic has 4 replies, 2 voices, and was last updated 9 years, 6 months ago by
.
-
Posts
-
During my last sales cycle we had a few individuals view this page when trying to purchase:
[https://secure.authorize.net/gateway/transact.dll#content]
I contacted authorize.net and this is their response:
If you are using a shopping cart it may be down. Authorize.net is not having any issues.
I searched your forum and see this could be linked to API/transaction key not being correct. I double checked this information with authorize.net and the settings in WPestore are correct.
What would trigger some individuals (not all) to view this error message when completing their purchase?
That means you need to get a new set of API keys (authorize.net is seeing the current one as inactive). Request a new set of keys from them and use that in eStore’s authorize.net payment gateway settings.
Here is a thread where another user had this error and solved it by getting a new set of API details:
https://support.tipsandtricks-hq.com/forums/topic/authorizenet-error
In the example thread, the individual was using incorrect API keys. We’ve checked with authorize.net and our keys are correct. I’m happy to request an updated set in an attempt to resolve this problem; however, if they keys were an issue why would some people be able to purchase without issue? Wouldn’t incorrect keys block all purchases? We had 40+ successful purchases using the same checkout process.
An additional follow up question: What might be other circumstances under which this situation might occur?
The following error comes from the Authorize.net gateway (not the plugin):
(13) The merchant login ID or password is invalid or the account is inactive.So you have to ask there support them why you authorize.net merchant account shows it. Then they can look into your merchant account and see what is going on.
- You must be logged in to reply to this topic.