Transaction details may contain an incorrect PSP reference and order amount in cases when 3DS authorization failed prior to successful authorization

[dpuhach]

Describe the bug
Transaction details may contain an incorrect PSP reference and order amount in cases when 3DS authorization failed prior to successful authorization.

To Reproduce
Steps to reproduce the behavior:

1. Try to pay by card with 3DSecure enabled.
2. Enter a wrong confirmation code once or more times.
3. Enter a correct confirmation code.
4. Check the newly created order in back-office.

Expected behavior
Transaction details provided by the Adyen module must contain the correct information regarding the successful transaction including correct "PSP reference" and "Order amount" (paid ammount).

Screenshots

Desktop (please complete the following information):

• (irrelevant)

Smartphone (please complete the following information):

• (irrelevant)

Additional context
It seems that the failed authorization event is processed by the module after the successful authorization event and is written to the module transaction log in the same order.
However, when displaying information in the upper part of the block with transaction details, information about the last authorization is displayed without taking into account whether it was successful or not.

[adyen-integrations-support]

Hello,

Thank you for reaching out. This is just a quick note to inform you that we received your ticket.

We will take this issue into consideration as soon as possible.

Best regards.

[adyen-integrations-support]

Hi @dpuhach ,

We want to inform you that the new plugin version 5.2.5 has been released. You can download it using the following link: https://github.com/Adyen/adyen-prestashop/releases/tag/5.2.5

If you need assistance with the update or have any questions, feel free to reach out.

Best regards

[dpuhach]

We want to inform you that the new plugin version 5.2.5 has been released. You can download it using the following link: https://github.com/Adyen/adyen-prestashop/releases/tag/5.2.5

It seems you made a mistake to close this issue. Apparently your module update solves two neighboring issues:

• Order Status Reverting to “Payment Accepted” when event "OFFER_CLOSED" is received #283
• Note that your releases contain the wrong file, which has been overridden by PrestaShop #281