---
title: "Update account collection status"
method: PATCH
path: "/statements-v2/v1/accounts/{accountId}"
tags: ["Account"]
---

# Update account collection status

`PATCH /statements-v2/v1/accounts/{accountId}`

## Request

- Base URL: `https://sandbox.pismolabs.io`
- URL: `https://sandbox.pismolabs.io/statements-v2/v1/accounts/{accountId}`
- Auth: HTTP bearer

Change an account's collection status from `NORMAL` to `OVERDUE` or vice-versa. `OVERDUE` accounts cannot do cash-outs (purchases, cash withdrawals, and so on).

When you try to change an account's collection status to `OVERDUE`, the Pismo platform first verifies that `OpenDueDate` is not `NULL` and that it is a date in the past. If this test fails, it returns `400 Bad request`.

No validations are done when you change the collection status to `NORMAL`.

Changing the account collection status does not affect the [account status](doc:managing-account-statuses#account-statuses-common-to-all-accounts). So, for example, changing the account collection status from `NORMAL` to `OVERDUE` does not cause the account status to change to `BLOCKED`, even though it does prevent cash-outs by blocking the ledger itself. When you change the account collection status from `OVERDUE` to `NORMAL`, the ledger is unblocked and the account is again able to do cash-outs, assuming the account status is not `BLOCKED`. The two fields are not linked.

<table>
  <thead>
    <tr>
      <th>Collection status</th>
      <th>Account status</th>
      <th>Result</th>
    </tr>           
  </thead>
  <tbody>
    <tr>
      <td><b>`NORMAL`</b>
      <td><b>`NORMAL`</b></td>
      <td>Account is usable.</td>
    </tr>
    <tr>
      <td><b>`NORMAL`</b>
      <td><b>`BLOCKED`</b></td>
      <td>Account is not usable.</td>
    </tr>
    <tr>
      <td><b>`OVERDUE`</b>
      <td><b>`NORMAL`</b></td>
      <td>Account is not usable.</td>
    </tr>
    <tr>
      <td><b>`OVERDUE`</b>
      <td><b>`BLOCKED`</b></td>
      <td>Account is not usable.</td>
    </tr>               
  </tbody>
</table>

For more information about the account collection status, refer to the [Credit liquidation](doc:credit-liquidation) guide.

**Note:** This endpoint requires an account token - an access token encoded with a Pismo account ID. Tokens can expire quickly, which can result in a **401 Unauthorized** message.

## Path parameters

- `accountId` integer, required

## Request body

- AccountCollectionStatusV1PatchRequest
  - `collection_status` 'NORMAL' | 'OVERDUE': Collection status: * NORMAL * OVERDUE If a customer fails to pay at least the minimum amount due on their credit account by a specified number of days after the due date, the account's `collection_status` is set to `OVERDUE`. In all other cases, it should be `NORMAL`. For more information, refer to [Credit liquidation](doc:credit-liquidation).

## Response `200`

Ok

- object
  - `org_id` string: Organization ID
  - `account_id` integer: Account ID
  - `collection_status` 'NORMAL' | 'OVERDUE': Collection status: * NORMAL * OVERDUE If a customer fails to pay at least the minimum amount due on their credit account by a specified number of days after the due date, the account's `collection_status` is set to `OVERDUE`. In all other cases, it should be `NORMAL`. For more information, refer to [Credit liquidation](doc:credit-liquidation).

## Other responses

- `400`: Bad request
- `500`: Internal Server Error

---

[API](https://skmtc.dev/pismo/apis/revolving-credit-statements.md) - [All operations](https://skmtc.dev/pismo/apis/revolving-credit-statements/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/revolving-credit-statements/revisions/09f552b0f850?raw)