SECPAY - Works then doesn't

This is a repeating theme across a number of threads but I'm seeking any help about an error when the payment cart returns back to zencart and displays the error :-

There has been an error processing your credit card. Please try again.

BUT ..... the payment process fires off successful emails to the customer and to the store owner email address but does not put it the order in the database.

All clues very welcome - even obscure ones - as I'm happy to take it apart - but having done so a few times I return to this message.

Kind Regards

John

We are having this same problem - if anyone could post a fix or any further suggestuions we would be very grateful.

Many Thanks

Just thought I'd throw my 2 penneth into the equation as well!

I've been trying to setup a new cart ( 1.3.7 ) with Secpay and have been having Digest errors when the info is sent to the Secpay server. All my settings seemed correct, so I asked them to have a look and it seems as though my " cb_flds " are incorrect!!

I'm just going to look at their integration manual and see if I can make any more sense of this? It could be part of the problem that people are having with the Secpay module in general??

Hi,

Just to say that we are still experiencing problems with this - any help would be fantastic. Sales have dropped dramatically since we introduced the paypal module!

Cheers,

Ok I believe there are upto 3 problems here.

The area to check is around the hash check when receiving the callback from the payment gateway.

The version of php has some potential part to play as later versions of PHP appraently do not support the $REQUEST_URI parameter. So that may affect the calculation in your version of PHP.

Secondly, there appears to be an else statement on the IF statment checking the has that has the same routing as a failed hash calculation, even if the has calculation was successful.

Thirdly, the parameters for security matching in the integration manual have spaces inbetween the words eg SECURITY CODE MATCH ONLY. However when the secpay cart calaculates its hash it has + signs instead of spaces eg SECURITY+CODE+MATCH+ONLY and so generates a different hash.

All three of these things were wrong for my version of Zencart & php and needed changing.

But now it works !!!

Cheers

I was thinking of changing from Protx to SECPay (SECPay fees much lower!) but am wondering if it is now such a good idea after reading about the SECPay problems that some users are experiencing.

If I arrange for the SECPay module (from this site) to be loaded to my ZenCart website will I have to make arrangements for the changes (above) to be made.

I'm running v 1.3.6

Many thanks