---
title: "Update features by account status"
method: PATCH
path: "/v1/features-by-account-status"
tags: ["Features by account status"]
---

# Update features by account status

`PATCH /v1/features-by-account-status`

Update features by account status at the program or organization level.
<b>Note:</b> This only applies to full balance credit card programs, and only features that were previously configured using [Configure features by account status](https://developers.pismo.io/pismo-docs/reference/postfeaturesbyaccountstatus) can be updated using this endpoint.

You can toggle the following features on or off for a particular account status by setting them to `true` or `false`, respectively. <b>By default, all these features are on (`true`)</b>. In the `FEATURES OBJECT` body parameter, `newKey`, `newKey-1`, and so on, must be one of these features.
* `close-statements`: If `false`, the platform won't perform any cycle closings if the account has the specified status.
* `late-payment-fee`: If `false`, the platform won't charge any late payment fees if the account has the specified status.
* `overlimit`: If `false`, the platform won't charge any overlimit fees if the account has the specified status.

When modifying an existing account status, all the features previously configured must be provided.
<b>Note:</b> If you send a feature name that does not exist, the endpoint returns an error.

A status can be removed if the `remove_status` flag is set to `true`.  

The configuration can be reset if the `reset_configuration` flag is set to `true`. Resetting the configuration causes all the features to go back to their default values (`true`).
<b>Note:</b> if you set `reset_configuration` to true, and also try to update some features for that status, the endpoint generates the following error:
<b>Request body is missing: account_statuses field is not allowed when it is set to reset this configuration.</b>

You can use the [List statuses](https://developers.pismo.io/pismo-docs/reference/v4-get-account-status) endpoint to list all the account statuses defined for your organization.

## Request body

- FeaturesByAccountStatusPatchRequest
  - `reset_configuration` boolean — Reset configuration?
  - `program_id` number — Program ID
  - `account_statuses` AccountStatusPatchItemRequest[], required — List of account statuses with the corresponding features marked to be disabled/enabled
    - `remove_status` boolean — Remove current status?
    - `name` string — Account status name
    - `features` object — Map of features and the corresponding enabled/disabled status

## Response `200`

OK

- FeaturesByAccountStatusResponse
  - `program_id` number — Program ID
  - `account_statuses` AccountStatusItemResponse[], required — List of account statuses with the corresponding features marked to be disabled/enabled
    - `name` string — Account status name
    - `features` object — Map of features and the corresponding enabled/disabled status
      - `close-statements` boolean
      - `overlimit` boolean
      - `late-payment-fee` boolean

## Other responses

- `400` — Bad Request
- `404` — Not Found
- `500` — Internal Server Error

---

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