Mobile Money at the POS — Any Wallet (M-Pesa, MTN, Airtel...)
by AminiTech Solutions https://www.aminitechsolutions.com$ 105.01
In-App PurchasesAfrica Mobile Money POS — M-Pesa, MTN & Airtel
Every mobile-money wallet, at one till. M-Pesa, MTN MoMo and Airtel Money in a single POS popup that re-skins to the rail you pick — Safaricom green, MTN yellow, Airtel red. STK push and scan-to-pay QR, direct-till listening and receipt-code verify where the rail supports them, all reconciled in one cross-rail ledger. Buy the wallets you use; add a rail any time.
Each rail does what its API really allows
We never fake a channel a rail doesn’t expose. Here is exactly what you get, rail by rail.
Refunds, wallet balance, payment recovery, single-use claims and the cross-rail ledger apply to every rail. Feature panes appear only for the rail that supports them — no dead buttons, no false promises.
One popup that becomes the wallet you tap
Real screens from the app running on Odoo — the rail-adaptive popup, the POS payment methods, and the cross-rail ledger.

The popup re-skins to the rail — and shows only what it can do
Pick M-Pesa and the popup turns Safaricom green with STK, QR, till-listening and receipt-verify. Pick MTN and it turns yellow with push and MoMoPay QR. Pick Airtel and it turns red with the PIN push and payer-name check. Panes appear per the rail’s real capabilities — never a dead button.

Configure a provider per rail, add it to the register
Each rail is a Mobile Money provider you configure once — M-Pesa Daraja, MTN Open API, Airtel Open API — and expose as a POS payment method. Run one rail or all three on the same till; each is server-side rail-locked so a method can only collect on its own rail.

Every rail, one reconciliation log
M-Pesa, MTN and Airtel payments land in a single cross-rail ledger — grouped by rail, provider, status, POS and date, with receipts, channels and result codes, in list, pivot and graph views. One place to reconcile the whole counter.
Open any panel — three rails, one engine, nothing oversold
Rail-adaptive branded popup
STK / RequestToPay / PIN push
Scan-to-pay QR (M-Pesa & MTN)
Direct-till listening (M-Pesa C2B)
Verify a receipt code (M-Pesa)
Payer-name confirm (MTN & Airtel)
“Already paid?” recovery (every rail)
One shared engine, three rail drivers
Server-side rail lock
Cross-rail reconciliation ledger
Exact-decimal amounts, every currency
Single-use claim & same-order re-claim
Refunds & wallet balance (per rail)
Cashier-safe & callbacks-never-proof
Odoo 17, 18 & 19 · Community & Enterprise
Turn on the rails you use, add them to the till

Install the app — the free M-Pesa, MTN and Airtel drivers come with it. Add a Mobile Money provider for each rail you use and paste its credentials.

Create a POS payment method per rail, point each at its provider, add them to your register. Open a session — the popup brands itself to whichever wallet the cashier taps.
We don’t just sell the app — we get you live on every rail you run.
Buying Africa Mobile Money POS includes hands-on implementation: installed on your Odoo, each rail connected to your merchant accounts, configured for your markets, and proven with a real payment before we hand it over.
Common questions
Do I have to use all three rails?
Why does M-Pesa have more options than MTN or Airtel?
Is this cheaper than buying each rail app?
Can a cashier fake a payment or read my keys?
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3250 |
| Technical Name |
aminitech_momo_pos |
| License | OPL-1 |
| Website | https://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