Hi @ostinatofreak
I hope you’re well today!
I’ve imported the form to my test site and I was able to replicate this.
It’s quite a specific case and related to a combination of payment amount and visibility conditions. The form has some very complex/advances visibility rules set for fields and it seems that in case of some choices of membership type along with “Already paid/will pay by other means” option and “Optional $25 Recycyling or Other Additional Donation” field value of 0 – the stripe field is still visible on a page at the time of submitting the form but then the conditional logic correctly removes it. Since at the submission time the field was there the requests were made to Stripe but then Stripe’s response cannot be processed as the field is no longer there (and it shouldn’t).
I think changing field a bit should help here. Currently the Stripe field is set to be visible based on options/status of other fields (also being conditionally visible – and such “nested” logic isn’t always as reliable as it could be; it’s not that simple to handle too).
But if I correctly understand the form, then the “Total” field value being the source of amount to charge would be good enough condition.
So instead of setting those multiple visibility conditions for stripe field, I’d try setting just one: “Show if Any of the following rules match” and rule being “Total is greater than 0”.
This way the stripe field would show only if there really is anything to be paid – right now and online. In my tests (on my test setup) it seems to do the job and I couldn’t replicate the issue anymore with this type of settings.
Kind regards,
Adam
