S2S MoMo (KES and GHS)

Initiate S2S

Authorization	Set to Bearer PUBLIC_KEY
Content-Type	Set value to application/json

The public key can be gotten from the 'Settings' page on your Startbutton dashboard.

Post a request to the URL below, where the base URL is determined by the environment you are in.

BaseUrls

PROD : https://api.startbutton.tech

DEV/ Staging: https://api-dev.startbutton.tech

Endpoint

POST {{baseurl}}/transaction/initialize/s2s/mobile_money

Here's a sample request below

Required parameters (KES)

{
    "provider": "mpesa",
    "phone": "0710000000",
    "email": "[e-mail]",
    "amount": 3000,
    "currency": "KES"
}

Optional parameters included (KES)

{
    "provider": "mpesa",
    "phone": "[phone]",
    "email": "[e-mail]",
    "amount": 3000,
    "currency": "KES",
    "reference": "de432cr4d34e"
}

Required parameters (GHS)

{
    "provider": "MTN",
    "phone": "0551234987",
    "amount": 300000,
    "currency": "GHS",
    "email": "[e-mail]"
}

We have 3 providers for GHS: - MTN- passed as "MTN" - AIRTEL passed as "ATL" - VODAFONE- passed as "VOD"

Optional parameters included (GHS)

{
    "provider": "MTN",
    "phone": "0551234987",
    "amount": 300000,
    "currency": "GHS",
    "reference": "de432cr4d34e",
    "email": "[e-mail]"
}

The amount should be in fractional units.

Here's a sample response

Success (GHS)

{
    "success": true,
    "message": "Charge attempted, requery to get status",
    "data": {
        "nextStep": "PIN",
        "reference": "610ae86889ee"
    }
}

Success (KES)

{
    "success": true,
    "message": "Charge attempted, requery to get status",
    "data": {
        "nextStep": "PIN",
        "reference": "42452be51db0"
    }
}

Failed

{
    "success": false,
    "message": "unknown provider"
}

The next step can either be OTP or PIN. If your customer is new to the service, they'll receive an OTP initially. Afterwards, for subsequent transactions, they'll be provided with a PIN.

When it is an OTP; you need to present the User with a screen to enter OTP and then call the endpoint below

OTP Verify

Endpoint

POST {{baseurl}}/transaction/initialize/s2s/mobile_money/otp-verify

Authorization	Set to Bearer PUBLIC_KEY

Here's a sample response

Verify OTP

{
  "reference": "610ae86889ee",
  "otp": "123456"
}

Here's a sample response

Success Response

{
    "status": true,
    "message": "Charge attempted",
    "data": {
        "status": "requery",
        "message": "Confirming payment"
    }
}

Failed Response

{
    "success": false,
    "message": "Invalid OTP",
    "data": null
}

However, if the next step is a PIN your users only need to enter their PIN on the prompt on their phone.