FirstData and 1.3.9h upgrade

Hi, all ... we are soon to upgrade to 1.3.9h from 1.3.7 (yup, it's about time ...). Our host will be doing the upgrade for us, but we wanted to have some idea of what 1.3.9h is about, so I installed Wampserver on a WinXp system, and installed 1.3.9h on it. Everything seemed to be going smoothly through configuration and shipping modules info, until I got to Payment modules. Installed the FirstData/Linkpoint API and tried a couple of live transactions. The first was OK, it was supposed to work as all the info was correct. However, found that you can enter a wrong expiration date, and the payment is still accepted as valid, and you don't even get an email (with 1.3.7 you have to have a valid expiration to continue). You can enter a wrong CC code, and the payment is accepted, but you don't get an email. You get an email if the billing address isn't correct. If you don't enter a CC at all, or if the credit card number is invalid to start with, you get an online message.

Looked around to see if I'd missed a setting somewhere, and searched the forums for a similar problem, but didn't find anything. It may be something in the Wampserver setup but I tend to think the processing wouldn't work at all in that case?

Or I could have missed something else, entirely different.

Version info shows:
HTTP Server: Apache/2.2.17 (Win32) PHP/5.2.11

If anyone has had a similar situation, or can shed some light on this, it would be appreciated.

TIA for any input!

so I installed Wampserver on a WinXp system

Unless you signed up for one of the Dynamic DNS services to link your PC to the Internet with its own dns address then your local WAMP web server is just that - local - and an offline Intranet and not an online Internet web server.

Email and off-site payment modules will not work. You can only test payments with the Check/Money Order module.

Vger

Hello, vger, thanks for the quick response ... was not aware of that ... however, we ARE getting emails for new orders, and, as I said, we get an email (of the "Potential Fraudulent Order - Bad Address - Action Required" sort) if the billing address isn't correct. However, the payments may be another item altogether, I expect.

So, with 1.3.9h, should the results be exactly the same as on 1.3.7? That is, an invalid expiration should prevent processing the payment, and an invalid CC produce an email?

I might mention that I also had a bit of a problem installing cURL on the wampserver, and now wonder if I may have messed that up some way. Any recommendations? ... anyone ?

I don't know how you are receiving emails, but then again I use XAMPP as an offline web server and not WAMP. With XAMPP you can try to get Mercury Mail running, but it's a pretty thankless task.

Payment modules require cURL. They shouldn't work offline at all except for the Check/Money Order module, or the old Zen Cart Credit Card module (if you still have that installed).

If you want to properly test a site upgraded to 1.3.9h then you should install it in a folder on your hosting.

Vger

OK, I'll give that a try, moving it to a host site.

Thanks much,

@inovermyhead I'm in the exact same situation as you: upgrading from 1.3.7 to 1.3.9h and testing firstdata payment module. EXCEPT I am testing it from my production server rather than a local test server like you were using. I also noticed that I can put in an incorrect expiration date and the transaction will go through. Has anyone else noticed this?

Between 1.3.7 and 1.3.9h there were no changes related to how an expiry date is passed or evaluated. It is simply collected from the customer and passed on to the gateway for processing. Invalid dates are only rejected if the gateway rejects the transaction. There is no way to know otherwise.

Did you properly uninstall and reinstall your FirstData/Linkpoint module after upgrading?

Turn on debug logging and do a transaction, and post the logs here for analysis. Maybe there's an error code coming back that you need to fix in your settings?

THank you for your prompt response I am going to run a test transaction now and will post the debug logs shortly...

I'm not sure that I want to post the logs unless it is absolutely necessary. First off to answer your question, after I completed the upgrade from 1.3.7.1 to 1.3.9h before I took my store out of maintenance mode I uninstalled the linkpoint/first data module and then reinstalled it. from the modules>payment section of the admin portal.

I just enabled debugging and tried another transaction with a different card...this time I put in an incorrect expiration date and an incorrect ccv number and the transaction was declined.

Next I tried the same transaction with the correct CCV but an incorrect expiration date and the transaction was processed.

Finally I tried another transaction with a different card that I usually use to make test transaction with for the site and I put an incorrect expiration date and CCV and the transaction was process successfully.

I hope there is something wrong with my configuration...thanks for all of your help Dr. Byte =)

I'm looking at the debug logs and I dont really see much info of use for you but if you want I could PM them to you.

Yes, please PM them to me.

If indeed the response coming back from FirstData is saying that the transaction is accepted, and it's charging the card, then you'll likely need to talk to FirstData about why it's not rejecting something you think it should be rejecting.

Just to clarify: you DO have the module set into "LIVE: Production" mode, right?

Dr. Byte I PM'ed you 2 log files, I appreciate your help looking into this. The first data module is definitely in live production mode as well.

The logs show that the gateway approved the transaction. You'll need to call them to find out why it approved a transaction with an invalid expiry date.

Response:
(
[r_csp] => FDMS
[r_time] => Fri Feb 25 03:29:24 2011
[r_ref] => 0799181476
[r_error] =>
[r_ordernum] => 502-rpiKJz
[r_message] => APPROVED
[r_code] => 82034Z0799181476:YYYM:
[r_tdate] => 1298622563
[r_score] =>
[r_authresponse] => 107
[r_approved] => APPROVED
[r_avs] => YYYM
)

before I call them is there anything else that could be going on here. I don't want to bring my store under scrutiny unless absolutely necessary.

is it a coincidence that the original poster and myself are both experiencing the same issue when we both upgraded from 1.3.7.1 to 1.3.9h?

csimmons83:

before I call them is there anything else that could be going on here. I don't want to bring my store under scrutiny unless absolutely necessary.
Short of maybe needing a re-issuing of your PEM file, I can't see anything else. I think you'd need to call them for that anyway ... ie: I don't think you can do that manually from your account console.

csimmons83:

is it a coincidence that the original poster and myself are both experiencing the same issue when we both upgraded from 1.3.7.1 to 1.3.9h?
Peculiar, yes.
But, short of calling them, I'm not seeing anything obvious that's wrong on our end.

@Dr.Byte I appreciate you looking into this, I will post an update as soon as I get to the bottom of it.