|
stevestaso
|
June 16, 2019 at 3:51 pm
Using Authorize.net AIM. This month, some customers started getting this error
However, sometimes the transactions DOES go through. Maybe they try again.
But I made no changes to any config with EE or A.net.
Any guidance to eliminate these errors.
On my EE payment form, I require the company name. So this field is filled in on all of them. But it must not be passing it properly to A.net. I temporarily disable the requirement for Company field at A.net to see if that eliminates the error.
|
|
Tony
|
June 17, 2019 at 7:10 am
Hi there,
To narrow this down you’ll need to check the logs sent to AIM (and the responses from them).
So first, find a registration this has happened on and note its transaction ID.
To do that go to Event Espresso -> Registrations
I’m assuming you know of a recent registration that ran into this problem, so find that registration in the list and click on the TXN Date for it – https://monosnap.com/file/iTcZNG238S1T54C0zK1ioFn1h2pCqM
Note the ‘Transaction #’ value at the top of the page.
Also within the payment section, you’ll see at least 1 payment object for Auth.net AIM, what error(s) does it show in the ‘Gateway Response’ field(s)?
Now, go to Event Espresso -> Payment methods.
Along the tabs at the top should show ‘Logs’, click that and search for the transaction ID you noted before.
You should have multiple log entries for the requests relating to that transaction, click on the log ID’s to the left (not the transaction ID on the right) to view each of the logs and confirm that the ‘Company’ field was set/sent in the requests.
You’ll also see the response from Auth.net which often includes additional details than the above.
If you prefer for me to view the logs directly rather than posting here I’ll need login details to take a look, you can send those using this form:
https://eventespresso.com/send-login-details/
(Note that I will not make any changes on the site, just view the logs as in this case it’s easier to view them than pass back and forth)
|
