1. Introduction

1.1 Overview

Boost MFB provides a comprehensive payment platform for the Nigerian market, supporting collection (Pay In), disbursement (Pay Out), identity verification, and virtual account management. This document describes all available API endpoints for the Nigeria market.

1.2 Environment

Environment	Description
Sandbox	BoostMFB provide test key for API debugging.
Production	Register a free merchant account and generate keys via the merchant platform.

1.3 Request & Response

Both request and response data are formatted in JSON. All responses follow a standard structure:

Field	Description
code	Response code. A value other than '00' indicates an exception (service or business error). '00' means success.
msg	Description message
data	Business data. See individual API documentation for detailed fields.

⚠️ For transaction APIs, if code ≠ "00", you must query the final result via the corresponding query interface.

1.4 Transaction Amount

The payment amount in the API parameters is kobo, without decimals. For example, 100 NGN should be transmitted as 10000 (100 × 100).

1.5 Merchant Order Number

The merchant order number is custom-generated by the merchant. Only the following English half-width characters are supported: letters (a-z, A-Z), digits (0-9), hyphens (-), underscores (_), pipes (|), and asterisks (*). Chinese characters or full-width characters are not allowed. The merchant order number must be unique (it is recommended to use Snowflake algorithm or UUID to generate order numbers).

1.6 Transaction Result Notification

To ensure security, it is recommended to whitelist the platform IP addresses.
After receiving a notification, it is recommended to confirm the transaction result by calling the corresponding query interface.
Request Method: POST
Request Body: See the notification parameter documentation for each API.
Response Body: Return the string "success" to indicate successful notification. If not received, notifications will be resent.

Notification Retry Interval

Notifications are retried at the following intervals if not acknowledged: 5 min, 5 min, 10 min, 10 min, 30 min, 1 hour, 1 hour, 3 hours, 6 hours, 6 hours, 6 hours.

Notification Request Header

Field	Description
signature	Data signature. See the signature algorithm for details.

Notification Signature Algorithm

String signResult = RsaUtil.verifyWithSha256(bodyStr);
Use the platform RSA public key to verify the request body signature using the SHA256WithRSA algorithm.

1.7 IP Addresses

Environment	IP Address
Sandbox (Test)	120.79.228.164
Production	8.209.67.112

IMPORTANT: Always follow the API instructions strictly. Do not change the transaction result before receiving an explicit response from the payment system to prevent financial loss. The payment system's result is determined by the final transaction status.

1.1 Overview#

1.2 Environment#

1.3 Request & Response#

1.4 Transaction Amount#

1.5 Merchant Order Number#

1.6 Transaction Result Notification#

Notification Retry Interval#

Notification Request Header#

Notification Signature Algorithm#

1.7 IP Addresses#