------------------------------------------------------
* Error At 2/12/2009 1:40:21 AM
* CustomerRefID: 519099580-13936
* Session ID: 519099580
* Error Number: 3704
* Error Source: ADODB.Recordset
* Error Description: Operation is not allowed when the object is closed.
* RequestMethod: GET
* ServerPort: 443
* HTTPS: on
* LocalAddr: 208.109.249.25
* HostAddress :87.194.118.70
* UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
* URL: /cart/pc/gwReturn.asp
* FormData:
* HTTP Headers:
*****************************
HTTP_CONNECTION:keep-alive
HTTP_KEEP_ALIVE:300
HTTP_ACCEPT:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
HTTP_ACCEPT_CHARSET:ISO-8859-1,utf-8;q=0.7,*;q=0.7
HTTP_ACCEPT_ENCODING:gzip,deflate
HTTP_ACCEPT_LANGUAGE:en
HTTP_COOKIE:ASPSESSIONIDCACRTSSC=HONJILOBPJJMHPKCIBHEBMGB; __utma=247316761.3184465478938330000.1234426706.1234426706.1234426706.1; __utmb=247316761.88.10.1234426706; __utmc=247316761; __utmz=247316761.1234426706.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); ASPSESSIONIDAACRQTRD=MLENAPOBLGBFEBOIHBHKKBCB
HTTP_HOST:www.leisureartslibrary.com
HTTP_REFERER:https://www.leisureartslibrary.com/cart/pc/gwUSAePay.asp
HTTP_USER_AGENT:Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
*****************************
------------------------------------------------------

 

I had something similar with a client using protx. I have several using protx successfully so it wasa client specific issue not a problem with the payment gatweay itself.  I'm trying to recall what the solution was because I had 2 payment isuues with 2 different clients at the same time. I know one was to do with the ssl settings.

 

Let me check my correspondence from around that time and I'll get back to you.

 

Nigel

 

 

 

We already had a merchant account with them for another site we have, which is a hosted store that sells both our instructional publications and other craft products (yarn, knitting needles, supplies) and fulfills out of a 3rd party distribution center (we don't ahve to maintain an inventory, it comes from a pool). USAePay was the preferred gateway for the developer of that hosted cart. So it was easy to just add another terminal ID for this store where we sell digital downloads of out-of-print patterns. It was easier on our Accounting department too, since they like to minimize the number of payment processors we deal with.

 

 

My personal experience, and that of a couple clients, was that response to support requests from these folks have been poor.  I'd be curious to know your general impression of their support, and why you happen to use them.

 

Another result of the timeout waiting for a response from the payment gateway is that the order doesn't get marked as completed in the PC database, so when they log in to look for their order info and get the download links for the digital product they bought, the order doesn't show up.

 

I'm checking with USAePay as well to see what troubleshooting they recommend for testing the pmt gw connection.

 

This may not address your specific concern, but I have a client whose customers seemed determined to frequently click SUBMIT more than once at the final stage of checkout.

 

This article made a big difference.  It uses JS to prevent clicking the submit button more than once.  Without actually seeing what your customers are seeing, I'm not certain if it will help you or not.