Netopia MobilPay Payment Acquirer

$ 235.88

v 18.0 Third Party 2

Availability	Odoo Online Odoo.sh On Premise
Odoo Apps Dependencies	• eCommerce (website_sale) • Discuss (mail) • Website (website) • Invoicing (account)
Lines of code	446
Technical Name	`deltatech_payment_mobilpay`
License	OPL-1
Website	https://www.terrabit.ro
Versions	16.0 17.0 18.0 19.0

You bought this module and need support? Click here!

Availability	Odoo Online Odoo.sh On Premise
Odoo Apps Dependencies	• eCommerce (website_sale) • Discuss (mail) • Website (website) • Invoicing (account)
Lines of code	446
Technical Name	`deltatech_payment_mobilpay`
License	OPL-1
Website	https://www.terrabit.ro
Versions	16.0 17.0 18.0 19.0

Description
License

Netopia MobilPay Payment Acquirer

Netopia MobilPay Payment Provider (Odoo 18)

This module connects Odoo with Netopia MobilPay, enabling secure card payments for web orders and customer invoices. It is designed for merchants selling online in Romania who want to centralize order‑to‑cash in Odoo while offering a familiar local payment experience.

What you can do

Offer “Pay by card (MobilPay)” 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 right documents.

How it works (one‑step)

MobilPay uses a one‑step flow in this integration: the customer’s card is authorized and captured immediately at checkout or when paying an invoice. This is ideal for online sales where you want funds collected right away.

Business benefits

Higher conversion for local shoppers through a Romanian payment provider.
Faster cash collection and fewer unpaid orders thanks to instant card authorization.
Less back‑office work: payments are recorded against the correct document automatically.
Better customer experience with a simple, secure checkout flow handled by MobilPay.

Typical workflow

A customer places an order on your Odoo website or opens an invoice in the portal.
They choose MobilPay as the payment method and complete the card payment (immediate capture).
MobilPay 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 Netopia MobilPay hosted payment page where 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).

Features

Hosted card payment via Netopia MobilPay (redirect flow)
Test and Live modes with their respective endpoints
Auto‑generated confirm and return endpoints
Website integration (website_sale) + standard payment status page
Provider configuration fields for POS Signature, API Key, and RSA keys (public certificate / private key)
Optional status “pull” on return, using Netopia REST client as a fallback when no IPN was processed yet

Requirements

Python packages (installed automatically if you use this repo’s aggregated requirements):
- netopia-sdk
- PyJWT
Odoo dependencies: payment, website_sale

Tip: in this repo you can install extras with:

pip install -r odoo-addons/bitshop/requirements.txt

Important installation note:

When installing Netopia’s SDK directly, use the following command to avoid pulling incompatible transitive dependencies:

pip install --no-deps netopia-sdk

Rationale: we pin/curate dependencies via Odoo and this repo; netopia-sdk may declare broad requirements that can conflict with Odoo’s stack. Installing with --no-deps ensures compatibility.

Configuration

Go to Invoicing/Accounting → Configuration → Payment Providers → Create or Edit provider “MobilPay”.

State: Test for sandbox, Enabled for live
Signature (POS signature)
API Key (Netopia REST API key)
Public Certificate (upload .cer or public PEM provided by Netopia)
Private Key (upload your merchant private key PEM)
Website: set to the website you use (base URL will be derived from it)

The module computes the correct endpoints automatically:

Sandbox: https://sandboxsecure.mobilpay.ro/payment/card/index
Production: https://secure.mobilpay.ro/payment/card/index

For website checkout, enable the provider and ensure it is available for the website.

Checkout Flow

Customer is redirected to Netopia hosted payment page.
Netopia calls your Confirm (IPN) URL to notify Odoo about status changes.
Customer is redirected back to the Return URL, which finally redirects to Odoo’s /payment/status page.

If a return happens before the IPN, the module attempts a status pull (GetStatus) via Netopia SDK and maps the result to the Odoo transaction.

Testing

Netopia test cards: Test Cards Support

Notes & Tips

Use Test mode first and verify both Confirm and Return flows.
Ensure your base URL is correct (consider running behind HTTPS in real scenarios).
Keep your RSA keys safe. Upload them as attachments on the provider record; the module reads them securely.

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:

dhongu

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

The author can leave a single reply to each comment.
This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
If you want to start a discussion with the author or have a question related to your purchase, please use the support page.