> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/integrations/openg2p-m-pesa-integration.md).

# M-Pesa Integration

## Introduction

M-Pesa is a virtual banking service that allows users to participate in financial transactions using their SIM cards. Once a SIM card is entered into a mobile phone, SMS messages are used to send and receive money.

M-Pesa was first introduced in Kenya as an alternative to the traditional brick-and-mortar set up. Being a digital tool, it is widely popular in over seven African nations as it speaks to financial inclusivity for marginalized and far-flung groups.

OpenG2P, in it's interoperable and modular approach, is able to easily integrate with M-Pesa to demonstrate the ease of access for its benefit delivery mechanism. The integration is done using an *M-Pesa simulator*. Here is the link to the simulator <https://africastalking.com/>

More information on M-Pesa can be found here <https://www.investopedia.com/terms/m/mpesa.asp>

## Integration

An M-Pesa simulator is used for demonstration. It is a direct integration that doesn't involve a payment switch like Mojaloop.

How does the integration work? The M-Pesa account is mapped to the person's phone number. When payment is initiated from the OpenG2P system, the individual dials the USSD code from their phone, enters the mobile number to which their M-Pesa account is linked, and then checks their balance to see if they have received any money or pays their dues to a vendor who may also have an M-Pesa account.

This diagram here encapsulates the flow and components for an M-Pesa integration. It is assumed that MOSIP is the ID issuer here, and that the M-Pesa account is created at the time of issuance of ID, and is mapped to the person's phone number instantly.

<figure><img src="https://github.com/OpenG2P/openg2p-documentation/blob/1.2.1/platform/.gitbook/assets/mpesa.jpg" alt=""><figcaption><p>Flow to demonstrate M-Pesa integration with OpenG2P where it begins with MOSIP ID issuance</p></figcaption></figure>

## Deployment

Instructions to deploy M-Pesa integration:

1. Download the kube-config file from the rancher of a particular environment
2. Set kube-config to that particular environment in your local dev environment
3. Clone this repo into your local environment - <https://github.com/OpenG2P/openg2p-deployment/tree/main/kubernetes/mpesa>
4. Edit the `config.yaml` file with appropriate database location, username and password
5. Edit the `virtualService.yaml` file with appropriate hostname.
6. Run the below commands:

{% code fullWidth="false" %}

```
kubectl create ns mpesa
kubectl -n mpesa apply -f config.yaml
kubectl -n mpesa apply -f deployment.yaml
kubectl -n mpesa apply -f service.yaml
kubectl -n mpesa apply -f virtualservice.yaml
```

{% endcode %}

## Demonstration

Here is a [link to the slides](https://docs.google.com/presentation/d/1CCk1JkUqnTcEbJeHk5au28ZLHd0SjAGYIHROuvSDkGU/edit?usp=sharing) which demonstrates payments to the M-Pesa simulator.

## Source code

Click [here](https://github.com/Abhishek-Wagh/openg2p-program/tree/15.0-develop/g2p_payment_simple_mpesa) to go to the program repository, under which all the M-Pesa functions and code can be found [here](https://github.com/OpenG2P/openg2p-program/tree/15.0-develop/g2p_payment_simple_mpesa).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openg2p.org/1.3/integrations/openg2p-m-pesa-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.