DigitalEnigma Posted March 17, 2010 Share Posted March 17, 2010 Hi, I've been trying to get the new SagePay Repeats module to work since upgrading our dev install for testing before rolling out live, we've been waiting for this updated module since November last year. The module for us is not working, if I use the old SagePay module the test transactions process fine, I get the 3DSecure prompt, enter the password for the test sever and the transaction processes without a problem. I try the same with the new module for a new transaction, I get to the 3DSecure prompt and enter the password but the transaction fails every time. I have logged a ticket but wanted to know if anyone else has been testing this or got it working? 0 Quote Link to comment Share on other sites More sharing options...
D9Hosting Posted March 17, 2010 Share Posted March 17, 2010 Hi, We've tested it out with v4.2, and are currently using it in a live environment without any problems (touch wood). Is there anything in your Gateway log to tell you why it's failing? 0 Quote Link to comment Share on other sites More sharing options...
DigitalEnigma Posted March 17, 2010 Author Share Posted March 17, 2010 Hi, Looking at the gateway logs it does the 3DSecure part fine, I enter the test server password and then on submission of that am returned to the unpaid invoice. The next log entry shows that the transaction could not be found, looking in the SagePay backend it shows as the transaction having failed. From speaking to SagePay they say it is to do with the call back. Using the old module works fine on the same test account. 0 Quote Link to comment Share on other sites More sharing options...
D9Hosting Posted March 17, 2010 Share Posted March 17, 2010 Hi, I've just done a live test transaction using my own card, and everything goes through fine, including the 3D Secure verification. Although after looking in the Gateway logs, I do see some "transaction could not be found" errors that come up after a clients successful transaction, so I'll submit a ticket to WHMCS with the details and see if they can track down what's causing it. 0 Quote Link to comment Share on other sites More sharing options...
DigitalEnigma Posted March 17, 2010 Author Share Posted March 17, 2010 Hi, Did you do any testing in a test environment before putting this live? I've been on the phone to SagePay and they have told me it is the termurl that is causing the problem, they have asked if we can get a version of the module to post to there showpost url for debugging so have asked in our ticket. I'm at a loss as to why this module fails yet the old module works fine in test mode. 0 Quote Link to comment Share on other sites More sharing options...
D9Hosting Posted March 17, 2010 Share Posted March 17, 2010 Hi, Yes, we did some transactions in the test environment before going live and they all went through without any problems. Although to be honest, as they all appeared to go through as expected I didn't do any digging in the Gateway log. It's strange that it's working for us and not you, I wonder if it's something as simple as the 3D secure rules you've got set in your account. I know Sagepay say it's to do with the module, but if that was the case you'd have thought ours wouldn't be working either. 0 Quote Link to comment Share on other sites More sharing options...
DigitalEnigma Posted March 17, 2010 Author Share Posted March 17, 2010 Hi, When the repeats module fails the error I see in the Gateway Log is: VPSProtocol => 2.23 Status => INVALID StatusDetail => 5036 : The transaction not found. If I login to SagePay and look there has been no successful test transaction, the failed transactions show: Transaction CANCELLED by Protx systems after 15 minutes of inactivity, or no reply from Notification POSTs. Auth Attempt in Database but with no TID assigned. Auths are placed in the TAQ in this state. It is not being cancelled after 15 minutes as the response is instant. 0 Quote Link to comment Share on other sites More sharing options...
DigitalEnigma Posted March 17, 2010 Author Share Posted March 17, 2010 Hi, It works fine with the old module, it's only when we attempt to use the new module that we start to have problems taking the initial transaction. 0 Quote Link to comment Share on other sites More sharing options...
DigitalEnigma Posted March 17, 2010 Author Share Posted March 17, 2010 Hi, Something else I have noticed, if you select to pay using an existing card and enter the security code then continue you are presented with the 3DSecure screen which sits there doing nothing preventing the completion of the payment. 0 Quote Link to comment Share on other sites More sharing options...
DigitalEnigma Posted March 18, 2010 Author Share Posted March 18, 2010 Hi, I've now gone and put our dev install into live mode and used my own card to test. the live transaction has processed fine which points to an issue with this new module and test mode. 0 Quote Link to comment Share on other sites More sharing options...
DigitalEnigma Posted March 18, 2010 Author Share Posted March 18, 2010 Hi, WHMCS has provided an updated callback file that now enables test mode, so all appears to be working. Just need to find a way to show better errors to customers that explain why the payment failed when it does fail such as not 3DSecure authed, invalid issue number, etc. rather than just a message saying there was a problem. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.