[8.0] Missing fields when calling create-payment

[joostdebruijn]

After upgrading to v8.0.0, the checkout doesn't work anymore. We don't ask our customers to provide a billing or shipping address and that seems to be an issue.

The debug logging is showing the following for an iDeal-payment, but it also happens with other payment methods:

2025-03-29T03:59:31+00:00 Foutopsporing ideal: Start process_payment for order 15029  
Aanvullende context
2025-03-29T03:59:31+00:00 Foutopsporing Creating payment object: type Payment, creating a Payment.
2025-03-29T03:59:31+00:00 Foutopsporing  Order 15029 returnUrl: https://[redacted]/afrekenen/order-received/15029/?key=wc_order_[redacted]&order_id=15029&filter_flag=onMollieReturn  
Aanvullende context
2025-03-29T03:59:31+00:00 Foutopsporing  Order 15029 webhookUrl: https://[redacted]/wc-api/mollie_wc_gateway_ideal?order_id=15029&key=wc_order_[redacted]&filter_flag  
Aanvullende context
2025-03-29T03:59:31+00:00 Foutopsporing {
    "amount": {
        "currency": "EUR",
        "value": "5.00"
    },
    "description": "Bestelling 15029",
    "redirectUrl": "https://[redacted]/afrekenen/order-received/15029/?key=wc_order_[redacted]&order_id=15029&filter_flag=onMollieReturn",
    "webhookUrl": "https://[redacted]/wc-api/mollie_wc_gateway_ideal?order_id=15029&key=wc_order_[redacted]&filter_flag",
    "method": "ideal",
    "issuer": "",
    "locale": "nl_NL",
    "dueDate": "",
    "metadata": {
        "order_id": 15029
    }
}
2025-03-29T03:59:31+00:00 Foutopsporing [2025-03-29T03:59:31+0000] Error executing API call (422: Unprocessable Entity): The following fields of the billing address are missing: streetAndNumber, postalCode, city. Documentation: https://docs.mollie.com/reference/v2/payments-api/create-payment. Request body: {"status":422,"title":"Unprocessable Entity","detail":"The following fields of the billing address are missing: streetAndNumber, postalCode, city","field":"billingAddress","_links":{"documentation":{"href":"https://docs.mollie.com/reference/v2/payments-api/create-payment","type":"text/html"}}}. Field: billingAddress
2025-03-29T03:59:31+00:00 Foutopsporing ideal: Failed to create Mollie payment object for order 15029: [2025-03-29T03:59:31+0000] Error executing API call (422: Unprocessable Entity): The following fields of the billing address are missing: streetAndNumber, postalCode, city. Documentation: https://docs.mollie.com/reference/v2/payments-api/create-payment. Request body: {"status":422,"title":"Unprocessable Entity","detail":"The following fields of the billing address are missing: streetAndNumber, postalCode, city","field":"billingAddress","_links":{"documentation":{"href":"https://docs.mollie.com/reference/v2/payments-api/create-payment","type":"text/html"}}}. Field: billingAddress

After downgrading to v7.10 there is no problem anymore.

It looks similar to #629, however the API-method used is the Payments API.

[djcprinse]

We’re facing the same issues. Both of our webshops only have iDEAL as available methods and using version 8.0.0 results in direct errors when trying to pay.

We do not ask our customers for a billing of shipping address since we’re handing out the orders ourselves.

We’re using the Payments API, since the orders API had the problems mentioned in the issue that joostdebruijn already mentioned.

[DomoticX]

Same issues here

[asotela3911]

We are currently looking into this and will provide and update soon

[InpsydeNiklas]

Hi folks, we're still investigating why Mollie expects some billing fields to be required in the new Payments API. We haven't been able to reproduce the issue yet, so any details you can share with the Mollie Support Team, like a system report and your Mollie log files, will help us swiftly resolve it.

Beyond temporarily downgrading to 7.10.0, you could try to remove the billing address object entirely from the iDEAL API call with this code snippet (e.g. by adding it to your theme's functions.php file or as a Code Snippet):

add_filter('woocommerce_mollie_wc_gateway_ideal_args',function ($data){
    unset($data['billingAddress']);
    return $data;
});

Please let us know if you have the chance to try this and if it resolves the error (at least for iDEAL payments, other gateways would need a different hook).

[DomoticX]

Well i unfortunatly do not have a "playground" for my live site, and i already missed a day in revenue and had to deal with not so amused customers due to these issues (that what happens when you live on the edge of new versions i believe), so.....i was spitting in the logs and i found these errors when using mollie 8.0.0 and these are not in 7.x.x (wich i am using now / reverted back to), hopefully it could help track down the problem:

2025-03-31T12:26:47+00:00 DEBUG [2025-03-31T12:26:47+0000] Error executing API call (422: Unprocessable Entity): Line item 5 is invalid. The 'imageUrl' field should be a valid URL. Documentation: https://docs.mollie.com/overview/handling-errors. Request body: {"status":422,"title":"Unprocessable Entity","detail":"Line item 5 is invalid. The 'imageUrl' field should be a valid URL","field":"lines.5.imageUrl","_links":{"documentation":{"href":"https://docs.mollie.com/overview/handling-errors","type":"text/html"}}}. Field: lines.5.imageUrl 2025-03-31T12:26:47+00:00 DEBUG ideal: Failed to create Mollie payment object for order 41003: [2025-03-31T12:26:47+0000] Error executing API call (422: Unprocessable Entity): Line item 5 is invalid. The 'imageUrl' field should be a valid URL. Documentation: https://docs.mollie.com/overview/handling-errors. Request body: {"status":422,"title":"Unprocessable Entity","detail":"Line item 5 is invalid. The 'imageUrl' field should be a valid URL","field":"lines.5.imageUrl","_links":{"documentation":{"href":"https://docs.mollie.com/overview/handling-errors","type":"text/html"}}}. Field: lines.5.imageUrl

Also it is wierd to me....what does mollie want with the images of products....i wonder....

[joostdebruijn]

Based on the provided code snippet, my guess is that the request contains empty fields in the billingAddress-object which is not allowed, so the billingAddress should be absent or null if the data is not available.

[mklasen]

I ran into this issue as well for a customer website. We are using the Flexible Checkout Fields plugin to disable address fields.

Here's a screenshot of our configuration:
https://github.com/user-attachments/assets/73571ae2-72d4-4b5b-9a8e-9be78c8cb55b

We are not using the shipping section but I noticed that the fields are not disabled for this section. This could be related. (screenshot)

Temporarily solved by downgrading to version 7.1.0 (direct download link)