MD5 signature - change from Pending to OK for PPRO payments about sagepay HOT 3 OPEN

Do you know what status detail you are sending back in the notification (callback) call? Is it "Notification has been tampered with" or "Transaction has already been processed"?

I have had occurrences of the same notification being sent from Sage Pay multiple times because the first "OK" response did not get back to Sage Pay for whatever reason. This library needs to recognise a duplicate notification and return the previous response again instead of an error. This may or may not be the issue you are having, depending on the details of the error your notification is returning. It should all be stored in the database - you are welcome to directly send me a an exported database record for a failed transaction and I will take a look at it.

from sagepay.

The message you got from Sage Pay may be technically correct, and is what this package does, but may be missing the context of what is actually going wrong here. If the PPRO callback happens 20 minutes after the initial transaction, then I have a hunch it is related to there being callbacks in two stages - and it failing only on the second callback, as it was only expecting one. Again, if you have any more details you can send me, I would be glad to take a look and fix this package if it highlights what could be going wrong.

It's this statement that makes me suspicious: "there is a problem with the MD5 signature built by your server". Sage Pay can only reach this conclusion if they see the response detail "Notification has been tampered with". Is that what they see?

from sagepay.

Does release 0.9.7 help fix this issue for you?

from sagepay.