MBI Up2pay ETransactions

🎯 Module Overview

MBI Up2pay ETransactions collects card payments online for your invoices and sales orders through Crédit Agricole's Up2Pay E-Transactions payment solution. The module adds an "Internet card" payment method to Dolibarr, generates a payment link for each document, emails it to your customer, then records the settlement and marks the invoice as paid as soon as the bank confirms the transaction. It complies with the PSD2 regulation and supports 3-D Secure v2.

An Up2Pay E-Transactions contract with Crédit Agricole is required, together with the shop credentials provided by the bank (site number, rank, identifier and secret key), a bank account configured in Dolibarr on which settlements will be recorded, and return pages reachable from the Internet, as the bank calls them directly to notify transaction results.

🌐 Demo: https://demo.mbicloud.fr 🛒 Discover our other modules on Dolistore.

💡 Benefits

• Your customers pay online, immediately, with no data re-entry on your side.
• The settlement, the bank entry and the paid status of the invoice are handled automatically.
• The payment link is sent along with the invoice, in an email you write once and for all.
• You can request a deposit, or offer payment in two or three instalments, without leaving Dolibarr.
• A test mode lets you validate the whole chain before collecting a single euro.

⚙️ Key Features

💳 Online card collection

• "Internet card" payment method: added to Dolibarr and available on customer invoices and sales orders.
• Secure payment link: generated per document, based on a single-use hash.
• Choice of payment page: a page in your own company's colours, or Dolibarr's native online payment page.
• Test mode: validate the integration without any real movement.

💶 Deposit and instalments

• Deposit: an extra field lets you collect only part of the amount, capped at the outstanding balance.
• Payment in two or three instalments: the amount is split into equal parts, each instalment being charged one month after the previous one.

✉️ Customer emails

• Automatic email delivery of the link: sent when the invoice is sent, with a customisable subject and message template, and optional copies to addresses of your choice.
• Trust image: displayed in the email, showing the customer's phone number.
• Paid invoice email: sent after collection, with the PDF attached, customisable subject and template.

🧾 Settlement and accounting

• Automatic settlement recording: on the bank's return, payment creation, entry on the configured bank account, invoice switched to paid.
• Invoice creation from the order: when the payment relates to a sales order.

🛡️ Security and architecture

• Multi-entity: payments made on a secondary entity are correctly attached.
• Signature verification: the bank's returns are verified using a 2048-bit key.
• Reliable handling of bank notifications: a duplicate notification does not create a second settlement, and a failure while recording is retried cleanly instead of leaving a partial entry.
• Permissions: three separate permissions, read, create or update, delete.

🆕 Recent updates (2.0.1 / 2.0 / 1.6.0)

• The payment result pages no longer load a stylesheet from Google, so your customer's browser is not contacted by a third party while paying, and the online payment stylesheet configured in Dolibarr is now applied to those pages.
• An optional branded payment page is available, or redirection to Dolibarr's native online payment page, the default behaviour being unchanged.
• Deposit and 2x/3x split payment are now available on orders as well, not only on invoices, and both options are restored and editable on the record.
• Security was strengthened on the public payment page and signature verification now uses a 2048-bit key; duplicate gateway notifications and payments made on a secondary entity are handled correctly.
• Payment can be started from a sales order, with the invoice created automatically, and the payment link can be generated when a payment is validated through the Dolibarr API.

✅ Compatibility

• Dolibarr: 12.0+ (tested up to Dolibarr 23)
• PHP: 7.2+
• Up2Pay E-Transactions contract: required, with the shop credentials provided by Crédit Agricole (site number, rank, identifier and secret key).
• Dolibarr bank account: required, settlements are recorded on it.
• Internet-reachable return pages: required, the bank calls them directly to notify transaction results.
• PHP openssl extension: optional, used to verify the signature of the bank's returns.
• No other Dolibarr module is required, and no incompatibility is declared. The module fits into the standard Dolibarr interface, without overriding the core.

Module version: auto
Publisher/Licence: MB Informatique / GPL-v3
User interface language: English, French
Help/Support: MB Informatique
Prerequisites:

• Dolibarr min version: auto
• Dolibarr max version: auto

🔧 Installation

1. Download the module's ZIP archive without extracting it.
2. In Dolibarr, go to Home > Setup > Modules/Applications.
3. Open the Deploy/Install external module tab.
4. Upload the module's ZIP archive.
5. Find and enable MBI Up2pay ETransactions.
6. Configure the module options from its administration page: the shop credentials provided by Crédit Agricole (site number, rank, identifier and secret key), the bank account on which settlements will be recorded, and the subjects and templates of both emails.
7. Grant the required permissions to the relevant users.
8. (Optional) For a manual installation, drop the mbietransactions folder into /htdocs/custom/.

