Troubleshooting
Whenever you experiencing some difficulties or troubles with the installation and/or configuration of the Mollie Payment extension for Magento® 2 you can check the following points to make sure the configuration is right.
1. Perform a API Check
Use the [Test API key] button to check if the API Key is valid. You can find the [Test API key] button in the configuration API Details section located in Stores » Configuration » Sales » Payment methods » Mollie.
2. Perform a Self Test
Use the [Run Self Test] button to check if your server meets the requirements. You can find the [Run Self Test] button in the configuration Debugging section located in in Stores » Configuration » Sales » Payment methods » Mollie.
3. Check if you enabled the payment methods in the Magento configuration of the extension
4. Check if you enabled the payment methods in your Mollie Dashboard
The payment methods are disabled by default in your account so you firstly need to activate the payment methods that you want to implement in your Mollie Dashboard.
5. Check if your currency is EURO
6. Check if the order amount min and/or max value is fulfilled
7. Check if there is any information in the logfile /var/log/mollie.log
8. Check if module output has been disabled
Located in the core_config_data tabel under path "advanced/modules_disable_ouput/Mollie_Payment". This ability to disable module output has been removed from the Magento Admin since Magento 2.2. If you disabled module output from the Magento Admin in a previous release, you manually need to remove this line from the core_config_table. If you have installed the module on Magento 2.2 or higher, please check the <Magento_install_dir>/app/etc/config.php file, see Magento DevDocs
Below you can find the most common Questions with answers, whenever your question is still unanswered don't hesitate to send a message using the contact form on www.magmodules.eu/contact
A: Whenever your Logfile says "API Key Invalid" you need to double check if you copied and pasted the right API codes from your Mollie Dashboard. After you checked and changed this make sure that you flush your Caches as some settings are cached which results the same error in your logfile.
A: In Magento® 2 the payment status "Pending_Payment" is invisible on the front-end by default. You can solve this by creating and assign a new payment status and set it to "visible".
A: Make sure that https://yourdomain.co.uk/.well-known/apple-developer-merchantid-domain-association is accessible to external parties (e.g. no basic auth, no rewrites/redirects) and it's identical to https://mollie.com/.well-known/apple-developer-merchantid-domain-association.
A: Apple Pay Direct unfortunately is not available in test mode. You'll need to switch to live mode and try again, making sure you use the same domain name you also use for production.
A: Make sure that https://yourdomain.co.uk/mollie/checkout/webhook/ is accessible to Mollie's servers (e.g. no basic auth, no rewrites/redirects).
A: If the selftest isn't successfully showing all the green checkmarks you should contact your hosting-company to make sure that your server meets the Mollie and Magento® 2 server requirements.
A: This is because Mollie is unable to reach the Webhook of your webshop. The Webhook needs to be accessible from any location on the web. Read More.
A: When you enabled and configured the extension but the payment methods aren't visible in the front-end please check the following things
- Check if the API Details are valid and activated using the Test API key button
- Check if the Selftest is running successfully
- Check if the order amount min and/or max value is fulfilled*
- Check if your currency is EURO
- Check if you enabled the payment methods in the configuration of the extension
- Check if you enabled the payment methods in your Mollie Dashboard
- Flush your Magento Caches
If the methods still don't show up, check if there is any information in the logfile /var/log/mollie.log to get a good sight on the reason why the payment methods aren't showing
A: When an order gets updated, Mollie sends a webhook to your webshop. Also, the customer returns from the payment screen to the webshop. To prevent race conditions, we lock the order so it doesn't get updated simultaneously. When processing an order takes long; for example, when ERP software is connected, this error might occur. To fix this issue, you can enable the option under Stores -> Configuration -> Mollie -> Advanced -> Triggers & Languages -> Process transactions in the queue to yes. The customer will not see a change, but a side effect may be that orders get processed a few minutes later than normal.
Note
Please make sure you have cronjobs running. They are required for Magento to function properly, but for queues they are even more essential.
When installing Hyvä, Mollie also gets automatically installed. This is because the hyva-themes/magento2-default-theme requires hyva-themes/magento2-theme-module, which requires hyva-themes/magento2-mollie-theme-bundle, which then requires the different Mollie modules.
To remove the hyva-themes/magento2-mollie-theme-bundle package and its dependencies in Magento, using the replace feature of Composer can help you effectively handle this. Composer’s replace feature allows you to tell Composer to replace a package with another or to effectively remove it from the system. Here’s how to do this:
Step-by-Step Guide:
- Understand the Context: The hyva-themes/magento2-mollie-theme-bundle package includes several dependencies. If you no longer need or want this package, you can tell Composer to remove it and avoid installing its dependencies.
- Locate Your Composer File: Open the composer.json file of your Magento project. This file manages your PHP dependencies and their configurations.
- Use the replace Feature:
To prevent the installation of the
hyva-themes/magento2-mollie-theme-bundlepackage, you can add a replace section to your composer.json. This tells Composer to ignore the hyva-themes/magento2-mollie-theme-bundle package and its dependencies. Example of how to add the replace section:
{
"replace": {
"hyva-themes/magento2-mollie-theme-bundle": "*"
}
}
Here’s what happens:
- The replace section will “replace” the hyva-themes/magento2-mollie-theme-bundle package with a wildcard (*), meaning Composer will not attempt to install or manage it.
- You can use this if you don’t want to delete the composer.json entry but wish to stop Composer from trying to install this package.
Remove the Package (if already installed):
If the hyva-themes/magento2-mollie-theme-bundle package is already installed and you want to remove it, run the following command:
composer remove hyva-themes/magento2-mollie-theme-bundle
This will remove the package from your composer.json file and also uninstall it.
Update Composer:
After making changes to your composer.json, run:
composer update
This will update your dependencies according to the new configuration in composer.json.
Verify the Removal:
After the update, you can verify that the package has been removed successfully by checking your vendor directory and ensuring that the hyva-themes/magento2-mollie-theme-bundle package no longer exists. You can also check your composer.lock file to ensure the package is no longer listed.
Why Use the replace Feature?
- It allows you to prevent further installations of the hyva-themes/magento2-mollie-theme-bundle package.
- It lets you keep your composer.json intact (in case you want to restore the package later).
- It ensures Composer won’t consider it when resolving dependencies, effectively “removing” the package.
