Payment Information fieldset label is misleading if mix of gateways supporting and not supporting stored payment methods is available

Created on 26 August 2024, 4 months ago

Updated 28 August 2024, 4 months ago

Describe your bug or feature request.

While all onsite payment gateway plugins implement SupportsCreatingPaymentMethodsInterface, and by extension SupportsStoredPaymentMethodsInterface, the situation may be different for offsite payment gateways.

If the mix of gateways implementing SupportsStoredPaymentMethodsInterface and not implementing it is available as payment options in the checkout the label can be misleading:

Depending on the selected option the payment method may or may not be created.

If a bug, provide steps to reproduce it from a clean install.

Install Payment and Payment Example modules
Create 3 payment gateways using: Example (Off-site redirect), Example (Off-site redirect with stored payment methods), Example (On-site)
Choose On-Site gateway and go to Review step
Go back to Order Information step and observe the label is now Add a new payment method but choosing Example (Off-site redirect) won't create a payment method.

🐛 Bug report

Status

Closed: outdated

Version

3.0

Component

Payment

Created by

🇳🇴Norway zaporylie

Live updates comments and jobs are added and updated live.

Release blocker

Comments & Activities

Issue created by @zaporylie
Comment 4 months ago →
🇮🇱Israel jsacksick
I've been thinking about this today and I think I'll probably just revert the change until we figure out a way to opt in for this new UX.
Additional tweaks are needed to figure out what to do for the different use cases / edge cases....
Comment 4 months ago →
🇮🇱Israel jsacksick
Status changed to Closed: outdated 4 months ago11:51am 28 August 2024
Comment 4 months ago →
🇮🇱Israel jsacksick
Closing this as I reverted the change introduced in ✨ Separate stored payment methods from new in the Payment Checkout Pane Needs work .

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024