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

# Configure features by account status

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

Configure features by account status at the program or organization level.
<b>Note:</b> This only applies to full balance credit card programs.

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>.
* `close-statements`: If `false`, the platform doesn't perform any cycle closings if the account has the specified status.
* `late-payment-fee`: If `false`, the platform doesn't charge any late payment fees if the account has the specified status.
* `overlimit`: If `false`, the platform doesn't charge any overlimit fees if the account has the specified status.
* `create-accruals`: If `false`, the platform doesn't calculate new accruals if the account has the specified status.

For example, suppose you set the `close-statements` feature to `false` for the `CANCELLED` account status for a specific program. (That is, you turn the feature off at the program level.) Then the Pismo platform won't perform any cycle closings for accounts in that status if they belong to that program.

<b>Important:</b> Once the status is set to bypass the billing cycle closure and the account reaches that status, it cannot revert to a previous status. In other words, no further cycle closures can occur for this account. The change is irreversible.

There are several points you should keep in mind when using this endpoint.
* You can use this endpoint to set a feature toggle at the organization level, whether or not you have created any full balance credit programs in your organization. However, if you try to use it to set a feature toggle at the program level, and the program isn't a full balance credit card program, the endpoint throws an error.
* If a feature is set to `true` or `false` at the program level, this overrules that feature's setting at the organization level. For example, if `close-statements` is set to `false` at the organization level and `true` at the program level, then the platform continues to perform cycle closings for accounts in the specified program. In other words, the organization level setting is ignored.
* If a feature is not set to `true` or `false` at either the program or organization level, it defaults to `true`.
* You can't use this endpoint to update a feature setting for an account status if it has already been configured at a particular level. For that, you need to use [Update features by account status](https://developers.pismo.io/pismo-docs/reference/patchfeaturesbyaccountstatus).

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

- FeaturesByAccountStatusPostRequest
  - `program_id` number — Program ID
  - `account_statuses` object[], required — List of account statuses with the corresponding features marked to be disabled/enabled
    - `name` string — Account status name
    - `features` object
      - `close-statements` boolean — Perform cycle closings?
      - `late-payment-fee` boolean — Charge late payment fees?
      - `overlimit` boolean — Charge overlimit fees?
      - `create-accruals` boolean — Calculate new accruals?

## Response `201`

Created

## Other responses

- `400` — Bad Request
- `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)