Payout

When performing a payout, the customer initiates a payout and then just waits for the funds to be credited to their account. The customer themself doesn't participate in the payout processing procedure.

Countries and regions Burkina Faso, Benin, Democratic Republic of the Congo, The Congo, Côte d'Ivoire, Cameroon, Ghana, Guinea, Kenya, Mali, Malawi, Rwanda, Senegal, Togo, Tanzania, Uganda, Zambia
Payment currencies CDF, GHS, GNF, KES, MWK, RWF, TZS, UGX, XAF, XOF, ZMW
Payment amount limits Contact your key account manager at Monetix for details. Also you can check the payment amount limits in your project by using Dashboard.
Payment processing time Contact your key account manager at Monetix for details.
Currency conversion On the Monetix side
Refund
Onboarding and access fee Contact your key account manager at Monetix for details.
Special considerations
  • The amounts for the GNF, RWF, UGX, XAF, XOF currency must be specified in major currency units (without any fractional part) according to the ISO-4217 alpha-3 standard.

    For example, if the customer initiates a 1000 GNF purchase in your system, you are required to submit the 1000 as the payment amount in your purchase request.

    You can check the number of digits for minor currency units for any currency in Currency codes.

  • For the XOF currency, in some cases the payout amount must be a multiple of 5.
  • For the GNF currency, in some cases the payout amount must be a multiple of 1000.

Operations support

Interfaces
Payment Page Gate Dashboard
Payout

You can check the payment amount limits in your project by using Dashboard. To check your payment amount limits, go to Dashboard, select the Projects section, and then click the Payment methods tab.

The following sections provide more information about the payment processing flow and the analysis of completed payments.

Supported mobile network operators

The table below lists the mobile network operators available for performing payout with the Mobile Commerce in Africa payment method.

Table 1. Supported mobile network operators
Mobile network operator ID Countries Currencies
Africell AFRICELL Democratic Republic of the Congo CDF
Airtel AIRTEL Democratic Republic of the Congo, Zambia, Kenya, Rwanda, Tanzania, Uganda CDF, KES, RWF, TZS, UGX, ZMW
AirtelTigo AIRTELTIGO Ghana GHS
Equitel EQUITEL Kenya KES
Eumobile EUMOBILE Cameroon XAF
Expresso EXPRESSO Senegal XOF
Freemoney FREEMONEY Senegal XOF
HaloPesa HALOPESA Tanzania TZS
Malitel Malitel Mali XOF
Moov MOOV Benin, Burkina Faso, Côte d'Ivoire, Mali, Togo XOF
MTN MTN Benin, Ghana, Guinea, Zambia, Cameroon, Côte d'Ivoire, Rwanda, Uganda GHS, GNF, RWF,UGX, XAF, XOF, ZMW
M-Pesa MPESA Kenya KES
Orange ORANGE Burkina Faso, Guinea, Cameroon, Democratic Republic of the Congo, Côte d'Ivoire, Mali, Senegal CDF, GNF, XAF, XOF
Telecel TELECEL Ghana GHS
Telkom Kenya TELKOM Kenya KES
Tmoney TMONEY Togo XOF
TNM TNM Malawi MWK
Tkash TKASH Kenya KES
Vodacom VODACOM Democratic Republic of the Congo, Tanzania CDF, TZS
Vodafone VODAFONE Tanzania TZS
Wave WAVE Côte d'Ivoire, Senegal XOF
Yas YAS Kenya, Tanzania KES, TZS
Yoomee YOOMEE Cameroon XAF
Zamtel ZAMTEL Zambia ZMW

Note that the list of mobile network operators in the table is provided for informational purposes only. To get the current list of mobile network operators, send a request to the payment platform as described below:

HTTP request method POST
Request body format JSON
API endpoint /v2/info/mobile/payout/list
Full API endpoint specification /v2/info/mobile/{operation_type}/list
Table 2. Parameters required in the request for the list of available mobile network operators
Object Parameter Description
general

project_id
integer strictly required

Project ID you obtained when integrating with Monetix.

signature
string strictly required

Signature created after you specify all the required parameters. For more information about, signature generation, see Signature generation and verification.

Here is an example of the data from the request for the list of available mobile network operators:

Figure 1. Example of the data from the request for the list of available mobile network operators
{
	"general": {
		"project_id": 1234,
		"signature": "K6jllym+PtObocZtr345st...=="
	}
}

Payout by using Gate

General information

To perform a payout by using Gate with the Mobile Commerce in Africa payment method:

  1. Send a request with all the required parameters and signature to the Monetix URL.
  2. Accept the callback with the payout result from the payment platform.

The following picture provides the details of the payout processing flow in the Mobile Commerce in Africa payment method.

Figure 2. Payout processing flow when performing a payout by using Gate
  1. The customer initiates a payout in your system.
  2. Your system sends the payout request to the Monetix payment platform.
  3. The payment platform sends you a response in which it acknowledges your request and provides the request validation result. (For more information about the response format, see Response structure.)
  4. The payment platform processes the request and forwards it to the provider service.
  5. The provider service informs the payment platform about the payout result.
  6. The payment platform sends a callback with the payout result to your system.
  7. Your system sends the payout result to the customer.

