Forum Moderators: buckworks
And it looks like they don't even have any intentions of fixing this issue!
Below is a summary of Authorize.net's live chat response to my question:
Mozilla based browsers have issues with our site, they do not parse the Java on our site correctly and as a result people may see issues with processing on Safari, Mozilla, Opera or Firefox.Those using these browsers may experience difficulties so it is recommended that they use IE or Netscape
Currently we are aware of the issue but we have no ETA as to when it will be resolved due to the fact that it is not entirely an issue with our site but partially the way the browser parses the code... as with most of the Internet our site is optimized for IE or Netscape, so unforutnaly there may be issues with other non standard browsers Safari, Mozilla, Opera or Firefox.
Netscape and IE possess well over 90% market share for browsers and as I have said it is not entirely an issue with our site... so the vast majority of users using either Internet Explorer or Netscape (which is the vast majority of the Internet users) should see no issue.
Does this seem absolutely ridiculous to anybody else? Is it not a MAJOR oversite on their part that these browsers are not supported?
So instead of doing it onscreen, upload a brief textfile with information for crediting a card. It isn't that much trouble to do a credit file. There are directions for it on authorize.net's site. Once you make one credit file, you can use it as a template to make others. It must be pretty easy if I can do it, as I don't have a techy mind.
In order to avoid the issue entirely, disallow automatic capturing of funds. Allow authorization automatically only. Then you capture by hand when you are ready to ship and always capture only as much money as you want and you pretty much never have to do a credit. Since I switched off automatic capture, I have had to write only one credit file in the past year. This is the only browser problem I know of on authorize.net's site.
So it's not a problem with people using the gateway on your site. It's a problem with you using authorize.net's site. In terms of people using a browser that has a problem with purchasing on a site, I have been using either old Netscape or Mozilla since 1994 and have never had a problem puchasing anything anywhere online. Periodically I purchase something off my own site to make sure there is nothing wrong with the cart (when people have problems with it). I have never had a problem puchasing anything through an authorize.net gateway using Netscape 4.7 or any of several versions of Mozilla, including the most recent (and last) one. People just abandon their carts sometimes. They change their mind. They think they're spending too much money. They can't find their wallet with their card in it (authorize.net allows only 2 minutes for them to put their number in once they get to the cc input screen). Their boss just walked into their cubicle.:)
All this to say I think either you misunderstood the person at authorize.net or the authorize.net person misunderstood your question.
The error is when customers purchase, and is not when I am within their system. I am sure this was because of the safari browser because he said it worked fine when he switched browsers. The latest error someone received was.
The following errors have occurred.
(5) A valid amount is required.
The error is when customers purchase, and is not when I am within their system.
We've done thousands of transactions through authorize.net and never once had a transaction problem due to the browser used.
The user never interacts with the authorize.net site, so the browser they are using is irrelevant.
When customers order via telephone, I enter their order from Firefox. I've done hundreds of these phone transactions and never had an error.
In addition, I personally have not noticed problems with Firefox, I just mentioned that browser because Authorize.net told me they had problems with it. I personally am only having difficulties only when customers order through the safari browser.
I believe I am using AIM
There aren't any resources loaded into the browser from Authorize.net. So their javascript is never involved - only your own.
This reminds me of about a year ago when I called them about the credit screen not working and they told me the fault was my browser and that I should switch to IE. I said that the fault was not in my browser but in the poor design of their site, and that IE was an security nightmare and more and more people would be switching away from it. They literally laughed at me. I got so mad that I spoke to a supervisor, who apologized profusely. But that sure fits with what you have been told. I can't understand that they would consider an inconvenience to the customer less of a concern than an inconvenience to themselves. The US auto industry used to have that same attitude. Look where they are now.
