LibraPay Payment Provider
by Terrabit https://www.terrabit.ro , Dorin Hongu https://www.terrabit.ro$ 235.88
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Discuss (mail) • Website (website) • Invoicing (account) |
| Lines of code | 351 |
| Technical Name |
deltatech_payment_libra_pay |
| License | OPL-1 |
| Website | https://www.terrabit.ro |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Discuss (mail) • Website (website) • Invoicing (account) |
| Lines of code | 351 |
| Technical Name |
deltatech_payment_libra_pay |
| License | OPL-1 |
| Website | https://www.terrabit.ro |
| Versions | 17.0 18.0 19.0 |
LibraPay Payment Provider

LibraPay Payment Provider (Odoo 18)
This module integrates Odoo with LibraPay, a secure payment gateway provided by Libra Internet Bank in Romania. It enables businesses to accept online card payments (Visa, Mastercard) for eCommerce orders and portal invoices, providing a reliable and localized payment experience for the Romanian market.
What you can do
- Accept Card Payments: Enable “Pay with card (LibraPay)” as a payment method during the Odoo eCommerce checkout.
- Portal Invoice Payments: Allow customers to pay their open invoices directly from the Odoo customer portal using their credit or debit cards.
- Automated Payment Status: Automatically update the status of Sales Orders and Invoices in Odoo based on the real-time feedback from Libra Internet Bank.
- Asynchronous Notifications (IPN): Use Instant Payment Notifications to ensure that payments are recorded even if the customer closes the browser before redirection.
How it works
LibraPay uses a secure redirect flow:
- When a customer selects LibraPay at checkout, they are redirected to the secure LibraPay hosted payment page.
- The customer enters their card details on the bank’s secure infrastructure.
- After processing, LibraPay redirects the customer back to Odoo.
- Odoo receives the transaction result (success, failure, or cancel) via both a synchronous return and an asynchronous IPN call, updating the records accordingly.
Business benefits
- Trust and Security: Leverage the reputation of a well-known Romanian bank (Libra Internet Bank) to build customer trust.
- Optimized for Romania: Specifically designed for merchants operating in Romania, supporting local card processing and currency.
- Reduced Manual Work: Automated synchronization of payment statuses reduces the need for manual reconciliation and speeds up order fulfillment.
- Improved Cash Flow: Instant card authorization ensures that funds are captured quickly, reducing the risk of unpaid orders.
Typical workflow
- A customer places an order on your Odoo website or accesses an invoice in the portal.
- They select LibraPay and are redirected to the bank’s secure payment page.
- Upon successful payment, LibraPay notifies Odoo.
- Odoo automatically marks the Sales Order as “Paid” (or “Authorized”) and creates the corresponding payment records.
- Your team can immediately proceed with shipping or service delivery.
Features
- Secure Redirect Flow: Customer card data never touches your Odoo server, ensuring PCI compliance.
- IPN Support: Reliable payment confirmation via asynchronous backend-to-backend notifications.
- Test & Live Modes: Support for both testing (sandbox) and production environments with separate endpoints.
- Integration: Works seamlessly with Odoo’s standard payment and website_sale modules.
- Customizable Messages: Ability to configure custom messages for different payment outcomes (Done, Cancel, Pending).
Requirements
- LibraPay Merchant Account: You must have an active merchant agreement with Libra Internet Bank.
- Python Dependencies:
- phpserialize (installed automatically via Odoo’s external dependencies).
Configuration
- Navigate to Accounting (or Invoicing) > Configuration > Payment Providers.
- Locate and open LibraPay.
- Set the State to Test Mode (for development) or Enabled (for production).
- Fill in the credentials provided by Libra Internet Bank:
- Merchant name
- Merchant URL
- Merchant ID
- Merchant Email
- Terminal ID
- User and Password
- Key (Security Key)
- Configure the Payment Journal where transactions should be recorded.
- Webhook (IPN) Setup: In your LibraPay merchant portal, configure the IPN URL to: https://your-domain.com/payment/libra_pay/ipn.
Support
Maintainer: Terrabit (Deltatech) — https://www.terrabit.ro — odoo@terrabit.ro
License: OPL-1
Table of contents
Bug Tracker
Bugs are tracked on Terrabit Issues. In case of trouble, please check there if your issue has already been reported.
Do not contact contributors directly about support or help with technical issues.
Credits
Authors
- Terrabit
- Dorin Hongu
Maintainers
Current maintainer:

This module is part of the terrabit-ro/bitshop project on GitHub.
You are welcome to contribute.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module