-
You can check the Mollie Plugin for Shopware 6 release notes↗ to learn whether your issue is known.
When you submit a support request, either to Mollie support or through the Shopware 6 plugin store, plugin automatically attaches the log files. You can also access them through your Shopware 6 installation.
Tip
You can customise the status mapping between Shopware 6 and Mollie.
If the statuses don't match, try the troubleshooting options listed in Payments aren't processing properly.
You can check whether the webhooks are working by comparing the update information in Shopware 6 with your Mollie Dashboard.
Tip
If you created an automated flow to tag Mollie webhooks, you can check whether they were successful in the Shopware 6 event logs↗.
-
View the webhook notification in your Mollie Dashboard:
-
Log in to your Mollie Dashboard.
-
Find the order:
-
To find one-off product and initial subscription orders, go to Orders.
-
To find subscription instalments, go to Transactions > Payments.
-
-
Click the order or payment and check the History column
If the webhook notification was unsuccessful, try the troubleshooting steps in Payments aren't processing properly.
-
-
If the order or payment webhook was successful, check the order in Shopware 6:
-
Log in to Shopware 6.
-
Go to
Orders > Overview.
-
Click the
context menu button and select View.
-
Go to Status and check the timestamps in the Payment status column.
-
Compare the timestamps with the webhook notifications in your Mollie Dashboard to ensure that they match.
-
Hover your mouse over the timestamp and check which system executed the update.
-
-
If the update was processed by a third-party or custom plugin, consult their troubleshooting documentation or contact their support team.
-
Log in to Shopware 6.
-
Go to
Extensions > My extensions.
-
Open the Mollie Payments
menu, and select Configure.
-
Go to API and click Test API keys.
If the API keys are incorrect, try to restore the connection.
Refer to the Mollie Plugin for Shopware 6 release notes↗ to check if your issue has been resolved in a newer plugin version.