Payment Object
Payment Life Cycle
| Status | Description |
|---|---|
processing | A payment is created in processing state when a payment request receives a success response from downstream |
completed | When the status of the payment is changed to completed, the in processing payment is verified as complete by Durianpay. After the capture, the amount is settled to your account as per the settlement schedule of the bank |
cancelled | Customer has cancelled this transaction |
expired | The payment ID is no longer payable as the transaction has exceeded the specified expiry time and remains unpaid by the customer |
failed | Any unsuccessful transaction is marked as failed and the customer will have to retry the payment |
Payment Entity
| Field | Description |
|---|---|
| id | string The unique identifier of Payment |
| amount | string The amount for which the Payment was created |
| currency | string The currency associated with the Payment's amount |
| status | string The status of Payment |
| type | string Type of payment. Possible values card, VA, wallet |
| created_at | integer Indicates the Unix timestamp when this Payment was created |
| metadata | json object Key-Value pair that can be used to store additional information about the entity. e.g. note: Force is with this payment |
| failure_reason | json object The failure_reason fields including code, message. integer code is the failure status code and string message is the failure description |
Payment Failure Codes
| code | description |
|---|---|
| 20010 | error due to end user action |
| 20011 | merchant is either blocked or invalid |
| 20012 | payment expired |
| 20013 | error from provider |
| 20014 | payment cancelled by merchant |