Airtel Money
Turn on Airtel Money — one app, 14 countries. This is the Airtel rail for the AminiTech Mobile Money engine: OAuth2 login, a USSD push to the customer's phone, RSA-encrypted PIN for payouts, and a status poll that decides the truth. Install it once and every channel app you own starts taking Airtel.
Airtel markets on one connector — Nigeria, Uganda, Tanzania, Zambia, DR Congo, Kenya, Rwanda, Malawi, Madagascar, Chad, Niger, Gabon, Congo-B and Seychelles, switched by the Country field.
Every pending Airtel push is re-queried by a one-minute cron until the rail itself says success or failed — nothing settles on a callback body.
One rail app lights up every channel you own — POS, eCommerce and Invoicing all start offering Airtel the moment this is installed.
One engine, one ledger, now with Airtel on it
Airtel Money runs through the same provider form, the same transaction log and the same single-use receipt guard as M-Pesa and MTN. Nothing new to learn.
Your Airtel keys, on one form, proven
One record holds the lot: Rail → Airtel Money, Flow push, Environment Sandbox / Test until you go live, Shortcode Type, and the credential block. Test Connection fires a real OAuth2 token request at Airtel and tells you straight away if the Client ID/Secret are wrong — before a customer ever waits on a prompt. The same connector serves all 14 Airtel markets: Country & Currency drive the X-Country / X-Currency headers, so Uganda, Zambia, Tanzania or Nigeria is a field, not a new module.
RSA-encrypted payout PIN, never sent in clear
Paste Airtel’s public key into the Encryption section once. Every payout then encrypts your Disbursement PIN with it at send time — your PIN never travels or sits in a request body as plain text. Miss either one and the connector refuses to send rather than fail halfway. Both fields, and the whole credential block, are manager-only: a cashier can take money all day and still never read your keys.
Airtel and MTN rows in one ledger
Airtel Money collections land in the same list as every other rail — Airtel receipt IDs, amounts, phone numbers, Successful / Failed / Request Sent, next to your MTN rows. No second log to reconcile. And a row only turns Successful when Airtel says so: callbacks are never trusted on their own, a poll re-queries the rail every minute until each transaction resolves.
Money in and money out, same connector
Airtel Money here is not collection-only. The 500.00 supplier payout in this list went out through the same provider record that takes your customer payments, and lands back in the same ledger with its own receipt and status. One rail, both directions, one audit trail.
Drops in beside MTN, no rework
Airtel Money installs onto the free Mobile Money core and simply appears next to your other rails — same engine, same ledger, same roles. This app ships the Airtel rail and its provider form. The till, checkout and invoice screens are not ours to claim: those ship in the Mobile Money at the POS, eCommerce and Invoice Payments apps, and they pick up Airtel the moment this connector is installed.
Live on Airtel sandbox in an afternoon
Installing pulls in the free Mobile Money core and seeds an Airtel Money provider for you. Open Providers and it is already there — beside any rail you already run.
Drop in your Client ID & Secret — plus the RSA key and PIN if you will pay out. Hit Test Connection, then flip Environment from Sandbox / Test to Production. That is the whole setup.
We don’t just sell the app — we get you live on mobile money.
Buying Airtel 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.”
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 actually take a payment?
Does the free Base app let me collect on Airtel by itself?
Which Airtel countries does this cover?
Can a fake callback to my server mark an order as paid?
Who can see my Airtel credentials?
What happens to a payment nobody confirms?
Can I run Airtel and M-Pesa in the same shop?
Talk to us today
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 895 |
| Technical Name |
aminitech_momo_airtel |
| 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