Skip to Content

Payment Provider: Monri

by
Odoo

$ 293.76

v 18.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 1323
Technical Name payment_monri
LicenseSee License tab
Websitehttps://wolfinne.com
Versions 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 1323
Technical Name payment_monri
LicenseSee License tab
Websitehttps://wolfinne.com
Versions 18.0 19.0

Payment Provider: Monri (Odoo)

This module adds Monri as a payment provider to Odoo (Website / Sales / Accounting). It supports the hosted form (redirect) and S2S/Components (saved card tokenization), as well as partial/full refund, void, and capture via Monri Transaction Management (XML).

Installation

To install this module:

  • Install standard Odoo apps: Website (if you use web shop), Sales, and Accounting.
  • In Apps, install payment_monri.
  • Enable Developer mode for easier diagnostics.
  • Load a generic chart of accounts and set the company Fiscal Country (Settings → Companies).
Monri module installed

Configuration

1) Create & enable the Monri provider

  • Go to Accounting → Configuration → Payment Providers.
  • Open Monri and switch to Enabled (Test or Production).
  • Fill in:
    • Authenticity Token (from Monri)
    • Merchant Secret Key (from Monri)
    • Form URL (test: https://ipgtest.monri.com/v2/form, prod: https://ipg.monri.com/v2/form)
  • Select a Journal (bank/electronic) for posting incoming/outgoing payments and refunds.
  • Optional: enable Tokenization to allow saved cards (S2S/Components flow).
  • Optional: set a Callback URL if you use server-to-server notifications.

2) Website payments (if you use the shop)

  • Go to Website → Configuration → eCommerce → Payment and make sure Monri is visible and enabled.
  • Adjust label, logo, and display order as needed.

3) Automatic invoicing (optional)

  • Go to Website → Configuration → Settings, section Invoicing, and enable Automatic Invoice — "Generate the invoice automatically when the online payment is confirmed".

4) Fiscal country & taxes

  • Set the company Fiscal Country in Settings → Companies.
  • In Accounting → Configuration → Taxes, ensure each tax has a Tax Country compatible with the company fiscal country; otherwise Odoo will block posting.

5) Currency & rounding

  • Make sure the transaction currency (e.g., BAM) is active and the number of decimals matches Monri expectations.
Monri provider form
Website payment methods with Monri enabled
Automatic Invoice setting
Tax/Fiscal country compatibility

Usage

A) Web shop (redirect / hosted form)

  1. The customer selects Monri at checkout.
  2. They are redirected to the Monri form, enter card details, and confirm.
  3. On success, Odoo marks the order as paid, creates an invoice (if enabled), and posts the payment.

B) Sales with saved cards (S2S/Components)

  1. Create a quotation → confirm the Sales Order.
  2. On the transaction, pick a token (saved card) and trigger the charge.
  3. The module sends an S2S purchase to Monri and records the provider reference.

C) Refund / Void / Capture (Accounting → Customers → Payments / Payment Transactions)

  • Refund: allowed for done charges; supports partial and full refunds.
  • Void: allowed for authorize transactions that were not captured.
  • Capture: partial or full capture of an existing authorization.

The module uses Monri Transaction Management (XML) and the original order_number saved on the initial charge. It is used for all refund/capture/void calls.

D) Auto-posting & reconciliation

  • Incoming/outgoing entries are posted on the selected Journal.
  • For refunds, the module attempts to auto-post and auto-reconcile refund bank lines against the original payment (best effort).
Payment Transactions list
Monri hosted form checkout
Refund wizard
Refund wizard after refund

Known Issues / Tips

  • Invalid order_number (422) — refund/capture/void use the original transaction's monri_order_number. If it is empty, fill it with the actual value (typically reference-id).
  • Taxes country mismatch — align the company fiscal country and each tax's Tax Country; otherwise posting will be blocked.
  • Access rights — refund/void/capture require Accounting Manager or Payment Manager privileges.
  • Currency — verify decimals/minor units (e.g., 100.50 → 10050).
  • Test vs Production — always set the correct URLs and credentials per environment.

Credits

Contributors

Maintainer

Maintained by wolfinne.com.
For support and customizations: hello@wolfinne.com. 

For copyright information, please see the COPYRIGHT file.

Payment Provider: Monri module is published under the Wolfinne Proprietary
License v1.0, as included below.

This license applies only to the part of the software that is
not distributed under other licences.

********************************************************************************

Wolfinne Proprietary License v1.0
Copyright (C) 2025 Wolfinne d.o.o.

This software and associated files (the "Software") can only be used (executed,
modified, executed after modifications) with a valid permission issued by
Wolfinne d.o.o.

With a valid Partnership Agreement with Wolfinne d.o.o., the above permissions
are also granted, as long as the usage is limited to a testing or development
environment.

You may develop new modules based on the Software and distribute them
under the license of your choice, provided that it is compatible with the terms
of the Wolfinne Proprietary License (For example: LGPL, MIT, or proprietary
licenses similar to this one).

You may use Odoo modules published under any license along with the Software,
provided that their license is compatible with the terms of the Wolfinne Proprietary
License (Including, but not limited to, any module published on the Odoo Apps
Store on odoo.com)

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.
There are no ratings yet!
Request for Odoo 19 Compatibility Update
by
Roger
on 10/17/25, 1:26 PM

Hello,

I recently discovered your Monri Payment Provider module for Odoo 18, and it looks excellent.

Since Odoo 19 has already been officially released, I would like to kindly suggest updating the module to ensure compatibility with Odoo 19.

Many users in Southeast Europe are now migrating to Odoo 19, and having Monri support would be very helpful for integrating local payment gateways in Serbia, Montenegro, and neighboring countries.

Could you please let me know if you plan to release a version compatible with Odoo 19 soon?

Thank you very much for your great work!

AdriaMart

Re: Request for Odoo 19 Compatibility Update
by
Bojan Nisevic
on 10/17/25, 2:16 PM Author

Hello,

Thank you very much for reaching out and for your thoughtful suggestions regarding the Monri Payment Provider module. We greatly appreciate the feedback and interest from the Southeast European Odoo community.

To address your first point, yes, we are planning to update the Monri module for Odoo 19 compatibility. The project is currently scheduled for completion by the end of next week.

However, I would also like to offer a word of caution regarding the immediate adoption of Odoo 19. While the official release is exciting, based on our experience, migrating to a brand-new major Odoo version right away is generally not recommended for production environments. It often takes a minimum of 6 to 12 months for a major release to mature sufficiently. My team has already identified a couple of critical bugs in version 19, and the frequent minor version releases we are seeing weekly are often symptomatic of a rushed release cycle, likely pressured by the deadline of Odoo Experience 2025. We strongly suggest holding off on building new solutions or performing production migrations until the version stabilizes.

Best regards,
Wolfinne IT