Plugin Support
Femi
(@femiyb)
Hello @tedocweb
I could not reproduce this on my side after trying a few times.
Are you abel to actively reproduce this?
Yes, i have this problem on serveral sites.
When I disable Mollie plugin: problem gone.
However. Just tested to replace the theme with Default 2025.. Then also problem gone.
Now i am confused.
What to do?
Also: i just rolled back the Mollie plugin latest version, to version 8.0.1
Now also problem gone.
So, this problem was introduced in 8.0.2
Hope this helps a little
-
This reply was modified 7 months, 3 weeks ago by
tedocweb.
We have the same issue.
BACS is removed in our payment list. When we disable the Mollie plugin it’s back.
Plugin Support
Femi
(@femiyb)
Thank you.
I will keep testing and trying to reproduce this issue, and will let you know as soon as I have any update.
Hey,
I’m having the same issue.
It is coming from MaybeDisableGateway class, line 59 here:
$notInCheckoutOrPayPage = $isWcApiRequest || !doing_action('woocommerce_payment_gateways') || !wp_doing_ajax() && !$isOrderPayPage && !$isCheckoutPage;
the $notInCheckoutOrPayPage check is not working as it should. Even though the user is on the payment page, this function says it’s not and disable BACS native method.
Hope that helps !
Here is a proposed fix:
$notInCheckoutOrPayPage = $isWcApiRequest || !doing_action('woocommerce_payment_gateways') || (!$isCheckoutPage && !$isOrderPayPage);
The issue is not happening in “blocks” mode but It’s happening with the “legacy” ajax fragment update (?wc-ajax=update_order_review) which points to this check ->
!wp_doing_ajax()
I just wasted 2 hours of my time …
I can confirm the same — the issue appears in the legacy checkout flow with ?wc-ajax=update_order_review. The logic in the Mollie plugin uses !wp_doing_ajax(), but this doesn’t behave as expected in that context.
I also tested this using woocommerce_available_payment_gateways directly (not just via Booster Plus), and it gets overridden after the AJAX update.
It would be helpful if Mollie could adapt the gateway filtering logic for legacy AJAX updates — or at least make it compatible with custom conditions again.
For now, I’m forced sticking to older version.
Plugin Support
Femi
(@femiyb)
Hello
Our developers have provided a beta package to solve this issue. This fix will be included in the next release.
If you would like, you can download the beta package here: https://mollie.inpsyde.com/803alpha1
We would appreciate your feedback to confirm that this does fix the issue on your site.
Regards,
Femi
