Monetary Value
All monetary is serialized as JSON string, with some restrictions:
- Only contains numeric characters and a
.character as a decimal-fraction separator. - Has at most 2 decimal-fraction digits.
Example of valid monetary values:
"10000""10000.0""10000.00"
NoteDecimal rounding might take place if the decimal fraction value is not equal to
.0/.00
Status
| Status Name | Description | Possible Change(s) |
|---|---|---|
approved | Payout request is approved by approver user | processedcompletedfailed |
rejected | Payout rejected due to error on validation or by the approver | Terminal state |
processed | Payout request is sent to the bank and currently being processed by the bank. There are 2 kind of processed status:
| completedfailed |
completed | Payout request is sent to the bank and received by beneficiary account | failedThis can happened if there's refund from bank. |
failed | Payout didn't go through | Terminal State |
Payout Notification Payload
| Parameter | Description |
|---|---|
| reference_no | Unique reference_no of a payout. |
| amount | Amount of the processed payout. |
| status | Status of the payout, please refer to here as reference. |
| updated_at | Payout status update time in ISO8601 format. |
| error_code | In case payout is failed we will send an error code, related to the failed payout failed payout error code and messages. |
| error_message | In case payout is failed we will send an error message, related to the failed payout failed payout error code and messages. |
| notes | The notes passed during creation of the payout. |
Note
- There might be a possibility that:
- Notification sent is not in the correct order
- Same notification sent more that once
Top up Notification Payload
| Parameter | Description |
|---|---|
| transaction_id | Unique id generated by Midtrans for top up to Bank |
| order_id | Unique id generated by Payouts |
| gross_amount | Amount topped up |
| status | topup |
| transaction_time | Transaction time in ISO8601 format |