-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is VPSSignature utilised? #31
Comments
Yes, it's in It checks there whether the notification has been tampered with, before accepting the results it provides. It means that SagePay can send the results of the transaction to your site over a HTTP channel (you don't need a HTTPS certificate on your server, though obviously it is desirable to have one for other user interaction with your site). |
The example of a callback controller that calls notification() is on the main readme https://github.com/academe/SagePay |
Thanks, and I'm sorry to trouble you - I should have searched harder before posting. |
Not a problem at all :-) Glad to see the package being useful, and more questions can only lead to improvements to the code or the documentation. |
Hi, given that this class is not yet complete, does it carry out the md5 hash check using VPSSignature, please?
The text was updated successfully, but these errors were encountered: