---
title: "Create status reason"
method: POST
path: "/accounts/v4/reasons"
tags: ["Statuses and reasons"]
---

# Create status reason

`POST /accounts/v4/reasons`

Create an account status reason on the platform.

This endpoint generates a [Reason created](https://developers.pismo.io/events/docs/account-reason-creation-1) event.

For more information, refer to the [Account status](https://developers.pismo.io/pismo-docs/docs/accounts-overview#account-status) guide section.

## Request body

- ReasonCreate — Object to create an account reason
  - `name` string, required — Reason name
  - `description` string — Reason description
  - `allowed_operations` OperationsBlocksOperation[] — List of operations allowed to bypass the block enforcement logic.<br> - `EARMARK_RELEASE`: Release an earmark even when an operation block is active. - `EARMARK_UPDATE`: Update an earmark (set amount, increase, or decrease) while the account is blocked by an operation block. - `PAYMENT_DEBIT`: Execute a debit transaction while the account is blocked by an operation block. - `PAYMENT_CREDIT`: Execute a credit transaction while the account is blocked by an operation block. - `PAYMENT_CONFIRM`: Confirm a value transaction while the account is blocked by an operation block. - `PAYMENT_CANCEL`: Cancel an existing transaction while the account is blocked by an operation block. - `ACCOUNT_STATUS_UPDATE`: Change the account status and the associated status reason. - `CHECK_POST`: Post a check while the account is blocked by an operation block. - `CHECK_RELEASE`: Release an uncleared check or operation while the account is blocked by an operation block. - `CHECK_CANCEL`: Cancel an existing check while the account is blocked by an operation block. - `RESTRICTED_FUNDS_CREATE`: Hold a specified amount by transferring it from the available balance to restricted funds. - `RESTRICTED_FUNDS_RELEASE`: Release restricted funds from hold. This transfers funds from restricted funds back to available balance.
  - `external_id` string — Client-created ID from an external system or application. **REQUIRED** for `VIRTUAL` accounts.

## Response `201`

Created

- ReasonResponse
  - `id` integer — Reissue reason identifier. You can get reason IDs using the [List reissue reasons](https://developers.pismo.io/pismo-docs/reference/get-reissue-reasons) endpoint. The `must_block` flag comes from the reissue reason object.
  - `description` string — Reissue reason description
  - `must_block` boolean — Should a `PLASTIC` card be canceled upon reissue or can it be used until the new card is activated? `VIRTUAL` cards are automatically canceled when reissued, regardless of this setting.
  - `must_charge` boolean — Should the reissue be charged? This field is information only as only issuers can make debit entries to a customer's account.
  - `cost` number — Reissue card cost
  - `type` string — Issuer-defined reissue reason enum
  - `enabled` boolean — Is reason active? This field is for information only and allows the issuer to provide only active reasons for re-issuance.

## Other responses

- `400` — Bad request
- `409` — Conflict
- `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)