Web & game design services from Leeds, Yorkshire
Web & game design services from Leeds, Yorkshire
Published Tuesday 19th March 2024
In case you missed it, Elavon began merging Opayo, formerly Sagepay, into their brand earlier in 2023, and in November Elavon announced that the next step to this merge would be to discontinue support for older Opayo URLs. As of 31st March 2024, which at the time of this writing is now just short of 2 weeks away, websites using these older Opayo URLs for payment integrations will stop working. If you're running such a website, it's critical that you update your integration before 31st March 2024.
Update: On March 22nd, Elavon extended this deadline to 31st May 2024.
This affects all of the available Opayo payment integration methods: Pi integration, Direct integration, Form integration, inFrame integration, Server integration, RAAPI, and Shared API. Information on all of these integration methods can be found at the Elavon developer portal.
The update is, thankfully, fairly straightforward. You just need to find where these old Opayo URLs exist in your website code, and replace them with the newer, Elavon branded variants. For example, if your website was built around Sagepay Direct or Opayo Direct integration, then the URLs you're looking for in your integration code should look like this:
https://live.sagepay.com/gateway/service/vspdirect-register.vsp
https://live.sagepay.com/gateway/service/refund.vsp
https://live.sagepay.com/gateway/service/release.vsp
https://live.sagepay.com/gateway/service/abort.vsp
https://live.sagepay.com/gateway/service/repeat.vsp
https://live.sagepay.com/gateway/service/direct3dcallback.vsp
https://live.sagepay.com/gateway/service/vspserver-register.vspExactly where these sit in your code is subject to how your website was built, and finding them is the tricky bit. Once found, all you need to do is swap out the live.sagepay.com part, with live.opayo.eu.elavon.com, like this:
https://live.opayo.eu.elavon.com/gateway/service/vspdirect-register.vsp
https://live.opayo.eu.elavon.com/gateway/service/refund.vsp
https://live.opayo.eu.elavon.com/gateway/service/release.vsp
https://live.opayo.eu.elavon.com/gateway/service/abort.vsp
https://live.opayo.eu.elavon.com/gateway/service/repeat.vsp
https://live.opayo.eu.elavon.com/gateway/service/direct3dcallback.vsp
https://live.opayo.eu.elavon.com/gateway/service/vspserver-register.vspWhile you're at it, you should also look for the protocol version referenced in your code. Again, finding where this is in your website code might be tricky, but you're looking for the value that your integration passes as a VPSProtocol parameter in the initial request to Elavon / Opayo. If this value is already 4.00 then you're sorted, but if it's 3.00, 2.23, or 2.22, then you need to look at migrating your integration to protocol 4.00, which differs slightly in a few important but relatively simple ways. Protocol migration is beyond the scope of this post, and Elavon provide various migration guides via their developer portal detailing the changes you need to make, subject to your current protocol version and type of integration.
If you're worried that your website will stop working on 31st March and you need somebody to investigate your current integration and advise or update it for you, please do get in touch. We're Elavon partners and very, very experienced with Opayo and Sagepay integrations.
Ric is a senior web and game programmer with nearly 30 years industry experience and countless programming languages in his skillset. He's worked for and with a number of design and development agencies, and is the proprietor of QWeb Ltd. Ric is also a Linux server technician and an advocate of free, open-source technologies. He can be found on Mastodon where he often posts about the projects he's working on both for and outside of QWeb Ltd, or you can follow and support his indie game project on Kofi. Ric also maintains our Github page of useful scripts.
Blog posts are written by individuals and do not necessarily depict the opinions or beliefs of QWeb Ltd or its current employees. Any information provided here might be biased or subjective, and might become out of date.
Nobody has commented yet.
Your email address is used to notify you of new comments to this thread, and also to pull your Gravatar image. Your name, email address, and message are stored as encrypted text. You won't be added to any mailing list, and your details won't be shared with any third party.