---
title: "Close delinquent account"
method: POST
path: "/v1/accounts/{account_id}/close"
tags: ["Delinquent account closure"]
---

# Close delinquent account

`POST /v1/accounts/{account_id}/close`

## Request

- Base URL: `https://sandbox.pismolabs.io/delinquent-account`
- URL: `https://sandbox.pismolabs.io/delinquent-account/v1/accounts/{account_id}/close`
- Auth: HTTP bearer

Sends the specified account to the delinquent account closure process.
This endpoint generates a [Delinquent account closed](https://developers.pismo.io/events/docs/delinquent-account-delinquent-account-1) event.

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

## Path parameters

- `account_id` integer, required

## Headers

- `x-cid` string

## Request body

- PostAccountCloseRequest: Resource used to request a delinquent closure of an account.
  - `tracking_id` string, required: Tracking identifier. Must consist of the characters [a-z,A-Z,0-9,-,:] with a range from 1 to 128. If a client clicks the button more than once when sending the command to close an account, the Pismo platform could create duplicate requests. The tracking identifier enables the platform to identify duplicates and ignore them.
  - `processing_code` string: Processing code for the transaction that the Pismo platform creates to zero out the account balance.
  - `reason` string: `external_id` of the status reason. This is the external ID that was used to create the reason.
  - `final_account_status` string: Final status for the closed delinquent account. Use the [List statuses](ref:v4-get-account-status) endpoint to list the available account statuses.
  - `excluded_steps` ExcludedStep[]: Steps to skip when closing a delinquent account

## Response `202`

Accepted - Indicates that the server has accepted the request, and the specified account has been sent to the delinquent account closure process.

- PostAccountCloseResponse: Resource used to return information about delinquent account closure requested.
  - `open_due_date` string: Open due date. This is the first day that the account became overdue. BRT (Brazilian time zone = UTC-03).
  - `due_days` integer: Due days. The number of days the account has been overdue. (Today minus `open_due_date`).
  - `created_at` string: Date/time (UTC) that asset was registered on Pismo platform
  - `status` 'CREATED' | 'STARTED' | 'INTEREST_ACCRUAL_POSTED' | 'INSTALLMENTS_ADVANCED' | 'CREDIT_SEPARATED_TRANSACTION_REQUEST' | 'CREDIT_SEPARATED_TRANSACTION_CREATED' | 'CREDIT_TRANSACTION_REQUESTED' | 'ACCOUNT_CANCELLED' | 'CARD_BLOCKED' | 'SUCCESS' | 'SUCCESS_EVENT_SENT': Delinquent account entity status This field can have the following values. `CREATED`—Created a delinquent account register to initiate the process. `STARTED`—Started posting interest accruals. `INTEREST_ACCRUAL_POSTED`—Finished posting nterest accruals. `INSTALLMENT_ADVANCED`—Checked all transactions that need to be deducted separately. `CREDIT_SEPARATED_TRANSACTION_REQUEST`—Requested a deduction for each transaction selected to be settled separately. `CREDIT_SEPARATED_TRANSACTION_CREATED`—Created deduction transactions. `CREDIT_TRANSACTION_REQUESTED`—Posted a credit transaction to the account. `ACCOUNT_CANCELLED`—Cancelled account. `CARD_BLOCKED`—Requested that all cards be blocked. `SUCCESS`—Blocked all cards. Generated account [delinquent closure event](https://developers.pismo.io/events/docs/delinquent-account-delinquent-account-1). `SUCCESS_EVENT_SENT`—Sent `SUCCESS` event to customer.

## Other responses

- `400`: Bad Request
- `409`: The specified resource status conflicts with the current request.
- `500`: Internal server error

---

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