- Issue created by @brandonlira
Opayo/Elavon have emailed us to say they will be updating the URLs we use for our transactions and reporting.
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.
SAGEPAY_SERVER_SERVER_TEST
and SAGEPAY_SERVER_SERVER_LIVE
respectively).Update the SagePay module by replacing the existing URLs (SAGEPAY_SERVER_SERVER_TEST
and SAGEPAY_SERVER_SERVER_LIVE
) with the new URLs provided by Elavon for both test and live environments.
But I'm not sure if we have to update all the URLs on the file
Test environment:
Before: SAGEPAY_SERVER_SERVER_TEST pointing to 'https://test.sagepay.com/gateway/service/vspserver-register.vsp'
After: SAGEPAY_SERVER_SERVER_TEST pointing to 'https://sandbox.opayo.eu.elavon.com/gateway/service/vspserver-register.vsp'
Production Environment (Live):
Before: SAGEPAY_SERVER_SERVER_LIVE pointing to 'https://live.sagepay.com/gateway/service/vspserver-register.vsp'
After: SAGEPAY_SERVER_SERVER_LIVE pointing to 'https://live.opayo.eu.elavon.com/gateway/service/vspserver-register.vsp'
SAGEPAY_SERVER_SERVER_TEST
and SAGEPAY_SERVER_SERVER_LIVE
in the SagePay module code.No direct user interface changes are expected from this update. However, users will experience improved transaction processing post-update.
No API changes are introduced; only the URLs within the module codebase are updated.
There are no data model changes associated with this update.
Active
1.0
Code