ℹ️ Usage notes

• An Up2Pay E-Transactions contract with Crédit Agricole is required, together with the shop credentials provided by the bank: site number, rank, identifier and secret key.
• A bank account must be configured in Dolibarr, as settlements are recorded on it.
• The module's return pages must be reachable from the Internet, as the bank calls them directly to notify transaction results.
• The PHP openssl extension is optional and is used to verify the signature of the bank's returns.
• Enable test mode first, pay an invoice end to end to check that the bank's return is properly processed, then disable test mode once the whole chain has been validated.
• A deposit is capped at the outstanding balance, and split payment charges each instalment one month after the previous one.
• Back up the database and the Dolibarr files before any update, and read the ChangeLog: some versions require disabling and re-enabling the module to take effect, which is stated explicitly at the top of the version concerned.
• Disabling the module releases the licence activation and removes the module's constants, permissions and declarations. Data created by the module is kept: the payment hash table and the extra fields added to invoices and orders are not deleted, so that the transaction history is preserved.

🎓 Services

• Training on the module is available at €80 excl. VAT.
• Support and updates included for the duration of your license.

📄 Terms of Use

Article 1 — Publisher. The MBI Up2pay ETransactions module is published by MB Informatique, a limited liability company (SARL) registered with the Mulhouse Trade and Companies Register under number 834 342 362 (SIRET 834 342 362 00029, intra-community VAT FR07834342362), whose registered office is located at 120 rue de l'Île Napoléon, 68170 Rixheim, France. Phone: 03 67 262 242 — Email: info@mb-informatique.fr — Website: https://www.mb-informatique.fr.

Article 2 — Purpose and acceptance. These Terms of Use govern the use of the MBI Up2pay ETransactions module ("the Module") for Dolibarr ERP/CRM as well as the associated services provided by MB Informatique SARL (support, updates, activation). Installing, activating or using the Module constitutes full and unconditional acceptance of these Terms of Use. They apply in addition to the terms of sale of the platform through which the Module was acquired (e.g. DoliStore), which govern the purchase.

Article 3 — Code license. The Module's source code is distributed under the GNU General Public License version 3 or later (GPL v3+), the full text of which is provided in the COPYING file delivered with the Module. These Terms of Use do not restrict the rights granted to the User by that license; they govern the services provided by MB Informatique SARL and the conditions of use of the Module.

Article 4 — Prerequisites and compatibility. The Module is designed for the environments indicated in its documentation (Dolibarr 12.0 minimum, tested up to Dolibarr 23, PHP 7.2 minimum). Its operation is not guaranteed outside these versions, in the event of a modification of the Dolibarr core, nor in the presence of conflicting third-party modules. It is the User's responsibility to verify the compatibility of their environment before installation.

Article 5 — User obligations. The User undertakes to: (a) perform a full backup (files and database) before any installation or update; (b) test the Module on a test environment before going into production where possible; (c) use the Module in accordance with its documentation and applicable regulations; (d) keep their Dolibarr instance under normal security and update conditions.

Article 6 — Support and updates. Support is provided by email at info@mb-informatique.fr, under the conditions and for the duration possibly specified at the time of purchase. The following are excluded from support: malfunctions due to a modification of the Module or of the Dolibarr core by the User or a third party, to an environment that does not meet the prerequisites, or to a conflict with a third-party module. Some updates may require a more recent version of Dolibarr.

Article 7 — Warranties. The Module is provided "as is", in accordance with articles 15 and 16 of the GPL license and within the limits permitted by law. MB Informatique SARL does not warrant that the Module is free of defects, operates without interruption or meets any particular need of the User. Applicable mandatory legal warranties are not affected by this article.

Article 8 — Liability. Within the limits permitted by law, MB Informatique SARL may not be held liable for indirect damages (in particular loss of data, loss of business, loss of revenue, damage to image), nor for damages resulting from: improper use of the Module; the absence of a prior backup; a modification of the Module by the User or a third party; a case of force majeure. For professional Users, the total liability of MB Informatique SARL, on all grounds combined, is limited to the amount actually paid for the Module over the last twelve (12) months. Nothing herein excludes liability that cannot legally be excluded, in particular in the event of willful misconduct or gross negligence.

Article 9 — Personal data. The Module operates within the User's Dolibarr instance: the functional data it processes remains stored on the User's systems, who remains the data controller within the meaning of the GDPR. When checking the version or activating the Module, technical information including the name and version of the Module, the licence key, the IP address and the domain of the instance may be transmitted to MB Informatique SARL's server, solely for the purpose of managing licences, activation and updates, and kept for the time necessary for those purposes. No business data contained in the Dolibarr instance is transmitted in this context. The User may exercise their rights of access, rectification, erasure, restriction and objection by writing to info@mb-informatique.fr.

