Support

Home Forums Event Espresso Premium Elavon (Opayo) integration

Elavon (Opayo) integration

Posted: April 3, 2024 at 10:02 am


hoffman

April 3, 2024 at 10:02 am

Hi there
We’re very happily running the SagePay plugin with Event Espresso, but have now received this scary email. Is there something we need to be doing at our end, please?

Elavon

Important Update

Update to Opayo URLs
Notice 1C 25th March 2024

Hi there,

We’ve been in touch a few times, to tell you we’re changing the URLs you use for your transactions and reporting. This is part of last year’s brand changes, with the Opayo gateway becoming a payment product under the Elavon brand.

We’d planned to stop supporting these old URLs from 31 March. We’ve noticed you’re still processing transactions using the older URLs though, and we don’t want any of your payments to fail. So, we’re going to extend this deadline. This will give you time to switch to the updated URLs – and we can continue to support you.

You now have until 31 May 2024 to upgrade to our new URLs, to make sure there’s no disruption to your business.

Where can you find the updated URLs?

We’ve already added these updated URLs to our Developer Hub. To help you make the changes quickly, here are the URLs specific to your integration below:

Pi integration
Direct integration
Form integration
Server integration
RAAPI
Shared API

If you haven’t visited the Developer Hub before, you’ll need to ensure the location is set to your country before these specific links will work.

We strongly recommend that you test any changes made to your integration in your TEST account before deploying the changes to go LIVE. Need more information on how to access your TEST account? You can find it here.

Of course, if you’ve recently made these changes, this advice doesn’t apply and there’s no action to take.

Important information to note!

You’ll need to note the following when making these updates, to support a smooth migration of your URLs:
With the new URLs, the http standard of all headers is lower case – 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’ve hard-coded an IP address in your website or shopping cart, you’ll need to update this too.
Flush DNS cache (local) or Internet Service Provider (ISP) may cache DNS records. In this case, you’ll need to speak directly with your ISP to ensure you have the most up-to-date DNS records.
You’ll need to ensure the new URLs are whitelisted and any firewall rules you have in place have been updated.
If you’ve implemented a content security policy, you’ll also need to update this.
We’re here to help

If you need any advice on making these changes, do get in touch with us. You can email opayosupport@elavon.com or call us at:
0191 313 0299 (if you’re in the UK)
01 240 8731 (if you’re in the Republic of Ireland).
Thanks again for your business,
The Opayo Product Support Team

Your information is processed in line with our Privacy Policy UK and Ireland
Elavon Financial Services DAC. Registered in Ireland with Companies Registration Office. The liability of the member is limited. United Kingdom branch registered in England and Wales under the number BR022122.
Elavon Financial Services DAC. Registered in Ireland – Number 418442. Registered Office at Block F1, Cherrywood Business Park, Cherrywood, Dublin 18, D18 W2X7, Ireland.


Sam

  • Support Staff

April 3, 2024 at 11:54 am

Hi there,

I’ve checked and the issue has already been reported to our developers and will be updated in the next update.

So please make sure you are using the latest version of the plugin and update the plugin as well when the update is available.


hoffman

April 4, 2024 at 12:58 am

Hi Sam

I’ve been advised to stay on an older version of EE while a separate issue is investigated (which seems to have gone quiet): https://eventespresso.com/topic/updated-ee-table-plugin-causing-problems/

So I can’t follow your advice, unfortunately. Also a little concerned that if there was a 1 April deadline (and now a revised May deadline), there’s no firm ETA for this update.

We spent yesterday dealing with numerous customer complaints about failed payments, and am expecting the same today. We can’t reliably take bookings as this stand – any way to prioritise this issue as urgent, please?


Sam

  • Support Staff

April 4, 2024 at 2:05 am

Sorry for the confusion above. You need to update the SagePay plugin to the latest version as the above issue is already in the queue.

Also, regarding the EE plugin that is also under testing, an update will be released soon.


hoffman

April 4, 2024 at 2:08 am

Thanks Sam – I’m on version 11.7 and can’t see an option to update?


Sam

  • Support Staff

April 4, 2024 at 2:11 am

That is the latest version for now and the issue will be fixed in our upcoming update.

I appreciate your patience.

You must be logged in to reply to this support post. Sign In or Register for an Account

Event Espresso