Skip to main content

Introduction

Cash-in operations allow distributors to credit wallets in exchange for physical cash. Distributors can cash-in to two types of destinations:
  • Individual wallets — identified by the end user’s phone number
  • Merchant wallets — identified by the merchant’s short code

Prerequisites

  • An active API key with Perform Operations permission
  • Sufficient distributor balance to cover the cash-in amount
  • End user’s mobile phone number or merchant’s short code
Cash-in operations follow the maker-checker pattern. API requests create pending operations that require approval before execution.

Cash-In to Individual Wallet

Send a cash-in with the phoneTo field to credit an individual wallet.

Request Body

Code Examples

Cash-In to Merchant Wallet

Send a cash-in with the merchantToShortCode field to credit a merchant wallet. The merchant is identified by their short code (e.g., 100000).

Request Body

Code Examples

You must provide either phoneTo or merchantToShortCode, but not both. The API will return a validation error if both fields are provided or if neither is provided.

Response

Success Response (200 OK)

Parameters

Endpoint

Request Headers

Fields

string
required
Type of operation. Must be "cash-in" for cash-in operations.
string
required
Amount to credit to the destination wallet. Must be a valid decimal string (e.g., “1000.00”).
string
End user’s mobile phone number in international format (e.g., “+234 8123456781”). Required when cashing in to an individual wallet.
string
Merchant’s short code number (e.g., “100000”). Required when cashing in to a merchant wallet.
string
Optional reference note or description (e.g., “Cash deposit - Receipt #1234”).

Next Steps

Cash-Out via API

Learn how to process cash-out operations

API Reference

Full API endpoint documentation