Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Users encountering an error while attempting to pay for order using UPE method #5808

Closed
timur27 opened this issue Mar 17, 2023 · 2 comments · Fixed by #6177
Closed

Users encountering an error while attempting to pay for order using UPE method #5808

timur27 opened this issue Mar 17, 2023 · 2 comments · Fixed by #6177
Assignees
Labels
category: projects For any issues which are part of any project, including bugs, enhancements, etc. priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. type: bug The issue is a confirmed bug.

Comments

@timur27
Copy link
Contributor

timur27 commented Mar 17, 2023

Describe the bug

When trying to Pay for order with any of the available UPE methods, user sees an error Invalid payment method. Please input a new card number.

To Reproduce

Enable split UPE and:

  1. Buy a product using the shortcode checkout and UPE method (e.g. Sofort)
  2. On the third-party test payment page, choose Fail test payment
  3. After redirected back to the checkout page, go to My account -> Orders, find the failed order and click Pay
  4. On the Pay for order page, choose any of the available UPE methods and click Pay for order

Actual behavior

Users are seeing Invalid payment method. Please input a new card number. error notice.

Screenshots

image.png

Expected behavior

Users shouldn be able to pay for order successfully, using any of the available payment method on the list.

Desktop (please complete the following information):

  • OS: MacOS
  • Browser: Chrome
@timur27
Copy link
Contributor Author

timur27 commented Mar 17, 2023

Hey team! Please add your planning poker estimate with Zenhub @FangedParakeet @mdmoore

@timur27 timur27 added priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue is a confirmed bug. labels Mar 17, 2023
@RadoslavGeorgiev RadoslavGeorgiev added the category: projects For any issues which are part of any project, including bugs, enhancements, etc. label Mar 22, 2023
@FangedParakeet FangedParakeet self-assigned this Apr 4, 2023
@FangedParakeet
Copy link
Contributor

I now have a PR ready that will (eventually) resolve this issue, but I am going to mark this issue temporarily blocked for now, since I have also learned that this functionality is also blocked by #5854 and we will not be able to return this functionality, until a hero appears to save us from despair by resolving that particular issue.

I have identified three issues that are causing these frustrating failures.

  1. If order currency and customer selected currency do not match, if the customer selected currency is not supported by available payment method, payment intent will produce an error and payment elements will fail to mount.
  2. Pay for order form incorrectly detects when WCPay payment method is selected at checkout.
  3. Payment intent confirms successfully, but process_redirect_payment function exits early, order is not updated, and instead marked as a failure.

Please see #6177 for more specific details on these maladies and their various cures.

@FangedParakeet FangedParakeet added the status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. label Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: projects For any issues which are part of any project, including bugs, enhancements, etc. priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. type: bug The issue is a confirmed bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants