SagePay URLs will cease to work

[graphicz]

The party line is that 18.2.3 does not support Opayo



Strangely all the Opayo plumbing seems to be there apart from in PSP selection as above and OCCUpgrade.ini has the Elavon URLs.

[OCCProvider:22]
ID=22
ProviderName='Opayo (Sage Pay)'
TestModeAvailable=1
PreAuthorizedAllowed=1
AuthorizedAllowed=1
ClassID='{AC180055-2C97-11D3-97D6-080000511272}'
ClassIDManager='{AC180055-2C97-11D3-97D6-080000511272}'
PlugInScriptName='OCCSagePay.pl'
ProviderURL='https://live.opayo.eu.elavon.com/gateway/service/'
RemoteProcessScript='vspserver-register.vsp'
DBPlugInScriptName='OCCSagePay.pl'
DBProviderURL='https://sandbox.opayo.eu.elavon.com/gateway/service/'
DBRemoteProcessScript='vspserver-register.vsp'
Debugging=?1
TechnicalFailAllowed=0
FinancialFailAllowed=0
OnlyAuthorize=?0
TemplateName='Act_OCCSagePay.html'
SiteSubDirectory='CommonOCC'
MaxURLLength=-1
AvailableOffline=1
AvailableOnline=1
AccountRegistrationURL='http://www.sellerdeck.co.uk/psp/sagepay/index.htm'

[graphicz]

Strangely all the Opayo plumbing seems to be there apart from in PSP selection as above and OCCUpgrade.ini has the Elavon URLs.

You may need to ask Hugh about this off piste.

[Mantra]

Thank you for the heads up on this one, Jonathan.

For now I have SD Payments by ClearAccept and this is working satisfactorily.

However, Elavon / Opayo appears to provide an alternative option that links to a third party payment service provider without embedded payment page scripts (I think) should the need arise.

I am in no rush to upgrade to SD v18.2.3.

[kev67]

Thanks for the PDF Jonathan, but has anyone tried this?

Forgive my questions but just for clarification, is the PDF file offering/saying that you can change the URL's by either manually editing the SD database or the other option is by editing the .pm scripts?
I'm fine with editing the .pm files but not really wanting to mess about with the database. I'm using V16.03

Thanks

[PA.com]

Hi Kev

I have gone through the procedure of upgrading the Opayo URLs as described here (and now featured on the KnowledgeBase) and can confirm it appears to be working fine for me. I didn’t change any .pm scripts, as Jonathan mentions you just need to locate and change the OCCUpgrade.ini file within the Program Files (x86) directory. To edit this, you need to open Notepad first by right-clicking on it and run as Administrator, and then locate and open the file from within the Notepad file menu. Edit it then select Save.

The only thing the pdf doesn’t mention is that after Forcing the PSP Upgrade then closing and reopening Sellerdeck, you still need to upload to website in order for the changes to take place. This in itself will change some perl scripts within the CGI bin, haven’t yet checked which ones though.

Good luck with it, do make sure everything’s backed up first for peace of mind.

[kev67]

Many thanks PA.Com
Editing the OCCUpgrade.ini shouldn't be a problem for me, I'll be fine with doing that. Reading all the above freaked me out a bit, but thanks again for confirming it to me

I'll do that this afternoon