Ubercart

OK - updated version with 3D Secure authentication for cards that need it.

Can't seem to get this working, filled all test account info in but when I try and process a transaction it just sits there with the page loading for ever until I manually stop it. Any info would be appreciated.

Cheers Dan

Great to see a CS payment module on here, Will start testing the module with our UC installations, If i find any issues, will let you know.

When I try and submit any payment details I get:

We were unable to process your credit card payment. Please verify your card details and try again. If the problem persists, contact us to complete your order.

Judging by looking through the code with a lot of hardcoded data such as URLs of CardSave as well as the shop of the module creator that this module isn't under any active development and probably doesn't work with updates made to CardSave, although of the 3 PHP files provided only one of them has changed.

James: sorry you're having trouble getting the payments to go through. All I can suggest is double-checking all the configuration settings. Are you using your test gateway? Are the API credentials correct? Are you using one of the test cards from the Cardsave documentation? Do you see the failed transaction in your Cardsave MMS?

We are using this module on four live websites, and are taking regular payments. There have been no changes to the module for a while because the Cardsave API hasn't changed. If anything does change, I will update the module code and upload it back here.

Yep, all set up to use the CardSave gateway, used details as specified in the documents.

In the CardSave MMS, it just says "Transaction Status: FAILED (Card referred)"

Do any specific options need to be set under Credit Card settings such as start date/issue number/card holder name etc?

Also, not sure if you have noticed or not but "www.dashcustom.com" is hardcoded in to the module and from the email sent to us by CardSave, there is a 3rd server to add on to the list.

Thanks for the heads-up on the dashcustom.com hardcoding and the new gateway URL - I'll add those in and upload a new version.

I'm not sure what to suggest about the transaction failure. The fact that it reaches the MMS says to me that the payment gateway module code is sending the transaction details correctly. In the MMS, you should be able to see the various transaction fields (cardholder name, expiry date, etc), and check that they are populated with the data you entered in your Ubercart checkout page. I'm not sure which of these fields are mandatory, but I suspect most of them are.

It may be a dumb question, but are you using one of the test credit cards which is supposed to be authorised, or are you using one which is supposed to generate a "Card referred" failure?

"Test Case 3 Card Details (Authorisation Referred with no 3D Secure):"

Damn it.

Tried authorised with no 3D Secure and that worked, thanks for the tip.

Then tried with 3D Secure which failed with a timeout error.

Updated module code with changes suggested by jamestombs

Looking good, couple of other things:

line to add ~360 of .module file:

$rgeplRequestGatewayEntryPointList->add("https://gw3.cardsaveonlinepayments.com:4430/", 300, 2);

Also within the ThePaymentGateway directory, one of the files has changed, not a lot (mostly redundant comments being removed and some default values being set). I have attached the new file, the other 2 have remained the same.

Hi,
I've just set up an e-commerce site and chosen CardSave as the provider after successfully testing uc_cardsave with a test account. I now have a live account but I am unable to process credit cards if I switch my site to the Live gateway (Test Gareway still works, including 3D Secure). I am using the latest update of uc_cardsave which includes the 3D Secure support.

All I see in the order admin view is: "Payment REJECTED: Input Variable Errors"

Is there an easy way I can get more information that this? In particular, can I somehow dump the SOAP object that's being passed to Card Save? I've tried enabling Debug mode, but I've not found any additional output.

The Username/Password appears to be correct for the gateway because if I change the password to one that is wrong, I get an authentication failure message instead.

Thanks in advance
Jonathan

Hi Jonathan

I'm afraid I can't help on the debugging front, We got exactly this issue for a single card payment about a month ago - all other payments were processing just fine. I contacted Cardsave tech support about this, and it was a problem at their end which they fixed, but perhaps it has become unfixed. Your best bet is to get in touch with their tech support: integrationsupport at cardsaveonlinepayments dot com

Hi Mark - Thanks for the tip. I emailed them and they just came back and asked me to check that there was no whitespace in the Username or Password.
I then stuck a var_dump($Message); at line 278 and saw that the actual message coming back was :
string(108) "Input Variable Errors Passed variable: MerchantAuthentication.Password [12aBCdE3fGHi4jK5] is type invalid "

NOTE: I have NOT disclosed my real password, but I have formatted a different string to be the same length + mix of upper/lower case + numbers.

It looks like this message is supposed to go somewhere in Drupal but I can't find it logged anywhere
278 $result = array(
279 'success' => FALSE,
280 'message' => t('Credit card payment failed: @message', array('@message' => $Message)),
281 'uid' => $user->uid,
282 );

I think that CardSave's MMS system has allowed my to set a password which is actually too long! I'm waiting on a response from them now because I have no option to reset the password in MMS.

It's incredible that for a mega-high-security application like credit card processing that the Gateways will only accept alpha-numeric passwords. I'm no security expert but I'm sure that massively reduces the permutations required for a brute-force attempt.

I'll post the outcome in case it's useful to someone in future.
Cheers
Jonathan

Hi, I'm getting an error 500 when trying to use the cardsave module on www.hedcamz.com
any clues anyone?
thanks
Jen

Better late than never for a reply If anyone else is having this problem, I did too. When a direct card payment was made, the cart review page just loads forever when you go to process an order. Eventually, it times out with reference to 504.shtml without taking payment. The error comes about because your hosting server has not allowed port 4430 to be opened for outgoing tcp connections. Simple to sort out, just contact hosting company, ask for port 4430 to be opened for outgoing tcp connections

www.whiteweddingpages.co.uk

Can anybody please update if this module is ready for production use, or is there a latest test version that we can use to report issues?

-gnat

If you contact Cardsave they have a module available which they promote as being ready for production use, which in my experience is exactly the same as the module available here. Check out the link:

http://www.cardsave.net/shopping-carts/item/all-carts/ubercart

Thanks stuhannaford. Your help is really appreciated. But the link that you mentioned does not have a downloadable module. Does it mean that I have to contact Cardsave to get the module?

They used to do a direct download, which was exactly the same as the module available here. It seems they now want you to call them for a link. It is worth doing as the package that I downloaded from them had the module but also included test credit card details so that you can make sure the module is working properly before putting it live. According to the site it is still free, I presume they want you to contact them to make sure you are setting things up properly and have the correct security installed... and to try and sell you the option of having them install it for you

For reference the module version I am using is 6x1.0a and can confirm it all works correctly with Ubercart 6x2.7 and Drupal 6.22. If the module available here is the same, I'd happily go with that.

Hi Gnat,
I've been using the Cardsave Ubercart module for nearly two years in production on www.totaltraining.me.uk - It has never given me any grief, which is more than I can say for the uc_ssl module.

I'm currently using version 6.x-2.0-rc7

The issues I reported a while back in this forum were really caused by Cardsave themselves who really did allow me to set a password that was longer than the maximum permitted size in their API.. The only thing I could fault this module on was that it didn't allow me to see the error message returned from Cardsave.

All in all - I'd give this module a big thumbs-up