SecPay payment module

[andyc28]

Hi

 

I can not get the Secpay module to load,

It wouldn't return any data back to OScommerce, so I was not able to see any of the orders.

 

Secpay said do not worry, download the latest contribution from the support site, it fixes any problems with that and works fine.

 

I downloaded the most recent contribution SECPAY using MD5 security....

It still did the same thing i.e Error...and wouldn't post anything back.

 

Now it say various different error messages..

 

Within the admin module / payment thing is says:

Fatal error: Cannot redeclare class secpay in /home/sites/site7/web/oscommerce-2.2ms2/catalog/includes/modules/payment/secpay.php on line 27

 

Various other errors I get are parse errors at line 27, 36...blah blah blah....

 

Any ideas???

 

Andy

[blueskiwi]

I have tried that new module. I don't get those code errors, but I do get bounced back to the payment method screen with the following message:

 

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

 

However I also receive an email from secPay telling they just billed my card!!

 

Argh!

[BMatt]

I have tried that new module. I don't get those code errors, but I do get bounced back to the payment method screen with the following message:

 

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

 

However I also receive an email from secPay telling they just billed my card!!

 

Argh!

 

I have a feeling that is only coz you ve tested it with the test credit card number. obviously this cannot be processed in real life so certain aspects of the callback to your server will be false. Secpay knows that the number is just a test, but OSC doesn't know that. I'm pretty sure once you re live, you won't have the problem.

[♥yesudo]

When using this module you may have to remove the spider/robot called 'java/' from your includes/spiders.txt file as this can stop this module working correctly.

[blueskiwi]

The problem was neither of these... I was using a live credit card (which was getting billed!), nor was it the spiders thing, though hopefully that tip is useful for someone else.

 

In the end I found I hadn't handled the hash/security checking right... the hash check was failing. Despite this being my fault, I feel there is something of a problem with the module if it can exhibit the behaviour I experienced. If the security side fails for whatever reason, the card should never be billed!!

[NikLP]

When using this module you may have to remove the spider/robot called 'java/' from your includes/spiders.txt file as this can stop this module working correctly.

 

 

THAAAAAAAAANK YOOOOOOOOUUUUUUUU!!! :)