$ 128.01
In-App Purchases| 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 | 1985 |
| Technical Name |
aminitech_mpesa_recovery |
| License | OPL-1 |
| Website | https://aminitechsolutions.com |
| Versions | 18.0 19.0 |
M-Pesa Transaction Recovery
The insurance policy for your M-Pesa books. Server down when a customer paid? Payment missing from the log? Fetch it back from Safaricom or record it from the SMS — with duplicate protection, so recovered never means double-counted.
Recovery paths — fetch the transaction from Safaricom by receipt number, or key it in manually from the customerâs confirmation SMS.
Duplicates. Every recovered receipt is checked against the existing log first — a transaction that already exists is refused with a clear message.
Reconciliation. The goal is simple: every shilling on your M-Pesa statement has a matching row in Odoo, even for the hour your internet was down.
When a payment goes missing, get it back in a minute
Real screens from the live demo. No mockups, no renders.
Pull the truth straight from Safaricom
Type the receipt number from the customerâs SMS or your G2 portal report and click Fetch from Safaricom — the transaction details come back from the API and save into your log as a completed payment. No re-typing amounts, no guessing.
Or record it by hand — guided and validated
For payments that predate your callback registration (or sandbox testing), the Add Missed Transaction form captures receipt, amount, phone, date and till — validated as you type, stamped as manually recovered for the audit trail.
Lives in the M-Pesa menu your managers already use
Both wizards sit under Point of Sale → M-Pesa, next to the transaction log — and they are manager-only. Cashiers cannot invent payments; your M-Pesa Administrators can fix any gap in seconds.
The log ends the day complete
Recovered transactions land in the same log as live ones — receipt, phone, amount, status — and become instantly usable for receipt-code verification on orders and invoices. Your statement and your Odoo agree again.
Install it before you need it
Requires the M-Pesa POS Payments app. Two new entries appear under Point of Sale → M-Pesa: Add Missed Transaction and Recover Missed Transaction — visible to M-Pesa Managers only.
Next time a customer says “but I paid” and the log disagrees: take their receipt number, fetch or record it, and hand them their goods. The transaction is now verifiable like any other.
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
When would I actually need this?
Can it create duplicates of payments I already have?
Who can use the recovery wizards?
Does a recovered payment work for receipt verification?
Does fetching from Safaricom need special access?
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 | 1985 |
| Technical Name |
aminitech_mpesa_recovery |
| 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