When something is going wrong and you cannot see why, this is where you look.
Where
Go to Mollie Payments, then the Logs tab.
What it records
The plugin keeps detailed records of API requests, webhooks, status changes and errors.
If a payment failed and you cannot work out why, this will tell you what actually happened, rather than what you assume happened.
It is off by default, and that is correct
Logging writes to your database. Most sites never need it, and leaving it on forever slowly fills your database with information nobody will ever read.
So switch it on when you have a problem, and switch it off when you have the answer. The plugin says exactly this, and it is good advice.
The safety guarantees
Two things worth knowing, because they are the things people worry about.
Logs are kept for up to 7 days, and removed automatically each day. They do not accumulate forever.
Sensitive data is redacted before anything is written. Your API keys and webhook tokens never appear in a log file, even if you go looking for them.
That means a log file is safe to send us, and safe to open in front of someone.
Using it
Enable debug logging, then save.
Reproduce the problem. Make the payment that fails. Do the thing that does not work.
Come back to the Logs tab and look.
You can filter by Category: business events, Mollie API calls, webhook activity, errors only, or general. Start with Errors only, because that is usually where the answer is.
There is a Search box, a Refresh button, and a Download .txt button.
Clear all logs empties it, if you want to start clean before reproducing a problem. That is a good habit: clear, reproduce, look. Then you are reading only what just happened.
Then switch it off
Once you have your answer, turn it off again.
When logging is off, nothing is written and your database stays clean.
Send it to us
If you are stuck, download the .txt and send it with your message, along with the Status report.
Between the two, we can usually see exactly what happened without a single round of questions.