Banca Transilvania iPay Payment Acquirer
by Terrabit https://www.terrabit.ro , Dorin Hongu https://www.terrabit.ro$ 234.24
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Discuss (mail) • Website (website) • Invoicing (account) |
| Lines of code | 354 |
| Technical Name |
deltatech_payment_bt_ipay |
| License | OPL-1 |
| Website | https://www.terrabit.ro |
| Versions | 17.0 18.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Discuss (mail) • Website (website) • Invoicing (account) |
| Lines of code | 354 |
| Technical Name |
deltatech_payment_bt_ipay |
| License | OPL-1 |
| Website | https://www.terrabit.ro |
| Versions | 17.0 18.0 |
Banca Transilvania iPay Payment Acquirer

This module connects Odoo with BT iPay (Banca Transilvania’s online card payment platform), enabling secure card payments for web orders and customer invoices. It is designed for merchants who sell online in Romania and want to centralize order-to-cash operations inside Odoo while offering a trusted local payment experience to shoppers.
What you can do
- Offer “Pay by card (BT iPay)” during website checkout in Odoo eCommerce.
- Let customers pay open invoices directly from the Odoo customer portal.
- Track payment attempts and final authorization status on orders/invoices in Odoo.
- Reduce manual reconciliation by linking successful transactions to the correct documents.
Usage modes (business choice)
BT iPay in Odoo can be used in two business modes, depending on what you sell and when you want to capture funds:
- 1‑Phase (one‑step) – Recommended for online services. The customer’s card is authorized and captured immediately at checkout. This is ideal when delivery is instant (e.g., digital goods, subscriptions, services) and there is no need to delay collection.
- 2‑Phase (two‑step) – Recommended for physical products. The card is authorized at checkout, but you capture the funds later, after you ship or when the customer confirms delivery. This gives your operations team control to capture only what is delivered and helps reduce post‑sale adjustments.
Configuration: choose the mode in the BT iPay payment provider settings in Odoo. Selecting 2‑Phase enables manual capture so your team can capture the authorized amount from Odoo once the order is fulfilled.
Business benefits
- Higher conversion for local shoppers through a familiar Romanian payment provider.
- Faster cash collection and fewer unpaid orders thanks to instant card authorization.
- Less back‑office work: payments are recorded against the right document automatically.
- Better customer experience with a simple, secure checkout flow handled by BT iPay.
Typical workflow
- A customer places an order on your Odoo website or opens an invoice in the portal.
- They choose BT iPay as the payment method and complete the card authorization.
- BT iPay confirms the result; Odoo updates the related order/invoice accordingly.
- Your team proceeds with fulfillment knowing the payment is secured.
Checkout and payment link flow (redirects)
- From both the customer portal payment link (invoice payment page) and the eCommerce checkout, Odoo redirects the customer to the BT iPay (Banca Transilvania) hosted payment page where the card data is entered and the payment is registered.
- After the payment is completed or canceled on the bank page, the customer is automatically redirected back to your website. Odoo then reflects the outcome on the related document (order or invoice).
Who is it for
- Online retailers and B2B sellers operating in Romania.
- Companies using Odoo 18 (Community or Enterprise) who want to accept card payments.
Requirements
- An active BT iPay merchant account (test or production) and valid credentials from the bank.
- Odoo 18 with website and/or accounting modules configured for online payments.
Notes and scope
- Card data entry and security are handled by BT iPay. No card details are stored in Odoo.
- The module focuses on the commercial flow (offer payment, receive confirmation, link to documents). Detailed risk or anti‑fraud settings remain managed in your BT iPay account.
- Compatibility targets Odoo 18; customizations may be needed for heavily modified checkout flows.
For assistance with onboarding, configuration, or tailored extensions (refunds flows, multi‑company setups, custom checkout UX), please contact the Terrabit team.
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