---
title: "Make payment"
method: POST
path: "/v1/payments/loan/make-payment"
tags: ["Payment"]
---

# Make payment

`POST /v1/payments/loan/make-payment`

## Headers

- `accept-language` string
- `idempotency-key` string

## Request body

- MakeLoanPaymentV1Dto
  - `loanId` string, required — Loan Id, for which you want to make payment
  - `paymentAmount` number, required — Payment Amount. - Support decimal values as well.
  - `paymentTypeId` number, required — We have 3 types of payments. For payment via bank transfer: ```1``` For payment using UEN number: ```2``` For payment using QR code: ```3```
  - `paymentReferenceNo` string — Payment reference number.

## Response `200`

Loan Payment done and verify Successfully

- MakeLoanPaymentResponse
  - `statusCode` number, required — The HTTP status code of the error
  - `data` LoanPayment, required
    - `paymentId` string, required — Id of the payment
    - `paymentDate` string, required — Date of the payment in UTC Format eg. 2023-03-30T11:46:42.195Z
    - `paymentAmount` number, required — Payment Amount
    - `paymentMethod` string, required — Payment Amount
    - `paymentReferenceNo` string, required — Payment reference number provided while making payment
    - `accountNumber` string, required — Account Number varies based on payment types. So for bank transfer payment( this field will contain ```bank account number``` & for UEN number payment this will contain ```UEN Number```
    - `accountName` string, required — Account Name to which payment has been made.
    - `bankName` string, required — Bank Name varies based on payment types. So for bank transfer payment this field will be present, for rest of the types it will be empty
    - `bankSwiftCode` string, required — Bank Swift Code varies based on payment types. So for bank transfer payment this field will be present, for rest of the types it will be empty
    - `paymentStatus` number, required — We have 3 types of payment status codes. For payment rejected: ```0``` For payment done, but verification pending: ```1``` For payment done & verified: ```2```
    - `loanId` string, required — Loan Id, for which payment has been made.
    - `customerReferenceNo` string, required — Customer Reference Number, for which payment has been made.
    - `metadata` string, required — Metadata for payments. It can be used for reporting, reconciliation purpose.
    - `createdAt` string, required — Created Timestamp of the payment in UTC Format eg. 2023-03-30T11:46:42.195Z
    - `updatedAt` string, required — Updated Timestamp of the payment in UTC Format eg. 2023-03-30T11:46:42.195Z
    - `currency` string, required — Currency Code
  - `message` string, required — Human-readable message containing all available details about the operation
  - `success` boolean, required — A boolean indicating whether this was a success response or an error response

## Other responses

- `400` — Invalid Request
- `401` — Invalid credentials
- `403` — Forbidden resource
- `500` — Internal Server Error, Some problem is there, please try after sometime

---

[API](https://skmtc.net/credilinq/apis/credilinq-apis.md) · [All operations](https://skmtc.net/credilinq/apis/credilinq-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/credilinq/credilinq-apis/revisions/fc4f4dd68f9b/schema)