| 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 | 1739 |
| Technical Name |
aminitech_mpesa_pos |
| License | OPL-1 |
| Website | https://aminitechsolutions.com |
| Versions | 18.0 19.0 |
M-Pesa POS Payments
Accept M-Pesa at the till — three ways, one popup. STK Push to the customerâs phone, a scan-to-pay QR code, or a direct Till/Paybill payment that matches itself to the sale. Verified receipts, single-use protection, full transaction log.
Ways to pay in one popup — STK Push to the phone, scan-to-pay QR, or direct Till/Paybill with automatic matching.
Unverified payments. Every payment is confirmed by Safaricom callback or receipt-code check — amount matched, each receipt usable exactly once.
Transaction log for every channel — STK, QR and C2B in one list with receipts, phones, result codes; pivot and graph views included.
Real screens from live shops taking real money
Every screenshot below is from a working Odoo POS processing genuine M-Pesa payments. No mockups, no renders.
Every payment path on one screen
The cashier hits M-Pesa and this opens: amount on top, STK Push phone entry on the left, scan-to-pay QR on the right — and it is already listening for direct Till payments in the background. Whichever way the customer pays, the popup catches it.
The PIN prompt lands on the customerâs phone
Type the Safaricom number, send. No typing your Till number wrong, no "confirm the name" back-and-forth. The till polls live and flips to success the second Safaricom confirms.
Scan to pay, or pay the Till directly
A dynamic QR with the amount pre-filled, plus your Till number in lights. Customers who pay your Till directly are matched automatically by amount — the payment pops up on the cashier screen in seconds.
Customer already paid? Verify in seconds
Enter the last 3+ characters from their M-Pesa SMS. The app finds the payment, checks the amount matches, and locks each receipt to one order — a screenshot of an SMS is not a payment, and a used receipt can never pay twice.
Receipt attached. Order done. Books balanced.
The M-Pesa receipt number lands on the POS payment line automatically. End of shift, the M-Pesa method total matches your Till statement — per shop, per till, no notebook.
Every shilling, logged and sliceable
STK, QR and direct Till payments in one list — date, business, till, phone, amount, receipt, status. Filter by day, group by shop, switch to pivot or graph for totals. Dedicated M-Pesa security roles keep credentials manager-only.
From install to first payment in one afternoon
Point of Sale → M-Pesa → Configuration. Enter your Daraja credentials (manager-only, encrypted from cashiers), pick Paybill or Till, then click Test Connection and Register C2B URLs — one click each.
Create a POS payment method with integration M-Pesa, pick your configuration, add it to your POS. Running six shops with six Tills? One method + one configuration each — payments never cross-match.
The complete M-Pesa family for Odoo
Every app below shares the same M-Pesa configuration and security roles. Buy any combination â enter your Daraja credentials once. All of them are covered by one documentation portal.
Other Odoo services we offer
Common questions
What do I need from Safaricom before I can use this?
Does it work when customers pay the Till directly, without the cashier doing anything?
Can I run several shops with different Till numbers on one Odoo?
Who can see my API credentials?
What happens if my internet drops or the server misses a payment?
Is there a version for my website, invoices, or self-order kiosk?
Talk to us today
| 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 | 1739 |
| Technical Name |
aminitech_mpesa_pos |
| 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