Hi @qwik3r
I’m seeing a lot more errors and failed orders with this plugin then I ever did with the official Stripe plugin by Woocommerce.
Then perhaps you should switch back to that plugin if it was working better for you. We offer this plugin for free and there’s no hard feelings if you find a plugin that better suits your business process and needs. We want what’s best for each merchant.
For example, no idea what this even means but seeing it a lot:
It’s hard to troubleshoot without some basic information like:
1. What credit card form are you using?
2. Was this a credit card payment or another payment method?
3. Are you using the latest version of the plugin?
4. Do you have a cache plugin that’s caching your checkout page?
5. What version of WooCommerce are you using?
Kind Regards,
Thread Starter
qwik3r
(@qwik3r)
That’s not an appropriate response and frankly very rude to tell me to “go back to another plugin”. Obviously you took the comment personally before thinking and were a bit too quick on the trigger…
What you perceived as a slight was merely me stating that I didn’t have issues with the official Stripe plugin so perhaps something is DIFFERENT with this one that you could enlighten me on instead of throwing in my face that it’s “free” and to more or less “take it or leave it”.
I have other orders going through so it has nothing to do with that. This is an error from Stripe and considering that you deal with Stripe I would suspect you would be able to decipher the error immediately and know what it means.
Hopefully your next response will be sans snark and more professional.
Please reference questions from the previous reply:
`1. What credit card form are you using?
2. Was this a credit card payment or another payment method?
3. Are you using the latest version of the plugin?
4. Do you have a cache plugin that’s caching your checkout page?
5. What version of WooCommerce are you using?`
Thanks,
Thread Starter
qwik3r
(@qwik3r)
Hello,
1. I’m using the Stripe form that is part of your plugin
2. It doesn’t say what card was used. In Stripe under the logs for POST /v1/payment_intents I do see the 400 error, but for payment method it’s some obfuscated number.
3. Yes, v3.3.31
4. I use Breeze by Cloudways and it shouldn’t cache any Woo pages. As mentioned previously, it’s not every order that is resulting in this error
5. v7.01
I reached out to Stripe also to try to get some clarification and this is what they said:
According to the request you provided, the error simply means you’re attempting to charge a customer card that has not been saved.
Since you are using some third party plugins to create your charges, you’ll want to reach out to WooCommerce for them to be sure they’re also collecting and passing customer information to Stripe correctly.
This mirrors something said in another thread as well about ‘saved cards’. So it seems like perhaps this error could pertain to previous customers and their saved cards. Maybe they expired? I’m not sure.
Hi,
1. There are 3 form types offered by this plugin, Stripe payment form, Stripe inline form and Custom form. Which of those 3 do you currently have enabled?
2. I mean which payment gateway. Was it the Credit Card gateway, Apple Pay gateway etc?
Do you know if the customer used a saved payment method or a new payment method? If it was a saved credit card, use the payment method ID and customer ID in stripe.com to find that particular payment method. Has it been detached?
If this was not the result of a detached or expired payment method then we’ve only seen 2 other reasons for that error:
1. Your checkout page is being cached, so the payment method ID is being re-used and a payment method ID can only be used once for security reasons.
2. A rapid double submit of your place order button took place. That should not be possible in more recent versions of the plugin however.
Thanks,
@qwik3r
3. You can login to your stripe.com account and search for that particular customer using their Stripe customer ID. There will be log entries of activity on their account. If the payment method was detached somehow, there should be an entry for that event.
