Replies: 5 comments 5 replies
-
Thank you for your information. In the OpenCart 3.0.x.x branch we have 3 flavors of SagePay: catalog/controller/extension/payment/sagepay_direct.php They all have a method send using the following URLs: sagepay_direct.php:
sagepay_server.php
sagepay_us.php
Would you please so kind to post the correct URLs for above payment methods? Thanks |
Beta Was this translation helpful? Give feedback.
-
Thanks for this. That clarifies it for sagepay_direct and sagepay_server. Is the URL for sagepay_us still good: |
Beta Was this translation helpful? Give feedback.
-
Will keep the sagepay_us as is, for the time being. What about the Simulator mode for sagepay_direct or sagepay_server? E.g. the old simulator URL is |
Beta Was this translation helpful? Give feedback.
-
Yeah, I think you are right. Will remove the simulator mode. Another question: What do you about the VPSProtocol? The docs seem to suggest using version 4.0.0 (as is the case with the OpenCart Opayo payment extension), yet the sagepay_direct and sagepay_server still use VPSProtocol 3.0.0, which might not work with the new URLs? |
Beta Was this translation helpful? Give feedback.
-
OK, I have now updated the SagePay URLs, and disabled the simulator, for sagepay_direct and sagepay_server, see #13766 |
Beta Was this translation helpful? Give feedback.
-
Just for your information - I know you have been updating the sagepay modules recently.
Following the updates last year with the Opayo gateway becoming a payment product under the Elavon brand, we wrote to you regarding upcoming changes to the URLs you use for your transactions and reporting.
We wanted to remind you that these URLs must be updated by 31st March 2024.
We've already added these updated URLs 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
Beta Was this translation helpful? Give feedback.
All reactions