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
ID of the payment object to update.
Body
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 represents a customer payment made through Monime’s platform.
It captures high-level information about the user-initiated payment, including the amount, status, channel (e.g., Mobile Money, Card, Bank), associated order, fees applied, and links to downstream financial transactions.
The Payment is a business object — the single record developers and merchants interact with when tracking or reconciling user payments.
It should not be confused with Financial Transactions, which are lower-level, fine-grained ledger entries.
In fact, one Payment usually generates multiple Financial Transactions — for example:
- A credit of the received funds into the merchant’s account.
- One or more debits representing platform charges or processing fees.