I am having this same error!!
Hi @rwky
Thank you for contacting Payment Plugins. Please share a site url where this can be replicated. The plugin doesn’t trigger any ajax requests on page load so I would like to observer what you’re describing.
Kind Regards
Hello @mrclayton ,
I cannot do this here, can you offer a secure channel? I can spin up a staging pretty easily.
Here’s my gravatar card: https://gravatar.com/eduarddoloc
Thank you,
Hi @rwky
You can reach the team privately via our support widget in the Stripe plugin settings of your WordPress site. Please reference this support thread.
Kind Regards
Providing an update to this thread which explains the issue, which is not a Stripe plugin bug.
Root cause: this is a bug in the Curiero plugin, exposed by the version 4.0.0 update, which changed some HTML attribute names.
What’s happening:
Curiero attaches a change event listener to any HTML element whose name attribute contains the string payment_method (their selector is [name*=payment_method]). When that event fires, it triggers WooCommerce’s update_checkout event, which sends an AJAX request. That AJAX request re-renders the checkout fields, which triggers the change event again on the element with name containing “payment_method” — and the loop repeats indefinitely.
Our Stripe plugin has a field named stripe_cc_payment_method_id, which matches Curiero’s overly broad selector. Since this naming convention is completely standard for payment gateway plugins, any plugin with a similarly named field would trigger this same loop — it’s not specific to Stripe.
The Curiero developers have been made aware of the issue.
