|
Rob Shapiro
|
September 1, 2017 at 2:27 am
We are having issue with EE4 Authorize.Net SIM Payment Gateway since the last update that we applied this week. It is showing following error however same credentials works fine for Authorize.Net AIM Payment Gateway.
—————————————————
The following errors have occurred.
(13) The merchant login ID or password is invalid or the account is inactive.
—————————————————
FYI, Authorize.Net AIM also throwing error with events which have long dash (–) in the Event name.
(TESTMODE) Line item 1 is invalid. (Reason Code: 270)
Please help!
|
|
Tony
|
September 1, 2017 at 5:18 am
Hi there,
The following errors have occurred.
(13) The merchant login ID or password is invalid or the account is inactive.
Have you double checked your credentials? That error is directly from Auth.net and usually means either your credentials are incorrect, the account is inactive or your using sandbox credentials with the payment method in live mode (or vise versa).
Here is the documentation from Auth.net on error 13:
https://support.authorize.net/authkb/index?page=content&id=A415
FYI, Authorize.Net AIM also throwing error with events which have long dash (–) in the Event name.
(TESTMODE) Line item 1 is invalid. (Reason Code: 270)
Can you link me to the event so I can view this please?
|
|
Rob Shapiro
|
September 1, 2017 at 6:51 am
Yes we double checked everything. SIM method stopped working since update. We did not change anything. All settings are same as they should also same credentials and settings are working fine with AIM.
Regarding long dash issue, I changed it with normal dash in all events and now it’s working fine. BTW, we sucked in new issue while testing website, I tried to create a promo code so that I should get 99.99% discount but still I pay some amount. But doing so the payment form just get hide if I apply the promo code.
here is the link http://swistraining.com/
|
|
Josh
|
September 1, 2017 at 9:34 am
Hi there,
I checked the SIM method add-on on a test site that has the current version and it’s working there. What may help in this case is you go to Event Espresso > Payment Methods > Authorize.Net SIM then completely blank out the Login ID and Transaction fields and replace with a fresh copy from your Authnet account page. Then please also be sure to set Debug Mode On? To No. Then you click Update Authorize.net SIM Payment Settings.
With regards to a 99.99% discount code, may I ask what is the actual ticket price you’re trying to discount by 99.99%?
|
|
Rob Shapiro
|
September 2, 2017 at 1:44 am
I’ll test SIM method as recommended later and get back to you. Regarding discount code, probably I was testing with lowest amount ticket i.e $100 or may be $150.
I tested system with other coupons, and it works fine, maybe the issue was due to very low amount with 99.99% discount?
|
|
Tony
|
September 4, 2017 at 2:28 am
Hi there,
At $150 using a 99.99% discount, you’ll be charged $0.01.
Most payment methods have a minimum payment amount of at least $1 in live mode (some are higher so I’d recommend using around $5) so the 99.99% will likely cause you problems anyway, however when I test a $150 with 99.99% dicsount I don’t get the above error from Auth.net.
The only time you should see error 13 from auth.net is if there is an issue with the account itself or if you using a Live account in Debug mode (you would need a Sandbox account to test payments in debug mode).
|
|
Rob Shapiro
|
September 7, 2017 at 12:41 am
We have tested the system with suggested settings, but still getting same error.
We have also tested with developer account in debug mode and got same error
(13) The merchant login ID or password is invalid or the account is inactive.
The only difference is error occurs in live mode just after redirect however in developer mode it occurs after submitting payment form.
FYI, we are receiving confirmation email from Authorize.Net in developer mode.
Please fix this ASAP.
|
|
Rob Shapiro
|
September 7, 2017 at 12:49 am
This link says that Authorize.Net SIM Payment has been deprecated and use Accept Hosted
Do you have a plan for Accept Hosted.
|
|
Tony
|
September 7, 2017 at 3:43 am
Have you checked with Auth.net to confirm this isn’t an issue with the account your using?
As mentioned the error is directly from Auth.net and usually indicates an issue with the account itself. Auth.net SIM is working fine on all of my test sites using the latest version of EE and SIM payment method, if this was an issue with either core or the payment method it would also prevent my test registrations from working.
A quick example from a test site and using SIM to make a payment – http://take.ms/VPhJB
If you’d like I’m more than happy to quickly swap out the credentials used on your site for our test account and run a test registration to confirm if that works?
If so you can send temporary login details using this form:
https://eventespresso.com/send-login-details/
This link says that Authorize.Net SIM Payment has been deprecated and use Accept Hosted
Do you have a plan for Accept Hosted.
We are aware of this and have a ticket to discuss this further, SIM is still supported and will likely continue to be supported for a while yet (although no new features added to it by Auth.net).
|
|
Rob Shapiro
|
September 14, 2017 at 4:21 am
Hi Tony,
As the website is live, client won’t allow us to enable the SIM on that.
Could you please try with my Auth.net developer account credentials to test SIM. It’s working fine with AIM on our website. If yes, how can I share my credentials? This form keep asking me WP admin credentials. https://eventespresso.com/send-login-details/
Thanks,
Deepti
|
|
Tony
|
September 14, 2017 at 7:32 am
Use that form and add your SIM credentials in the message section, just add dummy details for the wp admin credentials.
|
|
Tony
|
September 18, 2017 at 5:08 am
Testing your credentials with the payment method in debug mode works – http://take.ms/ArIF1
If debug mode is not enabled I get:
The following errors have occurred.
(13) The merchant login ID or password is invalid or the account is inactive.
Which is the error you’re reporting.
That’s expected as your account is a sandbox account (otherwise it wouldn’t work in debug mode) so if you try to use it in live mode it connects to the live server where your account doesn’t exist.
So can you confirm that your payment method is in debug mode when your testing the credentials, please?
|
|
Rob Shapiro
|
September 18, 2017 at 5:22 am
Yes, these are my sandbox account credentials but we get same error no matter if debug mode is enabled or disabled. I think, I should create a staging website with a copy and then we could share WordPress credentials so that you can investigate.
Could you please share instructions so that we can create a copy without affecting licence information of live website.
|
|
Tony
|
September 18, 2017 at 5:27 am
Just don’t set the license key on the dev set.
If you clone the site just go to Event Espresso -> General Settings -> License key
Remove the key and save the settings.
Note that in the time it takes to go that the site may ping our servers and invalidate the key, if that happens just request a reset on the key from your account page.
|
|
Rob Shapiro
|
September 19, 2017 at 6:59 am
We have now created a staging website and made a test with developer account credentials in debug mode and received following error after payment –
=======================
An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.
This transaction has been approved.
It is advisable for you to contact the merchant to verify that you will receive the product or service.
=======================
I will separately share staging website credentials using the secure form by tomorrow.
|
|
Tony
|
September 22, 2017 at 9:52 am
Hi Rob,
The staging’s sites certificate is invalid, this will prevent auth.net from loading the transactions and thank you pages which is likely why your getting the new error.
Can you fix the certificate on staging?
|
|
Tony
|
September 22, 2017 at 10:00 am
Note that although Auth.net SIM is offsite, it does require a valid SSL certificate on the site as it loads pages on your site via HTTPS and their site (the thank you page for example loads on auth.net’s server when finished, that needs to be over HTTPS).
Auth.net currently can’t connect to your site at all as the certificate isn’t valid.
|
