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

PaymentMethod and Issuer not set when already sending data #64

Closed
svondervoort opened this issue Oct 28, 2024 · 4 comments
Closed

PaymentMethod and Issuer not set when already sending data #64

svondervoort opened this issue Oct 28, 2024 · 4 comments

Comments

@svondervoort
Copy link

Description

Using the following code
{{ cart.gateway.getPaymentFormHtml({})|raw }}
It returns 2 select elements with options. One for the PaymentMethod and one for the Issuer.
How ever when selecting any of the options, the first page of Mollie when submitting to 'commerce/payments/pay' will still ask you to select a PaymentMethod and Issuer.

Is this something on the Mollie side, is the selected data not send to Mollie or are we sending the wrong data?

Steps to reproduce

  1. Add the Mollie gateway
  2. add {{ cart.gateway.getPaymentFormHtml({})|raw }} to the checkout and submit

Additional info

  • Craft version: Craft Pro 4.12.8
  • PHP version: 8.3.11
  • Database driver & version: MariaDB 10.10.7
  • Plugins & versions: Craft Commerce 4.7.0
Copy link

linear bot commented Oct 28, 2024

@nfourtythree nfourtythree self-assigned this Feb 7, 2025
@nfourtythree
Copy link
Contributor

Hi @svondervoort

Thank you for your message. I have just tried to replicate this and unfortunately I was not able to.

Below is a video showcasing the selection of different payment methods and the Mollie test suite showing the different forms/information based on that choice.

CleanShot.2025-02-07.at.09.37.54.mp4

This test was done with the latest version of the plugin and using Commerce's example templates.

It maybe worth taking a look at the payment example template and comparing it to your implementation to see if there are any differences.

Thanks!

@svondervoort
Copy link
Author

Thanks for looking into this.
I guess we will have to check the logic again, here is a screen capture of one of our implementations.

Screen.Recording.2025-02-07.at.11.17.19.mov

For now this is low priority, so I will close the issue and re-open if needed.

@nfourtythree
Copy link
Contributor

Hi @svondervoort

Thank you for your response.

I can see this is certainly an issue from your screen recording.

As you mentioned, when you have had a chance to investigate further please let us know your findings.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants