-
Notifications
You must be signed in to change notification settings - Fork 210
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
Add split PE support for APMs (eg GiroPay) with deferred intent on the classic Checkout #2827
Add split PE support for APMs (eg GiroPay) with deferred intent on the classic Checkout #2827
Conversation
…_upe_available_payment_methods()
…pending on Stripe Account country
…s for all of our payment methods
…lass - This function was copied over from the main UPE gateway class. - This function calls other methods from the main UPE gateway class and so they've been copied over as well.
…in base UPE class
…e_' before each payment method name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good and it tests great!
Should we remove "Pay with" from the titles of our UPE payment methods so that they don't show on the checkout as "Pay with EPS", and just have EPS?
This is a really good question @mattallan.
I think it's best to keep changes to a minimum.. the screenshot at https://woo.com/products/stripe/ does not have the Pay with
so I think we should remove them in the classic checkout.
But I'm fine with merging this as it is, and discussing the naming in a P2 or slack, and then changing them 🤷🏼
Should we look at calling the main UPE class payment_fields() function inside our UPE payment methods, instead of creating/duplicate the existing function and putting it in the base WC_Stripe_UPE_Payment_Method class?
Do you mean using WC_Stripe_UPE_Payment_Gateway::payment_fields()
instead adding the function WC_Stripe_UPE_Payment_Method::payment_fields()
?
I think it makes more sense for that rendering code to be in the WC_Stripe_UPE_Payment_Method
class, right?
…/split-pe-classic-checkout
Thanks @diegocurbelo for the review! I've just pushed up a small change to remove the description from the payment fields as I didn't realise this information was not intended for customers to see on the frontend and is for merchants to get more information about the payment method from the list of methods in the settings 😅 I replaced the description with gateway testing instructions if they exist.
That sounds good to me 👍
Thanks! Yeah you were correct in your understanding. I agree that it makes sense to have the rendering code in the |
Fixes #2788
Changes proposed in this Pull Request:
This PR is based of #2820 and brings Split-PE with deferred intent support for our APMs (giropay, eps, iDeal) to the classic checkout
Screen.Capture.on.2024-01-12.at.14-42-03.mp4
The changes in this PR should be pretty straightforward, but here's a quick summary of what was needed to implement split PE on the classic checkout:
payment_fields()
to properly render each UPE payment method on the classic checkout page.classic/upe/
andstripe-utils/
to correctly navigate the multiple stripe elements now being mounted on the checkout page.Open questions:
payment_fields()
function inside our UPE payment methods, instead of creating/duplicate the existing function and putting it in the baseWC_Stripe_UPE_Payment_Method
class?Testing instructions
Core checkout functionality:
npm run build:webpack
Other tests:
changelog.txt
andreadme.txt
(or does not apply)Post merge