Authorizations
Bearer HTTP authentication specified with the header Authorization: Bearer <access_token>
Headers
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
Path Parameters
Unique identifier of the payment code to retrieve.
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.