new version of sagepay (v3) coming at end of 2014

[kev67]

Strangely enough I got an email yesterday from SD about this, and a link on what to do although I'm puzzled about this bit:

"Unfortunately, there is one feature that is not available in Sage Pay’s updated service: the new service does not include the ability to send payment confirmation emails to the merchant and buyer. Order confirmation emails from SellerDeck will be sent as normal"

I've had nothing from Sagepay although I done what I was told in the SD email and I got an auto email back from Sagepay but even that don't look promising

"Acknowledgement of email, no further action needed

Thanks for applying for an extension.
Your email has been received by our team and will be actioned within 72 hours.
Once your disclaimer has been verified we will apply the extension to your Sage Pay account until the 30th October 2015 and confirm back to you via email.
If there are any problems with your disclaimer and we are unable to add the extension to your Sage Pay account our team will contact you directly with instructions.
As you have submitted your disclaimer before the 31st July 2015 there will be no disruption to your service.
There is no further action for you to take unless our teams advise otherwise"

[Buzby]

Just had my confirmation email from Sagepay extending the deadline 1 day before I leave the country for 3 weeks

I am glad that Sagepay seem to be on the ball, and efficient. I do hope from now on that they are leading this development of intergration and will be pressing Sellerdeck to sort it.

[MikeBooker]

OK - please see post #59 (Page 2)
I can confirm (as I have just tried it) if you send an email to upgrade@sagepay.com you get an automated reply a few minutes later with an attachment you can fill out and apply for the automated extention.
If you don't do this I am yet to be conviced that an extension will be given.

[kev67]

Sellerdeck

4 days before my 3 week holiday where my sites would break on the 31st is not an acceptable timeframe.

I have lost a lot of faith in Sellerdeck support over this issue.

I rest my case

Buzby, I know EXACTLY how you feel

Errrr, any emails sent out to anyone shitting bricks over this from SD by any chance as I'm buggered if I've got one telling me to do this

Piss poor service to be honest if you have to go on a forum to find this info out

Well done as always Louise but come on......the above from Buzby kind of says it all

[Buzby]

Sellerdeck

4 days before my 3 week holiday where my sites would break on the 31st is not an acceptable timeframe.

I have lost a lot of faith in Sellerdeck support over this issue.

[peblaco]

Confirmation today at Sage Pay v3 the extension has to be applied for, signed and sent to SagePay. Details on applying on the new topic here: Sage Pay Protocol v2.23 extension – Action required

[peblaco]

I assumed from the post by SellerDeck announcing the extension on the other topic that it is definite. SellerDeck Support also confirmed the extension of 30th October.

[MikeBooker]

A client emailed SagePay - upgrade@sagepay.com - about this today and received a reply (automated?) with a disclaimer doc attached. The doc was headed "Protocol migration – limited extension agreement" and was offering the extension to 30th October - and no later - if completed and signed. It stated this extension would then be automatic and there would be no further extensions after that date.
It's unclear to me if this is the "automatic" extension which Sellerdeck describe as it appears you have to apply for it.

[adaptive]

My client spoke with SagePay on 10th July, and they said they did not know of any specific agreement between SagePay and Sellerdeck, however an extension to the deadline would only likely if there were significant numbers of Sagepay customers who had not switched to the new protocol by 31st July.

Has anyone who has Sellerdeck support (I or my client do not unfortunately), contacted Sellerdeck to confirm that the extension to the deadline for Sellerdeck users has definitely been agreed?

[kev67]

At least that means that I and several million people can go on holiday without 'shitting bricks' if it's been extended till end of October

I take my hat off to SagePay for doing this, but I still cannot believe the SD gurus cannot sort this out given the time they've had to do so

This must be some serious complex code or what, for SD not to work with it and cause an extension

[Stevet]

Extension

I believe Sage Pay will be releasing an email on 13th July where you can apply for an extension to 30 Oct.

For Specman, thanks for your advice but I am the "hosting company"! They are our own company's servers that unfortunately I look after

[peblaco]

The extension meant users on older versions which use SagePay v2.23 will work until 30th October 2015. Then SagePay v2.23 will no longer work and those using older versions will need to upgrade.

[printerbase]

So with the extension from SagePay do we need to register with SagePay that we are using SellerDeck and they flick some magic switch somewhere for us that keeps us working on 2.23 or is it automatic ?

Thanks

[Specman]

Upgrading V8.5 to V11 for SagePay V3.0

Well with some struggle I have got my site from V8.53 to SellerDeckV1004LDZA, however I just can't get it upgraded beyond that to any V11

My left hand margin fails to display correctly, ends up down the middle of the page with the content displayed below it!

I will keep trying.

I have been working with Winsburys form and have come so close but fell at the last fence. I had my web guy working on it, cost me hundreds, got me nowhere! Its just not that easily fixable I don't think. If Sellerdeck can't do it, my guy can't do it and none of the technical guru's on the forum have a solution then its an impossible mess!
My PayPal is screwed now, not sure its related, but its not returning receipt of payments to the website so everything ends up in Pending Payment Service Provider, god only knows whats going on.

So I'm limping along!

Anybody else had more luck?

[Specman]

Hi Guys

I am still working on this, with Winsbury's version of OCCProtxScripttemplate.pl (I currently use Actinic Multi-Business version 8.5)

I researched on the prerequisite Perl scripts needed and had some success, however I am still learning. I have now run into this error message which I am now trying to solve:

Error executing the on-line credit card plug-in script. Can't locate loadable object for module Crypt::Rijndael in @INC (@INC contains: C:/Perl/site/lib C:/Perl/lib . cgi-bin cgi-bin cgi-bin cgi-bin cgi-bin cgi-bin) at (eval 42) line 64 Compilation failed in require at (eval 42) line 64. BEGIN failed--compilation aborted at (eval 42) line 64.

However at the same time I am writing a report for the company about switching from SagePay to WorldPay which could be a lifesaver for some of you (and me!) I mention this as WorldPay seem to be connected to SagePay as a parent company or something as when I gave them my Merchant ID number they could look up my account.

They (WorldPay) and Sellerdeck indicated to me that they can integrate with my current Actinic website but I am still checking this out as WorldPay Telephone support is nowhere near as good as SagePay and I went through 4 numbers and a lot of contradictory and confusing answers from them until I reached the "right" technical person.

Regards

Steve

Hi
I'm running 8.5 and go this far with Winsburys OCCScriptTemplate

Error executing the on-line credit card plug-in script. Global symbol "$bAuthenticate" requires explicit package name at (eval 44) line 111.

Trouble is there is NOTHING at line 111!

I had your problem. The Perl Scripts look like they are not on the server to me. Ask your hosting company to add them for you.