I've been having trouble processing certain transactions through Authnet for the last few days. Does anyone know what's gong on? I've sent support emails and gotten no answers. I tried holding on the phone for over an hour and just had to listen to bad music. Our Alabanza servers return errors and one of my other sites can't submit orders either (although I can't see what the error is on that one). I seem to be able to process transactions through Ubersmith and Optigold ISP though. I think we're using an older version of authnet - 2.5 I believe. anyone know what's going on, or am I the only one? DId they change some settings all of a sudden with their weblink thing? Here's the error we're getting with Alabanza:

HTTP/1.1 200 OK Connection: close Date: Sat, 11 May 2002 04:34:15 GMT
Server: Microsoft-IIS/5.0 Content-Length: 288 Content-Type: text/html -

Originally posted by rbro
DId they change some settings all of a sudden with their weblink thing? My understanding is that yes, they did... within the past couple of days reportedly Authorize.net has made some changs to the variables that have to be passed between your site and theirs. You should probably contact their support for details.

Additionally, I've had one client report that Authorize.net has said they've been having some network problems over the past couple of days.

They changed some of the variables they accept. Here's an e-mail I received. I don't use Authorize.net myself but I hope this info helps those that do.

It appears that authorize.net over the past 72 hours has made some changes on their side which have seized all online authorize.net scripts from working. They made it so that the "type" variable that we pass back in the form is now for some reason equal to their x_Type variable. They also made
is so that the "email" variable we pass is equal to the "x_Email" variable that they are expecting. Etc. They did this for several variables. Now all our scripts are getting a (53) transaction type not correct error from authorize.net.

At this time, all online authorize.net scripts that you
have off your website, will not work. If you use authorize.net , feel free to open up a support ticket with them
regarding this to make them aware of the issues that they have caused you.

Got a few lost orders because of that change.

Originally posted by WII-Aaron
They changed some of the variables they accept. Here's an e-mail I received. I don't use Authorize.net myself but I hope this info helps those that do.


This is amazing. You don't even use Authnet and you get an email explaining what happened. I've been using them since 1998 and I don't get anything. I've been on hold for hours and sent in support requests that have gone unanswered. Sometimes authorizenet just sucks.......

I agree! Information could be better.

:) That's why I don't use them, but I have customers that do and I keep up on things that might affect my customers service. Even at that, that's all the information I've been given. I hope everyone can get it worked out.

Just FYI: I use linkpoint.

Aaron

How much do they charge per month and transaction?

It depends. You'd have to fill out an application and describe your business. Personally I pay somewhere around 1.6% plus $.30 per transaction. I'd have to ask our acounting department to be sure, though. Here's a link:

http://www.cardservice.com

Aaron

Originally posted by rbro
This is amazing. You don't even use Authnet and you get an email explaining what happened. The email Aaron posted didn't come from authorize.net; it was sent out by dialupusa to their users, advising of problems that their proprietary account setup scripts were suddenly having when trying to connect with authorize.net.

Actually it came from a customer. Where they got it I don't know, but you're right, It didn't come from Authorize.net. From what I'm hearing here and elsewhere that's the problem, nothing's coming from Auth net. :)

Aaron

Well now I'm hearing conflicting stories. WII-Aaron says change the variables, alabanza says authnet's having network problems and if you call authnet and press 3, there's a recording about some other connection problem they're working on. In the meantime, I've sent multiple support emails without any reply and I've tried holding on the phone for over an hour on several occasions. In the meantime our order forms are down. Damn this is frustrating.....

I am on the phone with authnet support now, after 90 minutes on hold. They say they are not having network issues, they claim the errors are caused by the fact that the DLL has been updated to increase stability (ha-ha) and whereas previously invalid information (bad characters etc.) would allow a transaction to go through, now they are not. So there you have it. They say they need to address each and every merchant seperately to determine how to fix it for them. Can you say NIGHTMARE????

My information is second hand. Treat it as such.

Aaron :eek: