Hi there!
We recently released the latest version, 9.1.1, which fixes many issues that appeared in version 9.1.0. Could you please update your plugin to the latest version, 9.1.1, and see if that fixes your issue?
I have a similar issue.
Seems to be a problem with Sellkit and new Woo Checkout experience.
If you enable legacy checkout WooCommerce > Settings > Payments > Stripe > Settings > Advanced settings > Enable the legacy checkout experience, it will allow the payment to proceed.
More specifically, Sellkit is using an element ID like “#sellkit-billing_state”. But the payment gateway wants ID: “#billing_state”. Like it gets with “billing_country” or “billing_address_1”. Not sure why Sellkit adorns the ID, but they also have name attribute on the select element like “billing_state”.
Any chance the gateway can be adjusted to try the name attribute if the ID search fails?
Hi @tonnyquanticconseil,
This is a follow-up message. I’m unable to replicate the issue on my site, so it seems like the problem might be related to a plugin conflict on your site.
For testing purposes, could you please run a conflict test to see if that resolves the issue?
Here are instructions to guide you on how to run a conflict test: How to Test for Conflicts
Hi @fractaleater
It sounds like the issue arises from the custom ID used by Sellkit (#sellkit-billing_state) instead of the standard ID expected by the payment gateway (#billing_state). While the gateway primarily relies on the default WooCommerce element IDs, I can see how falling back to the name attribute could provide added flexibility in cases like this.
Unfortunately, the gateway is designed to work with the standard WooCommerce structure, and customizing it to accommodate third-party modifications like Sellkit’s altered IDs isn’t currently supported.
I would suggest submit a pull request on the Stripe Gateway GitHub repository with your proposed change. This will allow the development team and the broader community to review and discuss the implementation.
You can find the GitHub repository here: WooCommerce Stripe GitHub Repository.
When submitting the pull request, please provide a clear explanation of the issue, your proposed solution, and how it improves compatibility while maintaining functionality with standard WooCommerce setups.
In the meantime, you might want to reach out to the Sellkit team to see if there’s an option to align their element IDs with WooCommerce’s default structure or provide a workaround for compatibility.
Let me know if you have any further questions or need assistance with anything else!
I’m having the same problem. The issue is that for some countries, woocommerce hides the State field (#billing_state) and it turns out to be always empty. (Portugal and Italy, for example).
When that happens, it doesn’t pass initial validation for some payment methods. I’m having this issue with Klarna, but not credit card payment.
Can someone provide insights on how to solve?
Hi @talesf
I understand that you have a somewhat similar problem.
However, per forum best practices shown here, it is advised that you create a new thread so that we can address your issue(s) separately.
You can create a new thread here: https://ww.wp.xz.cn/support/plugin/woocommerce/#new-topic-0 and make sure to include as much information as you can.
Thanks for understanding!
I am also facing the same problem but this time with the city name. Please advise on any possible solutions.
You specified “never” for fields.billing_details.address.city when creating the payment Element, but did not pass params.billing_details.address.city when calling stripe.createPaymentMethod(). If you opt out of collecting data via the payment Element using the fields option, the data must be passed in when calling stripe.createPaymentMethod().
Hi @satyaiyer2007,
I understand that you have a somewhat similar problem.
However, as per forum best practices, it is advised that you create a new thread so that we can address your issue(s) separately.
You can create a new thread here: https://ww.wp.xz.cn/support/plugin/woocommerce-gateway-stripe/#new-topic-0 and make sure to include as much information as you can.
Thanks for understanding!
