Africa Mobile Money — All Rails
Every mobile money rail, every channel, one install. M-Pesa, MTN MoMo and Airtel Money running through a single engine — at the till, on website checkout, on customer invoices, and a recovery desk for the payments that slip through. One provider form, one transaction ledger, one receipt that can only ever settle one thing.
Rails on one engine — Safaricom M-Pesa (Daraja), MTN MoMo across 14 markets, Airtel Money across 14 markets.
Transaction ledger for every rail and every channel — the till, the website, the invoice and the recovery desk all write to the same log.
The status poll re-queries every pending payment once a minute, because a callback is never trusted on its own.
One catalogue, every rail, every channel
The screens below are what this package installs — the same provider form, the same till popup, the same ledger, whichever network the customer pays on.
Every rail configured in one list
One install pulls in every rail connector and every channel app, in dependency order, on one shared engine. Your Providers list carries a row per rail — each with its own credentials, environment and country. Add another rail later and it appears here; nothing else changes.
One ledger for every rail and channel
Airtel and MTN, collections and payouts, POS & website & invoice references — all in one list, not one silo per network. Filter by rail, group by direction, pivot by channel. Every receipt is unique at the database level, so a payment can never land twice.
The till prompt, on whichever rail they use
The cashier picks Mobile Money and the prompt goes to the customer’s phone on the rail they actually have. The paid order claims its transaction atomically — two tills can never settle the same receipt. This screen ships in the Mobile Money at the POS app, bundled here.
Customers pay from their own phone
Checkout and the customer portal get a pay page that pushes the request and listens for the result — the order confirms itself once the payer approves. Callbacks are never trusted alone; a poll cron re-queries every pending payment until it truly resolves. Shipped by the Mobile Money eCommerce & Portal app.
Request-to-pay from any posted invoice
Open a posted invoice, pick the rail, confirm the phone and amount — the request goes out while you are still on the call. The payment reconciles back against that invoice. Shipped by the Mobile Money Invoicing app.
The day the network drops, you still get paid
Customer’s phone says paid, your server says nothing? Key the receipt into the recovery wizard on any rail. It refuses a receipt already in the ledger, then drops a normal unclaimed inflow that the POS or the invoice can settle. Shipped by the Mobile Money Recovery app.
Live on your first rail in an afternoon
Install the suite — every rail and every channel arrive together. Then go to Mobile Money → Configuration → Providers and add one provider per rail: credentials, sandbox or live, country and currency. Hit Test Connection, then Register Callbacks. Secrets stay manager-only.
Add the mobile-money method to your POS registers, publish the website provider, and your invoices pick up request-to-pay automatically. From there every rail and every channel reports into one ledger — one place to reconcile, whatever the customer paid with.
We don’t just sell the app — we get you live on mobile money.
Buying Africa Mobile Money - All Rails 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.”
We install it on your Odoo and set it up for your business — nothing for you to work out.
We help you get your MTN, Airtel or Safaricom credentials and switch you from sandbox to live.
We run a real mobile-money payment with you, end to end, so you watch it work before launch.
A short session so your cashiers and admins know exactly what to do.
Real people on call for 90 days after you go live — included.
The complete Mobile Money family for Odoo
Every app below shares one engine, one configuration and one set of security roles. Pick the rails your customers use and the channels you sell through — enter your credentials once. All of them are covered by one documentation portal.
Other Odoo services we offer
Common questions
What else do I need to buy to go live?
I only sell in one country on one network. Should I buy this?
Who can see my API credentials?
A callback endpoint is public. Can someone forge one and mark an order paid?
Can the same payment settle two orders or two invoices?
Can I send money out, not just collect it?
What happens when a customer's payment fails?
Talk to us today
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Point of Sale (point_of_sale) • Inventory (stock) • Restaurant (pos_restaurant) • eCommerce (website_sale) • Website (website) |
| Community Apps Dependencies |
Show
•
Airtel Money
• M-Pesa Complete Suite • MTN Mobile Money • Mobile Money Invoicing (Request-to-Pay + Reconcile) • Mobile Money Recovery & Reconciliation — Any Wallet (M-Pesa, MTN, Airtel...) • Mobile Money at the POS — Any Wallet (M-Pesa, MTN, Airtel...) • Mobile Money eCommerce & Portal — Any Wallet (M-Pesa, MTN, Airtel...) • Mobile Money Base — Multi-Rail Core (M-Pesa, MTN, Airtel & more) • M-Pesa Invoice Payments • M-Pesa Kiosk & Self-Order Payments • M-Pesa POS Payments • M-Pesa Transaction Recovery • M-Pesa eCommerce & Portal Payments (STK Push) • POS Receipt: M-Pesa Till Details • M-Pesa Core (Technical) |
| Lines of code | 7117 |
| Technical Name |
aminitech_momo_suite |
| License | OPL-1 |
| Website | https://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