Skip to Content

MTN Mobile Money

by
Odoo

$ 90.00

v 19.0 Third Party
Versions 17.0 18.0 19.0
You bought this module and need support? Click here!
Versions 17.0 18.0 19.0
For Odoo 19.0 · Community & Enterprise

MTN Mobile Money

$129 $90 ★ 30% LAUNCH OFFER

Switch on MTN Mobile Money everywhere at once. This is the MTN MoMo rail — OAuth, request-to-pay push to the customer's phone, payouts, and a status poll that keeps asking MTN until the answer is final. Install it once and every AminiTech channel app you own can take MTN money.

✅ Request-to-pay + payouts ✅ One-click sandbox provisioning ✅ 14 MTN markets mapped ⭐ 90 days free support
📚 Full Documentation 💻 Try it live
MTN Mobile Money for Odoo
1

One rail app lights up every channel you own — POS, website and invoicing all start accepting MTN the moment it is installed.

14

MTN markets mapped to their target environment — Ghana, Uganda, Rwanda, Cameroon, Côte d'Ivoire, Benin, Zambia, Liberia, Congo, Guinea, Eswatini, South Sudan and more.

60s

The status poll re-asks MTN every minute until a pending payment resolves — a lost callback never costs you a sale.

★ Implementation included Features Setup in 4 steps Documentation ↗ Mobile Money family Services FAQ Support & Contact
See it in action

The MTN rail, wired the way MoMo actually behaves

Built against the official MoMo Open API — Collections and Disbursements, sandbox and production. Every screen below is the real configuration and the real channels it unlocks.

MTN MoMo provider form in Odoo: Rail set to MTN Mobile Money (MoMo), Flow push, Environment Sandbox/Test, Country Uganda, a Test Connection button, and the manager-only credential block with API User/UUID and Subscription Key.
01 · CREDENTIALS

Every MTN credential on one guarded form

This is the app’s own screen — pick the rail, set Country and Environment, paste your keys, done. Country drives MTN’s X-Target-Environment for you, so Uganda, Ghana, Rwanda, Cameroon, Côte d’Ivoire, Zambia and the rest need no code. The Subscription Key and API Key sit behind a manager-only group — cashiers can charge, but they can never read or export your secrets.

The same MTN provider form with Environment on Sandbox/Test, the API User/UUID and Subscription Key fields in the credential block, and Test Connection in the header.
02 · SANDBOX FIRST

Sandbox keys without the developer portal

Paste your Collections Subscription Key and hit Provision Sandbox: the app calls MoMo, creates the API user and API key, and writes them into the API User/UUID and API Key fields you see here. Test Connection then fetches a real OAuth token and tells you plainly if it worked. No UUID generation by hand, no curl.

The Transactions list showing MTN MoMo collections and a disbursement with MP2607-series receipt IDs, amounts, and Successful, Pending and Failed states, listed together with Airtel rows.
03 · ONE LEDGER

MTN and Airtel in one transaction ledger

Every request-to-pay and every payout lands as a row here — MTN receipt ID, amount, phone and state — right beside your other rails. Because MTN’s sandbox fires no callbacks and live callbacks can be missed or duplicated, a poll cron re-queries each pending request until MoMo itself says Successful or Failed. A forged callback can never settle a row: the rail is always re-asked.

The MTN payment prompt at the point of sale, where the cashier enters the customer's MoMo number to send the request-to-pay.
04 · AT THE TILL

The cashier just types the MoMo number

This app ships the MTN rail; this particular screen ships in the separate Mobile Money at the POS app. Install both and the till sends a real requestToPay → the customer approves on their handset → the order settles. The same rail also drives the website and invoice channel apps, unchanged.

The Providers list with the MTN Mobile Money provider installed alongside another mobile-money rail.
05 · ADD A RAIL

Add MTN as a rail, not as a rewrite

MTN registers itself as a driver on the shared Mobile Money core, so it shows up next to your other rails and reuses the same ledger, poll cron and callback controller. Collections and disbursements are both supported. Adding a country or a second network later changes a dropdown — not your workflow.

Setup in 4 steps

From subscription key to a live MTN payment

MTN MoMo provider form showing Rail, Flow push, Environment Sandbox/Test, Country Uganda, Test Connection, and the manager-only API User/UUID and Subscription Key fields.
1 · Install    2 · Configure

Install MTN Mobile Money — it pulls in the free Mobile Money core. Open a provider, set Rail to MTN Mobile Money (MoMo), choose your Country, leave Environment on Sandbox / Test, and paste your Collections Subscription Key.

Transactions ledger with MTN collections and a disbursement carrying MP2607-series receipt IDs and Successful, Pending and Failed states, next to Airtel rows.
3 · Test    4 · Go live

Hit Provision Sandbox, then Test Connection, and send a request-to-pay — watch it resolve to Successful in the ledger. Then flip Environment to Production / Live, drop in your production API User and key, and charge real customers.

Implementation included with your purchase - free setup

We don’t just sell the app — we get you live on mobile money.

Buying MTN Mobile Money includes hands-on implementation by our engineers: installed on your Odoo, connected to your mobile-money account, configured for your business, and proven with a real payment before we hand it over. No hourly fees, no “figure it out yourself.”

1
Install & configure

