|
By ianguest - Mon 2 Feb 2015
|
I have been informed that SagePay are updating their protocol to include additional functionality and payment form.
The change is now v3.00 and SagePay are pushing for everyone to upgrade.
Firstly, has anyone upgraded their SagePay yet? And does it work fine with Kartris?
Secondly, does it work find with Kartris v2.5009?
Currently trying to find time to upgrade everything to V2.8001, so need it to work with the older version.
|
|
By ianguest - Mon 2 Feb 2015
|
OK
I have spoken to SagePay. The Protocol V3.00 will be mandatory in the summer. All vendors will have to agree the upgrade before hand. Currently there is no date set.
The main differences are enhanced mandatory fields and encryption of data.
More information can be found:
https://www.sagepay.co.uk/support/find-integration-document/migrate-to-v3
|
|
By Paul - Wed 4 Feb 2015
|
|
The Sagepay plugins for Kartris have supported protocol v3.00 for some time now, probably 2-3 years I think.
|
|
By ianguest - Fri 6 Feb 2015
|
|
So can you confirm that Kartris v2.5009 is OK for SagePay protocol v3.00
|
|
By Paul - Fri 6 Feb 2015
|
I think it should be, suggest trying it - change the protocol from the config settings and see if you can pass orders ok.
If not, grab the sagepay plugin DLL from the latest Kartris, and it should work fine with 2.5.
Back everything up first of course, just in case. But pretty sure it should all work.
|
|
By ianguest - Mon 30 Mar 2015
|
This is for Kartris v2.5009
Sadly when I copy over the files SagePay.dll / SagePay.dll.config an error on the Sagepay system flags up.
*****************
This transaction attempt has failed. Please use the Proceed button go back to the web store from which you were purchasing. The details of the failure are given below.
| | Status: | INVALID
| | Status Detail: | 5068 : The encryption method is not supported by this protocol version.
|
|
|
By Paul - Tue 31 Mar 2015
|
|
This sounds like the old DLL is still in play. You might find the DLL is locked out when the site is live, so cannot be overwritten. Try stopping the site in IIS, or restarting from the back end, before uploading the new one.
|