Authorizations
Bearer HTTP authentication specified with the header Authorization: Bearer <access_token>
Headers
This header is used to uniquely identify a logical request, ensuring that it is not processed more than once during retries.
64
Specifies which version of the Monime API will handle this request.
caph.2025-08-23
, caph.2025-06-20
The value is the tenancy parameter that Monime uses to determine which space the request is intended for.
64
Body
Creates a new payment code with the specified parameters for value collection and provider restrictions.
Descriptive name for the payment code, used for display or tracking.
3 - 64
"Home EDSA Meter Top-up"
Defines whether the payment code is single-use ('one_time') or reusable ('recurrent').
one_time
, recurrent
Whether the payment code should be enabled for use on creation.
Amount to charge per use of the payment code. For 'recurrent' codes, this applies to each payment.
How long the payment code remains valid before expiring.
"1h30m"
Customer associated with the payment code, if any.
Reference tag to associate with this payment code for reconciliation or tracking.
64
List of mobile money provider IDs permitted to process payments using this code.
1 - 10
elementsMSISDN of the mobile money account exclusively allowed to use this code.
Defines the target number of payments or total amount for completing a recurrent code.
Financial account where collected funds are settled. Defaults to the main account if omitted.
64
Optional metadata for attaching custom business context to the payment code.
Response
OK
Represents the status of the query operation, confirming if it was successful. This field is always true
Contains a list of messages providing relevant information or feedback related to the query or operation
A Payment Code is a programmable, short-lived token that allows users to collect payments from others.
It is especially useful in USSD-like or QR-based flows, where the payer enters or scans a code to complete a transaction.
Payment Codes provide flexibility for both one-time and recurrent collections, with configurable restrictions and targets.
Use Cases
-
USSD Payment Collection
A merchant generates a Payment Code and displays it in USSD. Customers enter the code to make payments.
Example: A vendor creates a one-time code for SLE 50 which a customer redeems via their mobile money wallet. -
QR Code at Point of Sale
The Payment Code is encoded as a QR displayed at checkout. Customers scan the QR to pay.
Example: A shop generates a QR-based Payment Code for SLE 200, which is redeemed on the spot. -
Recurring Subscription Collection
A fitness center issues a recurrent Payment Code for monthly fees.
Example: The code accepts up to 12 payments of SLE 500 each, after which it auto-completes. -
Targeted Collection
Restrict a Payment Code to a specific MSISDN or provider.
Example: Only customers on Orange Money with a registered number can redeem the code.