[Vault] Template term is not translatable

[elisei]

Unable to create translation for highlighted term

Preconditions

1. Magento 2.3+
2. Payment method with vault support and using native template.

Steps to reproduce

1. Store uses any language other than en_US.
2. Use a payment method that allows you to save a card. (This method should consume the native template for managing stored payment methods).
3. Go on My Account -> Stored Payment Methods, click on delete

Expected resul

The content is not translatable.

Actual result

In a translation file for any language you can translate the term.

Possible solution

Presented on the pull

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @elisei. 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.

Please, add a comment to assign the issue: @magento I am working on this

---

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

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[magento-engcom-team]

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

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

[magento-engcom-team]

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

• 9cae620c1648b48b01cce3dcc9fea06c9249a14a
• a1808865c58768cc5e9afdb3c301893743ec6bfd

The fix will be available with the upcoming 2.4.3 release.