Repayment API Parameters Table
| Parameter Name | Required | Format | Comment |
|---|---|---|---|
| amount | Yes | Decimal | The total amount which was paid by the customer. |
| payment_mode | Yes | 1: Razorpay 3: Nach 4: Cheque 5: Neft or IMPS to bank account 6: Cash 7: Paytm 8: Pre deducted 10: Cashfree 11. UPI 12. Ex Gratia 13. Mobikwik 14. Bill Desk 15. PayU 16. eCollect 17. Waived 18. Write Off 19. eMandate 20. Other Payment Gateway 21. Others 24. Returns Note that integer codes should be passed in the API request. | This is the mode from which the payment was done. |
| payment_date | Yes | Date format - DD-MMM-YYYY. For e.g. 1 Jan 2019 should be passed as "01-Jan-2019" | On which date the payment was done. |
| payment_id | Yes | This should be the identifier from which the payment can be independently verified. | For payment gateways, this should be the id which the PG provider gives. For NACH it should be the Lan no. For cash deposits, it should be identification number which shows up in the bank account. |
| allocation | Yes | Array of JSON of allocations. | How the total amount paid by the customer is allocated to different heads. |
| payment_account | No | Payment Account Name | If you use multiple accounts, then payments to non default accounts should be passed. |
| is_foreclosure | Optional | Boolean | Loan foreclosure is the full repayment of the remaining loan amount in a single payment instead of paying it back in multiple EMIs. In this way, borrowers can save future interest by paying a lump sum amount at a time along with foreclosure charges. |
| bureau_date | Optional | Date format - DD-MMM-YYYY. For e.g. 1 Jan 2019 should be passed as "01-Jan-2019" | In case bureau reporting is to be done with payments being considered not on payment date. This should be passed. |