I had upgraded to PHP 7.2 on our site a week ago. It messed up my member database online and thought maybe that is what messed up my store. I changed the PHP version back to 5.6 and that fixed my member database problems, but sadly, not the store. Dead end there!

Does that coincide completely with authorize.net failing?

Andy

Please feel free to review / rate our software

quote:

---

They wanted me to ask you to get the response code that is being sent by the software and let them know what it is.

---

If you set the following in you includes.php file...
$debugmode=TRUE;
Then try another test transaction that will now display in brackets the error code and it should tell you the error message too. But I think the problem here sounds like your Auth.net details have been changed when you had the database problems. You should double check everything is ok in the admin payment providers page for Auth.net

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

I did that for you thanks to the help from Vince and the response code is 250

https://developer.authorize.net/api/reference/responseCodes.html?code=250

Details
CODE: 250

EXPLANATION: This transaction has been declined.

OTHER SUGGESTIONS: This transaction was submitted from a blocked IP address.

Maybe you can check that with your host and / or authorize.net to see if they can shed any light on possible IP blocking.

Andy

Please feel free to review / rate our software

I have checked with Authorize.net and the "unauthorized transactions" don't even reach them. I ran a report for Unauthorized and nothing comes up. I changed the Transaction Key and I still don't get a error code????

What if I made a whole new store from scratch?

I would check with your host, your store softwqare isn't blocking the IP so maybe something changed on their end when they swapped PHP versions.

Andy

Please feel free to review / rate our software

I checked with our hosting company and gave them a couple of IP's that were not working on the store and they searched for them and they did not come up!

Have you replied to authorize.net as they asked what response code was being returned and now you can give them an answer. Looking at your store you also have Email as a payment method and I assume those orders aren't being affected so it's not a general IP problem. Maybe that error code is used for other instances and they can advise on that.

Andy

Please feel free to review / rate our software

Yes, I gave them the error code, they still don't see anything on their end

quote:

---

I changed the Transaction Key and I still don't get a error code????

---

To see the error code you need to add this to includes.php $debugmode=TRUE; - remove it when you are finished. Can't authorize.net tell you what would trigger their 250 response code?

Andy

Please feel free to review / rate our software

We found it....I called Authorize.net again and it was caused by the API IP Addresses filter in the fraud suite. That filter will block all transactions unless they come from the safe IP address listed in the filter. I disabled that filter.

I ran a real transaction through, and above the receipt the following appears:
POST parameters
POST: xxpreauth : 2510
POST: xxpreauthmethod : 13
POST: thesessionid : dlvmptcdahg27jhjt8ogrqj216
GET parameters

Glad you got it sorted out and thanks for letting us know.

Andy

Please feel free to review / rate our software

Thank you for all your hard work!