Course Content
Building Your First Mpesa Integration
This topic focuses on guiding you through the process of building a functional Mpesa integration from scratch. You will learn how to set up a backend for handling API requests, generate secure access tokens for authentication, and implement an STK Push transaction to facilitate payments. By the end of this topic, you will have a working example of Mpesa integration.
0/3
Backend Setup with PHP/Node.js/Other Frameworks
Generating Access Tokens
06:32
Implementing an STK Push Transaction
12:18
C2B and B2C Integrations
In this topic, learners will explore the core concepts of integrating Mpesa's Customer-to-Business (C2B) and Business-to-Customer (B2C) payment functionalities. The lessons will cover configuring C2B payments to enable customers to pay businesses and using B2C for disbursing funds to customers. Additionally, the topic will explain how to implement real-time transaction status updates to ensure seamless payment tracking and reconciliation.
0/3
Configuring C2B (Customer to Business) Payments
Using B2C (Business to Customer) for Disbursements
Real-Time Transaction Status Updates
Testing and Debugging
This topic focuses on ensuring the reliability and correctness of Mpesa integrations by testing in the sandbox environment, debugging using logs and tools like Postman, and eventually transitioning to the production environment. By the end of this topic, learners will be equipped with practical knowledge of testing and debugging their integration effectively.
0/3
Testing Transactions in the Sandbox Environment
Using Logs and Postman for Debugging
Moving to Production
00:00
Security and Best Practices
This topic covers the critical aspects of securing your Mpesa integration by properly managing API keys and tokens, handling errors in a way that improves the user experience, and complying with Mpesa’s integration guidelines. Following these practices ensures that your integration is secure, reliable, and in line with best practices, minimizing the risk of fraud and ensuring smooth operations.
0/3
Securing Your API Keys and Tokens
Handling Errors Gracefully
Complying with Mpesa Integration Guidelines
Real-World Application
This topic explores how Mpesa can be seamlessly integrated into real-world applications, particularly e-commerce platforms. It covers integrating payment systems, customizing user experiences to enhance payment flows, and using analytics for business insights. By the end of this topic, learners will understand how to leverage Mpesa for creating smoother and more efficient payment processes, as well as tracking transactions for actionable insights.
0/3
Integrating Mpesa into an E-Commerce Platform
Customizing User Experiences with Mpesa Payments
Analytics and Reporting
Build a Payment Gateway with Mpesa
In this project, learners will apply the skills acquired throughout the course to build a functional payment gateway integrated with Mpesa. The project will walk through the entire process, from backend setup and API integration to handling transactions and user feedback. By the end of this topic, learners will have developed a working payment gateway and be ready to present their projects for review and feedback.
0/3
Step-by-Step Implementation of a Working Payment Gateway
Presenting Your Project for Feedback
Final Project Submission
Introduction to Mpesa Integration
Gain an understanding of Mpesa’s role in facilitating mobile payments. Learn about its features, real-world applications, and benefits in businesses. This module covers the prerequisites for starting your Mpesa integration journey.
0/2
Overview of Mpesa services and APIs
11:02
Requirements for Mpesa Integration
00:45
Setting Up The Environment
In this topic, you learned how to set up the environment for Mpesa integration. This includes registering on the Mpesa Daraja Portal, acquiring API credentials, and using tools like Postman and Ngrok for development and testing. You also set up a local server, configured callback URLs, and simulated transactions in the sandbox environment. Finally, you prepared for production by understanding the approval process and transitioning to live operations. These steps form the foundation for successfully integrating Mpesa APIs into your application.
0/4
Tools and platforms needed (Postman, Ngrok, etc.)
Registering for Mpesa Daraja API
Overview of sandbox and production environments
Tools, Registration, and Environments Quiz
Understanding Mpesa APIs
This topic provides an overview of the various Mpesa APIs available for integration. You will learn about the key API services that facilitate mobile money transactions, such as the STK Push, C2B, B2C, and Account Balance APIs. Understanding how each API works will help you design robust and efficient payment systems, and ensure seamless transactions between businesses and customers.
0/3
Mpesa API documentation walkthrough
Authentication: Consumer Key and Secret
Key API Endpoints: STK Push, C2B, B2C, Balance Inquiry
Mpesa Integration – Daraja API :Crash Course
Applying the skills acquired throughout the course, the video below will guide you to build a functional payment gateway integrated with Mpesa. The project will walk through the entire process, from backend setup and API integration to handling transactions and user feedback. By the end of this topic, you will have developed a working payment gateway and be ready to present your projects for review and feedback.
0/2
Using Node.Js
Using PHP
M-Pesa Integration MasterClass
About Lesson

This topic explains the difference between the Sandbox and Production environments in Mpesa API integration. The Sandbox is a testing environment where you can simulate transactions without involving real money, while the Production environment is used for live transactions. Learners will understand how to transition from testing to live deployment, including how to switch API credentials and what to expect in both environments.

 

  1. What is the Sandbox Environment?

    • Purpose:
      The Sandbox environment is a simulation platform provided by Mpesa for developers to test their integrations. It allows you to simulate transactions without involving real money, ensuring that the integration works correctly before going live.
    • Features:
      • Test payment requests (STK Push), transaction status, and other Mpesa features.
      • Use sandbox-specific API credentials (Consumer Key and Secret).
      • Use simulated phone numbers, shortcodes, and amounts for testing.
    • Environment URL:
      The Sandbox environment is available at: 
      https://sandbox.safaricom.co.ke
    • Testing Scenarios:
      • STK Push Simulation: You can simulate payment requests and responses.
      • C2B and B2C Transactions: Simulate customer-to-business and business-to-customer payments.
      • Transaction Status API: Verify the status of a transaction using simulated data.

  2. What is the Production Environment?

    • Purpose:
      The Production environment is used to process real transactions. After testing and ensuring everything works in the Sandbox environment, you will switch to Production for live operations.
    • Features:
      • Actual money transactions are processed.
      • You use live credentials provided by Mpesa after your application is approved.
      • You will need to configure the callback URL and handle actual payment requests and responses.
    • Environment URL:
      The Production environment URL is: 
      https://api.safaricom.co.ke
    • Live Transactions:
      • All transactions (e.g., payments, refunds) are real and involve actual money.
      • Your Consumer Key and Consumer Secret are changed from the Sandbox credentials to live credentials after approval.

  3. Difference Between Sandbox and Production Environments

    • Key Differences:
      Feature Sandbox Production
      Transactions Simulated transactions (no real money) Real money transactions
      API Credentials Sandbox credentials (for testing) Live credentials (after approval)
      Environment URL https://sandbox.safaricom.co.ke https://api.safaricom.co.ke
      Testing Scope Test API endpoints and flows Process real payments and data
      Callback URL Simulated response URLs Real callback URL for live responses
      Approval Process No approval required Application needs to be approved by Mpesa

  4. Transitioning from Sandbox to Production

    • Steps for Transitioning:
      1. After successfully testing in the Sandbox environment, submit your application for Production approval.
      2. Mpesa will review your integration, and if approved, you will receive live Consumer Key and Consumer Secret credentials.
      3. Replace your Sandbox credentials with live credentials in your application’s settings.
      4. Update your callback URL to reflect the live environment’s server.
      5. Test again in the Production environment using real transactions.
      6. Go live with your Mpesa integration!

Summary

In this topic, you learned about the Sandbox and Production environments for Mpesa integration. The Sandbox environment is used for testing, with simulated transactions and fake data, while the Production environment is where real transactions happen, involving actual money. You also learned about the transition process from the Sandbox to Production and the steps involved, such as obtaining live credentials and configuring real callbacks.

Previous
Next