authorize.net

[Guest]

hello,

 

i am using a default install of osc and have signed up with authorize,net as my merchant.

 

i have set up the payment module but get this error when attempting to checkout:

 

An error occurred while trying to report this transaction to the Merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card. 

     This transaction has been approved.

It is advisable for you to contact the merchant to verify that you will receive the product or service.

 

authorize say it is an osc script prob as the osc script is taking to long to action over 10 secs - BUT this error message comes up instantaniously ?

 

 

any ideas? is this a fault with the standard payment module for authorise ?

 

please help as i am stuck thankyou

[Lavarock]

I have been receiving the same error.

 

When testing today I saw that I have an "Unsettled Transaction" entry that has most or all of the information, but is listed with a status of "General Error". Then I realized that I was using AMEX (which I don't support).

 

When I switched back to a Visa card, the transaction went through without a script timeout error.

 

This is the first time it has worked for me on this server. I guess I will do lots more testing and voiding transactions and see if I get the timeouts again. If so, I will switch back to the "CC" module which does split transactions and requires me to manually enter data onto Authorize.Net's server.

[Lavarock]

After more testing, it still appears to give me script timeouts and have disabled the authorize.net module again.

 

I can imagine at least 3 things that might cause this type of error, but few if none of these are under our control... and I have no time soon to help Authorize.Net debug things.

 

1) The script might *really* be timing out, although they say there is a 10 sec wait and since it is not taking 10 secons, perhaps their timer is NOT 10 seconds.

 

2) Perhaps when they receive the debit information from us, they process it and then turn around and perform a lookup on our site to determine its validity. That lookup may be not working (like a DNS error or failure) and our server never replies because they never sucessfully called us back.

 

3) Because of the massive numbers of transactions they receive, they may "round-robin" a number of servers, one of which may not be working properly. Thus every so often, we get to a server that doesn't work and sometimes get the one that does.

 

4) My server company (MyDomain.Com) may have something configured incorrectly.

 

Good luck and I'd be interested in anything anyone finds out about this.

[Guest]

anyone - this is urgent.

 

thank you.

[mondi]

Diablo,

 

IF you are using a stock OSC setup, I would highly recomend using this mod for authnet:

 

http://www.oscommerce.com/community/contri...h,authorize.net

 

It is pretty easy to setup for a stock store and works very well.

 

Mondi