Problem with Beanstream since upgrade

We paid a very reasonable price ($150) to Rubikintegration to upgrade our site from 1.3.9h.
Because of the response times in MANY of our communications and ERRORS & OMISSIONS in the work contracted I have NO INTEREST in contacting this coder again.

Before the upgrade our Beanstream payment gateway was working fine.
Now the "Confirm Payment" page hangs while displaying "Loading next step" in the status bar. However:

The purchase/payment DOES go through.
Emails are sent to us AND the customer.
But the page does not switch to a Thank You page. This is VERY confusing to the customer.

Does anyone know what I should check first to sort this out?

Do you have any debug*.log files in your /logs directory? The contents of those files would be indicative of an issue.

No errors since Dec 12, 2012. Problem reported by customer Dec 15, 2012

Sorry, I can't be more help as I'm unfamiliar with that payment method.

It's been a long time since I've used the Beanstream gateway. But I'd also be interested in knowing how well you find it works on a fresh install vs one with a bunch of customizations on it.
By the way, you didn't answer any of the Posting Tips questions, so we really have no idea about how your site is different from original Zen Cart code ... which probably works fine with the Beanstream gateway. Again, without more information from you, it's hard to give you any meaningful assistance.

I am really at a loss with this. I am being told by Beanstream that Zen Cart uses Server to Server integration which after processing, Beanstream returns a transaction results back via the secure session rather than redirecting the purchaser to separate approved/declined response pages.

Can this method be confirmed rather than the Basic HTTP post Redirection Method in which “ The transaction request must include URLs for an error page, approved/declined transaction pages. When the transaction is completed, Beanstream returns the appropriate response messaging directly to the appropriate URL.”

With either one...which pages would I compare to the old-version to find the problem?

'In what ways is your site customized or different from a brand new uncustomized install?'
Customized version of lavender template with COWOA which was working FLAWLESSLY before the upgrade.

Again, it's been awhile since I used the Beanstream gateway myself, but I know that the preferred method for integrating gateways is to use a background transaction submission instead of doing HTTP redirection, since redirects can get ugly when things don't return properly or if any small thing is different on the way back (especially since many things need to be verified during the return process to make sure nobody's spoofing the system an introducing fraud on the way back from the external website which is temporarily outside Zen Cart's control until the customer is fully redirected back to your store).

So, if the module is doing a submission in the background over CURL instead of doing an HTTP redirect, I wouldn't be surprised.

Does the module have a "debug logs" setting in your admin? If so, enabling it could be helpful.

Yikes! Now that is an Excellent idea - and very indicative of the type of advise I am often given here - something I should have thought of myself, and very productive.

The beanstream module report follows:


Beanstream Alert 1115-K39VXj Dec-16-2012 04:02:55
Dec-16-2012 04:02:55
=================================

Response Code: 1.
Response Text: Approved

Sending to Beanstream: Array
(
[merchant_id] => *******
[username] => *******
[password] => *******
[RequestType] => BACKEND
[trnLanguage] => en
[trnType] => P
[paymentMethod] => CC
[trnOrderNumber] => 1115-K39VXj
[trnCardOwner] => *********
[trnCardNumber] => XXXXXXXXXXXXXXX1011
[trnExpMonth] => 04
[trnExpYear] => 14
[trnCardCvd] => ****
[trnAmount] => 9.04
[ordItemPrice] => 8.00
[ordShippingPrice] => 0.00
[ordTax1Price] => 1.04
[ordName] => *********
[ordAddress1] => 11*************
[ordAddress2] =>
[ordCity] => ***************
[ordProvince] => ON
[ordPostalCode] => *******
[ordCountry] => CA
[ordPhoneNumber] => ***********
[ordEmailAddress] => [email protected]
[shippingMethod] => free_free
[trnComments] => Website Order
[ref1] => 7
[ref2] => December 16, 2012, 4:02 pm
[ref3] => xx.xxx.xxx.xxx
[ref4] => 6025904af8ff739f6a69792941ba845e
[customerIp] => xx.xxx.xxx.xxx
[prod_id_1] => 224:331c7c5e9b9fe5d4c2eaf14fd56f
[prod_name_1] => Preliminary Name Clearance
[prod_quantity_1] => 1
[prod_cost_1] => 8.00
[url] => https://www.beanstream.com/scripts/process_transaction.asp
)


Results Received back from Beanstream: Array
(
[0] => Response from gateway
[trnApproved] => 1
[trnId] => 10000092
[messageId] => 1
[messageText] => Approved
[trnOrderNumber] => 1115-K39VXj
[authCode] => 225288
[errorType] => N
[errorFields] =>
[responseType] => T
[trnAmount] => 9%2E04
[trnDate] => 12%2F16%2F2012+5%3A02%3A55+PM
[avsProcessed] => 1
[avsId] => Y
[avsResult] => 1
[avsAddrMatch] => 1
[avsPostalMatch] => 1
[avsMessage] => Street+address+and+Postal%2FZIP+match%2E
[cvdId] => 1
[cardType] => AM
[trnType] => P
[paymentMethod] => CC
[ref1] => 7
[ref2] => December+16%2C+2012%2C+4%3A02+pm
[ref3] => 99%2E***%2E***%2E***
[ref4] => 6025904af8ff739f6a69792941ba845e
[ref5] =>
)


CURL communication info: Array
(
[url] => https://www.beanstream.com/scripts/process_transaction.asp
[content_type] => text/html
[http_code] => 200
[header_size] => 149
[request_size] => 990
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0.965725
[namelookup_time] => 0.036319
[connect_time] => 0.111556
[pretransfer_time] => 0.345288
[size_upload] => 831
[size_download] => 480
[speed_download] => 497
[speed_upload] => 860
[download_content_length] => 480
[upload_content_length] => 831
[starttransfer_time] => 0.965612
[redirect_time] => 0
[certinfo] => Array
(
)

[redirect_url] =>
)



--------------


I wish I had posted this in the Beanstream Support thread -sorry

I am a complete amateur when it comes any code other than html and css but this doesn't look right

(
)

[redirect_url] =>
)