Start here: what the System tab tells you

Before you go hunting through settings, let the plugin tell you what is wrong. It already knows.

Go to Mollie Payments, then the System tab, and click Run checks.

The plugin then examines your entire setup and reports back. It takes a few seconds, and it will usually point straight at your problem.

How to read the results

Results are colour-coded, and the plugin explains the colours on the page itself. Green means fine. Grey is just information. Amber is not critical, but worth sorting out. Red needs your attention, and something will not be working.

The five checks that matter most

Look at the Health section first. It runs five checks, and each one maps directly to a real problem.

Houzez theme. If this warns that Houzez is not the active theme, our plugin has nothing to attach to. Check under Appearance, Themes.

Gateway mode. If this says “Houzez WooCommerce mode is on (Mollie is bypassed)”, that is your answer, and nothing else you try will help until you fix it. Go to Theme Options, Payment Gateways, and set Choose Payment gateway type to Houzez Custom Gateways.

API key. If it warns that no API key is configured, the plugin cannot talk to Mollie at all. Go to the API keys tab and paste your key in.

Webhook. If it warns that the webhook is not configured, payments will complete at Mollie but nothing will happen on your website. This is the single most common cause of the most confusing problem there is.

License. If this is not active, your settings tabs are locked.

The section that catches the sneakiest problem

Scroll to Payment methods (plugin vs Mollie).

This compares two lists: what you have switched on in our plugin, and what is genuinely active in your Mollie account.

If a method appears in the first list but not the second, it will never show up at your checkout, no matter how many times you tick it. It has to be on in both places.

This one section answers a surprising number of support emails.

About recent errors

The last section is Recent errors, and it will probably tell you that debug logging is off.

That is normal. Logging is off by default because it writes to your database, and most sites never need it.

If you are hunting a problem, switch it on: go to the Logs tab and enable logging. Then reproduce the problem, and come back to the System tab. The errors will be waiting for you.

Switch it off again when you are done.

Sending this to us

At the bottom of the System tab you can copy the whole report.

If you message us, paste it in. It saves us both a round of questions, and it means we can usually answer you properly the first time instead of asking you to go and look at things.

Still stuck?

Send us a message and a real person gets back to you, usually within one business day.