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.

Sign up for GitHub

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

Jump to bottom

A payment's amount could be changed client-side (e.g., on a discount code application), and `amount_int: this.amountF()` will produce a wrong result in such case #3

Open

dmitrii-fediuk opened this issue Nov 5, 2017 · 1 comment

Labels

bug

Member

dmitrii-fediuk commented Nov 5, 2017

https://github.com/mage2pro/paymill/blob/1.6.1/view/frontend/web/main.js#L94-L100

dmitrii-fediuk added the bug label

Member Author

dmitrii-fediuk commented Nov 5, 2017 •

edited

Loading

Similar issues:

This was referenced Nov 5, 2017

A payment's amount could be changed client-side (e.g., on a discount code application), and we should update the installments table in such case mage2pro/allpay#3

Open

A payment's amount could be changed client-side (e.g., on a discount code application), and we should recall Dfe_SecurePay/main::debugMessage() in such case (though, it affects only the test mode) mage2pro/securepay#3

Open

A payment's amount could be changed client-side (e.g., on a discount code application), and we should recall Dfe_CheckoutCom/main::debugMessage() in such case (though, it affects only the test mode) mage2pro/checkout.com#4

Open

Df\Payment\ConfigProvider::config(): passing amountF to the client side is incorrect, because a payment's amount could be changed client-side (e.g., after a discount code application) mage2pro/core#45

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment