Hi @ataypamart
At this time, the credit card form integration validates required fields before the form is submitted to to Stripe and the server. That is done for several reasons:
- There was overwhelming feedback from merchants that this was desired.
- The Stripe payment method is generated client side and then submitted to the WordPress site. Certain field required for credit cards cannot be blank, so a client side validation is needed to the best integration with Stripe.
There isn’t currently an option to remove those client side validations because they have relevance to how the integration works with Stripe. My recommendation would be to not let notice location preference interfere with your selection of a secure solution.
This plugin uses the $.scroll_to_notices function which WooCommerce defines. You can try changing the Notices Location on the Credit Card Settings page of the Stripe plugin to see if that has any affect.
You can use our contact us page if you would like us to review the Kadence theme.
Kind Regards,
I understand 1., but not 2. yet.
If you have the patience, let me try to interpret what you say, and tell me if I understand you correctly.
It appears there are situations when you cannot usefully commnicate with the stripe API (which i presume to be client side integration) because some other fields (for instance, say, country) are not present or invalid. If I insist mindlessly on going through the usual mechancis, it means that
1/ either the plugin integration logic (which is necessarily client side to chat with stripe) would need to skip communication with stripe when country is not present (so far, so good), and probably report this as an error (for the sake of the argument, “cannot communicate with stripe yet”) or
2/ worse communicate with stripe and risk in some corner cases to book a payment with stripe while the order is in fact still invalid from a woocommerce perspective.
Of course this is grossly over-simplified and I am aware that the management of the communication state between woocommerce, stripe and the user is a bit of a balancing act…
Ultimately requiring the credit card errors to behave like the rest of the checkout form is either too brittle or the cause of possibly poor UX and thus 1.
Is that what you mean?
Kind regards (and thank you for your patience if you managed to read through this naive prose)
PS: I do not want to sound defensive, but to me the story is a bit deeper than a “preference on the location of the errors”. As it stands the UX is terrible and difficult to anticipate.
Hi @ataypamart
Ultimately requiring the credit card errors to behave like the rest of the checkout form is either too brittle or the cause of possibly poor UX and thus 1.
Is that what you mean?
Yes, that is what I mean. You can’t alway rely on the WooCommerce validations that occur server side because they occur after when a Stripe payment method ID needs to be generated.
As it stands the UX is terrible and difficult to anticipate.
That’s not typically a complaint that we receive. I recommend you play with the notice location setting to see if that affects the UX of the card notices.
Kind Regards,
