Click on "Purchase Order" cause error in discount section

[vovayatsyuk]

Preconditions (*)

1. Magento 2.3.5

Steps to reproduce (*)

1. Enable "purchase order" and "check/money" payment methods
2. Navigate to checkout
3. Proceed to payment step and expand the discount block section
4. Change payment to "Purchase order"
5. An error will be added to the discount sectiton.

Expected result (*)

1. I expect no errors at all because I just wanted to change payment method.

Actual result (*)

1. Error is shown

Explanation

The issue is caused by the 'setPaymentInformationAction' request added to fix per-payment coupon discount: b6880b2#diff-aa8b012e2fbfb8f3c2904b7ea0504606

Possible Solution

We need some "lightweight" version of savePaymentInformation method that will work with minimum data and will not trigger any errors.

[m2-assistant]

Hi @vovayatsyuk. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@vovayatsyuk do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[vovayatsyuk]

@magento give me 2.4-develop instance

[magento-engcom-team]

Magento instance deployment temporary unavailable due to service maintenance.

[m2-assistant]

Hi @sudheers-kensium. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[sudheers-kensium]

Issue is reproduced on Magento 2.3.5 and after few seconds error message is disappearing.

[magento-engcom-team]

✅ Confirmed by @sudheers-kensium
Thank you for verifying the issue. Based on the provided information internal tickets MC-34290 were created

Issue Available: @sudheers-kensium, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[CarmineDamore78]

Issue not reproduced on Magento 2.3.4

[sudheers-kensium]

Issue is reproduced on Magento 2.3.5p1.

[balaji-pinpoint]

@magento I am working on this

[m2-assistant]

Hi @balaji-pinpoint! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[balaji-pinpoint]

@magento I am working on this

[engcom-Alfa]

The issue is reproducible on fresh 2.4-develop

[surabhisrivastava09]

@magento i am working on this.

[surabhisrivastava09]

#dmcdindia2020

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[vovayatsyuk]

This issue is still relevant.

Additional note: when agreements are enabled you'll see the error about agreements when trying to change the selected payment method. And this time it's not related to the "Purchase Order" method. All methods are affected as well.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[vovayatsyuk]

This issue is still relevant. #28208 (comment)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 28 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[vovayatsyuk]

.

[hostep]

Issue was confirmed, so stalebot should shut up.

[engcom-Bravo]

Hi @vovayatsyuk,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is no more reproducible.Kindly refer the attached video.

Screen.Recording.2024-05-27.at.15.10.28.mov

We are able to change the payment method.

Hence We are closing this issue.

Thanks