Customer has no any vault token save, but vault payment method appears in admin checkout

[github-jira-sync-bot]

Issue:
Customer has no any vault token save, but vault payment method appears in admin checkout

Steps to reproduce:
1). Go to Magento Admin panel
2). Setup "Payflow Pro" payment method and enable vault payment (Stores - Configuration - Sales - Payment Methods - Configure "Payflow Pro" -
Enable this Solution : Yes, Vault Enabled : Yes)
3). Clear cache
4). Admin - Sales - Orders - Create new Order - Create New Customer / or Select any existing customer
5). Add Products
6). Payment Method section - Issue: "Stored Cards (Payflow Pro)" Payment option is getting displayed
Select this payment method option and other required options and fields to place the order
Submit Order: Issue: "Order saving error: Public hash should be defined" error message is displayed to the user.

Expected result:
If customer has no token saved, than Vault Payment should not be shown in Payment section of Admin Order creation page

Actual result:
Vault Payment option is available for the user even though user has not any token saved
Order saving error: Public hash should be defined" error message is displayed to the user.

[github-jira-sync-bot]

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1215

[m2-assistant]

Hi @github-jira-sync-bot. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

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

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• 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, join the Community Contributions Triage session to discuss the appropriate ticket.

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

[rogerdz]

@magento I am working on this

[chittima]

Internal Team started working on this issue and solution is almost ready

[engcom-Lima]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Lima. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Lima, here is your Magento Instance: https://5ac9debb5c3d53f742930b03ed2746e6.instances.magento-community.engineering
Admin access: https://5ac9debb5c3d53f742930b03ed2746e6.instances.magento-community.engineering/admin_4849
Login: 745bad55
Password: c912ee05d636

[chittima]

Issue is fixed and here is the commit:
1112cab