v 16.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 376
Technical Name payment_mtnmomo
LicenseOPL-1
Websitehttps://youtube.com/shorts/z7wrzcbakXM?si=OOTIwOK6M9X3RgVL
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 376
Technical Name payment_mtnmomo
LicenseOPL-1
Websitehttps://youtube.com/shorts/z7wrzcbakXM?si=OOTIwOK6M9X3RgVL
Banner
Supported Editions:
Community
Enterprise

Official MOMO Onboarding

To get the required MOMO credientials, follow these steps:

  1. Apply for a MOMO Live Account:

    Go to https://momodeveloper.mtn.com/golive

  2. Select your operating country:

    This will determine the acceptable payment environment

  3. Choose Product Set:

    Ensure to check, at least the CollectionsProduct. Only the Collections Product is needed for this integration.

  4. Complete the Registration Process:

    Ensure you complete the rest of the registeration.

  5. Create an API User Credientials:

    After, a successful acceptance by MOMO, you can proceed proceed to create a user credientials or Contact us for a free 30 minutes setup consultation

MOMO Payment Provider Setup

To enable MOMO payments in Odoo, follow these steps:

  1. Navigate to the Payment Providers Configuration:

    Go to Invoicing/Accounting >> Configuration >> Payment Providers

  2. Configure MOMO Provider Settings:

    Click on MOMO and set the following:

    • Secret Key: Enter your MOMO product secret key. This is required for both test and live environments.

    • Provider State:

      • Test: Use this mode for testing purposes without making real payments. It requires only the secret key, and other credentials will be automatically generated.

      • Enabled: Use this mode for real transactions. It requires a valid secret key, API User UUID, and API Primary Key.

      • Disabled: This deactivates the provider and hides it from the payment portal.

    • Credentials:

      • Secret Key: Enter a valid MOMO product secret key.

      • API User UUID (Live Mode Only): Enter the API User UUID assigned to your MOMO live account.

      • API User Key (Live Mode Only): Enter the API User Key assigned to your MOMO live account.

  3. Set the Payment Journal:

    Go to the Configuration tab of the MOMO provider settings and select or create a payment journal for MOMO transactions.

  4. [Optional] Set Status Messages:

    Customize the messages displayed to clients for each payment status from the Messages tab.

Customer Journey

Ecommerce Site

  1. Checkout: Customers complete their shopping and proceed to checkout.

  2. Payment Selection: Customers choose MTN MOMO as their payment method.

  3. MOMO Account Information: Customers enter their MOMO account details.

  4. Payment Confirmation: Customers click on "Pay Now."

  5. Push Notification: Customers receive a push notification on their MOMO app to approve the transaction.

  6. Payment Waiting Screen: Customers are redirected to a waiting screen while the transaction is processed.

  7. Transaction Approval/Rejection: Customers approve or reject the transaction on their MOMO app.

  8. Transaction Result Screen: Customers are redirected to a screen indicating successful or failed payment.

  1. Link Access: Customers receive a link to pay for an order.

  2. Payment Selection: Customers choose MTN MOMO as their payment method.

  3. MOMO Account Information: Customers enter their MOMO account details.

  4. Payment Confirmation: Customers click on "Pay Now."

  5. Push Notification: Customers receive a push notification on their MOMO app to approve the transaction.

  6. Payment Waiting Screen: Customers are redirected to a waiting screen while the transaction is processed.

  7. Transaction Approval/Rejection: Customers approve or reject the transaction on their MOMO app.

  8. Transaction Result Screen: Customers are redirected to a screen indicating successful or failed payment.

Implementation Details

  1. Payment Initiation: Upon clicking "Pay Now," an RTP API call is made.

  2. Push Notification: MOMO triggers a push notification to the customer's phone.

  3. Payment Waiting Screen: Odoo redirects the customer to a waiting screen.

  4. Payment Status Retrieval: Odoo repeatedly checks the payment status every 3 seconds until a status change occurs or 20 retries have been made.

  5. Transaction Recording: Upon receiving a successful or failed payment response, Odoo records the transaction details for reconciliation purposes.

  6. Transaction Timeout: If no status change occurs after 20 retries, the transaction is aborted.

Repository

https://github.com/EwetoyeIbrahim/momo-odoo.git
CONTACT FOR YOUR ERP NEEDS
(i.ewetoye@gmail.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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.
There are no ratings yet!
Hello
by
joelhenribig89@gmail.com
on 12/13/23, 3:52 PM

I need the verson 17 of the module and also customization to make it available in POS 



Hello
by
joelhenribig89@gmail.com
on 11/18/23, 9:52 AM

I need version 17 for this module. And I want to know whether it's working  in my country 

and also in odoo POS

Re: Hello
by
Ewetoye Ibrahim
on 11/18/23, 9:55 PM Author
I need version 17 for this module.

It should be available by January 2024, as I am gradually upgrading all my paid modules.


I want to know whether it's working  in my country

As long as momo is available in your country


and also in odoo POS

Wow, that is a great idea, but I don't think there is more demand for that yet. You can contact me for a custom implementation or wait for some time.