Request

This section provides the instructions on how to build the request for payout with the Mobile Commerce in Africa payment method.

HTTP request method POST
Request body format JSON
API endpoint /v2/payment/mobile/payout
Table 3. Basic parameters of a payout request

strictly required—the parameter must be in the initial request.

✱—the parameter may not be required in some cases. Contact your account manager at Monetix for details.

ObjectParameterDescription

general
object
strictly required

project_id
integer
strictly required

Project ID you obtained from Monetix when integrating.

Example: 1234

payment_id
string
strictly required

Payment ID unique within your project.

Example: payment_47

signature
string
strictly required

Signature created after you've specified all the request parameters. For more information about signature generation, see Signature generation and verification.

customer
object
strictly required

id
string
strictly required

Unique ID of the customer within your project.

Example: customer_123

ip_address
string
strictly required

IP address of the customer's device.

Example: 198.51.100.47

first_name
string
strictly required

Customer's first name.

Example: John

last_name
string
strictly required

Customer's last name.

Example: Doe

email
string
strictly required

Customer's email.

Example: johndoe@example.com

account
object
strictly required

number
string
strictly required

Customer's mobile phone number for receiving payout. The phone number must include a country code and must be specified without punctuation or special characters.

Example: 233123456789

service_provider
string
strictly required

ID of the customer's mobile network operator. For the information on how to get the list of supported mobile network operators IDs, see Supported mobile network operators.

Example: MTN

payment
object
strictly required

currency
string
strictly required

Code of the payment currency in the ISO-4217 alpha-3 format.

Example: GHS

amount
integer
strictly required

Payment amount in minor currency units without any decimal point or comma except for the cases when the currency doesn't have any minor currency units.

If the currency doesn't have any minor units (i.e. the number of digits for minor currency units is zero), set this parameter to the amount in the major currency units. To check whether the currency has any minor units, see Currency codes.

Example: 1000.00 GHS must be sent as 100000

You can also add any other optional parameters to the payout request, if necessary. For the list of all the parameters available in Gate, see API Reference.

Here is an example of the data from a request to initiate a payout with the Mobile Commerce in Africa payment method:

Figure 3. Example of the payout request body
{
    "general": {
        "project_id": 1234,
        "payment_id": "payment_47",
        "signature": "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y19vySO/RLUkDJrOcZzUCwX6R/ekpZhkIQg=="
    },
    "customer": {
        "id": "customer_123",
        "ip_address": "198.51.100.47",
        "first_name": "John",
        "last_name": "Doe",
        "email": "johndoe@example.com"
    },
    "account": {
        "number": "233123456789",
        "service_provider": "MTN"
    },
    "payment": {
        "currency": "GHS",
        "amount": 100000
    }
}

Callback

In the Mobile Commerce in Africa payment method, the payment platform returns the payout result in a callback. For the information about the callback structure, see Callbacks in Gate.

In this payment method, callbacks also have the account object with the number and type parameters containing information about the customer's phone number and their mobile network operator.

The following is an example of a callback body with the information about a successfully completed payout.

Figure 4. Example of the data from a successful payout callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "payout",
        "status": "success",
        "date": "2024-12-07T19:08:45+0000",
        "method": "mobile",
        "sum": {
            "amount": 100000,
            "currency": "GHS"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 47,
        "type": "payout",
        "status": "success",
        "date": "2024-12-07T19:08:45+0000",
        "created_date": "2024-12-07T19:08:05+0000",
        "request_id": "1a23456bc7890de",
        "sum_initial": {
            "amount": 100000,
            "currency": "GHS"
        },
        "sum_converted": {
            "amount": 100000,
            "currency": "GHS"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "account": {
        "number": "233123456789",
        "type": "MTN"
    },
    "signature": "U7HQO7ToISZhMPKdM4XrUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

The following is an example of a callback for a declined payout.

Figure 5. Example of the data from a declined payout callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "payout",
        "status": "decline",
        "date": "2024-12-07T19:08:45+0000",
        "method": "mobile",
        "sum": {
            "amount": 100000,
            "currency": "GHS"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 47,
        "type": "payout",
        "status": "decline",
        "date": "2024-12-07T19:08:45+0000",
        "created_date": "2024-12-07T19:08:05+0000",
        "request_id": "1a23456bc7890de",
        "sum_initial": {
            "amount": 100000,
            "currency": "GHS"
        },
        "sum_converted": {
            "amount": 100000,
            "currency": "GHS"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "account": {
        "number": "233123456789",
        "type": "MTN"
    },
    "signature": "U7HQO7ToISZhMPKdM4XrUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

Payout by using Dashboard

To make a payout through Dashboard, the merchant sends a request and receives a notification with the request processing result. There are two ways to initiate payouts through Dashboard:
  • single payout—you specify the currency and amount for a payout available for this method and fill in all the fields required for the selected payment method on the Dashboard pages.
  • as a part of a mass payment—all the parameters are specified in a CSV file. Refer to the Payouts by using Gate section for the parameters required by your payment method.

Information about completed payouts is available for viewing in the Payments and Manual Payments sections of Dashboard.

For more information about payout processing by using Dashboard, see Performing payouts.