Public Hash Error - Githubissues

CelinaNguyen114 commented 3 years ago

Hi Magento Supporter,

Currently, we have discovered the Public Hash error when customers try to create a new order with a saved credit card, they get this error. Also, we see this error when we try to place an order for an existing customer from the Admin panel. It has to do with the Vault where credit cards are saved.

Preconditions

Magento CE 2.3.6-p1
Linux (x86_64)
PHP 7.3.28
mysql Ver 15.1 Distrib 10.3.28-MariaDB

Steps to reproduce:

Case 1: When customers try to create a new order with a saved credit card, they will see the Public Hash error. Case 2 : we see this error when we try to place an order for an existing customer from the Admin panel.

Actual result: Appear the public Hash error.

Public Hash error

Expected results:

The Public Hash will no longer appear

Case 1: When customers try to create a new order with a saved credit card, they will not see the Public Hash error. Case 2: we see not this error when we try to place an order for an existing customer from the Admin panel.

Could you please check this issue and let me know if you need further any information?

Thanks! Celina

m2-assistant[bot] commented 3 years ago

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

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

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: 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.

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

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

m2-assistant[bot] commented 3 years ago

Hi @Penchal-magento. 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: :point_down:

[ ] 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.

m2-assistant[bot] commented 3 years ago

Hi @engcom-Alfa. 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: :point_down:

[ ] 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.

engcom-Alfa commented 3 years ago

Hi @CelinaNguyen114

We followed the steps provided to reproduce the issue unfortunately we did not get any option to select payment method in admin while placing the order.

So, Can you please provide us more details regarding the payment method.

CelinaNguyen114 commented 3 years ago

Hi Manjunath, Thanks for your feedback,We are using payflow from PayPal for our website. Please let me know if you need further information,Best,Celina

On Fri, May 21, 2021 at 8:12 PM Manjunath @.***> wrote:

Hi @CelinaNguyen114 https://github.com/CelinaNguyen114

We followed the steps provided to reproduce the issue unfortunately we did not get any option to select payment method in admin while placing the order.

So, Can you please provide us more details regarding the payment method.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/magento/magento2/issues/32943#issuecomment-845940627, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT6OYKWBBTJSRRIIV6LBSIDTOZL4JANCNFSM44ED3KUA .

CelinaNguyen114 commented 3 years ago

Hi Manjunath, I just wanted to update some information. The public hash happens when we create an order for customers who used to save the credit card at least once on the front end. After debugging the issue, at the time we choose a payment method, we see, it will have a public hash key. However, when I choose the shipping method for the order, the public hash key will disappear.Then, when saving the order, we will see this error. I guess, maybe this issue is related to the public hash key. I hope these information will helpful and let me know if you need anything else,Thanks!Celina

On Mon, May 24, 2021 at 2:38 PM Celina Nguyen @.***> wrote:

Hi Manjunath, Thanks for your feedback,We are using payflow from PayPal for our website. Please let me know if you need further information,Best,Celina

On Fri, May 21, 2021 at 8:12 PM Manjunath @.***> wrote:

Hi @CelinaNguyen114 https://github.com/CelinaNguyen114

We followed the steps provided to reproduce the issue unfortunately we did not get any option to select payment method in admin while placing the order.

So, Can you please provide us more details regarding the payment method.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/magento/magento2/issues/32943#issuecomment-845940627, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT6OYKWBBTJSRRIIV6LBSIDTOZL4JANCNFSM44ED3KUA .

magento-engcom-team commented 3 years ago

:white_check_mark: Confirmed by @engcom-Alfa Thank you for verifying the issue. Based on the provided information internal tickets MC-42425 were created

Issue Available: @engcom-Alfa, 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[bot] commented 3 years ago

Hi @engcom-Lima. 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: :point_down:

[ ] 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.

engcom-Lima commented 3 years ago

Hi @CelinaNguyen114 ,

I went through the magento document, There is no default component implementation for the Admin, so your component must implement all logic for validation and order placing. Please follow the documentation here. https://devdocs.magento.com/guides/v2.4/payments-integrations/vault/admin-integration.html

So, here i have the question have you added vault component for the admin by your self or you trying without doing anything.

Please let me know if you have any query.

engcom-Lima commented 3 years ago

Hi @CelinaNguyen114,

Can you please confirm if this issue still exists for you ? And if yes, please answer the question asked in my previous comment.

engcom-Lima commented 3 years ago

Dear @CelinaNguyen114,

We have noticed that this issue has not been updated for a long time. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Regards

flashtechusa commented 2 years ago

I am having almost the exact same issue in 2.4.3 when an order i being place in the admin order area, if the stored payment method is selected then we get the "Order saving error: Public hash should be defined"

If i login as the customer on the front end the stored payment method works.