URGENT Auth.net Error S2member Pro

Hello,

We have successfully conducted over 300 paid transactions using s2member pro and Authorize.net as our payment gateway.

However, since 15 Jan, we haven’t processed a single payment. Given the amount of targeted traffic we’re getting, this is odd.

Then yesterday I may have figured out why. A customer emailed us and said when attempting to pay they got the following error code:

Error 103: This transaction cannot be accepted.

I looked up the code and it said:

A valid fingerprint, Transaction Key, or password is required for this transaction.

We have not changed anything in Authorize.net, nor have we changed any of the API settings in S2Member.

Also, I haven’t upgraded to the latest version yet, so It’s not that.

I’m not sure what the issue is. I’m wondering if s2member stopped passing the transaction key… I really don’t know. Please Help!

If any one has any insight on this, please let me know because we really need to get this resolved very quickly.

Hi there. Thanks for reporting this important issue.

Interesting. That’s a very general error code, so in this case we’ll need to have a look at your Authorize.Net API log file. If you’ve enabled s2Member’s logging routines for Authorize.Net, you will find your API log file here: /wp-content/plugins/s2member-logs/authnet-api.log.

You can enable logging from your Dashboard:
s2Member -> Authorize.Net Options -> Authorize.Net Account Details -> Logging/Debugging

Please email your log file for review, using this private contact form.
s2Member® » Private Contact Form

Great! Thanks Jason. I’ll email you right now.

-JL

Thank you. I just took a quick look at your log file, and I’m seeing this error code: E00007

You can look that up here: http://developer.authorize.net/tools/arberrorcodes/
It sounds like you might have s2Member in Sandbox Mode?
Or perhaps your Authorize.Net credentials that s2Member is using belong to a developer account?

API Error Code: E00007 
Error Code Text: User authentication failed due to invalid authentication values. 
Description: The name/and or transaction key is invalid. 
Other Tips: Try switching between production and developer test URL's. The test URL requires a separate developer test account, which can be set up by filling out the following form: http://developer.authorize.net/testaccount. 

I think you were defnitely right Jason. Authorize.net did a test on our account for some odd reason and they must have put it in test mode and never changed it back. That would indicate why when we changed the transaction key that it all worked out fine.

Thanks for your help on this. We’re back in business. :-)

Great to hear this was resolved. Thanks for following up!
~ Much appreciated :-)