|
afqam_webmaster
|
April 21, 2017 at 6:52 am
I am having the same Error 13 error that others have experienced with Authorize.net SIM payment method. The transaction is getting processed, but it seems the error occurs at the redirect back to our website. I have attempted the various combinations of debug and test mode, and it has no impact.
Authorize.net recommended changing the transaction post URL to https://secure2.authoriz… We’re willing to try that, but my developer could not immediately find how to do that. The closest thing I’ve found is the General Settings–>Critical Pages–>Transaction Page, but the page says the [ESPRESSO_TXN_PAGE] shortcode shouldn’t be changed. Maybe this isn’t even on the right track.
|
|
Tony
|
April 21, 2017 at 7:10 am
Hi there,
Generall Error 13 means your Merchant login credentials you’ve set in the Payment Method settings are incorrect.
Double check you Authorize.Net API login ID and Authorize.Net Transaction Key are the correct values from your account.
Are you in Debug mode within the Payment Method? If so the credentials you use must be a from a sandbox account, not your live account.
These settings are found within Event Espresso -> Payment Methods -> Auth.net SIM – http://take.ms/te9PtN
|
|
afqam_webmaster
|
April 21, 2017 at 7:26 am
I’m not in debug mode within EE…I’ve got my Auth.net account in TEST mode.
|
|
Tony
|
April 21, 2017 at 7:30 am
Ok, great.
Did you double check your API login ID and Transaction Key matches the details from your account?
|
|
afqam_webmaster
|
April 21, 2017 at 7:36 am
The transactions are actually being processed…would that still happen if the ID and Key didn’t match?
|
|
Tony
|
April 21, 2017 at 8:04 am
Possibly, iirc auth.net in test mode ignores errors on authentication which may not be happening on the re-direct, so, for example, a space on the end of either of those credentials may cause problems. Either way it’s worth confirming the credentials are correct, it takes less time than a reply.
We don’t currently have a filter that can be used to change the POST URL for auth.net SIM although you can change it within the code to confirm if that fixes your problem.
You’ll need to change: \eea-authnet-sim\payment_methods\AuthorizeNet_Sim\EEG_AuthorizeNet_Sim.gateway.php
Line 63 will be:
$this->_gateway_url = 'https://secure.authorize.net/gateway/transact.dll';
Change that to:
$this->_gateway_url = 'https://secure2.authorize.net/gateway/transact.dll';
Then run another test and see if it works.
(Note – We do not recommend changing core files like this, however if the above is the issue we can add a filter to the payment method to allow that change to be made without modifying core files)
|
|
afqam_webmaster
|
April 21, 2017 at 11:25 am
We tried that modification and it did not impact the error. Will touch base again with Authorize.net help to see what else to try.
|
|
Josh
|
April 21, 2017 at 5:06 pm
Hi there,
This is the technical information about the error you’re seeing:
https://support.authorize.net/authkb/index?page=content&id=A415
Since you mentioned that you have your Authnet account in TEST mode, then you should also be sure to set “Send Test transactions” to Yes in Event Espresso > Payment Methods > Authorize.net SIM Settings.
https://www.evernote.com/l/AAQ6lJGJI21OV4cXhAI6Bijl9P9JlLbzCC0
This will set the field x_test_request to TRUE and that lets Authnet know it’s a test transaction.
Debug Mode should only be used if your account is from
https://developer.authorize.net/hello_world/sandbox/
|
|
afqam_webmaster
|
April 24, 2017 at 6:39 am
We never figured out why it was not working while my Authorize.net account was in TEST mode. I took my account out of TEST mode, and everything works fine.
|
|
Tony
|
April 24, 2017 at 7:09 am
Unfortunately, we can’t see why you are getting the above error on your account as the error is thrown on auth.net’s server.
I’d recommend creating a sandbox account with auth.net and setting the payment method to debug mode whilst using those account credentials for testing payments on auth.net.
The main reason for doing this is a live account in test mode does not log any of the details of the test transactions you make, a sandbox account does and so provides more details of what is happening with the transaction when it’s failing.
|
