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

New deferred intent UPE compatibility with WooPay #6291

Closed
FangedParakeet opened this issue May 12, 2023 · 2 comments · Fixed by #6656 or #6965
Closed

New deferred intent UPE compatibility with WooPay #6291

FangedParakeet opened this issue May 12, 2023 · 2 comments · Fixed by #6656 or #6965
Assignees
Labels
category: projects For any issues which are part of any project, including bugs, enhancements, etc. component: upe component: WooPay WooPay related issues

Comments

@FangedParakeet
Copy link
Contributor

Description

Currently, the split-UPE achieves compatibility with WooPay by falling back to the legacy card element for the CC gateway when WooPay is enabled. With the deferred intent UPE, this is no longer a necessity, since we will create the payment method prior to confirming the intent, allowing us to perform the regular WooPay cloning procedures in time.

This issue is to add WooPay compatibility to the deferred intent UPE card payment method. At this point, when the deferred intent UPE is enabled, we will no longer need to include any legacy Stripe scripts and we can present a UPE payment method in all available payment gateways. Consequently, we will need to amend the code where gateways and scripts are registered to reflect this.

As discussed in our roundtable, we would also like this issue to cover all available WooPay flows, so this should support an implementation in both the shortcode and blocks checkouts.

Acceptance criteria

  • When WooPay is enabled, UPE card payment method remains.
  • WooPay registration and checkout are both functional.
  • WooPay is implemented on both blocks and shortcode checkouts.

Dev notes

We should to reuse as much as possible from the existing legacy card gateway implementation, but from this vantage point I cannot yet see how much will be reusable.

Additional context

Blocked by #5020

@FangedParakeet FangedParakeet added status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. component: upe category: projects For any issues which are part of any project, including bugs, enhancements, etc. component: WooPay WooPay related issues labels May 12, 2023
@FangedParakeet
Copy link
Contributor Author

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

@FangedParakeet
Copy link
Contributor Author

Blocked by #6393.

@timur27 timur27 self-assigned this Jun 21, 2023
@FangedParakeet FangedParakeet removed the status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. label Jun 23, 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 component: WooPay WooPay related issues
Projects
None yet
2 participants