| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Website (website)
• eCommerce (website_sale) • Invoicing (account) • Discuss (mail) |
| Lines of code | 294 |
| Technical Name |
nf_monopay_payment |
| License | OPL-1 |
| Website | https://netframe.org/ |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Website (website)
• eCommerce (website_sale) • Invoicing (account) • Discuss (mail) |
| Lines of code | 294 |
| Technical Name |
nf_monopay_payment |
| License | OPL-1 |
| Website | https://netframe.org/ |
| Versions | 17.0 18.0 19.0 |
Payment Provider: Plata by Monobank
Accept online payments on your Odoo website with plata by mono — Monobank Acquiring. Buyers pay on plata by mono side and the order is confirmed automatically via signed webhooks.
An invoice is created through the Monobank API and the buyer is redirected to the secure pay.monobank.ua page — card data never touches your server.
Every webhook from Monobank is verified with an ECDSA + SHA256 signature against the merchant public key — forged status updates are rejected.
Transaction status is synced automatically as Monobank reports it: pending → authorized → done / canceled — no manual reconciliation needed.
Supports UAH, USD and EUR. The provider is offered at checkout only when the order currency is supported.
With Odoo's Automatic Invoice enabled, a paid invoice is created and reconciled on successful payment — the order moves straight to Paid.
Limit availability by maximum amount, currencies and countries. Orders that don't match the rules simply won't see the provider at checkout.
Use a test token to try the full flow with any Luhn-valid card — no real charge. Switching to production only means swapping the token and the provider state.
The Monobank X-Token is stored restricted to system administrators and is never written to the logs.
POST /api/merchant/invoice/create and redirects the buyer to pay.monobank.ua./payment/monobank/webhook on every status change./payment/monobank/return → the payment status page.| Monobank | Odoo |
|---|---|
created | pending |
processing | pending |
hold | authorized |
success | done |
failure | canceled |
reversed | canceled |
expired | canceled |
Apps → search nf_monopay_payment → Install.
payment, website_sale, account_accountant
cryptography (already in the Odoo venv) and requests
Odoo 19.0
- Test token: api.monobank.ua (personal cabinet)
- Production token: web.monobank.ua (merchant cabinet, after enabling Internet Acquiring / plata by mono)
- State → Test Mode (testing) or Enabled (production)
- Monobank X-Token (Credentials tab) → the token from your Monobank cabinet
- Published → toggle the provider to Published so it is visible to buyers
- Maximum Amount — if the order total exceeds this value, plata by mono is hidden at checkout
- Currencies — allowed currencies (supported: UAH, USD, EUR)
- Countries — allowed countries (leave empty to make it available everywhere)
web.base.url
set a real public HTTPS URL if it isn't already correct.
The API URL is the same (https://api.monobank.ua). Only the token differs. To go live: sign an acquiring contract with Monobank, get a production token at web.monobank.ua, replace the token and switch State from Test to Enabled.
In test mode any card number that passes the Luhn algorithm works and no real charge is made. Note: Apple Pay and Google Pay are not available with a test token.
UAH, USD and EUR. The provider only appears at checkout when the order currency is one of these.
Each webhook is validated with an ECDSA + SHA256 signature against the Monobank merchant public key. Requests with an invalid signature are rejected.
/payment/monobank/return (GET) — buyer return after payment, and /payment/monobank/webhook (POST) — status webhooks from Monobank.
Author: Netframe
For implementation assistance, custom configuration, or any questions — reach out to the Netframe team.
Monobank Acquiring docs: API · Testing · Brandbook
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