• Resolved Twiks Media

    (@thijmens)


    After updating to version 8.0.0 of the Mollie plugin, we’re experiencing an issue during checkout caused by an API error. The payment request returns the following response:
    Error executing API call (422: Unprocessable Entity): The following fields of the billing address are missing: streetAndNumber, postalCode. Documentation: https://docs.mollie.com/reference/v2/payments-api/create-payment

    In this case, the fields streetAndNumber and postalCode of the billingAddress were not included in the request, which is expected behavior. According to the official Mollie API documentation, these fields are not required unless a specific payment method requires them (e.g., Klarna).

    This seems to be a bug introduced in version 8.0.0 of the plugin, where these address fields are incorrectly treated as required, even for standard payment methods. As a result, the checkout process fails.

    Could you please investigate whether this behavior is unintended and possibly fix it in an upcoming release?

    Thank you in advance for your help.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Support Femi

    (@femiyb)

    Hello @thijmens

    To better judge what could be causing this, we are interested in a copy of your WooCommerce system report and your latest Mollie plugin log files.

    The system report can be accessed from here:
    WooCommerce > Status > Get system report > Copy for support

    You can copy the log files from here:
    WooCommerce > Status > Logs > select “mollie-payments-for-woocommerce-[…]”.

    You can share it either via https://privatebin.syde.com/

    Regards,
    Femi.

    Hi there!

    I created an account just for this particular post :-). Sorry for hijacking @thijmens , but I hope this helps you too!

    I am experiencing the same issues with the latest version of the mollie plugin. Before, I was able to generate payment requests for my customers and this did not require an emailaddress or particular address information. Now all of a sudden, it gives me the following entries in the logs:

    2025-03-29T22:39:59+00:00 DEBUG Creating payment object: type Order, first try failed: [2025-03-29T22:39:59+0000] Error executing API call (422: Unprocessable Entity): The ’email’ field is missing. Documentation: https://docs.mollie.com/overview/handling-errors. Request body: {“status”:422,”title”:”Unprocessable Entity”,”detail”:”The ’email’ field is missing”,”field”:”billingAddress.email”,”_links”:{“documentation”:{“href”:”https://docs.mollie.com/overview/handling-errors”,”type”:”text/html”}}}. Field: billingAddress.email

    2025-03-29T22:39:59+00:00 DEBUG [2025-03-29T22:39:59+0000] Error executing API call (422: Unprocessable Entity): Line item 6 is invalid. The ‘unitPrice’ field cannot be negative, unless the ‘type’ is one of the following: ‘discount’, ‘store_credit’, and ‘gift_card’. Documentation: https://docs.mollie.com/overview/handling-errors. Request body: {“status”:422,”title”:”Unprocessable Entity”,”detail”:”Line item 6 is invalid. The ‘unitPrice’ field cannot be negative, unless the ‘type’ is one of the following: ‘discount’, ‘store_credit’, and ‘gift_card'”,”field”:”lines.6.unitPrice”,”_links”:{“documentation”:{“href”:”https://docs.mollie.com/overview/handling-errors”,”type”:”text/html”}}}. Field: lines.6.unitPrice

    The logs can be found here:

    https://privatebin.syde.com/?3f49a60819fe391e#DT2MWPSRzj2jyvHMJWishYbGRjVZJN5baczSQwLjkPxM –WC Log

    https://privatebin.syde.com/?418b6829f8143106#2hMGM56SbyYPj43WU2zX2oPKFhjk9ancJS3QaQUrDuKM — Mollie log 30-03-2025

    https://privatebin.syde.com/?e204df6f36695c46#D6QjrQbD7o8a4wGZxkQTeiThotxvLKRKU3yCQdyQzwKs — Mollie log 29-03-2025

    They are password protected; how can I send you the password. Through private message?

    Thanks in advance for the support!

    Plugin Support Femi

    (@femiyb)

    Thanks for sharing the logs @peeetr

    I will forward these to the developers, and let you know as soon as there is an update.

    Sure @femiyb , not a problem! Just let me know if you need any more information from my side.

    Peter

    Same issue here. Payments are suddenly not accepted. With error: “The following fields of the billing address are missing: streetAndNumber, postalCode, city.”

    Reverting to previous version.

    Plugin Support Femi

    (@femiyb)

    Hello @tezalsec

    Thank you. I will let you know as soon as there is an update on this issue.

    Job van Harn

    (@jvhwebbouw)

    Yep, same issue here with two of our clients. It seems to occur when a checkout is missing some of the default address fields.

    For example, we have a customer who accepts simple payment donations, only asking for an email address and name. This worked fine before, but after the latest update, it’s no longer working. The error log shows that it’s due to the required address fields mentioned above.

    The same issue applies to another customer selling digital products, where no address is needed. The address fields were removed from the checkout, but after the update, the same error appears in the logs, asking for required billing address fields.

    ldwd

    (@ldwd)

    I know we are not supposed to reply with I have the same problem but need to create a new topic according to the forum guide lines… Though I do experience the same problem: payments are not accepted without billing address. Reverting to 7.10.0 resolved the issue.

    Plugin Support Femi

    (@femiyb)

    Hello all.

    Our developers have provided a beta release that fixes these issues. You can download the beta fix here.

    We would appreciate some feedback on this beta fix.

    Thank you.

    Regards,
    Femi

    Hi Femi,

    Great, thanks.
    I’ve updated the plugin with the provided beta-release from Github and it’s all working as before.

    So it seems to lift the checkout adress-fields restriction indeed and that the issues regarding this topic are fixed in this version.

    @femiyb Sorry for the late reply and thank you for the beta version. I tested and the iDEAL page is loading now, no error message. Looking forward to the official update!

    Plugin Support Femi

    (@femiyb)

    Hi everyone,

    Thanks again for your reports and patience regarding this issue.
    We’re happy to confirm that this has been addressed in version 8.0.1.

    If you’re still experiencing the issue:

    • Please make sure you’ve updated to version 8.0.1.
    • Clear any relevant caches after the update.
    • If the issue persists, please reach out so we can assist further.

    Thanks for your cooperation and for helping us track this down!

    Regards,
    Femi

Viewing 12 replies - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.