snappermorgan

Most of my clients have many security and compliance issues with this model, and the lack of warning really put me off, and indeed has caused me hours of grief.

I still believe this was not thought out from a compliance or security standpoint, regardless of how many people requested the feature. Some of my clients are actually major regional banks who are none too happy with this upgrade.

And I really love your plugin, which is the biggest shame of all. I wish I could use it.

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.

Not to hijack this thread, but I too was getting this error. I was looking through the developer console to see what every response was, and I noticed that I was getting this error if I used an incorrect credit card number. Your plugin seems to submit whether the card number is correct or not, and since it failed the cc number validation, the “Card” string is empty when submitted to stripe and the weird error is what is shown. Of course, using a correct number gives success.