search

mollie / magento2

Mollie Payments for Magento 2
https://www.mollie.com
Other
101 stars 52 forks source link

[Amasty Extra Fee] Klarna payment with GBP and Amasty Extra Fee 422 Error #576

Closed Ahmet-Djedovic closed 1 year ago

Ahmet-Djedovic commented 1 year ago

Describe the bug The moment a customer try to place an order with a Amasty Extra Fee item on the a storeview with sterling pounds, then choose Klarna, we get an error message and the customer can't continue with checkout.

Used versions

To Reproduce Steps to reproduce the behavior:

  1. Go to admin panel and create a Fee this example fee: image

  2. Go to frontend side and select a storeview with GBP: image

  3. Proceed to the checkout section and fill in Netherlands as a billing and shipping adress:

  4. Select a your fee that you have created in step 1 image

  5. Select Klarna Pay Later as a payment method: image

  6. Proceed to finish checkout and see error: image

Expected behavior As a user of i would like to be able to buy a product using mollie with a extra fee with my preferred payment method (klarna) and preferred currency (GBP)

Actual behavior Expetion gets thrown when i try to pay for my goods:

[2022-10-25T09:46:42+0000] Error executing API call (422: Unprocessable Entity): The amount of the order does not match the total amount from the order lines. Expected order amount to be €220.37 but got €220.42. Field: amount. Documentation: https://docs.mollie.com/overview/handling-errors

Screenshots image

Additional context Please make the fee above the ~0.30, 0.25 does work. Any amount higher then 0.30 cent wont work

Frank-Magmodules commented 1 year ago

Hi @Ahmet-Djedovic , thank you for opening this issue, and sorry for the late response. We've tried to find the plugin that you are using to reproduce the issue but didn't succeed. Can you please contact us directly so we can take a look with you? Thanks a lot!

Frank-Magmodules commented 1 year ago

Hi @Ahmet-Djedovic,

Due to the lack of information and we can’t reproduce this issue, we will close this issue for now. Please feel free to reopen the issue or contact us directly through our contact form so we can investigate this issue further with you.