Bank Transer Payment Instuctions switch back to default

[rstylenl]

Summary (*)

The default Magento 2 Bank Transfer Payment has an issue when you have multiple stores.
If you create an order and select Bank Transfer Payment as payment method. Then go look at the just created order the title doesn't reflect the one we have setup in the store configuration. (Says: Bank Transfer Payment instead of "Überweisung (per Bank)"

The instructions are fine. But if you click Ship, Invoice the instuction gets reset to the default value that is in the system->configuration.

Preconditions (*)

1. Magento 2.2.x, 2.3.x, 2.4-develop
2. PHP 7.1, 7.2

Steps to reproduce (*)

1. Create second store & store view.

2. Enable Bank Transfer Payment.
   

3. Change title & instructions of Bank Transfer Payment for second store.
   

4. Create a new order with Bank Transfer Payment from second store.

5. Go to the Order information in the backend.
   

6. Check email
   

7. Then click invoice or ship.

8. Check order info again in the backend & email

Expected result (*)

1. Payment information should be collected from the store the orde was placed in.

Actual result (*)

1. Payment information show the default information from Store configuration. (in backend and in emails for Invoice/Shipment):
   Admin:
   
   Email:
   

[magento-engcom-team]

Hi @rstylenl. 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-engcom-team give me {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[ghost]

Hi @rstylenl , thank you for your report.
We've acknowledged the issue and added to our backlog.

[rstylenl]

Small update - Even when you cancel the order the payment information will revert to the default config info.

[rstylenl]

@engcom-backlog-nazar @prakashpatel07

I have just tested this on a Vanilla Magento 2.2.3 installation and the payment information was as expected so it did not change it back to the default store. In the email that is send to the 'client' the Payment information Title is reset to the default store, but the Instructions are from the store the client order at. See screenshots below (i removed my personal info).

After placing the order (Backend):

Info in Email after order is created:

After creating the invoice: (Backend)

Info in Email after creating invoice:

In the invoice email the title of the payment method is reset to the Default store.
Store title is set to: Virement bancaire like you see in the backend.
Payment instructions however are correct.

[m2-assistant]

Hi @engcom-Charlie. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[magento-engcom-team]

✅ Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-30147 were created

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

[m2-assistant]

Hi @Bartlomiejsz. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[magento-engcom-team]

Hi @rstylenl. Thank you for your report.
The issue has been fixed in #26765 by @Bartlomiejsz in 2.4-develop branch
Related commit(s):

• 7c4be6a770ff543a6906b3d6f77b31d1988addf1

The fix will be available with the upcoming 2.4.0 release.