Installation
Prerequisites
Before installing the module, make sure your environment meets the following requirements:
- Dolibarr version 18.0 (LTS) or higher, tested up to version 23
- PHP version 7.4 or higher
- An active Mollie account (https://www.mollie.com)
- The Dolibarr Bank and Direct debit modules enabled
- HTTPS access to your Dolibarr from the Internet
Why HTTPS is mandatory
Mollie only sends its notifications (webhooks) to an https URL. Without HTTPS, a payment would be collected by Mollie without anything recording it in Dolibarr.
The module therefore refuses to start a payment if your Dolibarr URL ($dolibarr_main_url_root in conf.php) does not start with https. A warning banner is displayed at the top of the Setup > Mollie > Settings page.
Installing the files
- Download the module archive from the DoliStore or your usual source
- Unzip the archive
- Copy the
molliefolder into thehtdocs/custom/directory of your Dolibarr installation
The expected structure is:
htdocs/custom/mollie/
├── admin/
├── class/
├── core/
├── langs/
├── lib/
├── public/
├── sql/
└── ...
Activating the module
- Go to Home > Setup > Modules
- Find Mollie in the module list (category "Interfaces")
- Click the activation button

Automatic actions on activation
On activation, the module automatically performs the following actions:
- Creates a "MOLLIE" bank account in Dolibarr, dedicated to storing Mollie transactions
- Generates a security token for the public pages (payment, IBAN)
- Registers the scheduled tasks (disabled by default)
- Creates the SQL tables required for the module to work
Post-installation checks
After activation:
- Check that the Mollie submenu appears under the Bank menu
- Go to Setup > Mollie > Settings to enter your API keys
- Fill in the user for actions: without it, the module refuses to record the payments received by webhook (see Configuration)
- Check that no red HTTPS warning banner is displayed at the top of the page
- See the Configuration page for the full setup
Security token for public pages
The module generates the PAYMENT_SECURITY_TOKEN constant on activation if it does not exist. It protects the public payment pages and the SEPA mandate creation link.
If this constant is empty (Setup > Other setup), the SEPA mandate link is no longer generated at all and a message is displayed in its place. Set it to a long random value.
Tip: Start in test mode using your test API key (
test_xxxx). You can switch to production once the integration has been validated.
Update
To update the module:
- Replace the contents of the
htdocs/custom/mollie/folder with the new version - Go to Home > Setup > Modules
- Disable then re-enable the module to apply the SQL migrations
If a warning message indicates an inconsistency between the module version and the database, disable and re-enable the module to resolve the issue.