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

Enhanced UPE - Blocks integration #5020

Closed
FangedParakeet opened this issue Oct 31, 2022 · 2 comments · Fixed by #6537
Closed

Enhanced UPE - Blocks integration #5020

FangedParakeet opened this issue Oct 31, 2022 · 2 comments · Fixed by #6537
Assignees
Labels
category: projects For any issues which are part of any project, including bugs, enhancements, etc. component: upe priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. size: large The issue is sized large. type: enhancement The issue is a request for an enhancement.

Comments

@FangedParakeet
Copy link
Contributor

Description

Stripe will soon release a new refactor of their UPE offering new payment integration flows. The most crucial addition is that they will now offer server side payment intent confirmation for the UPE, meaning that the payment intent is no longer required prior to presenting the UI element and the intent can be created and confirmed after collecting the payment information into a payment method.

This necessitates a refactor for both shortcode and blocks checkouts, where both create a payment intent as the first order of business, before loading any UI elements. This new refactored blocks implementation may now have significant resemblance to the previous legacy card element implementation. This issue is to complete this blocks integration.

This issue is currently blocked until Stripe accepts us into their beta release program for their new enhanced UPE tool. This is also likely blocked by #5019. Although it would not be impossible for these two pieces to be completed in parallel, there will likely be significant overlap on the back-end portions of both implementations, so it would be preferable to complete the PoC prior to this effort.

Acceptance criteria

  • Able to successfully complete checkout with new payment method via Blocks checkout.

Additional context

Stripe UPE – Options to solve WooPay compatibility and WC Pay loss of control over the payments UI/UX
#4603

@FangedParakeet FangedParakeet added type: enhancement The issue is a request for an enhancement. 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. size: large The issue is sized large. component: upe labels Oct 31, 2022
@RadoslavGeorgiev RadoslavGeorgiev added the category: projects For any issues which are part of any project, including bugs, enhancements, etc. label Nov 1, 2022
@FangedParakeet
Copy link
Contributor Author

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

@timur27
Copy link
Contributor

timur27 commented May 1, 2023

I think we need to update the description and the ACs.

From a technical standpoint, the success of this issue would be the working Blocks checkout page. However, we need to consider which payment methods should be working after this issue is completed. In addition to card and non-card gateways, there is also WooPay and Stripe Link. Should we include them both in the scope? They also need to be implemented for the shortcode, so a separate issue to cover Stripe Link & WooPay for both shortcode and Blocks seems to be a good option to consider as well.

Furthermore, any reusable components from issue #5869 should be re-used in this issue, and we can emphasize this in the ACs as well.

@FangedParakeet FangedParakeet removed the status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. label May 25, 2023
@timur27 timur27 self-assigned this May 26, 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. component: upe priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. size: large The issue is sized large. type: enhancement The issue is a request for an enhancement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants