Skip to Content

Mobile Money Base — Multi-Rail Core (M-Pesa, MTN, Airtel & more)

by
Odoo
v 17.0 Third Party 5
Download for v 17.0 Deploy on Odoo.sh
Versions 17.0
You bought this module and need support? Click here!
Versions 17.0
For Odoo 17.0 · Community & Enterprise

Mobile Money Base — Rail-Agnostic Core

Free ★ FREE FOREVER

One mobile money engine for every African rail. M-Pesa, MTN MoMo and Airtel Money all run through one provider form, one cross-rail transaction ledger and one pluggable driver per network. Free foundation — add a rail app and a channel app to take money.

✅ Rail-agnostic engine ✅ One ledger for every network ✅ Free foundation — no lock-in ⭐ 90 days free support
📚 Full Documentation 💻 Try it live
Mobile Money Base - Rail-Agnostic Core for Odoo
1

Provider form for every rail — pick the network, enter your credentials, hit Test Connection, done.

60s

The poll cron re-queries every pending transaction every single minute until the rail gives a final answer.

0

Transactions this app can settle on its own — it is the engine, so a paid rail app and a channel app do the collecting.

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

The engine under every AminiTech mobile money app

This is the shared core our POS, website, invoice and recovery apps are built on. Same provider form, same ledger, same security — whichever network your customers pay from.

The Mobile Money Providers list showing two configured providers side by side: Airtel Money and MTN MoMo, with their rail, environment and country
01 · TWO RAILS

Two rails, one list of providers

Airtel Money and MTN MoMo sitting in the same Providers list — same form, same fields, same rules. Each rail is a pluggable driver, so adding a network later is a new record, not a new integration. This engine is free.

The MTN MoMo provider form showing the Rail selector, Flow=push, Environment=Sandbox/Test, Country, Shortcode and the Test Connection button
02 · ONE FORM

One form, every rail, tested in one click

Pick the Rail and the form tells you what that network does — Flow, Country, Shortcode, Sandbox or Live. Test Connection authenticates against the network and answers pass or fail on the spot, so you never discover a bad key at the till.

The Airtel Money provider form: Rail=Airtel Money, Flow=push, Sandbox environment, Test Connection button, the CREDENTIALS (MANAGER-ONLY) block and the Base Callback URL field
03 · CREDENTIALS

Staff can charge. Only managers see the keys.

Every secret sits in a Credentials (manager-only) block — restricted field by field, so a cashier can take a payment without ever reading, exporting or RPC-ing your keys. Base Callback URL is the only address the rail needs; leave it blank and it auto-detects.

The cross-rail Transactions ledger: 12 rows mixing Airtel Money and MTN MoMo, with Created on, Rail, Provider, Direction, Phone, Amount, Currency, Payment Reference, Receipt-Provider ID and State columns and a 2,502.00 total
04 · ONE LEDGER

One ledger for every rail

Airtel Money and MTN MoMo in one list — date, rail, provider, direction, phone, amount, reference, receipt and state, collections and payouts together, totalled at the bottom. Every paid app in the family writes here; the POS, website and invoice screens ship in those apps, not in this one.

The same cross-rail ledger with colour-coded states across Airtel Money and MTN MoMo rows: Successful, Failed, Request Sent and Pending
05 · TRUTH BY POLL

The rail is asked. The callback is not trusted.

Request Sent and Pending rows are never left hanging — a cron re-asks the network every minute until each one lands on Successful or Failed. A callback is logged but never treated as proof: the rail is re-queried first, so a forged one cannot mark money received.

Setup in 4 steps

Install the core, then bolt on what you sell through

The Providers list with Airtel Money and MTN MoMo configured
1 · Install    2 · Add a rail

This engine is free and comes down automatically with any Mobile Money app you buy. Then open Mobile Money → Providers and add one record per network — the Rail selector lists whichever connectors you have installed.

The MTN MoMo provider form with Environment, Country, Shortcode, the manager-only credentials block and the Test Connection button
3 · Paste keys    4 · Test

Set Environment, Country and Shortcode, then paste your keys into the manager-only Credentials block. Hit Test Connection — it authenticates against the rail and tells you pass or fail before a single customer is ever charged.

Implementation included with your purchase - free setup

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

Buying Mobile Money Base - Rail-Agnostic Core 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

This app is free. What else do I have to install to actually take money?
Two things. A rail app — MTN Mobile Money or Airtel Money (or the Suite for all rails) — because the network drivers live there, and without one the Rail dropdown on the provider form is empty and no provider can be saved. And a channel app — POS, eCommerce or Invoicing — because that is what asks a customer to pay. This app is the shared engine those two plug into; it collects nothing by itself. Recovery is the one exception: it records a payment you already received from its receipt, so it does not need a live rail.
Why is the Rail dropdown empty after I install this?
Because it is working as designed. A rail only exists once its driver is installed, and drivers ship inside the paid rail apps. Until then the dropdown just tells you to install MTN Mobile Money or Airtel Money. Nothing is broken and nothing is missing — the core is simply inert until you give it a network.
Do I need a separate core for each network?
No, and that is the point. One provider record per account, one ledger for all of them. M-Pesa, MTN and Airtel run through the same engine with the same statuses, the same single-use guard and the same poll. Add a second rail and every channel app you already own can use it immediately, with no reconfiguration.
Who can see my API credentials?
Only Mobile Money Managers. Secrets — consumer secret, API key, subscription key, passkey, disbursement PIN, webhook secret, RSA key and the callback token — are locked to the Manager role at field level, so an ordinary user cannot read them through the interface, an export or an RPC call. Access tokens are tighter still, visible only to system administrators. A cashier can take a payment without ever being able to see what authorised it. Settings administrators get the Manager role automatically, so there is nothing to assign after install.
The callback endpoint is public. Can somebody fake a payment?
No. The endpoint accepts the call and always answers politely so the network stops retrying, but the engine deliberately discards the status from that body. It saves the identifiers and the raw payload for audit, then asks the rail directly what actually happened, and only that authoritative answer can mark a transaction successful. You can also set a Callback Token on the provider and mismatched calls are rejected outright.
What happens when the network never sends the callback?
It gets polled anyway. Callbacks go missing, arrive twice or never fire at all in some sandboxes, so the engine does not depend on them: a cron re-queries every pending transaction once a minute until the rail returns a final answer, and any staff member can hit Query Status on a transaction to force it. A payment does not sit unknown because a webhook got lost.
Does it handle payouts, and does it work across companies?
The engine supports both collections and payouts, but what you get depends on the rail — each driver declares what its network can do and the form adapts, so a rail that cannot send payouts says so in plain words instead of throwing an error. Providers and transactions are both scoped by company, so in a multi-company database each company only sees its own accounts and its own payments.
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)
Lines of code 633
Technical Name aminitech_momo_base
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, please use the developer contact information. They can usually be found in the description.