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)

[dmitrii-fediuk]

https://github.com/mage2pro/checkout.com/blob/1.4.7/view/frontend/web/main.js#L7-L34

[dmitrii-fediuk]

Similar issues:

• 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 allpay#3
• 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) core#45
• 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 paymill#3
• 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) securepay#3