README

This Laravel package provides convenient methods for integrating Mpesa Daraja API's functionalities into your Laravel application. The package will allow using more than one shortcodes. It also includes the recent Tax Remmitance and Bill Manager APIs.

Installation

You can install the package via composer:

composer require akika/laravel-mpesa-multivendor

After installing the package, publish the configuration file using the following command:

php artisan mpesa-multivendor:install

This will generate a mpesa.php file in your config directory where you can set your Mpesa credentials and other configuration options.

.env file Setup

Add the following configurations into the .env file

MPESA_ENV=
MPESA_DEBUG_MODE=

The value is either production or sandbox

NOTE: The mpesa.php config file sets the default MPESA_ENV value to sandbox. This will always load sandbox urls.

Function Responses

All responses, except the token generation response, conform to the responses documented on the daraja portal.

Usage

Initializing Mpesa

use Akika\LaravelMpesaMultivendor\Mpesa;

$mpesa = new Mpesa($mpesaShortCode, $consumerKey, $consumerSecret, $apiUsername, $apiPassword, $passKey = null);

$mpesaShortcode: The shortcode to use for the current operation
$consumerKey: Obtained from Daraja portal
$consumerSecret: Obtained from Daraja portal
$apiUsername: Mpesa portal API user's username
$apiPassword: Mpesa portal API user's password
$passKey: Optional field used for C2B transactions

Important Urls

Daraja utilizes the two main urls for callbacks. Timeout Url and Result Url. The two urls will also be used in this package as follows:

$resultUrl : Endpoint to send the results in case of success
$timeoutUrl : Endpoint to send the results in case of operations timeout

Fetching Token

You can fetch the token required for Mpesa API calls as follows:

$token = $mpesa->getToken();

Getting Account Balance

You can fetch mpesa account balance as follows:

$balance = $mpesa->getBalance($resultUrl, $timeoutUrl);

C2B Transactions

Registering URLs for C2B Transactions

You can register validation and confirmation URLs for C2B transactions:

$response = $mpesa->c2bRegisterUrl($confirmationUrl, $validationUrl);

Simulating C2B Transactions

You can simulate payment requests from clients:

$response = $mpesa->c2bSimulate($amount, $phoneNumber, $billRefNumber, $commandID);

$commandID is either CustomerPayBillOnline or CustomerBuyGoodsOnline and if not set, the package will assume CustomerPayBillOnline

Initiating STK Push

You can initiate online payment on behalf of a customer:

$response = $mpesa->stkPush($accountNumber, $phoneNumber, $amount, $callbackUrl, $transactionDesc);

$transactionDesc can be null

Querying STK Push Status

You can query the result of a STK Push transaction:

$response = $mpesa->stkPushStatus($checkoutRequestID);

Reversing Transactions

You can reverse a C2B M-Pesa transaction:

$response = $mpesa->reverse($transactionId, $amount, $receiverShortCode, $remarks, $resultUrl, $timeoutUrl, $ocassion);

$ocassion is an optional field

Business to Customer (B2C) Transactions

You can perform Business to Customer transactions:

$response = $mpesa->b2cTransaction($commandID, $msisdn, $amount, $remarks, $resultUrl, $timeoutUrl, $ocassion);

$ocassion is an optional field.

B2C Topup

This API enables you to load funds to a B2C shortcode directly for disbursement. The transaction moves money from your MMF/Working account to the recipient’s utility account.

$response = $mpesa->b2cTopup($accountReference, $receiverShortCode, $amount, $resultUrl, $timeoutUrl, $remarks);

$accountReference: A unique (system generated) identifier for the transaction.
$receiverShortCode: The shortcode to which money will be moved
$amount: The transaction amount.
$remarks: Any additional information to be associated with the transaction.

Business to Business (B2B) Transactions

B2B Paybill

You can perform Business to Business transactions:

$response = $mpesa->b2bPaybill($destShortcode, $amount, $remarks, $accountNumber, $resultUrl, $timeoutUrl, $requester = null);

$destShortcode: This is the party receiving the money.
$accountNumber: The account number to be associated with the payment. Up to 13 characters.
$requester is an optional field.

B2B Buy Goods

This api accepts variables as provided in section B2B Paybill above.

$response = $mpesa->b2bBuyGoods($destShortcode, $amount, $remarks, $accountNumber, $resultUrl, $timeoutUrl, $requester = null);

B2B Express Checkout

$response = $mpesa->b2bExpressCheckout($destShortcode, $partnerName, $amount, $paymentReference, $callbackUrl, $requestRefID);

$destShortcode: This is the party receiving the money.
$partnerName: This is the organization Friendly name used by the vendor as known by the Merchant.
$paymentReference: This is a reference to the payment being made. This will appear in the text for easy reference by the merchant. e.g. Order ID
$requestRefID: This is an auto-genarated reference ID generated by your system.

QR Code Generation

You can generate QR codes for making payments:

$response = $mpesa->dynamicQR($merchantName, $refNo, $trxCode, $cpi, $size, $amount = null);

$amount is an optional field

Bill Manager

You can optin to the bill manager service and send invoices:

$response = $mpesa->billManagerOptin($email, $phoneNumber, $sendReminders, $logoUrl, $callbackUrl);

$response = $mpesa->sendInvoice($reference, $billedTo, $phoneNumber, $billingPeriod, $invoiceName, $dueDate, $amount, $items);

