• Resolved spreid

    (@spreid)


    Like many others, I’m having the same problem where the payment in WooCommerce stays on “Payment initiated.” I have to manually check the payment with Mollie for each order. I contacted Mollie’s chat about this; they acknowledged the problem and suggested going back to 8.0.4 as a solution, which I did. But the problem persists.

    Because I read here that you need to go back to 8.0.3, I did so, but without any results.
    Because I can’t do a manual check then and the problem isn’t resolved, I went back to 8.0.6 to at least be able to check via WooCommerce.

    I also added the filter suggested in other threads.

    I’ve already spent euros on transaction fees for testing, and that’s not my money. Very inconvenient.

    I’ve transferred the logs and configuration files via chat. What else can I do?

    Could this be prioritized by the developers? And what can we do to help?

    The page I need help with: [log in to see the link]

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

    (@femiyb)

    Hello @spreid

    We are currently looking into this issue, and working on a resolution.

    Thanks for sending the logs and system report through to Mollie Support.

    Could you please test for this issue in Test/Sandbox mode? Please share the logs for this also, as we would like to compare logs between Sandbox and Live payment for this issue.

    Thank you for understanding.

    Regards,
    Femi.

    • This reply was modified 8 months, 1 week ago by Femi.
    Plugin Author Mollie

    (@mollieintegration)

    @spreid Do you have some examples of Orders/Payments where this was a problem and it was fixed by manually triggering the webhook?

    Thread Starter spreid

    (@spreid)

    Yes I do, with the mollie ID
    tr_NWWce8WgKU86UNXgR4xEJ
    tr_xuBkNcX72AS5daf9ufvEJ
    tr_sECF3XV9ppomJgsWLnvEJ
    And more, so if you need I can provide you more ID’s

    Plugin Author Mollie

    (@mollieintegration)

    @spreid would you be willing to jump into a call with us to dig deeper into this issue? Feel free to dial in or let me know any time that works for you.
    https://meet.google.com/jtu-whfd-obu?authuser=0

    @mollieintegration @spreid Sorry for hijacking this thread but since several people have this problem, we would also be happy to help and give you all details / access you need to our systems, same problem and same symptoms – just in case @spreid is not available in time.

    Thread Starter spreid

    (@spreid)

    Sorry @mollieintegration, I was working on another project. If you need anything else, please let me know.
    The problem is still there, and I don’t see any solutions from others either.

    @femiyb @mollieintegration everybody here is waiting for your help?!

    Plugin Support Femi

    (@femiyb)

    Hello everyone,

    Apologies for the inconvenience this issue has caused.

    Please rest assured that we are actively investigating and working to resolve it as quickly as possible. We’ve been reviewing the details you’ve shared, and your input has been very helpful, thank you for that.

    We’ll provide an update as soon as we have a resolution.

    Thank you again for your patience and understanding.

    • This reply was modified 8 months, 1 week ago by Femi.
    Plugin Support Femi

    (@femiyb)

    Hello

    We’ve noticed that several of the affected sites mentioned in another support thread are hosted on SiteGround. To help us confirm whether hosting might be a contributing factor, could you please let us know which hosting provider your site is running on?

    Thank you

    we are on siteground but the others seems not.

    Thread Starter spreid

    (@spreid)

    @femiyb, Yes I’m using Siteground for both websites. They have the same issue.

    When I read two days ago that someone else was also hosting through SiteGround, I disabled the Security Optimizer 1.5.7 and Speed ​​Optimizer 7.7.2 plugins.

    However, that didn’t solve the problem.

    And at the risk of giving away unnecessary information, the DISABLE_WP_CRON constant is set to true. WP-Cron spawning is disabled.

    Thread Starter spreid

    (@spreid)

    I also have a few orders that automatically changed their status an hour or so later. It only concerns three or four orders.
    What struck me about this is that the order status change was always around the clock.
    Like this order:
    Order completed using Mollie – iDEAL payment (ord_PWquYibXMmvM5yTnLFvEJ).

    September 30, 2025 at 5:00 PM Delete note

    Order status changed from Pending payment to Processing.

    September 30, 2025 at 5:00 PM Delete note

    iDEAL payment initiated (ord_PWquYibXMmvM5yTnLFvEJ).

    September 30, 2025 at 3:45 PM

    See, the order was placed at 3:45 AM, the status changed exactly at 5:00 AM.

    We finally identified the root cause of the problem where only some WooCommerce orders were getting their Mollie payment status updated automatically.

    It turned out not to be a bug in WooCommerce or Mollie directly, but rather an interaction with SiteGround’s security system.

    SiteGround’s logs showed that certain Mollie webhook IPs (in our case 34.76.201.228 and 34.76.90.110) were being challenged by their CAPTCHA / firewall service and ended up greylisted. This explains why only some webhook calls reached the shop while others silently failed.

    The reason for the block is important: SiteGround detected a large number of PHPMail executions triggered from those Mollie IPs across their infrastructure. From the host’s point of view, this is suspicious behavior and justifies the security response.

    SiteGround has now whitelisted these IPs for us, and the webhook updates are flowing again. But the underlying issue remains: if Mollie’s servers keep generating PHPMail-like requests, they risk being blocked again by hosting providers with strict security layers.

    For other users affected:

    • If you are on SiteGround and see the same symptoms, ask support to check their firewall/greylist logs for Mollie IPs.
    • Once confirmed, they can whitelist those IPs.

    For Mollie / the plugin developers:

    The webhook servers really should not be generating traffic that looks like PHPMail spam. This is causing unnecessary friction with hosting firewalls. Please investigate this behavior on the mentioned IPs and clarify whether this is intentional or a misconfiguration. Otherwise, SiteGround (and likely other hosts) may continue to block webhook requests.

    Hope this helps

    Plugin Support Femi

    (@femiyb)

    Hello everyone,

    Thanks for bearing with us while we dug into this. SiteGround has confirmed that their automated security system was mistakenly blocking Mollie’s webhook callbacks.

    What SiteGround has done

    • Allowed requests to our webhook endpoints:
    •  /wp-json/mollie/v1/webhook and /wc-api/mollie_return
    • Unblocked IPs that were affected in the last 24 hours
    • Clarified that callbacks were flagged due to email-like traffic patterns; these URIs are now excluded from their mitigation, so this shouldn’t recur

    What we need from you

    • Please test new payments and confirm whether order status updates now work as expected
    • If you still see issues, share: store URL, timestamp (UTC), Mollie payment ID/event ID, and hosting details so we can investigate with SiteGround
    • If you are using a different hosting provider and still experiencing this problem, kindly confirm your host so we can investigate.

    We’re continuing to work with SiteGround on the exact trigger and on any plugin-side adjustments to prevent similar false positives. If you have input or logs that could help, we’d love to hear it.
    Thank you for your patience, we’re on this until it’s fully resolved.

    Regards,
    Femi

    Thread Starter spreid

    (@spreid)

    Just now, payments were accepted directly on the live environment, and the order status was updated correctly. This also caused the emails to be sent again to both the seller and the buyer.
    That’s good news, and I’ll continue to monitor this in the coming days to see if there are any further issues.
    Thank you for your support.

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

The topic ‘No order update after Payment’ is closed to new replies.