|
PSURACI
|
May 20, 2016 at 1:41 pm
Hello! Having enormous difficulty with Error 13 returned for every test in debug mode trying to configure EE AIM method. Multiple calls to Authorize.net support and they are saying issue is on EE side. Please help, I have been struggling with this issue for the last 3 days and close to giving up and having my client move to another workshop registration solution. Not having a tech to talk to by phone is a major negative to your support solution. I should have just had to enter ID and Key and been done. Thanks in advance.
|
|
Josh
|
May 20, 2016 at 2:09 pm
It sounds like you are using sandbox credentials on live mode (debug mode is off) or vice versa.
If you know of a way that we can fix this for you over the phone, we’re open to any ideas.
|
|
PSURACI
|
May 20, 2016 at 2:33 pm
No, I have worked with Authorize.net support to confirm that we have our settings set correctly for testing. They have told us we have set correctly at Debug set to ON and Send Test Transactions set to NO. Maybe if we were working and running test together in real-time by phone, you could understand issue better and solve? Can you access my clients WordPress site admin to see we have everything set correctly? Since this is WP plugin there are coding solutions regarding connect to Authorize servers we can not control and must be tested to be correct by EE. Someone from EE needs to work with Authorize tech support is what I am understanding to be solution. Give a phone number to call you please.
|
|
Josh
|
May 20, 2016 at 2:48 pm
This doesn’t sound like something I can fix by talking over the phone. I’m sure we can help you via the support channel we offer here.
It sounds like what they told you was incorrect because unless it’s an account for developer.authorize.net, Debug should be set to OFF and Send Test Transactions should be set to Yes. Have you tried that?
I can assure you that the coding was and continues to be tested and verified by Event Espresso staff to ensure that the Authnet gateway works as expected.
Someone from Event Espresso staff can log in and check your client’s site to make sure the settings are correct if you can submit the information requested on this secure form:
https://eventespresso.com/send-login-details/
|
|
PSURACI
|
May 20, 2016 at 3:06 pm
OK, went ahead and made settings to your instructions. Now not getting Error 13, but got Transaction Declined Error #2. Where do I go from here?
|
|
Josh
|
May 20, 2016 at 3:22 pm
You’ll want to make sure that your Authnet account is set to Test Mode while having EE set to send a Test transaction. Then, you can find the reason why it was declined by logging into your Authnet account and following the steps from Authnet’s guide:
https://support.authorize.net/authkb/index?page=content&id=A59
|
|
PSURACI
|
May 20, 2016 at 4:53 pm
Hi Josh. Got in touch with Authorize support to ask about error #2. Tech said that he was now seeing transaction info being passed from EE to the gateway and that not being set to TEST MODE at Authnet did not matter. They suggested that I run a real transaction for $1 with a verified credit card. I put EE into run mode, ran my own credit card and a positive transaction confirmation was returned from the system. Looks like we finally figured out the problem. Thanks for the help.
|
