I am reaching out to request a change in how the Mollie module handles its dependencies on the "PrestaShop Accounts," "PrestaShop EventBus," and "PrestaShop Marketplace in your Back Office (MBO)" modules. Currently, the configuration page states that these are required for the module to work correctly.
Technical Justification
The core functionality of the Mollie payment gateway—processing payments via the Mollie API—technically only requires a valid API Key and the ability to communicate with api.mollie.com.
The forced dependencies introduce several issues for performance-oriented merchants:
Performance Degradation: Modules like EventBus and MBO inject significant overhead into both the Front Office and Back Office (hooks, external API calls, and background synchronization tasks).
External Reliance: These modules often rely on external CDNs (e.g., unpkg.com) or PrestaShop's own cloud infrastructure. If these services experience latency or downtime, it can slow down or even break the shop's admin interface.
Privacy & Bloat: Many users prefer not to synchronize their store data (orders, customers, technical specs) with the PrestaShop Cloud via EventBus if it is not strictly necessary for payment processing.
Suggested Change
Please consider making these modules optional.
Allow users to enter their API Keys and configure payment methods without being forced to install/link PrestaShop Accounts.
Provide a "Basic Mode" that bypasses the PrestaShop Cloud services and only uses the direct Mollie API integration.
While these services might offer benefits for marketing or centralized management, they should not be a hard requirement for a payment gateway. Many merchants choose Mollie specifically for its reliability and independence.
I am reaching out to request a change in how the Mollie module handles its dependencies on the "PrestaShop Accounts," "PrestaShop EventBus," and "PrestaShop Marketplace in your Back Office (MBO)" modules. Currently, the configuration page states that these are required for the module to work correctly.
Technical Justification
The core functionality of the Mollie payment gateway—processing payments via the Mollie API—technically only requires a valid API Key and the ability to communicate with api.mollie.com.
The forced dependencies introduce several issues for performance-oriented merchants:
Performance Degradation: Modules like EventBus and MBO inject significant overhead into both the Front Office and Back Office (hooks, external API calls, and background synchronization tasks).
External Reliance: These modules often rely on external CDNs (e.g., unpkg.com) or PrestaShop's own cloud infrastructure. If these services experience latency or downtime, it can slow down or even break the shop's admin interface.
Privacy & Bloat: Many users prefer not to synchronize their store data (orders, customers, technical specs) with the PrestaShop Cloud via EventBus if it is not strictly necessary for payment processing.
Suggested Change
Please consider making these modules optional.
Allow users to enter their API Keys and configure payment methods without being forced to install/link PrestaShop Accounts.
Provide a "Basic Mode" that bypasses the PrestaShop Cloud services and only uses the direct Mollie API integration.
While these services might offer benefits for marketing or centralized management, they should not be a hard requirement for a payment gateway. Many merchants choose Mollie specifically for its reliability and independence.