|
UnionChamber
|
February 10, 2025 at 8:51 am
the site was updated to use the authorize.net accept payment gateway with the new plugin authorize.net accept integration. and the payments were working fine,
Now, today I am getting an error “there was an error initializing the payment form from authorize.net” on this when trying to process payment for any event that requires payment
|
|
Garth
|
February 10, 2025 at 9:33 am
A couple thoughts.
1) Mixed Content
I noticed your web page has mixed content (http/https) urls. The logos are loading over http, not https. Authorize.Net requires secure HTTPS requests for API calls, and any HTTP requests could block the payment form from initializing. I’m not sure if that is causing this issue, but you should load all resources https. You can see this in action by inspecting the page and looking at the console messages.
2) What changed?
If payments were working fine recently, what has changed?
3) Do you see any errors in the Event Espresso > Payment Methods > Logs (tab)
|
|
UnionChamber
|
February 10, 2025 at 1:23 pm
This reply has been marked as private.
|
|
Tony
|
February 11, 2025 at 7:13 am
Hi there,
Logging in here isn’t really going to help tell us why this is happening, although I’ll happily take a look over the payment logs.
You can send temp login details using this form:
https://eventespresso.com/send-login-details/
This is the issue:
[{“code”:”E00007″,”text”:”User authentication failed due to invalid authentication values.”}]
But that error is directly from Auth.net themselves and means they are saying either the Authorize.net API login ID or Authorize.net Transaction Key aren’t valid, but we can’t see why that is from our end/your site.
I can see from the details you sent above that the request is going to the correct URL and has both of the above values set on it, but Auth.net return the above error.
|
|
UnionChamber
|
February 11, 2025 at 12:42 pm
My very first thought on this was that I had the wrong authorize.net API key, but that turned out not to be the case. The issue is still not solved, I have both authorize.net and the merchant services account (who is also the reseller for authorize.net in the loop to assist. )
One last question – who does the event espresso module reach out to in order to start the payment process….the merchant services account or directly to authorize.net
|
|
Tony
|
February 11, 2025 at 2:23 pm
My very first thought on this was that I had the wrong authorize.net API key, but that turned out not to be the case.
Normally, that would be my first port of call and ask you to check the credentials… but, in your case you mentioned is worked earlier and that only you have access to make changes… so I assumed this hadn’t changed or that you’d have already confirmed it (which you have).
The issue is still not solved, I have both authorize.net and the merchant services account (who is also the reseller for authorize.net in the loop to assist. )
It’s all directly to Auth.net, but if that was working previously I can’t imagine the requests should be going elsewhere (otherwise I wouldn’t have worked at all, right?).
It looks like your last test payment worked as respected, but not the ones before.
I think the next step I would take here would be to contact Auth.net and have them check the account, the error returned is directly from them so they should be able to see more details on this from their end.
|
|
UnionChamber
|
February 11, 2025 at 2:31 pm
Well, it’s solved, and the issue was indeed the api key at authorize.net. How did it work and then not work? According to authorize.net support, they had several “updates” in early feb, which they claim probably corrupted the API key! They actually told me that over the phone today.
Hmmm, for my thinking, they should have sent out a notice to clients suggesting that if they encounter issues with validation, regenerate the key. While this was the first place I checked, what I saw was that I was the last person to generate an API key, so I ASSUMED the key was still valid.!
anyway, its all fixed, it was the most obvious solution! thanks for all your help!
|
|
Tony
|
February 11, 2025 at 2:49 pm
Hmmm, for my thinking, they should have sent out a notice to clients suggesting that if they encounter issues with validation, regenerate the key. While this was the first place I checked, what I saw was that I was the last person to generate an API key, so I ASSUMED the key was still valid.!
As would I! That’s…. frustrating to say the least.
But… note to self, any E00007 errors the first step is to regenerate the keys, not just confirm them but regenerate!
Either way I’m glad your fixed it and hopefully you don’t run into any more errors.
|
