Payment failing (Bad_request: intent_mismatch)

  • Resolved Esch

    (@esch)


    4 years, 9 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, 9 months ago by Esch.
Viewing 10 replies - 31 through 40 (of 40 total)

  • @drwpcom Thank your for your suggestion! I am speaking with the plugin tech support now to work through some issues. I appreciate your reply. ??

    Hi @drwpcom. I have not seen it mentioned as a suggestion in this or any other threads discussing the INTENT_MISMATCH error but for us, the problem was a conflict between Woocommerce settings and the plugin’s settings in combination with some incomplete conditional logic in the front-end javascript.

    On our site, we have all “Account Creation” options disabled in WooCommerce/Settings/Accounts_&_Privacy so essentially all checkouts are guest checkouts.

    However, we also had the “Allow customers to securely save their payment details” option turned on in WooCommerce/Settings/Payments/Square.

    One might assume that the Square plugin checks that account creation is possible before displaying the Save to Account option or before attempting to store payment info, but it doesn’t.

    The result is that the “Securely Save to Account” checkbox was visible to customers at checkout and inevitably some customers chose to Save. When the plugin attempts to save but can’t because there’s no account to save it to, it throws the INTENT_MISMATCH error.

    It’s been a few days now since we turned off the “Securely Save” option and so far all orders have processed normally. This may not be the source of the problem for everyone but it may help some.

    Plugin Support Damianne P (a11n)

    (@drwpcom)

    Hi @candyhammer! Thank you for taking the time to share your experience here! I’ve passed on this information to our developers.

    @esch @chandlerjfc please let us know if you still need help with this issue.

    Hi! I am having the dame issue for one of my customers today. Have there been any solution to it yet?(@drwpcom)

    Plugin Support Damianne P (a11n)

    (@drwpcom)

    Hi @lindsey13 Were you able to check the workaround solutions provided here and here?

    We do expect a fix in Square version 2.1.2 which will be released soon.

    Hi @drwpcom ! I did follow the instructions but for some reason the problem still exists. What is the expected date of the new update?

    Hi there @lindsey13, @esch, @candyhammer, @adelleable,

    Square 2.1.2 has been released on 29 April. As you can see from the changelog, INTENT_MISMATCH bug was resolved there: https://www.ads-software.com/plugins/woocommerce-square/#developers

    I’ll mark this thread as Resolved, but please don’t hesitate to open a new one if you’re still seeing errors.

    Enjoy the rest of your day and stay safe!

    @treibalen

    I have version 2.1.5 downloaded now, but I’m still experiencing the “Square Payment Failed (Status code BAD_REQUEST: INTENT_MISMATCH)” error for some of our online orders. Any ideas?

    Im having the same issue on some orders 5-6 in the last 2 days im running version
    Version 2.1.5, this is very frustrating that it’s still happening.

    It seemed like it got better after the last update but now it’s back?

    Please help

    Hi there @jvarain and @agould45,

    I’m sorry to hear that you’re still seeing INTENT_MISMATCH errors on your site.

    Please contact us at WooCommerce.com > My Account > Tickets. You may need to create an account before you can access that page.

    Please include a link to this forum thread, so that we can keep track of what’s already been done.

    Cheers!

Viewing 10 replies - 31 through 40 (of 40 total)
  • The topic ‘Payment failing (Bad_request: intent_mismatch)’ is closed to new replies.