---
title: "Update Account Balance"
method: POST
path: "/pws/pws_update_balance/"
tags: ["Account"]
---

# Update Account Balance

`POST /pws/pws_update_balance/`

This API enables the user to update account balances. The API call accepts either a Token or an Account ID. If a Token is provided, the associated account will be updated. It is recommended to use the Account ID (Input type "a") as best practice.This API is primarily designed for Stand-In Processing (STIP) and is not intended for updating balances in day-to-day financial activities when the ledger is managed by Paymentology. It allows for bulk updating of account balances in an array format. Using this API disrupts the transaction narrative on the account, making it unsuitable for reconciliation purposes. However, it can be useful for testing scenarios that require specific amounts to analyze transaction scenarios.

## Request body

- UpdateBalanceModel
  - `api_call_unique_identifier` string, required — Unique number that must be passed at each API request. Identifier to make each API request unique
  - `balance_list` UpdateAccountBalance[], required — List of account/token with corresponding balance to update. Maximum allowed list size is 25.
    - `act_balance` number, required — Actual Balance
    - `bill_ccy` string, required — Balance currency of account. If other currency is provided, it will be converted to account’s base currency. (Three digit ISO-4217 standard currency code . i.e. : 048 → BHD, 060 → BMD, 036 → AUD).
    - `blk_balance` number, required — Blocked Balance
    - `input_id` integer, required — Public token / account number.Pass public token when input type is t./Pass account number when input type is a.
    - `input_type` string, required — <p>Input Type :</p> <ul> <li class="docBullet">a ==&gt; account</li> <li class="docBullet">t ==&gt; Token</li> </ul>
    - `ac_ext_ref` string — account external reference.
  - `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

## Response `200`

Successful Response

- UpdateBalanceResponse
  - `header` UpdateBalanceResponseHeader — Response Header contains success/failure status
    - `error_id` integer — error id
    - `error_desc` string — error message
  - `body` UpdateBalanceResponseBody — Response Body contains detail status of api call
    - `total_count` integer — Total Count
    - `total_success` integer — Total Success Count
    - `total_failed` integer — Total Failed Count
    - `failed_note` string — Failed reason in format "input_id: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)