Support

January 15, 2024 at 7:43 am

Hi. We received the below email from SagePay regarding their change to Opayo – will any urls within the Events Expresso plugin change from Sagepay to Opayo before the SagePay change deadline? If you could kindly confirm – or if they are able to be set in the plugin if you could kindly advise where that would be much appreciated. Thank you.

Please see below email from SagePay/Opayo:

Hi,
  
Following the updates earlier this year with the Opayo gateway becoming a payment product under the Elavon brand; we wanted to let you know about further exciting changes.  
 
Opayo has been a key member of the Elavon family for over three years now, and as we continue with the integration into Elavon we will soon make updates to the URLs you use for your transactions and reporting.
 
What does this mean?
The URLs you use to send transactions to Opayo will be changing to an Elavon domain and you need to make the changes to send your transactions to the updated URLs. 
  
These changes must be made by 31st March 2024, this is when the SagePay URLs will cease to work.
 
We’ve already added these updated URL’s to our Developer Hub to help you make the changes, you can find the URLs specific to your integration below:
 
Pi integration
Direct integration
Form integration
Server integration
RAAPI
Shared API
 
If you’re using a shopping cart provider speak with them directly regarding this to make the relevant updates.
 
Important information
The HTTP standard of all headers is lower case with the new URLs, be aware of this if you have specific code to look for case sensitivity. 
We recommend using domain names instead of hard code, if you have hard-coded an IP address in your website or shopping cart you’ll need to update this also. 
Flush DNS cache (local) or Internet Service Provider (ISP) may cache DNS records. In this case, you will need to speak directly with your ISP to ensure you have the most up-to-date DNS records.
You will need to ensure the new URLs are whitelisted and any firewall rules you have in place have been updated. 
If you have implemented a content security policy you will also need to update this.
As always, we recommend testing any changes you make in your testing environment before implementing them to production.
 
Upgrade your protocol version 
When making these updates take this opportunity to upgrade to our latest protocol version.
 
Following previous communication on 31st January 2024 we are retiring protocol version 2.22 and 2.23, this would be a great opportunity to upgrade to our latest protocol version ensuring your transaction are processed compliantly and you have access to all the latest features that Opayo have introduced.
 
We’re here to help
For advice on making the relevant changes please contact your account manager, or contact support directly at opayosupport@elavon.com or 0191 313 0299.

Opayo by Elavon Team