Loan Action : Create Disbursal Breakup
POST Create Disbursal Breakup
In order to produce Disbursal Breakup against a Loan ID, a user can use the SynoFin API.
URL: {{base_url}}/loan-management/v1/createDisbursalBreakup
Run in Postman: Create Disbursal Breakup
Request:
Query Params:
Schema
Attribute | Data Type | Description | Mandatory | |||
loan_id | Number (Big Serial) | Unique Loan Id for agains which Disbursal Breakup Should be Created | Yes | |||
disbursal_breakup | Array Of Objects | Multiple Breakups Can be Added | Yes | |||
disbursal_schedule_id | Number (Big Serial) | Unique Disbursal Schedule Id for against which Disbursal Breakup Should be Created | Yes | |||
disbursal_breakup | Array Of Objects | Breakup Details | Yes | |||
breakup_number | Number | Breakup number for the Disbursal Id | No | |||
business_partner_name | String | Name of the Business partner | No | |||
business_partner_type | String | Type of the Business partner (customer, primary_applicant, etc.) can be Added therough SynoFin Masters). | No | |||
other_payables | Double | Other payables Charges that are needed to be added (Default 0.0) | No | |||
net_disbursal_amount | Double | Net Disbural amount For the disbursal Schedule (Default 0.0) | No | |||
disbursal_amount | Double | Disbursal Amount (Default 0.0) | No | |||
paid_amount | Double | Paid Amount (Default 0.0) | No | |||
payment_status | String | Payment Status (Paid, Pending, Outstanding) | Yes | |||
pending_amount | Double | Amount Pending (Default 0.0) | No | |||
bank_name | String | Name of the Bank | No | |||
ifsc_code | String | Bank IFSC Code | No | |||
account_number | String | Bank Account number of the Customer | no | |||
instrument_type | String | Type of instrument (rtgs, cheque) | No | |||
payment_date | Date | Date of Payment (Should be in format)(yyyy-MM-dd) | Yes | |||
payment_type | String | Type of payment done | No | |||
disbursal_breakup_identifier | String | Unique Identifier for the Disbursal Breakup | Yes | |||
Body
{
"loan_id": 00000, // Replace with the actual loan ID
"disbursal_breakup": [
{
"disbursal_schedule_id": 00000, // Replace with actual schedule ID
"disbursal_breakup": [
{
"breakup_number": "4",
"business_partner_name": "Partner 1",
"business_partner_type": "Type 1",
"other_payables": 100.0,
"net_disbursal_amount": 500.0,
"disbursal_amount": 600.0,
"paid_amount": 400.0,
"payment_status": "Paid",
"pending_amount": 200.0,
"bank_name": "Bank 1",
"ifsc_code": "IFSC123",
"account_number": "1234567890",
"instrument_type": "Type A",
"payment_date": "2023-09-14", // Replace with the actual date
"payment_type": "Type X",
"disbursal_breakup_identifier": "Identifier 3"
}
]
},
{
"disbursal_schedule_id": 00000, // Replace with actual schedule ID
"disbursal_breakup": [
{
"breakup_number": "5",
"business_partner_name": "Partner 1",
"business_partner_type": "Type 1",
"other_payables": 100.0,
"net_disbursal_amount": 500.0,
"disbursal_amount": 600.0,
"paid_amount": 400.0,
"payment_status": "Paid",
"pending_amount": 200.0,
"bank_name": "Bank 1",
"ifsc_code": "IFSC123",
"account_number": "1234567890",
"instrument_type": "Type A",
"payment_date": "2023-09-14", // Replace with the actual date
"payment_type": "Type X",
"disbursal_breakup_identifier": "Identifier 4"
}
]
}
]
}
Response:
Success: 200 OK
Schema
Attribute |
Type | Description |
Mandatory | |||
response |
String | Internal status code that denotes the status of request |
Yes | |||
data | Object Data | Object | Success Response Object |
Yes | ||
Attribute |
Data Type | - | ||||
Identifier 4 |
Integer | yes | ||||
Identifier 5 | Integer | yes | ||||
error |
String | Internal error object for the given inputs |
Yes |
Body
{
"response": true,
"data": {
"Identifier 4": 0000,
"Identifier 3": 0000
},
"error": null
}
Unauthorized: 401
Note: If the API is not authorized with the Token or if the authorization token has expired, this error is going to show up.
Body
{
"code": 401,
"message": "auth fail, you can retry!"
}