-
Notifications
You must be signed in to change notification settings - Fork 79
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
Support Sage Pay Form #112
Comments
This API does not provide a However, there are no plans for this at this time, as the |
…pport. For thephpleague#114 the `billingForShipping` flag copies the billing address to the delivery address, so only the billing address needs to be supplied.
This is now functional, though there are some additional message parameters to support for |
The encryption uses openssl and not PHP's mcrypt (which is deprecated as of PHP 7.1 |
The linked branch now supports Sage Pay Form if anyone else would like to try it out. It needs more tests, and there are some Form-only features and parameters to be added, but it is functional. It needs openssl to be available, as it does not have a fallback to mcrypt (this can be added if anyone wants to provide it - should be simple enough). |
…sactionReference, where available.
…`Form` direct.
…9-1 by default. Provide an option to disable this for when the merchant site handles it already. In the vast number of cases, the conversion should stand. That is, until Sage Pay get their ISO8859 technical debt sorted out for good.
Released as 3.2.0 |
Though mostly front end, Sage Pay
Form
shares a lot of the back end APIs and data structures withServer
andDirect
.The text was updated successfully, but these errors were encountered: