---
title: "Get Current Fees"
method: POST
path: "/pws/pws_get_current_fees/"
tags: ["Fees"]
---

# Get Current Fees

`POST /pws/pws_get_current_fees/`

## Request

- Base URL: `https://api.uat.paymentology.com/ppws/api`
- URL: `https://api.uat.paymentology.com/ppws/api/pws/pws_get_current_fees/`
- Auth: none declared

This web service gets the details of a fee that was applied and is still active

## Request body

- PwsGetFeeTemplateModel
  - `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
  - `user_id` string: User Id of the Customer who triggered the API request.
  - `remarks` string: Remarks for API request
  - `fee_rate_id` integer: Fee Rate Id. [Optional]
  - `fee_type` string: Fee Type. [Optional]

## Response `200`

Successful Response

- GetCurrentFeeResponse
  - `header` GetCurrentFeeHeader
    - `error_id` integer: error id
    - `error_desc` string: error message
  - `body` GetCurrentFeeBody
    - `applied_to` 'TXN,BLC,AANN,DAY,ONC', required: <p>Fee that is applied to.</br>possible options are:</p><ul><li>TXN: transaction</li> <li>BLC: Billing Cycle (Period)</li> <li>ANN: Annually</li> <li>DAY: Daily (Computed during the overnight computational cycle)</li> <li>ONC: Once (non-recurring charge)</li></ul>
    - `effective_date` string, date-time, required: Effective Date
    - `fee_descr` string, required: Fee Description
    - `fee_priority_section` integer, required: <p>Fee Priority Section (to decide about how to apply concurrent fees belonging to the same Fee Priority Section).</br>If concurrency = FALSE, this parameter must be NULL</p>
    - `fee_sectional_priority` integer, required: Priority of the current fee in presence of multiple fees from the same Fee Priority Section (0 is the highest prioority)
    - `fee_title` string, required: Fee Title
    - `fee_type` 'FEE,FCC,FFT,COL,FLP', required: <p>Fee Type that is to be applied.</br>Possible Options are:<ul><li>FEE: General Fee</li>n<li>FCC: Currency Conversion Fee</li> <li>FFT: Foreign transaction Fee</li> <li>COL: Over-Limit Charge</li> <li>FLP: Late Payment Fee</li></ul></p>
    - `fee_id` integer: Fee Id
    - `client_id` integer: client Id
    - `condition_function_call` string: <p>Condition Function Call (to determine if the fee should be applied or not.</br>Empty string means that the fee can be applied unconditionally</p>)
    - `amount_referenced` string: The amout percentage is counted from
    - `concurrency` boolean: If set to TRUE, then the fee will possibly be concurrent with other fees in the same Fee Priority Section
    - `special_actions` string: Function call for a function making special actions
    - `priority_section_name` string: Priority Section Name

## Other responses

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

## Changes

- **2026-11-03** `73c2771493b1`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/paymentology/apis/payapi-docs/changes/pws/pws_get_current_fees/post.md)

---

[API](https://skmtc.dev/paymentology/apis/payapi-docs.md) - [All operations](https://skmtc.dev/paymentology/apis/payapi-docs/llms.txt) - [OpenAPI document](https://skmtc.dev/paymentology/apis/payapi-docs/revisions/73c2771493b1?raw)