Error on Transaction

Hi there, I was getting that error a lot when developing the plugin and I thought I ironed it out, but I guess not. It happens when the javascript doesn’t create a token so there should be errors in your console when that happens (I hope). If you can send me a screenshot of the console errors I could help you fix it. Or even better would be a link to the site you’re testing on to see what exactly is breaking so I can release a quick patch for you.

Here’s some documentation on how to open up the chrome console: https://developer.chrome.com/devtools/docs/console

I was able to replicate the issue and found the culprit. 1.11 should work.

I will give it a try. Been buried in work / Will let you know how I make out.

works 100% flawlessly!

Glad to hear it. Don’t hesitate to let me know if you have any more issues.

Thanks,
Stephen

Yes it worked great > If can make a small suggestion. The check marks are ideal. No idea if a method of identifying the type of card could be performed. I noticed with some other plugins, they will recognize the card as a MC or VISA and they load an image of either or. Plus any of the other cards accepted by Strip. Just a suggestion. But yes it works. No idea if you will grow this plugin (I assume you would)

That’s already a part of the plugin, it adds a class to the credit card number input which then loads an svg of the big 4 logos. What browser/version/oerating system are you using? And do you have a link to the site you’re working on so I can see if something else is conflicting with it? If you don’t want it public, you can send it to [email protected]

If your site isn’t live then I don’t exactly know what I can do to help you solve this issue.

will email you direct

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.

Hi guys, I think I may have fixed this but before I push this to WordPress I want to make sure it works for you. Download the plugin directly from GitHub and install it manually to see if it works as expected. I think it should.

https://github.com/stezu/stripe-for-woocommerce
https://codex.www.ads-software.com/Managing_Plugins#Manual_Plugin_Installation

Let me know what happens.

Thank you,
Stephen

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.

It should behave like the standard error on submission, so if you have an invalid field or a missing one, the errors should pop up in the woocommerce error box and scroll you to the top of the screen.

It should look similar to this: https://imgur.com/bdSJqeE

That’s with every other form field correct, if I submit an empty form, I get this: https://imgur.com/IxAvZby

I haven’t tried the plugin with an account creation, but I will do that soon and get back to you.

Thanks.

The bug with account creation should be fixed now with 1.23