We install it on your Odoo and set it up for your business — nothing for you to work out.

2
Rail go-live

We help you get your MTN, Airtel or Safaricom credentials and switch you from sandbox to live.

3
Live payment test

We run a real mobile-money payment with you, end to end, so you watch it work before launch.

4
Team walkthrough

A short session so your cashiers and admins know exactly what to do.

5
90 days of support

Real people on call for 90 days after you go live — included.

Already purchased? Send us your order reference and we’ll book your setup within one business day. Book my free setup →
Services

Other Odoo services we offer

🏠
Full Odoo setup for your shop
From your products to your tills, your printers, and your accounting — we put it all together and train your team.
💳
Payment-gateway integrations
M-Pesa, MTN MoMo, Airtel Money, Stripe, PayPal, bank IPN — wired into your POS and Invoicing so customers pay and Odoo reconciles in the same second.
✏️
Custom development
A workflow only your shop has? We build the small Odoo add-on for it — cleanly, documented, supported.
🔁
Migration to a newer Odoo
Move from Odoo 15, 16, 17 to the current version without losing your data, customisations, or a single day of trading.
☁️
Managed hosting
We run your Odoo on a server we manage — backups, updates, monitoring. You focus on selling.
🛒
Point-of-sale hardware
Receipt printers, barcode scanners, customer displays, drawers, scales — sourced, configured, and live on your Odoo.
📚
Staff & admin training
On-site or online sessions tailored to your cashiers, supervisors, and back-office team.
📱
Ongoing support contract
A monthly retainer for when you want a real person to call. Bug fixes, small changes, friendly check-in every month.
🔌
Third-party integrations & API work
Connect your Odoo with tax authorities, e-invoicing gateways, shipping carriers, marketplaces, CRMs — via clean, documented APIs.
FAQ

Common questions

What else do I need to install to actually take money?
Two things, and we would rather tell you now than refund you later. This rail needs the free Mobile Money Base engine underneath it — that is a free download and it installs automatically as a dependency. Then you need at least one paid channel app for the place you want to charge people: POS for the till, Website for online checkout, or Invoicing for invoices. This rail on its own gives you a working, testable MTN connection and the transaction ledger, but no till screen or checkout button — the channel app is what puts a pay button in front of a customer.
Why isn't the free Base enough on its own?
Because the Base ships the engine, not the rails. With no rail app installed there is literally nothing to pick in the Rail field — it just tells you to install a rail app — so no provider can be configured and no money can move. The rail apps are where the actual network integration lives, and they are what you are paying for. Buy this one and you have MTN. Buy Airtel Money too, or the all-rails Suite, and the same channel apps handle those as well with no extra work.
I already bought your POS app. Do I need to buy anything else for MTN?
Just this. The channel apps are rail-agnostic on purpose — your POS, website and invoice apps all sit on the same engine, so installing the MTN rail switches MTN on in all of them at once. There is no MTN-for-POS and MTN-for-website to buy separately, and no second set of credentials to maintain.
Who can see my API credentials?
Only Mobile Money Managers. The API Key, Subscription Key, Passkey, Disbursement PIN, Webhook Secret and Callback Token are all restricted at the field level, so a cashier cannot read them through the interface, an export, or an RPC call — the access token MTN issues is locked down tighter still. The driver reads them internally to sign a request, but the user driving the payment never sees them.
Can someone fake a callback and mark an order as paid?
No. The callback endpoint is public because MTN needs to reach it, but the app never settles on what the callback says. It saves the body for your audit trail with the state deliberately stripped out, then goes back to MTN and asks for the real status before anything is marked paid. On top of that, you can set a Callback Token and mismatched calls are rejected outright. And because MoMo's sandbox fires no callbacks whatsoever, the poll is the path we actually rely on — the callback is only ever a hint to check early.
Which countries does this work in?
The rail maps Ghana, Uganda, Rwanda, Cameroon, Côte d'Ivoire, Benin, Zambia, Liberia, Congo-Brazzaville, Guinea, Eswatini, South Sudan, Guinea-Bissau and Afghanistan to their MTN target environments, and any other MTN market falls back to a derived one from the country name. Sandbox always runs in EUR, as MTN requires — production uses your provider's currency, or the country's currency if you leave it blank.
What happens if the customer just ignores the prompt?
Nothing gets marked paid. The transaction stays as Request Sent, and the poll keeps re-asking MTN once a minute until MTN comes back with SUCCESSFUL or FAILED — then, and only then, does the state change. Because the reference we send is also the idempotency key, retrying the same request is safe: MTN recognises a duplicate rather than charging twice, and the app shows the cashier that a payment for that request is already in progress.
Support & Contact

Talk to us today

🏆
90 days of free support included with your purchase
Real people, business hours, typical first reply under 4 hours — including help getting your MTN, Airtel or Safaricom credentials and going live. Start with the full documentation.
⭐ Included — no extra cost
✉️
Email
reach@aminitechsolutions.com
📞
Phone / WhatsApp
+254 746 883 809
📚
Documentation
docs.aminitechsolutions.com
💻
Try it live
demo.aminitechsolutions.com
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 955
Technical Name aminitech_momo_mtn
LicenseOPL-1
Websitehttps://www.aminitechsolutions.com 
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.