INVALID_VALUE: Charge amount does not match error with version 2.0.5

  • Resolved nicethreads

    (@nicethreads)


    5 years ago

    Hi,

    I have been running into the ‘INVALID_VALUE: The charge amount does not match the order total’ problem as well. I was using the 2.0.5 version of the plugin successfully on 2 stores in a multisite environment, then when we set up the third store we started getting these errors on most transactions. (WordPress version is 5.2.4, woocommerce is 3.8.0, php is 7.2.24)

    The funny thing is that the customer would retry and it would go through. I am not sure if they used a different card or the same card. I didn’t have the debug log turned on at that point. I downgraded to 1.0.38 and it seemed to fix that part of the problem as others have suggested. It created others though, so I’d like to try and get back up to the current version.

    Is this something that was looked at in the 2.0.6 update? If so I will give it a shot, if not I will probably stay with 1.0.38 for the time-being.

    All of the stores had the same settings and were using the same location in square. We weren’t syncing any item/inventory information. Prices were entered exclusive of tax, we are using USD so the currency has 2 decimal places. The only thing I can think of that’s different from some of the users I’ve seen is that we are set to calculate tax on the order subtotal as opposed to by line item. Calculating tax by line item was throwing some transactions off by several cents, by calculating this way we are just off by 1 cent every so often. We aren’t offering any discounts on the items.

    Let me know your thoughts.

    Thanks,
    Tim

Viewing 7 replies - 1 through 7 (of 7 total)
  • AJ a11n

    (@amandasjackson)

    Hi @nicethreads

    Our developers are still looking to make sure all scenarios are covered by the fix. They had believed that 2.0.6 had the fix included, but there were still a few scenarios that were not covered.

    That being said, there is a potential workaround that may work for you here, otherwise updating to 2.0.6 may also work. If it doesn’t please do let us know and we can add your report of this error to the open issue as well.

    Thread Starter nicethreads

    (@nicethreads)

    Hi Amanda,

    Thanks for the quick reply!

    I had looked into that fix for the version 2.0.5 code and it looked to me like it had already been integrated into the release (I may be mistaken though!), so I think the problem might be cropping up elsewhere.

    I will give 2.0.6 a try early next week and let you know how I do.

    Thanks!
    Tim

    AJ a11n

    (@amandasjackson)

    Hi Tim,

    Please do let us know how it goes!

    AJ a11n

    (@amandasjackson)

    Hi @nicethreads

    Just wanted to check in to see if you were able to update and test with the most recent version?

    Thread Starter nicethreads

    (@nicethreads)

    Hi Amanda,

    So far 2.0.6 has been working well. We have received orders on one of the sites that wasn’t having the problem, and it still isn’t having the problem. We will be opening up orders on the problematic site this next week I think.

    I thought I saw somewhere that it is now possible to run test transactions through the sandbox environment, is this the case? I’d like to try testing this a bit more comprehensively before we have people placing orders on that problem store.

    Plugin Support Ryan Ray, a11n

    (@ryanr14)

    Hi @nicethreads,

    Thanks for keeping an eye out for the issue returning after 2.0.6. I’ve seen in other cases a quick disconnect and reconnect helps fix this, seemingly it could be caused by an access token gone bad and hadn’t auto renewed.

    Plugin Support con

    (@conschneider)

    Engineer

    Hi there,

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

    Kind regards,

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘INVALID_VALUE: Charge amount does not match error with version 2.0.5’ is closed to new replies.