Thanks! It works great now, but does not give an error message or indication that the cc number is invalid, it just brings the user back to the same page with a cleared out Stripe form. I suggest some kind of error message for UX consistency.
There is one more issue that I don't know will be a problem. In my scenario I have Woocommerce set to require the customer to register to make a purchase. Therefore it asks for registration information and a password. If an invalid cc is posted, the account is registered but the user is brought back to the same payment screen, but now without a password. The user account has been created due to the posting. I don't know what kind of issues this might create. Personally, so far, I like this behavior, having the account created regardless, as it means I don't have to re-enter the password every time. Just wanted to bring up that scenario. It may not even be an issue.
Thanks though for the quick fix! You rock.