• Still the same error; after more than a year. Still no solution.
    Tried both API’s, tried new keys everything, seems like I’m stuck to version 7.10
    Mollie with WooCommerce.

    Orders without decimal quantity working very well.

    Failed to create Mollie payment object for order ### Error executing API call (422: Unprocessable Entity): Line item 1 is invalid. The ‘quantity’ field should be a whole number. Documentation: https://docs.mollie.com/reference/handling-errors. Request body: {“status”:422,”title”:”Unprocessable Entity”,”detail”:”Line item 1 is invalid. The ‘quantity’ field should be a whole number”,”field”:”lines.1.quantity”,”_links”:{“documentation”:{“href”:”https://docs.mollie.com/reference/handling-errors”,”type”:”text/html”}}}. Field: lines.1.quantity

    • This topic was modified 3 weeks, 4 days ago by vanmeij.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Krystian Syde

    (@inpsydekrystian)

    Hello @vanmeij

    Indeed, there is a gap in handling fractional quantities here. However, this is also a limitation from Mollie’s side: their API does not support fractional quantities at all. The challenge is that simply rounding the quantity to a whole number may introduce another issue.

    I will raise this with the developers.

    Kind Regards
    Krystian

    Thread Starter vanmeij

    (@vanmeij)

    Thank you, because it is working in version 7.10 so is it a bug?
    Or is it a change on Mollie’s way to handle orders. It seems not that difficult to get this thing right.

    Also a musthave for some webshops right? Handle weights, liters or gallons, handle square meters etc.

    Plugin Support Krystian Syde

    (@inpsydekrystian)

    Hello @vanmeij

    Mollie’s API requires line item quantities to be whole numbers. Because of that, WooCommerce stores using plugins that allow decimal quantities (for example selling 1.5 kg, liters, square meters, etc.) currently receive a 422 error from Mollie and the payment fails entirely.

    The good news is that a fix has already been added to the sprint.

    Kind Regards
    Krystian

    Thread Starter vanmeij

    (@vanmeij)

    @inpsydekrystian Thank you!

    Any idea when can we expect the fix?

    Plugin Support Krystian Syde

    (@inpsydekrystian)

    Hello @vanmeij

    The fix is currently planned for version 8.1.8 (the release after next). We are still discussing the best approach for the implementation to make sure the solution is handled properly.

    Kind regards,
    Krystian

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.