M-Pesa eCommerce & Portal Payments (STK Push)
by AminiTech Solutions https://aminitechsolutions.com$ 79.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• eCommerce (website_sale) • Discuss (mail) • Website (website) |
| Lines of code | 1448 |
| Technical Name |
aminitech_mpesa_website |
| License | OPL-1 |
| Website | https://aminitechsolutions.com |
| Versions | 18.0 19.0 |
M-Pesa eCommerce & Portal Payments
M-Pesa on your website checkout — the way Odoo does payments. A Stripe-style payment provider that sends the STK Push to your customerâs phone, listens for the money in real time, and confirms the order the second Safaricom does.
Ways a customer can finish paying — STK Push to their phone, verify a payment they already made by receipt code, or manual Paybill with live listening.
Payment provider, configured like Stripe or Flutterwave — and with the Shared Configuration Bridge it reuses the credentials your POS already has.
Manual confirmations. Safaricomâs callback confirms the order, sets the transaction to completed and logs the receipt — hands-free.
From cart to confirmed â all inside your website
Real screens from the live demo store. No mockups, no renders.
A pay page your customers already know
Green Lipa na M-Pesa header, the exact amount, their saved phone number pre-filled. One tap sends the PIN prompt to their phone — and the page is already listening for the payment in the background, whichever way it arrives.
M-Pesa where your customers expect it
A first-class Odoo payment provider — M-Pesa appears on the checkout payment step, on customer-portal invoices and on payment links, exactly like Stripe or PayPal would. Publish it and every storefront visitor can pay with the money they actually carry.
Daraja credentials on one tab — or reused from your POS
Consumer Key, Secret, Passkey, Paybill/Till and storefront display options on a single provider tab, with a built-in Safaricom setup guide. Already running our POS app? The Shared Configuration Bridge links the provider to your existing M-Pesa configuration — credentials entered once, synced forever.
Every shilling in one sliceable log
Website payments land in the same M-Pesa transaction log as your POS and invoice payments — date, phone, amount, receipt, status. Filter by day, group by channel, pivot for totals. Reconciliation stops being a spreadsheet.
From install to first online payment in one afternoon
Install the app — the M-Pesa STK Push provider appears under Configuration → Payment Providers, created disabled. Enter your Daraja credentials (or pick your existing M-Pesa Configuration if the bridge is active) and set the Callback Base URL to your domain.
Flip the provider to Enabled (start in Test Mode with Safaricomâs sandbox if you like), publish it, and M-Pesa shows on your checkout. Register your C2B callback URLs once and even direct Paybill payments confirm themselves.
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
Do I need the POS app for this to work?
Where does M-Pesa appear once enabled?
What if the customer already paid via Paybill before clicking Pay?
Can I test without real money?
Which Safaricom products does it use?
Does it support multiple websites or companies?
Talk to us today
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• eCommerce (website_sale) • Discuss (mail) • Website (website) |
| Lines of code | 1448 |
| Technical Name |
aminitech_mpesa_website |
| 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