Workflow and How It Works

Before accepting cash payments, a merchant must first create an offline product

1. The merchant creates products for customers using the Monnify dashboard or API
2. The customer visits any Moniepoint business owner/Agent to pay for a listed product
3. The Agent validates the customer by entering their ID on the POS or web app
4. After verification, the agent either sees the payment amount (for fixed products) or the customer specifies the amount (otherwise)
5. The Moniepoint business collects the cash and processes the payment.
6. If the customer requires a token after payment, the Moniepoint business generates and issues a receipt or value token; otherwise, only a receipt is issued
7. The merchant is notified of the transaction

Offline Collection Products

An offline product is a commodity of interest to the customer that they are willing to pay for. Monnify supports four categories of offline products:

This product has a fixed amount that a customer must pay for a service or product. Merchants must state the amount on the Monnify platform. For fixed product types, the amount must be stated by merchants on the Monnify platform. An example is a monthly fixed contribution.

This product has a flexible amount. The merchant does not specify the amount, and the customer specifies how much they want to pay at the Moniepoint Business Owner’s location. Example: variable amount for betting.
For variable product type, you do not specify the amount as the customer specifies how much they want to pay at the Moniepoint Business Owner’s location where collection is done.

This requires an invoice to be created for every payment. Unlike other types, the invoice does not become fully active upon creation on Monnify. To activate it, the Monnify Create an Invoice endpoint must be called, specifying "CASH" as the payment method. The amount to be paid is then tied to the generated invoice ID.

This product type allows merchants to designate a custom payment amount for each user. Merchants can dynamically adjust the product price during the payer verification stage by including the desired amount in their successful response to Monnify.

Payer Verification Endpoint (Mandatory)

1{
2    "productCode": "P10101",
3    "paymentRecipientId": "LAHRAY101"
4}

When user is verified successfully;

1{
2    "responseCode": "00",
3    "responseMessage": "User details retrieved successfully.",
4    "paymentRecipientId": "21220002312312",
5    "paymentRecipientDescription": "DAMILARE OGUNNAIKE SAMUEL"
6}

1{
2    "responseCode": "00",
3    "amount": 2000,
4    "responseMessage": "User details retrieved successfully.",
5    "paymentRecipientId": "21220002312312",
6    "paymentRecipientDescription": "DAMILARE OGUNNAIKE SAMUEL"
7}

When user does not exist;

1{
2    "responseCode": "02",
3    "responseMessage": "User does not exist."
4}

Payment Request Endpoint (Optional)

1{
2    "amount": 200,
3    "transactionReference": "MNFY|66|20210825115615|000002",
4    "productCode": "{productCode}",
5    "paymentRecipientId": "{paymentRecipientId}"
6}

Success response;

1{
2    "responseCode": "00",
3    "productCode": "121221212",
4    "paymentRecipientId":"{paymentRecipientId}}"
5    "transactionReference":"MNFY|66|20210825115615|000002",
6    "paymentToken": "{paymentToken}"
7}

Failed Response;

1{
2    "responseCode": "01",
3    "responseMessage": "Reason for failed response"
4}

Payment Requery Endpoint (Optional)

1GET {{merchantPaymentRequeryUrl}}?transactionReference=MNFY%7C44%7C20220407112123%7C000684

For a successful response;

1{
2    "responseCode": "00",
3    "productCode": "121221212",
4    "paymentRecipientId":"{paymentRecipientId}}"
5    "transactionReference":"MNFY|66|20210825115615|000002",
6    "paymentToken": "{paymentToken}"
7}

For a failed response

1{
2    "responseCode": "01",
3    "responseMessage": "Reason for failed response"
4}