Article 10 — Intellectual property and trademarks. "Dolibarr" is a trademark belonging to its respective holders. The Module is an independent development by MB Informatique SARL, not affiliated with or endorsed by the Dolibarr association. The copyright notices contained in the Module's files must not be removed, in accordance with the GPL license.

Article 11 — Duration and changes. These Terms of Use apply from the first use of the Module and for the entire duration of its use. MB Informatique SARL may change the Terms of Use for future versions of the Module; the applicable version is the one delivered with the version of the Module used. The termination of the services does not affect the rights granted by the GPL license.

Article 12 — Governing law and disputes. These Terms of Use are subject to French law. In the event of a difficulty, the User is invited to first send a written complaint to MB Informatique SARL in order to seek an amicable solution. Failing an amicable resolution, any dispute with a professional User falls under the exclusive jurisdiction of the Commercial Court of Mulhouse, including in summary proceedings, warranty claims, incidental claims or where there are several defendants. Consumer Users retain the benefit of the mandatory rules of jurisdiction and may use, free of charge, the consumer mediation scheme under the conditions provided for by articles L.612-1 et seq. of the French Consumer Code. Up-to-date information on the consumer mediation applicable to MB Informatique SARL's services is set out in its Terms and Conditions of Sale, available at https://www.mb-informatique.fr/cgv.html.

Article 13 — Miscellaneous. If any provision hereof is declared void or unenforceable, the others retain their full validity. These Terms of Use are written in French; in the event of a discrepancy between the French version and a translation, the French version prevails.

👨 💻 Publisher

MBI Up2pay ETransactions is a custom Dolibarr module developed by MB Informatique.

It is aimed at companies holding a Crédit Agricole Up2Pay E-Transactions contract who want to collect card payments for their invoices and sales orders directly from Dolibarr, without re-entering data and without an intermediate tool.

Publisher: MB Informatique
Contact: info@mb-informatique.fr
Website: https://www.mb-informatique.fr

🛠 CHANGELOG

UPDATE 2.0.1 (2026-07-30)

• Security: the payment result pages no longer load a stylesheet from Google, so your customer's browser is not contacted by a third party while paying.
• Fixed: the online payment stylesheet configured in Dolibarr is now applied to the payment result pages; it was built and then discarded.
• Improved: the module documentation is shown in the user's language on the About tab, in English, French, German, Italian and Spanish.

UPDATE 2.0 (2026-06-18)

• ⚠️ Action required: disable then re-enable the module after updating to apply the changes introduced by this version.
• New: optional branded payment page, or redirection to Dolibarr's native online payment page (default behaviour unchanged).
• New: deposit and 2x/3x split payment are now available on orders as well, not only on invoices.
• Security: fixed a vulnerability on the public payment page and hardened signature verification, now using a 2048-bit key.
• Improved: a duplicate gateway notification no longer creates a second settlement, and a failure while recording is retried cleanly instead of leaving a partial settlement.
• Fixed: the deposit and split payment options had been ignored since 1.6 and were not editable on the record; both are restored.
• Fixed: an amount with a fractional cent could be charged up to one hundred times too high.
• Fixed: a deposit larger than the outstanding balance can no longer collect more than what is due.
• Fixed: payments made on a secondary entity were lost and are now recorded.
• Compatibility: PHP 8.5 support, minimum Dolibarr version raised to 12.0.

UPDATE 1.6.0 (2025-08-08)

• New: payment can be started from a sales order, with the invoice created automatically.
• Improved: the payment link can be generated when a payment is validated through the Dolibarr API.
• Fixed: minor phone number validation issue.

UPDATE 1.5.0 (2024-09-25)

• New: phone number settings added to the module configuration.

UPDATE 1.4.0 (2024-08-20)

• New: setting to control when an invoice is marked as paid.
• Compatibility: support for the latest Dolibarr version and for multi-company.

UPDATE 1.3.0 (2023-11-15)

• Fixed: payment mode check against the Dolibarr core.
• Improved: code cleaned up and optimised.

UPDATE 1.2.0 (2023-10-06)

• Security: public key added and signature verification enabled.
• Security: overall protection strengthened.
• Fixed: various minor issues.

UPDATE 1.1.0 (2023-07-26)

• New: email subjects can be set from the module configuration.
• New: English translations added.
• Improved: display style updated.
• Fixed: various issues.

UPDATE 1.0

• Initial version.