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.
Unique identifier for the payment object.
Current status of the payment. Can be one of:
- pending: Created but not yet processed.
- processing: Payment is currently being processed.
- completed: Payment was successfully completed.
pending
processing
completed
Total payment amount requested from the payer.
Payment channel details (e.g., Mobile Money, Bank, Card) used to complete this payment.
Optional label for identifying or grouping the payment. Useful in dashboards or reporting tools.
External reference to associate this payment with a system outside Monime (e.g., an order ID or invoice number).
Monime Order Number — internal order identifier associated with this payment. Used to track payments initiated from an embedded commerce or checkout session.
ID of the destination financial account where the funds will be credited after a successful payment.
Reference to the resulting financial transaction(s), if the payment was successful.
List of applied fees associated with this payment, such as platform or processing fees.
Timestamp indicating when the payment was created.
Timestamp indicating when the payment was last updated.
Ownership chain showing how this payment was initiated — enabling full audit traceability.
Custom metadata attached to the payment