$sendReminders is a boolean field. Allows true or false (1 or 0)

Tax Remittance

You can remit tax to the government:

$response = $mpesa->taxRemittance($amount, $receiverShortCode, $accountReference, $remarks, $resultUrl, $timeoutUrl);

Mpesa Ratiba

The Standing Order APIs enable teams to integrate with the standing order solution by initiating a request to create a standing order on the customer profile.

$response = $mpesa->ratiba($name, $startDate, $endDate, $transactionType, $type, $amount, $msisdn, $callbackUrl, $accountReference, $transactionDesc, $frequency)

$name: Name of standing order that must be unique for each customer.
$startDate: The date you wish for the standing order to start executing
$endDate: The date you wish for the standing order to stop executing
$transactionType: This is the transaction type that is used to identify the transaction when sending the request to M-PESA. Either till or paybill
$type: This is the transaction type that is used to identify the transaction when sending the request to M-PESA.
$amount: This is the money that the customer pays to the Shortcode.
$phoneNumber: The phone number sending money. The parameter expected is a Valid Safaricom Mobile Number that is M-PESA registered in the format 2547XXXXXXXX
$callbackUrl: This is the endpoint to which the results will be sent.
$accountReference: This is a unique identifier for the transaction and is generated by the system. It has a maximum limit of 13 characters.
$transactionDesc: This is any additional information/comment that can be sent along with the request from your system. Maximum of 13 Characters
$frequency: The frequency of the standing order (one-off, daily, weekly, monthly, bi-monthly, quarterly, half-year, annually)

Mpesa Transaction History

The following API takes in the start and and end dates and returns the transactions between that period.

$response = $mpesa->mpesaTransactionsHistory($startDate, $endDate, $offset = 0);

Successful Response

{
    "ResponseRefID": "8bab-42cc-bb85-5056a6c01e6915928124",
    "ResponseCode": "1000",
    "ResponseMessage": "Success",
    "Response": [
        [
            {
                "transactionId": "XXXXXXXXX",
                "trxDate": "2025-01-24T10:56:11+03:00",
                "msisdn": 2547XXXXXXXX,
                "sender": "MPESA",
                "transactiontype": "c2b-buy-goods-debit",
                "billreference": "",
                "amount": "2697.0",
                "organizationname": "VENDOR"
            }
        ]
    ]
}

API Response Body

$response has the following as a json object

{
    "OriginatorConversationID": "5118-111210482-1",
    "ConversationID": "AG_20230420_2010759fd5662ef6d054",
    "ResponseCode": "0",
    "ResponseDescription": "Accept the service request successfully."
}

Succssful result body

A successful result body has the following structure

{
 "Result":
 {
   "ResultType": "0",
   "ResultCode":"0",
   "ResultDesc": "The service request is processed successfully",
   "OriginatorConversationID":"626f6ddf-ab37-4650-b882-b1de92ec9aa4",
   "ConversationID":"12345677dfdf89099B3",
   "TransactionID":"QKA81LK5CY",
   "ResultParameters":
     {
       "ResultParameter":
          [{
           "Key":"DebitAccountBalance",
           "Value":"{Amount={CurrencyCode=KES, MinimumAmount=618683, BasicAmount=6186.83}}"
          },
          {
          "Key":"Amount",
           "Value":"190.00"
          },
           {
          "Key":"DebitPartyAffectedAccountBalance",
           "Value":"Working Account|KES|346568.83|6186.83|340382.00|0.00"
          },
           {
          "Key":"TransCompletedTime",
           "Value":"20221110110717"
          },
           {
          "Key":"DebitPartyCharges",
           "Value":""
          },
           {
          "Key":"ReceiverPartyPublicName",
           "Value":000000– Biller Companty
          },
          {
          "Key":"Currency",
           "Value":"KES"
          },
          {
           "Key":"InitiatorAccountCurrentBalance",
           "Value":"{Amount={CurrencyCode=KES, MinimumAmount=618683, BasicAmount=6186.83}}"
          }]
       },
     "ReferenceData":
       {
        "ReferenceItem":[
           {"Key":"BillReferenceNumber", "Value":"19008"},
           {"Key":"QueueTimeoutURL", "Value":"https://mydomain.com/b2b/businessbuygoods/queue/"}
         ]
      }
 }
}

Unsuccessful reusult body

An unsuccessful result body has the following structure

{
 "Result":
 {
   "ResultType":0,
   "ResultCode":2001,
   "ResultDesc":"The initiator information is invalid.",
   "OriginatorConversationID":"12337-23509183-5",
   "ConversationID":"AG_20200120_0000657265d5fa9ae5c0",
   "TransactionID":"OAK0000000",
   "ResultParameters":{
     "ResultParameter":{
        "Key":"BillReferenceNumber",
        "Value":12323333
      }
   },
   "ReferenceData":{
     "ReferenceItem":[
      {
        "Key":"BillReferenceNumber",
        "Value":12323333
      },
      {
        "Key":"QueueTimeoutURL",
        "Value":"https://internalapi.safaricom.co.ke/mpesa/abresults/v1/submit"
      }
      {
        "Key":"Occassion"
      }
     ]
    }
 }
}

License

The Laravel Mpesa package is open-sourced software licensed under the MIT license. See the LICENSE file for details.

akika / laravel-mpesa-multivendor

Maintainers

Details