---
title: "Update Interest Template"
method: POST
path: "/pws/pws_cr_update_interest_template/"
tags: ["Credit interest"]
---

# Update Interest Template

`POST /pws/pws_cr_update_interest_template/`

This web service updates a given interest

## Request body

- PwsUpdateInterestTemplate
  - `amount_referenced` string, required — <p>The amount percentage is counted from.</br> .possible options are;<ul><li>N/A: Amount is irrelevant</li><li>TXN: transaction</li><li>OWD: Amount owed</li><li>ATA: Aggregated amount of all transactions during the day, billing cycle, or annual (depending on the value of applied_to)</li><li>ATD: Aggregated amount of debit transactions during the day, billing cycle, or annual (depending on the value of applied_to)</li><li>ATC: Aggregated amount of credit transactions during the day, billing cycle, or annual (depending on the value of applied_to)</li></ul>
  - `api_call_unique_identifier` string, required — Unique number that must be passed at each API request. Identifier to make each API request unique
  - `client_id` integer, required — Unique identifier for the client which Paymentology will provide at outset
  - `effective_date` string, required — Effective Date
  - `interest_rate_descr` string, required — Interest Rate Description
  - `interest_rate_id` integer, required — interest_template_id
  - `interest_rate_note` string, required — Interest Rate Note
  - `method` integer, required — Interest Method.</br>There are 5 interest methods out of which method (1 to 5) are in implementation.</br>Following are the type of method that can be used:<ul><li>1--> Average Daily Balance Method</li><li>2-->Previous Balance Method</li><li>3-->Adjusted Balance Method</li><li>4-->Murahaba-Markup Method</li><li>5-->Average Daily Balance AMEX Method</li></ul>
  - `priority` integer, required — Interest Priority.Lowest the number Highest the priority
  - `user_id` string — User Id of the Customer who triggered the API request.
  - `remarks` string — Remarks for API request
  - `condition_function_call` string — <p>Condition Function Call (to determine if the interest should be applied or not.</br>Empty string means that the interest can be applied unconditionally</p>)
  - `special_actions` string — Function call for a function making special actions
  - `grace_period_cycles_no` integer — Defines the interest that is to be computed by either due date or grace period.</br>possible value are:<ul><li>0-->Accure Interest From Transaction Date</li><li>1--> Normal Grace Period(pay by due date)</li><li>2--> Extended Grace Period</li></ul>
  - `start_counting_from` 'SET,TXN' — Interest computed should be counted from. Default value is 'SET'.</br><ul><li>SET-->From the settlement date/ fee settled</li><li> TXN--> From the transaction date/ fee computed</li></ul>

## Response `200`

Successful Response

- UpdateInterestResponse
  - `header` UpdateInterestResponseHeader
    - `error_id` integer — error id
    - `error_desc` string — error message
  - `body` UpdateInterestResponseBody
    - `message` string — Updating message

## Other responses

- `404` — Webservices does not exist
- `500` — Internal Server error

---

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