Payment failing (Bad_request: intent_mismatch)

Resolved Esch
(@esch)

4 years, 2 months ago
I use your plugin on my WordPress site and it’s been working great for long time. However, the past two weeks I’ve been getting this intermittent problem where clients try to pay and their payments fail with a “Bad_request: intent_mismatch” error message.

I tried to do a search for this online but have come across only one instance of someone else having this issue but no solution. (That was on Square’s forum)

I’m putting this here hoping it has something to do with your plugin since it’s connected to Square. I’ve disconnected and reconnected the plugin, but don’t think that helps. To make matters more annoying, some clients have this problem, others do not, so it’s hard to nail down what is going on.

WooCommerce had a major update to 3.9.2 about two weeks ago, so my guess is there’s something in it that is now conflicting with your plugin.

Any help is appreciated, thanks!
E
- This topic was modified 4 years, 2 months ago by Esch.

Viewing 15 replies - 16 through 30 (of 40 total)

← 1 2 3 →

tagani
(@tagani)

4 years, 1 month ago

Thank you @esch. I will wait for the next customer. And see what happens.

tagani
(@tagani)

4 years, 1 month ago

I confirmed “2.0.8” was worked well, despite it was just a few cases.

wallacelin
(@wallacelin)

4 years ago

Hello all, the same issue has occurred on my site (BAD REQUEST: INTENT_MISMATCH) and I was running 2.1.1 before I downgraded to 2.0.8. Seems like the issue only occurred to one customer but I cannot confirm much else.

I am also running WooCommerce 3.9.2 and WordPress 5.3.2. Perhaps need to update these?

Looking forward to a resolution, thank you!

mfonville44
(@mfonville44)

4 years ago

Same issue here – Square Payment Failed (Status code BAD_REQUEST: INTENT_MISMATCH).

The error only happens to small percentage of users. I’m using the following versions: WP 5.4, WooCommerce 4.0.1, WooCommerce Square 2.1.1.

I’ve rolled back to an earlier version of the Square plugin version 2.0.8 and will see if this prevents the issue from happening again.

czeller
(@czeller)

4 years ago

Same problem for me with many client websites, only happens occasionally and randomly, but a very big problem.

Plugin Support Elvira K. a11n
(@treibalen)

4 years ago

Hi there @esch, @reai, @tagani, @uxuidesign and @brattdev,

I’ve reported the error you’re seeing (BAD_REQUEST: INTENT_MISMATCH) to our developers and they will investigate it further.

Meanwhile, adding the following code to your site should stop it from happening:

add_filter( 'wc_square_is_3d_secure_enabled', '__return_false', 0, 1 );

Please add it to your child theme’s functions.php file. Alternatively, you can use the Code Snippets plugin to do that: https://wordpress.org/plugins/code-snippets/

Please create a full backup of your site before adding any custom code to your site.

Hope it helps!

Thread Starter Esch
(@esch)

4 years ago

@treibalen , thanks for the code tip. Can you tell me what it does exactly so I can wrap my head around it? Also, I assume once they find and fix the bug this code will be redundant? If so, will it mess anything up if it’s still in the functions file after updating the plugin that has it working again?
adelleable
(@adelleable)

4 years ago
This problem is happening on an e-commerce site I launched a few days ago. Most of the transactions process smoothly, but some are failing due to “BAD_REQUEST: INTENT_MISMATCH”. Out of 40 orders, 18 failed. This is really bad. The owner of the e-commerce site will want peace of mind that I can fix this, and that it won’t happen again in the future. What solutions do we have? This is a brand new WordPress site but the domain is well-established and was previously using Square for the webshop. What solutions do we have?? Thank you!!!

Site is operating:
WordPress 5.4
Woocommerce 4.0.1
Woocommerce Square plugin 2.1.1
Flatsome Theme 3.11.0
Hosting: GetFlyWheel.com

EDIT: I just saw the code provided 5 hours ago, I will implement that. Thanks!!! Hoping this patch works! 🙂
- This reply was modified 4 years ago by adelleable.
adelleable
(@adelleable)

4 years ago
Thanks for the fix code!
- This reply was modified 4 years ago by adelleable.
adelleable
(@adelleable)

4 years ago

@treibalen I installed the code fix 3 days ago on the site that is having failures and we are still seeing some orders fail, although less, which is good but not ideal. Can you help further? Thank you!!

adelleable
(@adelleable)

4 years ago

@treibalen or @nixiack8 – Does your team have any further updates to fix this? THANKS!

chandlerjfc
(@chandlerjfc)

4 years ago

Same, receiving “Bad_request: intent_mismatch” for two sales now.

WooCommerce:Version 3.8.1
Woo with Square 2.1.1

Plugin Support Ena P (a11n)
(@drwpcom)

4 years ago

Hi @brattdev, @esch, @tagani, @reai, @rezzsiddiqui, @uxuidesign. Our developers are working on a solution to this issue and we expect a fix in version 2.1.2. Please look out for the update.

In the meantime (until the plugin update), you can use a plugin like Code Snippets or edit the functions.php file of your theme to add the following filter to disable 3DS:

add_filter( 'wc_square_is_3d_secure_enabled', '__return_false', 0, 1 );

adelleable
(@adelleable)

4 years ago

Hi @drwpcom , been trying that solution and now the web shop is getting nearly every order coming in as a double, triple or quadruple order – one customer checked out 15 times for the same product trying to use our webshop so we had to issue 14 refunds to that one customer, who spent around $450 instead of $35. I’m wondering if the add_filter code is preventing failures but causing massive problems with multiple orders? It seems the customer doesn’t think the first order went through. Or if I”m personally just having this issue, I’m not sure..?! Anyone else? Perhaps it’s my hosting? Still trying to figure this out…

Plugin Support Ena P (a11n)
(@drwpcom)

4 years ago

Hi @adelleable. Wow, having to process 14 refunds is a lot for both you and the customer! I’m sorry to hear that the snippet my colleague and I provided as a solution did not work for you. In that case, please open a support ticket at https://woocommerce.com/my-account/tickets/. Be sure to include your system report. You can find it by going to WooCommerce > Status > Get system report and then click Copy for support to be able to paste it in your message.