Hi,
By just looking in the HikaShop Payment log, it is possible to see that data:
Received data from SagePay
crypt: @bfdc8961d059b5.....
Data: VendorTxCode=77&VPSTxId={F7209D35-9FB6-10B6-3875-E475371D1D7C}&Status=MALFORMED&StatusDetail=4001 : The VendorTxCode has been used before. All VendorTxCodes should be unique.&Amount=20
I also made a test where I just cancel when I arrived in the SagePay website and it generated that data:
Received data from SagePay
crypt: @5dcee0750f33d270...
Data:
VendorTxCode=80&VPSTxId={006CC44A-C4AE-7C58-3813-B232D59597E9}&Status=ABORT&StatusDetail=2013 : The Transaction was cancelled by the customer.&GiftAid=0&Amount=33.90
For sure I can't explained the element in your log where the crypt data is fully empty
-- 10.30.15 08:25:53 --
Received data from SagePay
crypt:
Data:
But like Philippe wrote in a previous message ; having a look in your web-server log will be the best in order to know who call the notification URL and with which arguments.
Just in case, we added an extra parameter in the cancel url given to SagePay ; but that URL also contain the crypt data when used, as my test transaction show that.
Now I recommend you to see with SagePay support team about your used VendorTxCode.
Because the message which we can see in your log indicate that you have an issue with non unique order id
The VendorTxCode has been used before. All VendorTxCodes should be unique
Regards,