Documentation Index Fetch the complete documentation index at: https://docs.monime.io/llms.txt
Use this file to discover all available pages before exploring further.
{ "id" : null , "status" : "pending" , "amount" : { "currency" : null , "value" : null }, "source" : { "financialAccountId" : null , "transactionReference" : null }, "destination" : { "providerCode" : null , "accountId" : null , "transactionReference" : null }, "charges" : [], "delayedReason" : null , "failureDetail" : { "code" : "unknown" , "explanation" : null }, "createTime" : null , "metadata" : null }
The unique identifier for the payout object
The status of the payout object. Available options: pending processing delayed completed failed
The monetary amount to payout to the destination The value representation in the currency’s minor unit. E.g. For 1 Leone (SLE 1), the value should be 100, denoting cents, the minor unit.
The source of fund for the payout object. The ID of the financial account where the amount was disbursed from.’
The Monime transaction reference for describing the debiting of the amount and charges from the financial account.
The destination for the fund of the payout object. The code for the provider as identified by Monime.
The account ID of the account in the provider’s ecosystem that the payout amount was disbursed to.
The transaction reference from the provider’s ecosystem after the amount was disbursed.
The charges that applied to the payout.
The reason when the payout is being delayed.
The detail for the failed status. The failure code. Available options: unknown expired providerUnknown fundInsufficient authorizationFailed providerAccountBlocked providerAccountMissing providerAccountQuotaExhausted
An explanation of the failure code.
The creation time of the payout object.
This holds key-value pairs, where both the keys and values are strings not exceeding 64 and 100 characters respectively. This allows for flexible and descriptive tagging or additional information to be associated with the object.
