Opayo URL migration FAQ

Opayo has been a key product in the Elavon family for four years. As we continue to integrate Opayo into Elavon, we’re updating the URLs you use for your gateway transactions and reporting.

It’s time to make changes at your end, to send your Opayo transactions to these updated URLs (which you’ll find below). It's easy to make this switch, and it’s important: this change will ensure you can keep processing transactions so there’s no disruption to your business.

• If you’re using the Pi integration, you can find the updated URLs here.   
• If you’re using the Direct integration, you can find the updated URLs here.
• If you’re using the Form integration, you can find the updated URLs here.
• If you’re using the Server integration, you can find the updated URLs here.
• If you’re using the Reporting and Admin API, you can find the updated URLs here.
• If you’re using the Shared protocol integration, you can find the updated URLs here.

To support our customers and give them time to make these updates, we’ve extended the deadline to 31 December 2024.

If you’re using Virtual Terminal in the MyOpayo portal, there's no action for you to take. If you use a virtual terminal outside of the MyOpayo portal, then you need to make these updates.

You can trust Elavon to protect your business, your reputation and your customers’ data. We work hard to stay one step ahead of industry developments, advances in technology and our security obligations. We put customers first and this why we need you to make these changes – so we can continue to give you our very best service. We don’t cover costs of switching URLs, but we do supply everything you need to make these changes so we can continue to support your business. You’ll find more detailed information and the tools to help you here. If you need any extra help, do get in touch.

Before you migrate to the new URLs, here are some tips to head off any potential problems:

• Make sure you’re using the current set of Cipher suites for the new URLs:

TLS-AES-256-GCM-SHA384
TLS-CHACHA20-POLY1305-SHA256
TLS-AES-128-GCM-SHA256
TLS-AES-128-CCM-8-SHA256
TLS-AES-128-CCM-SHA256
ECDHE-ECDSA-AES256-GCM-SHA384
ECDHE-ECDSA-AES128-GCM-SHA-256
ECDHE-RSA-AES256-GCM-SHA384
ECDHE-RSA-AES128-GCM-SHA256
ECDHE-ECDSA-CHACHA20-POLY1305
ECDHE-RSA-CHACHA20-POLY1305

• You’ll need to ensure the new URLs are whitelisted and any firewall rules you have in place have been updated.   
• 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 an IP address. 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.